How to Fix Page With Redirect in Google Search Console (2026 Step-by-Step Guide)

To fix Page with redirect in Google Search Console, first check whether anything is actually broken, because in most cases nothing is. Per Google's Page indexing report help, the status means the URL is a non-canonical URL that redirects to another page, so that URL will not be indexed; the page it redirects to is the one Google considers for the index. You only need to act when a URL you want in Google redirects by mistake, or when your sitemap, canonical tags or internal links still point at the old redirecting URL. Fix those, inspect the destination URL, then select Validate fix.

Last updated: November 2026. This guide is for small business owners and anyone who looks after their own website. Every step and every statement about how Google treats redirects was checked against Google Search Console Help and Google Search Central on November 11, 2026; the sources are linked inline and listed at the end.

• It is a status, not a penalty: a redirecting URL is not indexed itself, and Google says Not indexed is not necessarily bad.
• Usually correct: http to https, non-www to www, trailing-slash versions and old URLs you moved on purpose should all show up here.
• Fix it only when: a page you want indexed redirects by mistake, or your sitemap, canonical tag or internal links still use the redirecting URL.
• Use the right redirect type: Google shows the redirect target in results for permanent redirects (301, 308) and the source page for temporary ones (302, 303, 307).
• Validation is slow: Google says validation typically takes up to about two weeks and can take much longer.

Page with redirect is one of the reasons listed in the Why pages aren't indexed table of the Page indexing report. Google's definition is short: it is a non-canonical URL that redirects to another page, so the URL will not be indexed, and the target of the redirect might or might not be indexed depending on what Google thinks about that target. Elsewhere on the page Google puts it in one line: redirect URLs are not indexed, only the redirect target. Read the definition in Search Console Help.

Do not confuse it with Redirect error, which is a separate reason in the same report and a real fault. Google lists four causes of Redirect error: a redirect chain that was too long, a redirect loop, a redirect URL that eventually exceeded the maximum URL length, or a bad or empty URL in the redirect chain. Page with redirect means the redirect worked; Redirect error means it did not. Both are described in the Page indexing report help.

Often, no. Google says you should not expect every URL on your site to be indexed, only the canonical pages, and that it is fine for a URL not to be indexed for the right reasons. Its own guidance on redirects and Google Search recommends picking one preferred URL when a page can be reached several ways and redirecting the others to it. Every one of those other addresses will then appear as Page with redirect. Use this comparison to sort your list.

• Leave it alone: the http version of a page that redirects to https.
• Leave it alone: the www or non-www version, or the trailing-slash variant, that redirects to the format you chose.
• Leave it alone: an old page, product or blog post you moved or merged on purpose and redirected to its replacement.
• Fix it: a live page you want in Google that redirects somewhere else by mistake, for example to the home page.
• Fix it: a URL listed in your XML sitemap that redirects. A sitemap should list only the final addresses.
• Fix it: a redirect that lands on the wrong page, a missing page (404) or an unrelated page, and links on your own site that still point at the old URL.

You can do all of this yourself in Google Search Console, which is Google's own free tool. No paid service or middleman is required. What to prepare: a Google account with access to your Search Console property (owner permission if you plan to submit a sitemap), a login to your website builder, CMS or hosting where redirects are managed, and the address of your XML sitemap.

• Step 1. Open the report: sign in to Search Console, choose your property and open the Page indexing report (search.google.com/search-console/index). In the Why pages aren't indexed table, click the Page with redirect row.
• Step 2. Check the Source column: Google says that in general you can fix only issues where the source is listed as Website.
• Step 3. Get the list: the details page shows a chart and an examples table. Use the Export button to download it to a spreadsheet. Google notes the examples list is limited to 1,000 rows and may not show every affected URL.
• Step 4. Sort every URL into two groups: "expected" (http, www, trailing slash, pages you moved on purpose) and "needs a look" (anything you did not expect to redirect). Open each "needs a look" URL in a browser and note where the address bar ends up.
• Step 5. Inspect the destination: paste the URL into the inspection bar at the top of Search Console. For a redirecting URL the result describes the tested URL, not the target, so click the INSPECT button in the Page indexing section to see the page that is actually in the index. If it says URL is on Google, that URL needs no fix.
• Step 6. Remove wrong redirects: if a page you want indexed redirects by mistake, delete or correct that rule where it was created: your CMS redirect settings, a redirect plugin, your hosting panel or the server configuration. Google notes that platforms such as Blogger or Shopify may have built-in redirect tools, so check your platform's help pages.
• Step 7. Point redirects at the right place: every redirect you keep should go straight to the closest matching live page in one hop, not through a chain of several redirects.
• Step 8. Clean the signals that still name the old URL: update the XML sitemap so it lists only final URLs, make sure the canonical tag on the destination page names the destination itself, and change internal links to the final address.
• Step 9. Test and resubmit: on the corrected page, click Test live URL in the URL Inspection tool, then Request indexing if the page is one you want crawled soon. If you changed the sitemap, open the Sitemaps report, paste the sitemap URL into the Add a new sitemap box and click Submit.
• Step 10. Validate: back on the Page with redirect details page, click Validate fix, but only after fixing every URL you intended to fix. If only expected redirects remain, skip validation.

The inspection steps come from Google's URL Inspection tool help, the sitemap steps from the Sitemaps report help (the report itself is at search.google.com/search-console/sitemaps), and the report steps from the Page indexing help, whose own button opens the Page indexing report. Submitting a sitemap there requires owner permission on the property, and Google applies a daily limit to indexing requests; for many pages it says to submit a sitemap instead.

The redirect type tells Google which address to show. According to Google Search Central, visitors generally cannot tell the types apart, but Google Search treats them differently.

• Permanent redirect (HTTP 301 or 308): Googlebot follows it and the indexing pipeline uses it as a signal that the redirect target should be canonical. The new address is shown in search results. Use it when you are sure the move will not be reversed.
• Temporary redirect (HTTP 302, 303 or 307): Googlebot follows it, but the redirect is not used as a signal that the target should be canonical. The source page is shown in search results. Use it when a page is unavailable for a short time.

• The count has not changed after a few days: this is normal. Google says validation typically takes up to about two weeks, but in some cases much longer, and it sends a notification when validation succeeds or fails.
• Validation failed: Google stops validation when it finds a single remaining instance. Open the issue details page, click See details to find the URL that caused the failure, fix it, then click Start new validation. Wait for one validation cycle to finish before requesting another.
• The number will never reach zero: expected whenever you keep legitimate redirects, which will go on "failing" validation. Google says it might not always make sense to fix and validate an issue, and that it updates the count as it recrawls whether or not you request validation.
• A URL you already fixed is still listed: check the crawl date for that URL. Google says you may have fixed it after the last crawl. Confirm the fix with a live test and request re-indexing.
• The destination page is not indexed: this is a separate question from the redirect. Inspect the destination URL and read the reason given in its Page indexing section, such as a noindex tag or a robots.txt block.
• You see Redirect error, not Page with redirect: look for a loop or a long chain. Google suggests using a web debugging tool such as Lighthouse to get more detail about the redirect.

• Mistake, deleting good redirects: removing an http to https or old-page redirect just to clear the report breaks links and bookmarks.
• Mistake, leaving old URLs in the sitemap: Google says to include in your sitemap the URLs you want to see in search results, written as full absolute URLs.
• Mistake, redirect chains: Google advises redirecting to the final destination directly. Googlebot can follow up to 10 hops, but Google says to keep a chain to ideally no more than 3 and fewer than 5 when a chain cannot be avoided.
• Tip, link to the final URL: Google recommends linking within your site to the canonical URL rather than a duplicate, because consistent linking helps it understand your preference.
• Tip, validate a smaller set: Google's own pro tip is to submit a sitemap containing only your most important pages, filter the report by that sitemap, and then request validation, which can complete faster.

The strength of each signal is set out in Google's guide to specifying a canonical URL: redirects and rel="canonical" are strong signals, while sitemap inclusion is a weak one. The sitemap rules are in Build and submit a sitemap and the chain advice is in Site moves with URL changes. Related reading: our complete guide to technical SEO, our guide to improving INP (Interaction to Next Paint) and our walkthrough of robots.txt and Google-Extended.

• Opened the Page with redirect row, exported the list and marked each URL as expected or needs a look.
• Inspected the destination of each "needs a look" URL with the INSPECT button.
• Removed mistaken redirects; moved-for-good pages use a permanent redirect (301 or 308) straight to the final page.
• Sitemap lists only final, absolute URLs and has been resubmitted.
• Canonical tag on each destination page names that same page, and internal links use the final URLs.
• Ran Test live URL on corrected pages, then requested indexing where needed.
• Clicked Validate fix only where real fixes were made, and allowed about two weeks.

Nobody can honestly promise that. Removing a mistaken redirect makes it possible for Google to index that page again, but Google decides whether and when: its help says even the status URL is on Google does not guarantee a page appears in search results, and that indexing typically takes a few days. If your list holds only expected redirects, the honest result is "nothing to fix". See the URL Inspection tool help.

All sources were opened and checked on November 11, 2026.

Google Search Console Help: Page indexing report | Google Search Console Help: URL Inspection tool | Google Search Console Help: Manage your sitemaps using the Sitemaps report | Google Search Central: Redirects and Google Search | Google Search Central: How to specify a canonical URL | Google Search Central: Build and submit a sitemap | Google Search Central: Site moves with URL changes