Direct answer

“Page with redirect” means the inspected source URL sends Google somewhere else and normally will not be indexed as its own page. Inspect the final destination separately because the target may or may not be indexed.

What to remember
  • Judge the source redirect and the final destination as two different URLs.
  • A deliberate redirect is often expected; a wrong target, unnecessary chain, or stale internal link needs repair.
  • Point canonicals, sitemaps, and internal links directly at the preferred final URL.

01

Definition

Aerial view of a highway interchange crossing an urban area
A redirect changes the route from a requested source URL to a different destination. Credit: Photo by Horizon flights on Unsplash

“Page with redirect” is normally a description, not a failure. Google requested one URL, received a redirect response, and followed or evaluated the destination instead. Search Console therefore reports the source URL as noncanonical and does not expect to index that source as a separate page. The redirect target has its own crawl, indexing, canonical, and quality state. Page indexing report[1]

For example, requesting an obsolete product URL might return 301 Moved Permanently with a Location header pointing to its replacement. The old URL belongs in the redirect report. The replacement belongs in URL Inspection and may be indexed, excluded, canonicalized elsewhere, or not yet processed.

The important distinction is:

  • Source URL: the address that returns the redirect.
  • Destination URL: the next address named by the redirect.
  • Final URL: the last address after every hop.

Do not read the source status as proof that the final URL is indexed.

02

Mechanism

Google’s crawlers generally follow redirects and process the content received at the final target rather than content attached to the redirecting response. A 301 or 308 is a strong signal that the destination should be processed as the replacement. A 302, 303, or 307 is a weaker, temporary signal. Google recommends choosing the redirect that truthfully describes whether the move is permanent or temporary. How HTTP status codes affect Google's crawlers[2]

Requested URLStatusLocationFinal URL
https://example.com/old-guide301/new-guidehttps://example.com/new-guide
http://example.com/new-guide301https://example.com/new-guidehttps://example.com/new-guide
https://www.example.com/new-guide301https://example.com/new-guidehttps://example.com/new-guide

This trace is functional, but it reveals three different source URLs converging on one final page. Each source can appear as “Page with redirect.” That is expected if the redirects are intentional.

Permanent redirects tell Google that the new target should normally be shown in search. Temporary redirects tell Google that the source may remain the preferred search URL. Server-side redirects are the clearest method when the platform permits them. Redirects and Google Search[3]

URL Inspection does not make the source and destination interchangeable. Inspect the final destination directly. Review its page fetch, indexing permission, user-declared canonical, and Google-selected canonical. The live test is useful for confirming current access, but it does not reproduce every indexed-data decision. URL Inspection Tool[4]

03

Examples

Expected migration redirect

An article moved from /blog/site-audit to /articles/site-audit. The old URL returns one permanent redirect to the new URL. All navigation and sitemap entries now use the new address. “Page with redirect” for the old URL is correct. Continue by inspecting the new article and monitoring the migration.

Wrong destination

A deleted product redirects to the store homepage even though a direct successor exists. The response works, but it does not satisfy the original intent. Map the old product to the real successor or return a genuine not-found response if no replacement exists.

Canonical contradiction

A page returns 200, declares itself canonical, but a routing rule redirects it for some devices or hostnames. Test the exact protocol, hostname, path, query, and user-facing route. Then align the redirect with the canonical decision.

Stale site-controlled links

The redirect is correct, but menus, body links, and the sitemap still point to the source. Browsers and crawlers must take an unnecessary hop. Update those controlled references to the final URL. Keep the redirect for external links and old bookmarks.

04

Boundaries

The status becomes a problem when the redirect:

  • points to the wrong or irrelevant destination;
  • enters a loop or an excessive chain;
  • produces an empty or malformed Location value;
  • changes unpredictably by request;
  • ends at a blocked, missing, or failing page;
  • contradicts canonicals, sitemap entries, or internal links;
  • exists accidentally on a page intended to return its own content.

Do not remove a valid redirect merely to make the report row disappear. Search Console includes many intentionally excluded URLs. The goal is a coherent URL system, not an all-green inventory.

Use the Redirect Error playbook when Google cannot complete the path. Use the migration checklist when many URLs are moving together. Return a true 404 or 410 when content is gone without a replacement instead of sending every missing URL to the homepage.

Completion checklist

  • The source returns the intended permanent or temporary status.
  • The Location value is absolute or safely resolvable.
  • The path reaches one relevant final URL without a loop.
  • The final URL returns usable content.
  • URL Inspection has been run on the destination itself.
  • Internal links and sitemap entries point directly to the final URL.
  • The final page’s canonical agrees with the intended destination.
  • The redirect remains available for old external links where appropriate.

Once those conditions hold, “Page with redirect” can remain an expected report status. The destination’s indexing outcome belongs to the broader indexing diagnostic flow and the Page Indexing report.

References

Sources behind this record

  1. Page indexing report — Google (accessed July 25, 2026)
  2. How HTTP status codes affect Google's crawlers — Google (accessed July 25, 2026)
  3. Redirects and Google Search — Google (accessed July 25, 2026)
  4. URL Inspection Tool — Google (accessed July 25, 2026)

Corrections

Correction history

No corrections recorded.

To report an error, use the public corrections path.

Claim limit

A technically correct redirect is a canonicalization signal, not a guarantee that Google will index or rank its destination.