GLOBAL BRIDGE LABS
← All posts/Website Development

Reading the Page indexing report after a migration

Reading the Page indexing report after a migration: which statuses to expect for old and new URLs, and which ones point to real problems.

By Hojitha Weerasinghe, Co-founder / DirectorPublished 3 min read
Page indexing report: key takeaways infographic by Global Bridge Labs
Key takeaways from this article. Share it with the link and credit Global Bridge Labs.
On this page

Key takeaways

The Page indexing report in Search Console shows which URLs Google has indexed and why others are not indexed. After a migration, old URLs should move into page with redirect, while new URLs become indexed. Watch for spikes in not found, soft 404, blocked by robots.txt, excluded by noindex and server error. Each points to a fixable problem.

  • Old URLs should show as page with redirect.
  • New URLs should move into indexed.
  • Spikes in not found or soft 404 need checking.
  • Noindex and robots.txt blocks need urgent fixes.

Confused by your Page indexing report? Message us on WhatsApp.

Chat on WhatsApp →

What should you expect to see?

Google's Page indexing report help page explains each reason. In a healthy migration, the pattern is clear over a few weeks: the number of page with redirect URLs rises as Google recrawls old addresses, indexed pages on the new site rise to roughly match the sitemap count, and not found errors stay low. Some not found entries are normal for pages you retired on purpose.

Which statuses point to problems?

Click into each reason and look at the example URLs.

  • Not found (404): old URLs missing from the redirect map.
  • Soft 404: redirects to irrelevant pages or empty pages.
  • Blocked by robots.txt: a blocking rule left from staging.
  • Excluded by noindex: noindex left on live pages.
  • Server error: capacity or configuration problems.
  • Duplicate without user-selected canonical: inconsistent URL versions.

How do you act on it?

Export the examples for each problem reason and match them to the redirect map. Fix the cause, which is often one rule or one template rather than individual pages. Then use the validate fix button so Google rechecks the affected URLs. Check the report daily in the first week and weekly for three months, and note the totals against your baseline.

Want help prioritising the errors? Send us a screenshot on WhatsApp.

Chat on WhatsApp →

What does this look like in practice?

A pattern we see: two weeks after launch, not found errors jump. The examples are all old blog URLs with a date folder, missed by a pattern redirect that only matched recent posts. Widening the rule and validating the fix clears most of the errors within a few weeks.

Page indexing checklist

  • Check the report daily in week one.
  • Expect page with redirect to rise.
  • Investigate not found and soft 404 examples.
  • Fix noindex and robots.txt blocks at once.
  • Validate fixes and track totals weekly.

Next step

Take a screenshot of your Page indexing report before launch. It gives you a simple baseline to compare against in the weeks after the migration.

Message us on WhatsApp about indexing errors, or book a 30-minute consultation.

Chat on WhatsApp →

Sources and further reading

Frequently asked questions

What does page with redirect mean in Search Console?

It means Google found the URL but it redirects elsewhere, so Google indexes the destination instead. After a migration, old URLs moving into this status is expected and healthy. Check that the destinations are correct and that the new URLs are being indexed.

Why are my new pages not indexed after migration?

Common reasons are noindex left from staging, robots.txt blocks, canonical tags pointing elsewhere, thin content or simply time, because Google has not crawled them yet. Use URL Inspection on a few examples to see the reason, fix any blocks and request indexing of key pages.

Should I worry about not found errors after a migration?

Look at the examples. Errors for pages you retired on purpose, with no traffic or links, are fine. Errors for old URLs that had traffic or links mean missing redirects, which you should add. A sudden spike usually points to a broken rule rather than many separate pages.

Written by

Hojitha Weerasinghe
Hojitha Weerasinghe
Co-founder / Director

Global Bridge Labs (GBL) is a UK–Sri Lanka partner for social media, websites and BPO. Everything here comes from client delivery, not theory.

Share this article

Reading is good.
Fixing is better.

30 minutes with our team and you'll leave knowing which of the three problems to fix first.

Get a Free Quote →
Keep reading