Page with Redirect in Search Console: What It Means and How to Fix
'Page with redirect' in Search Console is usually normal. Here is how to spot the redirects that need fixing and clean them up step by step.
- "Page with redirect" means Google found a URL that sends visitors to another URL, so it indexes the destination instead. This is usually normal.
- You only need to act if the redirect is wrong, the destination is not indexed, or your own links and sitemap still point to the old URL.
- Fix the cause: update internal links, list only final URLs in your sitemap, use one clean 301 redirect and remove redirect chains.
- Do not click Validate fix for URLs that are meant to redirect. They will stay in this list, and that is fine.
You open Google Search Console and see a long list of URLs marked "Page with redirect" under "Why pages aren't indexed." It looks like an error, and many new site owners panic and start changing settings.
In most cases nothing is broken. This guide shows you how to check whether your redirects are healthy, which ones need fixing, and the exact steps to clean them up.
What does "Page with redirect" mean in Search Console?
Google's Page indexing report help page describes it simply: this is a non-canonical URL that redirects to another page, so this URL will not be indexed.
Think of it like a change of address. If your old house sends all post to your new house, the post office stops using the old address. Google does the same. It follows the redirect and indexes the page at the end of it.
So the old URL being "not indexed" is exactly what should happen. The real question is whether the destination page is indexed.
Common reasons your site has "Page with redirect" URLs
Almost every website has some of these. Here are the usual sources:
- HTTP to HTTPS. After you install SSL,
http://yoursite.com/pageredirects tohttps://yoursite.com/page. - www and non-www.
www.yoursite.comredirects toyoursite.com, or the other way round. - Trailing slash.
/blog/postredirects to/blog/post/. - Changed slugs. You renamed a post and added a redirect from the old URL.
- Deleted or merged pages. You combined two weak posts into one strong post.
- Login or language redirects. Some pages send visitors to a login page or a language version.
If you are not sure about the HTTPS part, our guide on the "Not secure" SSL and HTTPS fix explains how the redirect from HTTP should work.
Is "Page with redirect" bad for SEO?
Usually not. Use this table to decide if a URL in the list needs work.
| What you see | Is it a problem? | What to do |
|---|---|---|
| http:// version redirects to https:// | No | Nothing. This is expected. |
| www redirects to non-www (or the reverse) | No | Nothing, as long as you use one version everywhere. |
| Old slug redirects to the new post | No | Update any internal links still using the old slug. |
| A page you want ranked is in this list | Yes | Find and remove the redirect on that page. |
| Destination page is "not indexed" too | Yes | Fix the destination first (noindex, 404, thin content). |
| Redirect goes to the home page for many URLs | Often | Point each old URL to the closest matching page, or let it return 404. |
| URL goes through 2 or more redirects | Yes | Change it to one direct redirect. |
How to check a "Page with redirect" URL step by step
Step 1: Open the list
- Open Search Console and choose your property.
- Go to Indexing > Pages.
- Scroll to "Why pages aren't indexed" and click Page with redirect.
- Click the export icon if the list is long, so you can sort it in a spreadsheet.
Step 2: Group the URLs
Look for patterns. Most lists split into a few groups, such as "all http:// URLs," "all www URLs" or "old post slugs." Groups that match the "No" rows in the table above can be ignored. Spend your time on the rest.
Step 3: See where each URL goes
Paste a URL into the search bar at the top of Search Console to run URL Inspection. It shows whether Google sees a redirect. Then open the URL in a private browser window and note the final address in the bar.
To count the number of hops, you can use a free redirect checker tool or run this in a terminal:
curl -sIL https://example.com/old-page/ | grep -i -E "^(HTTP|location)"
Each HTTP line is one step. If you see more than one 301 or 302 before the final 200, you have a redirect chain.
Step 4: Check the destination
Inspect the final URL in URL Inspection. It should say "URL is on Google," or at least be indexable. If the destination shows noindex, a 404 or "Duplicate without user-selected canonical," fix that first. Our guide on duplicate without user-selected canonical covers that case.
How to fix redirect problems the right way
1. Update your internal links
Your menus, footers and old posts should link straight to the final URL. If your post links to http:// or an old slug, every click and every crawl goes through a redirect for no reason. Search your content for old URLs and replace them.
2. Clean your sitemap
A sitemap should list only final, indexable URLs that return a 200 status. If your sitemap contains URLs that redirect, Google keeps crawling them and they keep showing up in this report. Regenerate the sitemap and resubmit it. Our guide on how to submit a sitemap in Search Console shows where to do this.
3. Use one permanent redirect, not a chain
Google's guide on redirects and Google Search recommends server-side redirects as the most reliable choice. Use 301 or 308 for permanent moves and 302 or 307 only for temporary ones. Permanent redirects tell Google the new URL should be the one shown in results.
Avoid chains like this:
http://www.site.com/post → https://www.site.com/post → https://site.com/post → https://site.com/post/
Set your rules so every old version jumps straight to the final URL in one step.
4. Choose one version of your domain
Pick https plus either www or non-www, and use it everywhere: in your CMS settings, your canonical tags, your sitemap and your links. Mixed versions are the biggest cause of extra redirects on small sites.
5. Redirect to a matching page, not the home page
When you delete a post, send its URL to the closest related page. If there is no related page, it is better to let the old URL return 404 than to send everything to the home page.
Should you click "Validate fix" for Page with redirect?
Only if you removed a redirect from pages that should be indexed. For URLs that are meant to redirect, validation will not change anything, because they will still redirect.
When you do validate, Google says it typically takes up to about two weeks and can take longer. Do not click Validate fix again until the current check has passed or failed. For one or two important pages, you can also use Request indexing on the final URL. Our guide on how to request indexing explains when that helps.
Redirect checklist for new websites
- One preferred domain: https plus www or non-www.
- All other versions redirect in one step with a 301.
- Canonical tags point to the final URL.
- Sitemap lists only final URLs that return 200.
- Menus and internal links use the final URLs.
- Deleted posts redirect to a close match or return 404.
- No redirect loops or chains of two or more hops.
Final word
"Page with redirect" is mostly Google telling you it followed your redirects correctly. Leave the expected ones alone. Fix the real problems: important pages that redirect by mistake, chains, redirects to the home page, and old URLs in your sitemap and links.
Next step: export your "Page with redirect" list today, group it by pattern and check only the groups that do not match a planned redirect. If you want to learn Search Console and site setup properly, see our courses.
Frequently asked questions
Is 'Page with redirect' an error in Search Console?
Usually not. It means Google followed a redirect and indexed the destination page instead. It only needs action if an important page redirects by mistake or the destination is not indexed.
Should I click Validate fix for Page with redirect?
Only if you removed redirects from pages that should be indexed. URLs that are meant to redirect will stay in this list, and that is fine.
What is the difference between Page with redirect and Redirect error?
Page with redirect means the redirect works and Google indexed the target. Redirect error means Google hit a loop or a bad URL in the chain, which always needs fixing.
Should I use a 301 or 302 redirect?
Use a 301 or 308 for permanent moves, such as a changed slug or HTTPS. Use 302 or 307 only for short-term, temporary changes.