Page with redirect
The address redirects to another one, so Google indexes the other one instead. In most cases that is exactly what the redirect is for. It needs work only when your own links or sitemap keep sending Google to the old address.
What Google is telling you
Google’s help page says this is a non-canonical URL that redirects to another page, so it will not be indexed; the target may or may not be, depending on what Google thinks of it. Redirect URLs are not indexed, only their targets.
Google’s page on status codes adds how it reads the redirect: a 301 or 308 is a strong signal that the target should be processed, a 302, 303 or 307 a weak one, and whatever the redirecting address itself returns is ignored.
Is it a problem? Look at what is in the list
| The URLs are… | What to do |
|---|---|
| The http:// or www versions of your pages, redirecting to the one address you chose | Nothing. That is the redirect doing its job. |
| Old addresses after a redesign or a move, each redirecting to its new page | Nothing, as long as each lands on its own replacement. |
| Addresses your menu, your articles or your sitemap still use | Change the links and the sitemap to the final address. Google asks that both name the canonical. |
| A page you want in search, redirecting somewhere you did not intend | Find the rule that sends it there: a plugin, a server rule, a trailing slash added or removed. |
Check one address
- In URL Inspection, the indexed information is about the address you typed, redirects ignored. To see the page it redirects to, use the Inspect button in the report’s indexing section.
- The live test follows the redirect and tests the final address, without saying it did. A green live test is the target’s.
- From a terminal, curl -sIL and the address prints every hop and its status code.
What the Trakis audit finds
The cases worth fixing are the ones where your own site points at the redirecting address:
- Internal links written to another address of the site, such as http or the other host, which go through a redirect each time (LINK-006).
- A sitemap that lists addresses that redirect, instead of where they land (CRAWL-010).
- The site on two addresses, with and without www: once one redirects to the other, the redirecting copies land here, which is expected (CRAWL-008).
- http serving the site instead of redirecting to https; once it redirects, the http addresses move here (CRAWL-009).
A redirect that takes several hops is a different status when it fails: Redirect error.
How to set redirects that work
- For a page that moved for good, a permanent redirect on the server (301 or 308), as Google’s redirects guide recommends.
- Straight to the final address, in one hop.
- Links and the sitemap to the final address too: Google’s canonical guide asks for both to name the canonical.
Common questions
Will the count go down? It does not need to. The list is not a backlog: each line is an old address doing what it should, as long as it lands on its own replacement.
Should I remove the redirects to empty the list? No. An old address that people or other sites still link to should keep sending them to its page.
Is it bad for SEO? Not by itself. Google judges the target and indexes it if it thinks it should. The cost is in your own links and sitemap pointing at addresses that redirect.
Check the whole site
The Trakis audit follows every internal link and reads the sitemap, and reports the links and entries that point at addresses that redirect, each problem once with the pages it covers. Create a free account and add your site, or see every Search Console status, explained.
Last changed 28 October 2026.