Page with redirect: the URL search will not keep

Read the status as a hop, not a missing page

‘Page with redirect’ means Google requested a URL and received a redirect. The URL stays out of the index. The target is the page that can rank and be cited. This is the expected row for http copies, old slugs, and host variants you meant to retire. It is not a redirect chain, which is several hops before the final page, and it is not a 404.

The SEO issue appears when a URL you still publish is the one that redirects: a service page, a guide, or a Traditional Chinese version. The GEO issue is the same hop. An answer engine cites the destination. A passage that exists only on the URL that 301s never reaches the answer, and a redirect to the homepage or a thin category page replaces a specific source with a page that is harder to quote.

• Treat a redirecting retired URL as expected.
• Keep this status separate from a chain of hops and from a 404.
• Check whether the URL that redirects is one you still want cited.

Sort the redirects you meant from the ones that hid a page

Open the sample URLs and write the final destination beside each one. A permanent redirect from an old path to the current guide is doing its job. Leave it. A redirect from the preferred URL to a parameter, a trailing-slash twin, or the wrong language version is the page you wanted, filed as gone.

On a Hong Kong site, the usual miss is language or host. The zh-HK URL 301s to English, or the apex host 301s to www while the sitemap and the internal links still name the apex. Both look like a tidy migration in the report. Only one address should be the one a person would send to a colleague. Compare the destination with the query. If the hop lands on a different intent — a district page sent to the citywide service, or a guide sent to the homepage — search and answer engines will keep the wrong document.

Make the kept URL the one that answers

When the redirect is correct, point internal links and the XML sitemap at the final 200 URL, and stop requesting indexing for the address that redirects. Put the bounded answer on the destination, with the organisation and the place next to the claim, so the passage an answer engine lifts is the page search will keep.

When the redirect is wrong, remove it and serve a 200 on the URL you want found. Give that URL a self-referencing canonical, one internal link from a page Google already crawls, and a first paragraph that matches the query. Keep a single permanent hop only for addresses you have truly retired. Then re-check URL inspection. The page-with-redirect row should remain on the old URLs and clear on the one you reclaimed.

• Leave true retirements as one hop to the current URL.
• Reclaim a URL that still answers its own query.
• Request indexing for the 200, not for the address that redirects.

What does Page with redirect mean in Search Console?

Google requested the URL and was sent to another address. The redirected URL is not indexed. The destination is the URL that can rank and be cited.

Is a page with redirect the same as a redirect chain?

No. This status is any URL that redirects, including a single healthy hop. A redirect chain is several hops before the final page. One is a coverage reason. The other is a route that is longer than it needs to be.