Page with redirect in Search Console: what to do

Recognise a normal exclusion

Search Console labels a source URL ‘Page with redirect’ because Google found it and followed a redirect elsewhere. That is expected when an old service URL moves to an equivalent new one, when HTTP consistently moves to HTTPS, or when one preferred hostname is enforced.

Do not try to index both the old URL and destination. The destination is the candidate for indexing. Instead, make sure the final page is accessible, relevant to the old page’s intent, and is the URL used in internal links, navigation and the sitemap.

• Identify the final destination
• Check the redirect is intentional
• Use the destination in internal links and sitemaps

Next decision: Canonical URLs: choose the page Google should understand. If you want this applied to a live site, see the SEO audit scope.

Choose the redirect that matches the move

For a permanent URL change, use a server-side permanent redirect such as HTTP 301 or 308. For a short, temporary change, an appropriate temporary redirect can be suitable. Google’s guidance focuses on clear, durable signals rather than a specific code as a magic SEO lever.

Avoid redirecting removed pages to the homepage merely to preserve a response. A user looking for a discontinued product should reach the nearest helpful category or replacement only when it genuinely answers the same need. Otherwise, a clear 404 or 410 can be more honest.

• Use permanent redirects for permanent replacements
• Send users to the closest equivalent destination
• Return 404/410 when no relevant replacement exists

Test the whole redirect path

A browser can hide a messy chain. Test the response sequence from the old URL through to the final canonical destination, including HTTP/HTTPS, www/non-www and trailing-slash variations. Every extra hop adds delay and makes maintenance harder; loops stop visitors and crawlers altogether.

After a migration, test a representative list of high-value URLs rather than only the homepage. Include service pages, top landing pages, PDFs, old campaign URLs and backlinks that send traffic. A redirect map is a decision record, not just a development handover.

• Look for one-hop routes where possible
• Check query strings and language versions deliberately
• Monitor 404 reports after launch

Keep redirects as part of information architecture

Update internal links after redirects are in place. Leaving every menu and footer link pointed at retired URLs makes the site slower to navigate and obscures the current structure. Update canonical tags, hreflang references and XML sitemaps to the final URLs too.

Retain valuable redirects for as long as users, links and search systems need them; do not remove them immediately after a redesign. Review them periodically, particularly when changing platforms. The goal is a stable, explainable set of routes—not a spreadsheet of redirects for its own sake.

• Replace internal references to retired URLs
• Keep redirect maps with migration records
• Review old routes before a platform change