SquishPixel Blog · SEO · Tools · Web performance

Google Search Console's 'Page with redirect' status is often fine, but not always

A DEV Community article looks at the grey 'Page with redirect' row in the Pages report of Google Search Console. The row sits under 'Why pages aren't indexed', so it looks like an error. According to the article, it usually is not one. A URL that redirects should not be indexed. The destination should be.

The status means Google asked for a URL and received a redirect. That can be a 301, 302, 307 or 308, or a meta refresh or JavaScript redirect that Google detected. Google then follows it and considers the target instead. The article says you can usually ignore entries caused by HTTP to HTTPS moves, www changes, trailing slash fixes, and old URLs from a migration. Some old URLs found through outside links may keep being re-crawled, which is a reason to keep those redirects.

The article says the report is still useful for spotting links on your own site that point at old URLs. It lists four cases worth fixing. A sitemap may list redirecting URLs, when it should hold only final URLs that return 200. Internal links in menus, footers and old posts may point at redirecting addresses. Canonical tags, which name the main version of a page, may point at a URL that redirects. And some redirects go to the wrong place, such as product pages sent to the homepage or chains ending in a 404.

The author suggests exporting the example URLs, running a script to check where each one ends up, how many hops it takes and whether the final status is 200, and then crawling your own site to find the pages that link to them. On redirect types, the article says 301 and 308 signal a permanent move, while 302 and 307 signal a temporary one, so Google may keep the old URL indexed longer. It also warns against removing redirects, blocking them in robots.txt, or using the 'Remove URLs' tool.

Why it matters

A large count in this report can cause needless worry, or lead to the wrong fix. Deleting redirects to shrink the number would turn the entries into 404 errors and break external links to those pages. The article's advice is to sort the list first and act only on what points to a real fault.

The real faults are quiet ones. Pages sent to the homepage, redirect chains and temporary redirects used for permanent moves can cost visitors and crawlers extra requests, or lose content altogether. Cleaning up your own sitemap, links and canonical tags is a small job that removes these problems at the source.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.