← Back to blog
Technical SEO

Page With Redirect in Google Search Console: What It Means and When to Fix It

Most URLs in this row are exactly where they should be. The ones worth fixing are pages you want ranked, temporary redirects on permanent moves, and redirecting URLs still in your sitemap.

By Rajhussain Kanani7 min read

The short answer

“Page with redirect” in Google Search Console means the URL redirects somewhere else, so Google indexes the destination instead of this URL. Google’s Page indexing report describes it as a non-canonical URL that redirects to another page, which is why it isn’t indexed. For old URLs, http:// versions, non-www variants and pages you’ve moved, that is exactly what should happen, and there’s nothing to fix. It needs attention only when a URL in the list is one you want indexed, when the redirect is temporary but the move is permanent, or when the redirecting URLs are still in your sitemap and internal links.

A real example

This site renamed some tools when it was rebuilt. The old address /tools/broken-links now answers with a 308 permanent redirect to /tools/broken-link-checker. Inspecting the old URL in Search Console on 9 November 2026 showed: coverage Page with redirect, last crawled 8 November, page fetch Successful, and both the user-declared and the Google-selected canonical set to /tools/broken-link-checker.

That’s the healthy version of this status. The redirect is permanent, it goes straight to the replacement in one hop, the replacement isn’t redirecting anywhere itself, and the old URL isn’t in the sitemap. The same applies to http://checkseo.dev (308 to HTTPS) and www.checkseo.dev (301 to the bare domain): those URLs belong in this row.

Is it a problem? A quick test

What’s in the listVerdict
Old URLs, moved pages, retired campaignsFine
http://, www/non-www, trailing-slash variantsFine
A page you expect to rank on its ownProblem: something is redirecting it
URLs that are still in your XML sitemapFix the sitemap
URLs your own pages still link toUpdate the links
Lots of old URLs all redirecting to the homepageRisky: may be treated as soft 404s

Permanent vs. temporary redirects

Google’s redirects guide splits redirects into two groups, and the difference matters for this status. Permanent redirects — 301, 308, an instant meta refresh and a JavaScript location change — show the target in search results, and the indexing pipeline uses them as a signal that the target should be canonical. Temporary redirects — 302, 303, 307 and a delayed meta refresh — show the source page in search results and aren’t used as that signal.

So if you moved a page for good but used a 302, you’re telling Google to keep the old URL as the real one. Use a permanent redirect when you’re sure it won’t be reverted. Google also recommends server-side redirects wherever possible: JavaScript redirects only work if rendering succeeds, and Google calls them a fallback for when server-side and meta refresh redirects aren’t available. The 301 vs 302 guide goes deeper on choosing the code.

How to clean it up

1

Make sure no page you want indexed is in the list

Open Indexing → Pages → Page with redirect and scan the examples for URLs you expect to rank. If you find one, the redirect is the bug: a CMS rule, a trailing-slash setting, a language redirect or a leftover from a migration. Fix: Remove the redirect, or move the content to the URL it points at and update your links.

2

Take redirecting URLs out of the sitemap

A sitemap should list final URLs that answer 200. Google’s site-move guide says to submit a sitemap with the new URLs and update it, not keep the old ones. Fix: Replace each redirecting entry with its destination, or drop it.

3

Point internal links at the destination

Every internal link to a redirecting URL costs a hop for visitors and crawlers. Google’s advice after a move is to change internal links from the old URLs to the new ones. Fix: Update navigation, footers, body links and canonical tags to the final URL.

4

Flatten chains

Google says Googlebot can follow up to 10 hops in a redirect chain but advises redirecting to the final destination directly — and if that isn’t possible, keeping chains short, ideally no more than 3 hops. Fix: Point every old URL straight at the final page, not at another redirect.

5

Redirect to the right page, not the homepage

Sending many old URLs to one unrelated page, such as the homepage, can confuse users and might be treated as a soft 404. Redirect each URL to its real replacement; if there isn’t one, let it return a 404 or 410.

The Redirect Chain Checker follows a URL hop by hop — up to 10 — and shows each status code and destination, so temporary redirects, chains and loops stand out. No signup.

Trace a URL’s redirects

Find redirects in your sitemap and links

# Every hop: status code and Location header
curl -sIL "https://example.com/old-page" | grep -iE "^http|^location"

# Which sitemap URLs redirect? (prints status, URL and where it goes)
curl -s https://example.com/sitemap.xml | grep -o "<loc>[^<]*" | sed 's/<loc>//' \
  | xargs -n1 -P8 curl -s -o /dev/null -w "%{http_code} %{url_effective} -> %{redirect_url}\n" \
  | grep -E "^30[1278]"

Without a terminal, the Sitemap URL Extractor lists every URL in your sitemap, and the Broken Link Checker flags links on a page that redirect as well as the ones that are broken.

Page with redirect vs. Redirect error

They sound alike, but only one is an error. Page with redirect means the redirect worked and Google followed it. Redirect error means Google couldn’t get to the end: Search Console lists a redirect chain that was too long, a redirect loop, a redirect URL that grew past the maximum URL length, and a bad or empty URL in the chain. Redirect errors on pages you care about should be fixed first — see every “Why pages aren’t indexed” reason for where both sit in the report.

How long to keep redirects

Google’s site-move guide says to keep redirects for as long as possible, generally at least a year, so it can transfer signals to the new URLs, including links from other sites. For users it suggests considering keeping them indefinitely. It also notes that 301 and other permanent redirects don’t cause a loss in PageRank — so a long “Page with redirect” list after a migration is a sign the migration was done properly, not a loss.

If the same URLs also show up as Duplicate without user-selected canonical, the report is usually older than your redirect; inspect the URL to see the current state. And if pages that used to redirect now show as Soft 404, check whether they’re pointing at an unrelated page.

The free site scan finds your site’s pages, checks a sample for unreachable URLs, noindex tags, missing canonicals and other problems, and estimates how many pages across the site share each one.

Scan your whole site, free

Sources

Frequently asked questions

What does page with redirect mean in Google Search Console?

The URL redirects to another page, so Google doesn't index it and indexes the destination instead, if the destination qualifies. Search Console describes it as a non-canonical URL that redirects to another page.

Do I need to fix page with redirect?

Usually not. Old URLs, moved pages, http:// and www variants belong here. Act only if a page you want indexed is listed, if a permanent move uses a temporary redirect, or if redirecting URLs are still in your sitemap or internal links.

Why is my page with redirect not indexed?

Because it redirects — Google indexes the target URL, not the redirecting one. If you expected the listed URL itself to rank, find out why it redirects (a CMS rule, trailing-slash setting or migration leftover) and remove the redirect.

What's the difference between page with redirect and redirect error?

Page with redirect means the redirect worked and Google followed it. Redirect error means Google couldn't reach the end: a chain that was too long, a loop, a URL that exceeded the maximum length, or a bad or empty URL in the chain.

How long should I keep redirects in place?

Google's site-move guide says to keep them as long as possible, generally at least a year, and suggests considering keeping them indefinitely for users. Permanent redirects don't cause a loss in PageRank.

Check your own site with the Redirect Chain Checker.

Open Redirect Chain Checker

Want every check at once?

The free Full Audit runs 33 checks on any URL, most of them in seconds. Add your email afterwards and we send a detailed one-page report; the full-site report covers up to 1,000 pages.

More from the blog

We use cookies to analyze site usage and improve your experience. You can decline non-essential cookies. Privacy Policy