Page With Redirect in Search Console: Is It a Problem?
Search Console lists pages as "Page with redirect" and not indexed — it means those addresses forward somewhere else, so Google indexes the destination instead. Usually fine, occasionally a sign of a mix-up.
Common signs of this issue
- Search Console's Pages report lists "Page with redirect" under "Why pages aren't indexed".
- The example URLs are http versions, www or non-www versions, or old addresses of your pages.
- The count jumped after you moved to https, changed domain, redesigned the site or changed your permalink structure.
- Some listed URLs have a trailing slash difference, such as /services versus /services/.
- You get an email from Search Console about a new indexing reason on your site.
- A page you expected to be indexed shows this status instead.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Open Search Console, then Indexing, then Pages, click Page with redirect, and look at the example URLs. If they are
http://versions of your https pages, or www versions when your site uses non-www (or the reverse), that is expected and correct. - Click a few of the example URLs in your browser. Each one should land on a working page in one hop — the version you actually want people to see. If one lands on the homepage, an error page or an unrelated page, note it.
- Use a free redirect checker (search "redirect checker") on a couple of the URLs. You want one redirect, a 301, straight to the final page. Several hops in a row, or a 302 on a permanent move, is worth mentioning to your developer.
- Open your sitemap (often
yourdomain.com/sitemap.xml) and check whether it lists any of the redirecting addresses. A sitemap should list only final destination URLs. If it lists old or http addresses, ask whoever manages the site to regenerate it. - Check your menu and main page links. If internal links point at old addresses that then redirect, they still work, but updating them to the final URL is cleaner and saves Google a step.
- If a page you want indexed shows this status, inspect it with URL Inspection. It may be redirecting by mistake — a plugin rule, a leftover redirect from a redesign, or a language or location redirect.
- Do not confuse this with Redirect error, a separate status. Redirect error means the redirect is broken — a loop, a chain that is too long, or a bad destination — and that one does need fixing.
What this usually means
Page with redirect means Google tried the listed address and was sent somewhere else. Because a redirecting URL has no content of its own, Google indexes the destination page and records the original address here as not indexed. This is a report of redirects doing their job, not a warning.
It nearly always shows up after normal housekeeping: moving to https, settling on www or non-www, changing domain, or renaming pages and redirecting the old addresses. Google remembers old URLs for a long time and will keep checking them, so this list can stay large for months after a site move. That is fine — the redirects are what carry your old search visibility over to the new pages.
It becomes a real issue only in a few cases: a page you want in Google is redirecting when it should not, redirects point to the wrong place (everything dumped on the homepage instead of the matching new page), your sitemap or internal links keep feeding Google redirecting addresses, or redirects chain through several hops. Those are worth tidying; a list of old and alternate addresses is not.
What not to do
- Don't remove working redirects to make the count go down. That turns old links and bookmarks into 404 errors and throws away the search value they carry.
- Don't redirect every old page to the homepage after a redesign. Send each old page to the closest matching new page.
- Don't click Validate fix for this status when the redirects are intentional. There is nothing to fix and the validation will not clear it.
- Don't list redirecting addresses in your sitemap. Sitemaps should contain only the final pages you want indexed.
- Don't stack new redirects on top of old ones. Chains of redirects slow visitors down and can stop Google following them.
- Don't edit .htaccess or server redirect rules yourself on a live site unless you are comfortable undoing it. A small typo can take the whole site down.
When to get help
If this status appeared alongside a drop in traffic after a redesign, platform change or domain move, it is worth getting someone to audit the redirects properly. A mapping mistake — old pages sent to the homepage, missing redirects, or pages redirecting in a loop — can quietly cost a lot of the search visibility you had built up, and it is far easier to fix in the first weeks after a move than months later. Help also makes sense if pages you want indexed are redirecting and you cannot find where the rule is coming from.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Frequently asked questions
What does Page with redirect mean in Search Console?
It means the listed address sends visitors and Google to a different address. Google indexes the destination page instead, so the original URL is shown as not indexed.
Do I need to fix Page with redirect?
Usually not. If the listed URLs are http, www or old versions of your pages and they redirect to the right place, everything is working as intended. Only act if a page you want indexed is redirecting by mistake.
Why are my http pages showing as Page with redirect?
Because your site redirects http to https, which is correct. Google still checks the old http addresses from time to time and reports that they redirect.
How long will old URLs keep showing as Page with redirect?
Often for months, sometimes longer. Google remembers old addresses and rechecks them occasionally. That is harmless as long as the redirects stay in place.
What is the difference between Page with redirect and Redirect error?
Page with redirect means the redirect works. Redirect error means it is broken, such as a loop, too many hops, or a destination that fails. Redirect error needs fixing.
Should redirects be 301 or 302?
For a permanent move, such as a new domain or a renamed page, a 301 is the clearest signal. A 302 is meant for temporary changes, though Google may treat a long-standing 302 as permanent.