IndexVerdict
URL changes

Page with redirect

The URL sends visitors somewhere else. A redirecting URL normally does not need its own indexed result; the destination is the page to inspect next.

Troubleshooting guide · Public signals and practical next steps

What this means

Search Console identifies this URL as a redirect rather than the page to index. This status does not confirm that the destination is indexed.

When it’s normal—and when to investigate

Often expected

HTTP-to-HTTPS upgrades, domain normalization, renamed pages, and carefully planned migrations commonly produce this status.

Worth investigating

Investigate an unintended destination, a loop, a long chain, or a redirect that leads to an error, login screen, or unrelated homepage.

Work through these checks

  1. Follow every hop

    Record each status and destination. Start with the submitted URL, not just the page that eventually appears in your browser. Confirm the final URL is the one you meant to publish.

  2. Inspect the final page independently

    A redirect is not a health check for its destination. Confirm a successful content response, crawl access, no unwanted noindex, and a sensible canonical.

  3. Check the reason for the move

    Permanent and temporary redirects communicate different intent. Choose the response that matches whether the move is lasting, and avoid redirecting unrelated removed pages to the homepage.

  4. Update links you control

    Point navigation and sitemap entries directly to the preferred final URL. This avoids forcing every new discovery through the old address.

FREE URL DIAGNOSTICOne page. Public signals.

Use a public HTTP or HTTPS URL. No login needed. Don’t submit private links or URLs containing access tokens.

HTTP & redirectsCrawl & index controlsCanonical & content

Common causes

  • A normal HTTPS or preferred-host redirect.
  • An old slug permanently moved to a relevant replacement.
  • Conflicting domain or trailing-slash rules create repeated hops.
  • A plugin or authentication layer redirects a public page unexpectedly.

Possible fixes

  • Leave an intentional, working redirect in place.
  • Simplify avoidable chains and repair loops at the rule that creates them.
  • Use a relevant replacement when content moved; return a genuine 404 or 410 when it is gone without a replacement.
  • Test both old and new URLs after a migration and monitor the new URL in Search Console.

Make changes that match the page’s intended purpose. A technically valid page is not guaranteed to be indexed.

What this tool can and cannot verify

It can

Follow up to five HTTP redirects, show each response, and inspect the final page’s technical signals.

It cannot

Follow JavaScript or meta-refresh navigation, verify migration completion, or establish which URL Google currently indexes.

Google’s own indexing status is available through Search Console / URL Inspection for a verified property. The live test and the recorded indexing report answer different questions.

A useful follow-up

Should the old URL be in my sitemap?

For an ordinary current sitemap, use the canonical final URLs you want indexed. Keep useful redirects for visitors who still use old links.

Official reference: Google: Redirects and Google Search. See also the Page indexing report documentation.