Page With Redirect in Search Console: When It Is a Problem

“Page with redirect” in Google Search Console lists URLs that Google found but did not index because they redirect somewhere else. In most cases this is correct and needs no action. A redirected URL is not supposed to be indexed; its destination is.

The status only becomes a problem in a few specific situations: when an important page is redirecting by mistake, when your sitemap or internal links keep pointing to redirected URLs, or when redirects chain or loop. This guide explains how to separate normal entries from the ones worth fixing.

Why the report fills up

Every site that has ever changed URLs accumulates redirected addresses. Common sources include:

• HTTP to HTTPS and non-www to www redirects (or the reverse).
• Trailing slash normalisation, where /page redirects to /page/.
• Old URLs from a redesign, migration or slug change.
• Deleted products or posts redirected to replacements.
• Marketing links and short URLs that forward to real pages.

Google keeps discovering these through old backlinks, previous sitemaps and its own crawl history, so they appear in the report for a long time. That is expected.

When “page with redirect” is fine

If the listed URL is an old or alternative version of a page, and it redirects with a 301 or 308 to the correct, indexable destination, there is nothing to fix. The destination should appear in the indexed list. You can confirm by inspecting the destination URL in Search Console.

Large numbers in this report are not a ranking problem in themselves. Sites that have been through a migration can show thousands of entries for months.

When it signals a real problem

An important page is redirecting

Sort the list by URL and look for pages you expect to be live: service pages, key categories, current blog posts. If any appear here, something is redirecting them. Typical causes include a plugin redirect rule created by accident, a slug change that created a redirect from the current URL to an old one, or a language or location redirect sending Googlebot elsewhere.

Your sitemap lists redirected URLs

Sitemaps should only include final, indexable URLs. If the report shows URLs that are also in your sitemap, the sitemap is out of date or misconfigured. Common examples are HTTP versions, URLs without trailing slashes, or old slugs that a plugin did not update.

Internal links point to redirects

A redirect from an internal link costs very little on a single page, but across a site it adds crawl work and slows users slightly. After migrations, menus and in-content links often still point at old URLs. A crawler such as Screaming Frog will list internal links that hit redirects so you can update them to the final destination.

Redirect chains and loops

A chain is URL A redirecting to B, which redirects to C. Google follows a limited number of hops and may give up on long chains. A loop is A to B and back to A, which means neither page can be indexed. Both usually come from layered redirect rules: one in the server config, another in a plugin, another from a CDN.

Temporary redirects used permanently

A 302 or 307 redirect tells Google the move is temporary. Over time Google may treat a long-standing 302 like a permanent redirect, but if you know a move is permanent, use a 301 or 308 to send a clear signal.

A practical review process

Export the report and filter out patterns you know are fine, such as HTTP and non-www variants. Look at what remains and ask whether each URL should be live. For the ones that should, find and remove the redirect rule. For the ones that should redirect, confirm the destination is correct and indexable, and update internal links and sitemaps to point straight to it.

If a recent migration is behind most entries, our website migration SEO guide covers how redirect mapping should be planned to avoid traffic loss.

Should you click “Validate fix”?

Generally no. Validation is meant for issues, and “Page with redirect” is mostly an informational status. Validating it will not remove entries that are correctly redirecting. Use validation only after fixing a page that was wrongly redirecting, and even then, requesting indexing for that single URL through URL Inspection is usually more direct.

Keeping redirects under control

Redirect problems tend to build up quietly through redesigns, plugin changes and content updates. A periodic check of redirect rules, sitemap contents and internal links keeps the report meaningful, so the entries that matter stand out.

If you are unsure whether redirects are holding back important pages, our technical SEO service audits redirect rules across server, CMS and CDN layers and cleans up chains, loops and outdated links.