301 Redirects in Google Search Console: SEO Audit and Corrections in 2026

This page is for SEO managers, marketers and business leaders preparing a redesign, an http → https migration or a domain change. It explains how to read 301 redirects in Google Search Console, spot chains, loops and non-indexable targets, and then decide what to fix first.

It complements the complete guide to Google Search Console and also covers the HTTPS report and the Change of address tool.

Understanding 301 Redirects in Google Search Console: Audit and Secure Your Migration

A 301 signals a permanent URL change. GSC does not apply your server rule: it reports what Googlebot has observed. Three questions structure the reading:

• does the source URL redirect, and in a single hop?
• which final page has Google retained?
• is that final page indexable and consistent (canonical, content, access)?

Expect old and new URLs to coexist for a while. The full reading of the Pages report is covered in the guide to indexing in Google Search Console.

When to Prioritise a 301: Redesigns, URL Changes, Consolidation and Domain Migrations

A 301 is the right choice when the change is permanent: redesign, content merger, domain change, URL normalisation. Prioritise pages with backlinks or strong traffic. Here is how to choose the status code:

Server rules are a development matter; in Search Console, what matters is the observed effect: a final URL that is indexable and canonical.

Implementing Reliable 301 Redirects (Without Cannibalising Indexation)

Core Rules: 1:1 Matching, Topical Relevance and a Single Target Page

Aim for a 1:1 "old URL → new URL" correspondence with equivalent intent. Mass redirects to the homepage or generic pages are treated as soft 404s. Where there is no real equivalent, leave the 404 or switch to a 410; the full rule is in the guide to 404 errors in Google Search Console.

Classic Pitfalls: Chains, Loops, Irrelevant Redirects, Mixing HTTP/HTTPS and www/non-www

Four pitfalls come up in most audits:

• Chains (A → B → C): each hop delays consolidation and consumes crawl budget.
• Loops (A → B → A): the page is never reached and Google reports a "Redirect error".
• Non-indexable targets: the redirect ends on a page in noindex, 404 or 410.
• Non-normalised variants: http/https and www/non-www redirected in cascade instead of a single hop.

Standardise host and protocol from the design stage to reduce the variants Googlebot sees.

Auditing a 301 Redirect with Search Console

URL Inspection: Verifying Recognition, Canonical URL and Final Page

The URL Inspection tool shows the behaviour seen by Googlebot. On the source URL, then on the target, check:

• the number of hops before the final page;
• the code returned by the final page (200 expected);
• the declared canonical and the one selected by Google;
• the target's indexability (no noindex, access allowed).

Reserve this URL-by-URL check for high business-value pages.

Pages Report: Interpreting "Page with Redirect" and "Redirect Error"

Redirect-related statuses do not call for the same decision:

• "Page with redirect": the listed URL redirects and is not indexed; no problem if the target is indexable, returns a 200 and is consistent.
• Abnormal volume of "Page with redirect": a sign of an overly broad server rule or parasitic URLs generated by the site.
• "Redirect error": a chain or loop Googlebot could not follow to the end; fix it first, then confirm with "Validate fix".

Sitemaps and Performance: Checking the Switch and Measuring Its Effect

After the switch, submit a sitemap in the Sitemaps report that lists only final URLs returning a 200, and track the gap between submitted and indexed URLs.

In the Performance report, compare the periods before and after the switch, then filter by:

• page, to isolate migrated URLs that lose or gain clicks;
• query, to check that the target answers the same intent;
• country and device, to spot a localised regression.

If a target's CTR drops, it may not match the intent of the old page.

Diagnosing and Correcting Redirect Anomalies Flagged in the Console

Errors and Warning Signals: Redirect Error, Page Not Found, Access Denied and Soft 404

A target showing "Not found (404)", "Blocked due to access forbidden (403)", "Soft 404" or "Crawled – currently not indexed" is always diagnosed with the same three-point check:

• the behaviour of the source URL;
• the status of the final page;
• the semantic consistency between the two.

For a chain or a loop, identify the first link responsible (URL pattern, global rule), rewrite the redirect as a single hop, then correct internal links.

SEO Conflicts and Prioritisation: Canonicals, Hreflang and URL Parameters

The target must be the canonical, hreflang tags must follow the variant logic and URL parameters must be stabilised. To order the fixes, cross three criteria:

• SEO value: traffic, backlinks, conversions;
• technical risk: chains, loops, non-indexable targets;
• business exposure: pages that carry sales or leads.

Start with pages that combine high value and high risk.

Migrating from HTTP to HTTPS: A Successful Transition in Search Console

In GSC, http and https are two separate sets. A Domain property aggregates all variants and reveals residual http URLs; it can only be verified via DNS (see the guide to verifying a Google Search Console property).

Also keep the http and https URL-prefix properties: an http property that still receives impressions signals an incomplete migration.

Migration Steps and How to Check Them in GSC

Each migration step has its own checkpoint in Search Console:

Certificates, HSTS and TLS configuration are hosting matters: they are not managed from GSC.

Checking the HTTPS Canonical with URL Inspection

During a migration, the declared canonical and the one selected by Google must both point to the https version. If Google still retains an http URL or the wrong variant, look for the cause among:

• internal links that have not been updated;
• a sitemap that still references http;
• canonical tags left on the old version;
• a redirect chain between variants instead of a single hop.

Fix the issue, then test the live URL.

The HTTPS Report in Search Console: How to Read It and Its Limits

The HTTPS report works as a dashboard: it shows whether indexed pages are served over https and flags site-wide anomalies, which you then refine page by page with the URL Inspection tool. It does not cover mixed content, which is checked in templates. Here is how to read the issues to address:

Deal first with what blocks access, then with redirect or canonical inconsistencies, and finally with mixed content.

Use Case: Domain Change and "Change of Address"

Before declaring a domain change, verify:

• https consistency across the whole new domain;
• server access and the absence of blocking in robots.txt;
• www/non-www normalisation, to avoid cascading redirects;
• the readiness of target pages (content and linking).

Build the mapping from URLs that are actually visited and linked to: a single target per source URL, one reference page per merger.

The Change of Address Tool: What GSC Specifically Adds

The Change of address tool sits in the Settings of the old domain's property. It tells Google that the whole site has moved to a new domain. It requires both properties to be verified in Search Console and 301s from the old domain to the new one to be in place. It is not used for an http → https migration or for a URL change within the same domain.

Post-Migration Monitoring: Indicators to Track and Realistic Timescales on Google's Side

Every week after the switch, monitor:

• the number of indexed URLs on the new domain, in the Pages report;
• 404 and 5xx errors on old and new URLs;
• the volume of redirected URLs;
• clicks, impressions, CTR and positions in the Performance report.

Consolidation is progressive and may fluctuate depending on crawl frequency.

Best Practices to Stabilise the Index After a Wave of 301 Redirects

Retention Period, Clean-Up and Continuous Control

Google recommends keeping a 301 redirect in place for at least one year (at the time of writing). Removing a 301 too early turns an asset into a 404 and loses historical signals. After the switch, the clean-up covers:

• internal links, rewritten to final URLs;
• the sitemap, republished without redirected URLs;
• server rules, simplified;
• reference content (menus, hubs) that generates the most links.

Every week, the Pages, Crawl stats and Security issues reports act as alerts; every month, the Performance report drives decisions; after a fix, "Validate fix" confirms the effect. With every release, inspect a few critical URLs.

Depending on Your Situation

Depending on the redirect problem you face, the right starting point differs:

• Your target returns access denied: the diagnosis of 403 errors in Google Search Console details causes and fixes.
• Your sitemap still lists old URLs: managing sitemaps in Google Search Console explains how to regenerate and monitor it.
• Googlebot slows down after the migration: crawl monitoring in Google Search Console helps you read Googlebot's activity on the new site.
• You are preparing a full redesign: a technical SEO audit sets the scope of URLs to redirect before mapping.

To spot chains, loops and non-indexable targets before going live, the Incremys 360° SEO and GEO audit lists at-risk URLs and helps you prioritise fixes.

FAQ

Why Does Google Search Console Display "Page with Redirect" and Is It a Problem?

This status means the listed URL redirects to another page and is therefore not indexed itself. It is not a problem if the destination returns a 200, remains indexable and matches the old page. Investigation is only needed if the volume rises for no reason or if redirects point to irrelevant pages.

How Long Does Google Take to Transfer SEO Signals After a 301 Redirect?

There is no single timeframe for transferring signals after a 301. Consolidation depends on crawl frequency, the volume of migrated URLs, the popularity of the old pages and technical stability. Fluctuations are normal before things stabilise.

Should Legacy URLs Be Kept in the Sitemap After a Permanent Redirect?

No, the sitemap should list only the final URLs you want indexed, returning a 200. Leaving redirecting URLs sends Google a contradictory signal and complicates diagnosis in Search Console. After a migration, submit a regenerated sitemap and track the gap between submitted and indexed URLs.

What Should You Do If Google Still Indexes the Old URL Despite the Redirect?

First inspect the old URL to confirm a single-hop redirect. Then check the target: 200 response, no noindex, consistent canonical. Finally, correct internal links and the sitemap. Google may temporarily retain the old URL as long as external links still point to it.

How Can You Reduce the Impact of Redirect Chains on Crawling and SEO Performance?

Replace each chain with a direct redirect to the final URL, in a single hop. Then correct internal links so they point to final URLs rather than intermediates. This reduces latency for users and preserves crawl budget for strategic pages.

What Is the Purpose of a Redirect Mapping Tool Before Going Live?

A redirect mapping documents the correspondence between old and new URLs before deployment. It prevents omissions and generic redirects to the homepage. It also serves as the reference for testing, prioritising and tracking the migration in Search Console.

What Does the HTTPS Report in Google Search Console Show?

The HTTPS report shows whether indexed pages are served over https and flags site-wide anomalies: invalid certificate, canonical left in http, reversed redirect to http. It does not cover mixed content, which is checked in templates. Its alerts are then refined page by page with the URL Inspection tool.