Page With Redirect in Search Console Explained
Page with redirect is a status in the Page indexing report of Google Search Console that lists URLs Google found but left out of its index because they send visitors to another address. Most of the URLs in it are there by design, since every retired page, old domain and http address that redirects correctly ends up on the list. The status matters most during restructures and domain changes, which is why it sits at the centre of technical SEO for organisations planning a migration.
Reading the report well comes down to separating the redirects you meant to create from the ones you did not. The sections below cover what the status means, how it differs from a redirect error, what usually causes it and how to check and fix the URLs that should not be there.
What Page With Redirect Means in Search Console
Page with redirect means Google requested a URL, received a redirect and recorded the original address as one it will not index. Google’s help page for the Page indexing report describes these as URLs that are not canonical and redirect to another page, adding that the target of the redirect may or may not be indexed depending on what Google thinks of that target.
The status sits in the table of reasons why pages are not indexed, which makes it look like a fault at first glance. In most cases it is the opposite, because the redirect is doing its job by passing visitors and ranking signals from an old address to the current one. A long list of URLs under Page with redirect is usually a record of past changes rather than a queue of problems waiting to be fixed.
The same help page notes that a canonical URL with a redirect can still be indexed. Google also keeps track of the old address as an alternate name after a domain move, so old URLs can still appear in results now and then until people get used to the new domain.
Page With Redirect Versus Redirect Error
Page with redirect and Redirect error are separate statuses, with only the second one always pointing to something broken. Page with redirect means the redirect worked and Google reached a destination, while Redirect error means Google could not complete the journey at all.
Google lists the causes of a redirect error as a chain that was too long, a redirect loop, a redirect URL that grew past the maximum URL length or a bad or empty URL somewhere in the chain. Any URL under Redirect error needs attention, because neither visitors nor Google can reach the content behind it.
Google’s crawlers follow up to 10 redirect hops by default, according to its documentation on HTTP status codes and redirects. A chain shorter than that still shows as Page with redirect, yet each extra hop adds another request before the visitor or crawler reaches the page.
Common Causes of Page With Redirect
Most URLs under Page with redirect come from routine housekeeping that sends one address to another. The list below covers the sources that account for most entries on a typical business website.
- The http version of every page redirecting to https after a security certificate was added
- The www and plain versions of the domain redirecting to whichever one was chosen as the main address
- Trailing slash or capital letter rules that send variations of a URL to one consistent version
- Retired pages, products or campaign pages redirecting to their closest replacement
- Old URLs from a redesign, restructure or domain change pointing at their new homes
- Internal links, sitemaps or backlinks from other websites that still point at addresses which now redirect
The list keeps growing while internal links, sitemaps or other websites still point at the old addresses, because Google keeps finding and requesting them. Internal links are the part you control directly. Pointing them straight at the final URL removes the hop for visitors and crawlers alike, as our guide to internal linking and website architecture explains.
Your XML sitemap deserves the same check. Google’s guidance on building a sitemap says it should list the canonical URLs you want shown in search results, so a sitemap that still includes redirected addresses sends a mixed signal. Our guide to XML and HTML sitemaps covers how WordPress generates one and what it should contain.
When Page With Redirect Needs Fixing
Page with redirect needs fixing when a URL you expect to rank appears in the list. A live service page, product or article showing under this status means something is sending it elsewhere, so the page you want in search results is not being indexed.
The cause is usually a rule that matches more than intended. A redirect plugin pattern written for an old section can catch new URLs with a similar path, a trailing slash rule can clash with the way WordPress builds permalinks and an old migration rule can outlive the structure it was written for.
Temporary redirects left in place cause a quieter problem. Google treats a 302 as a weak signal that the target should be processed, so a page that moved for good behind a 302 can keep its old address in search results for far longer than anyone intended.
Redirects that send every retired page to the homepage are another pattern worth catching. A retired page is better served by a redirect to its closest relevant replacement, since a homepage rarely answers what the visitor was looking for.
How to Check and Fix Page With Redirect URLs
Checking the report means sorting the expected redirects from the unexpected ones and tracing each unexpected redirect back to the rule that created it. The same four steps work for websites of any size, with a crawling tool doing more of the work on larger ones.
-
1
Export the List
Open the Page with redirect row in the Page indexing report and export the affected URLs. Filtering to submitted pages first shows any redirected URLs still listed in your sitemap.
-
2
Sort Expected From Unexpected
Mark the old, retired and http addresses you meant to redirect. Anything left over is a URL that probably should be indexed.
-
3
Inspect Each Unexpected URL
Run the URL Inspection tool on each one and check which canonical Google selected in the indexed data. Then confirm where the redirect leads.
-
4
Fix the Rule
Remove or narrow the rule causing the redirect, then update links and sitemaps. Request indexing once the page loads directly.
URL Inspection needs a little care with redirected addresses. The URL Inspection tool documentation explains that the indexed result for a redirected URL describes the tested URL rather than the redirect target, while the live test follows redirects without saying so or showing which URL it finally tested.
Redirect rules on a WordPress website usually live in one of a few places, which makes them quicker to trace when you check them in order. Start with the settings in your SEO or redirect plugin, then the .htaccess file or server configuration, then any rules set at the CDN.
Once the rule is fixed, the URL drops out of the list the next time Google crawls it. Search Console updates the count as pages are recrawled, so the list shrinks gradually rather than all at once.
Choosing the Right Redirect Type
The right redirect for a page that has moved for good is a permanent redirect set on the server, such as a 301 or 308. Google’s documentation on redirects and Google Search orders the methods by how likely Google is to interpret them correctly, with server redirects first and JavaScript redirects near the end.
| Redirect method | How Google treats it | When to use it |
|---|---|---|
| HTTP 301 or 308 | Permanent, with the target treated as the canonical URL | Pages, sections or domains that have moved for good |
| HTTP 302 or 307 | Temporary, so the source page usually stays in search results | Short moves such as a service that is briefly unavailable |
| Instant meta refresh | Read as a permanent redirect | Only when server redirects are not possible on the platform |
| Delayed meta refresh | Read as a temporary redirect | Rarely appropriate for pages that matter in search |
| JavaScript redirect | Seen only if Google renders the page successfully | A last resort when nothing else can be set up |
Meta refresh redirects count as permanent only when they fire instantly, since Google reads a delayed meta refresh as temporary. JavaScript redirects depend on Google rendering the page, which is why Google advises using them only when neither a server redirect nor a meta refresh is possible.
Either a redirect plugin or the server configuration can set proper 301 redirects on WordPress without touching theme code. Whichever method you use, keep a record of each rule and the reason it exists, so nobody has to work out later why a page is redirecting.
Redirects After a Website Migration
A website migration is the moment Page with redirect becomes a verification tool, because every old URL should appear in it pointing at the right new address. Google’s guidance on moving a website with URL changes recommends mapping each old URL to its new equivalent, using permanent server redirects, redirecting straight to the final destination and keeping the redirects for as long as possible, generally at least 1 year.
Save the full list of old URLs before launch and crawl it again once the new website is live. Every address should return a single redirect to a page that loads, so anything that errors or passes through several hops goes straight onto the fix list.
Priority Pixels plans migrations that protect existing rankings through proper redirects and URL mapping. The page on SEO migration services sets out how redirect mapping, launch checks and monitoring after launch fit together.
The redirect map is only one part of a migration, alongside staging, canonicals, sitemaps and analytics. The website migration SEO checklist covers each of those stages in the order they happen.
Keeping the Report Healthy Over Time
Keeping Page with redirect healthy comes down to a short review every month or two and a record of every redirect rule. Scan the list for URLs that should be indexed, spot check a few destinations and look for new chains created by the latest round of changes.
Clean URL structures make the job easier, because a URL that never changes never needs a redirect. Our guide to URL structure for search covers how to choose addresses that last through future redesigns.
Treated this way, the report becomes an audit trail of every change the website has been through rather than a source of worry. The URLs that matter are the few that should not be there. Finding them early keeps the pages you care about in the index and stops ranking signals leaking through redirects nobody meant to create.
FAQs
What does page with redirect mean in Google Search Console?
It means Google requested the URL, was sent on to a different address and left the original URL out of its index. The destination may be indexed in its place, depending on how Google assesses that page.
How do you fix a page with redirect issue?
Start by checking whether the redirect was intended, because redirects from old, retired or http addresses need no action. If a page that should rank is listed, find the rule sending it elsewhere in your redirect plugin, server configuration or CDN and remove or narrow it. Then update internal links and the sitemap so they point at the live URL.
Should redirected URLs be removed from your XML sitemap?
A sitemap should list only the final URLs you want to appear in search results, so redirected addresses belong outside it. Leaving them in sends Google a mixed signal and keeps them appearing under Page with redirect.
Do redirects lose SEO value?
A permanent 301 or 308 redirect is a strong signal to Google that the target should take the place of the old URL. Problems tend to come from chains of several hops, redirects to unrelated pages and temporary codes used for moves that are permanent.
Co-Founder at Priority Pixels
Paul leads on development and technical SEO at Priority Pixels, bringing over 20 years of experience in web and IT. He specialises in building fast, scalable WordPress websites and shaping SEO strategies that deliver long-term results. He’s also a driving force behind the agency’s push into accessibility and AI-driven optimisation.
Nathan Yendle | 02/10/2026
