Two weeks ago we rebuilt this blog: a new theme, 19 rewritten posts and 18 redirects from the old addresses to the new ones. A few days later Search Console's Page indexing report showed a number that looks alarming at first glance: 23 indexed, 43 not indexed. This is a field note on what that number really meant, what we tested, and the one item we have not solved yet.
Reason by reason: what each line meant
| Reason (pages) | What it turned out to be | Action |
|---|---|---|
| Alternate page with proper canonical (23) | Every URL in this group ended in ?m=1. Blogger serves phones a mobile version at that address, and each one correctly points back to the clean address as its canonical. | None. This is the intended result. |
| Discovered, currently not indexed (16) | These were the old post addresses, with "last crawled: N/A". Google had them from the old sitemap and had not visited them since we redirected them. | None. They now redirect to the new posts and will drop out. |
| Page with redirect (2) | Old addresses that Google had already revisited and found redirecting. | None. Expected after a migration. |
| Crawled, currently not indexed (1) | The Privacy Policy page. Legal boilerplate is often left out of the index. | None needed. |
| Redirect error (1) | The homepage. | Open question, see below. |
The pattern is worth remembering: after a migration, a long "not indexed" list is often just the evidence that the redirects are working. What matters is whether your real pages are in the indexed column, and ours were (23, up from only a handful in September).
What we tested instead of guessing
The report names reasons, but it does not show what Google's crawler actually received. So we checked it directly with plain command-line requests that imitate Googlebot's phone user agent, following every redirect hop by hop.
- All 18 old post addresses: each redirected once, permanently (301), straight to the correct new post. No chains, no loops.
- Deleted pages: they return a proper 404 to a normal request. One trap here: Blogger answers the lighter
HEADrequest with 200 even for missing pages, so a check that uses onlyHEADwill report a false "OK". Always confirm with a realGET. - Robots and indexing rules: no
noindextag or header, each page's canonical points to itself, androbots.txtblocks only Blogger's internal/searchpages. - The homepage path for a phone crawler:
http://tohttps://to/?m=1, ending in a normal 200 page after one to three hops.
The one item we have not solved
Search Console still labels the homepage "Redirect error" in its stored result from October 23, even though our traces show a clean path that ends in a working page. We have not been able to reproduce the error from our side. Our working explanation is a known Blogger behaviour: it sends every phone to /?m=1, and that page names the clean address as its canonical, which Google's tool sometimes reports as a redirect problem for the homepage. We have not confirmed that, so we are treating it as unresolved and re-testing with Search Console's "Test live URL". The 23 indexed pages show that it is not blocking the rest of the site.
A related bug that Search Console did catch
The same tool surfaced a real problem earlier: "Unparsable structured data" on the homepage. Our theme had wrapped its JSON-LD in a CDATA marker that Blogger printed literally onto the page, so Google could not parse it. The fix was to remove the wrapper; we then confirmed the live page's JSON-LD parsed as valid JSON. Lesson: when structured data fails, extract the exact text the server sends and run it through a JSON parser instead of trusting how the template looks in the editor.
Where the site stood after the cleanup
For context, these are the checks we ran on the mobile homepage in the same period (lab scores vary a few points between runs):
- PageSpeed Insights (mobile): Performance 97, Accessibility 100, SEO 100, Best Practices 92, with 2.0 s Largest Contentful Paint and zero layout shift. The Best Practices drop came from a console note triggered by Google's own ad frame and from server headers that Blogger controls.
- GTmetrix: Performance 93%, Structure 89%, Largest Contentful Paint 930 ms, Total Blocking Time 52 ms, layout shift 0.
- Sitemap in Search Console: status Success, after one earlier "temporary processing error" that cleared by itself.
A checklist you can reuse after a migration
- Read the reasons, not the total. Group the not-indexed URLs by reason and look at which URLs sit in each.
- Separate real pages from duplicates and old addresses.
- Trace the redirects yourself, hop by hop, with a mobile crawler user agent.
- Check
noindex, canonicals androbots.txton the live page. - Test live URLs in Search Console, and request indexing once per important page.
- Give it weeks, not days, before judging.
How this article was produced
This article was researched and drafted with AI assistance from our own Search Console reports, test results and the primary sources listed below, then published by the site owner, who is responsible for it. The checks described were run by the AI assistant under the owner's direction, and the owner supplied the Search Console and speed-test screenshots. If you find an error, tell us. Our standards are described in the editorial policy.
What is and is not verified
The counts, statuses and scores come from the owner's own Search Console, PageSpeed Insights and GTmetrix reports. The redirect behaviour comes from live request traces we ran on October 22 to 26. Our explanation for the homepage message is a hypothesis, not a confirmed cause, and we say so above.
Sources
- Search Console Help: Page indexing report
- Google Search Central: Redirects and Google Search
- Google Search Central: Consolidate duplicate URLs (canonicals)
- Google Search Central: Introduction to structured data
Related: Moving to a custom Blogger theme: 9 errors we hit and Mastering SEO in 2026.
About the author
I'm Junaid. I'm a sales professional with more than seven years across several industries, and I have no coding background. I use AI to diagnose and fix technical problems like these and I write down exactly what happened, mistakes included. If a process in your business is eating your time, tell me about it and we can look at whether AI could take some of the load.