Expertise

How to Check Whether Google Indexed the Final URL in a Redirect Chain

This guide shows how to check whether Google indexed a redirect chain’s final URL, distinguish index status from live fetches, and choose a next check.

How to Check Whether Google Indexed the Final URL in a Redirect Chain
Contents

To check whether Google indexed the final URL after a redirect chain, first identify the chain’s intended destination, then inspect that exact URL in an owned Google Search Console property. The indexed URL status tells you what Google has in its index; a live test checks the page as it can be fetched now, which is a different result.

By Ethan Cole

Summary

  • Record the starting URL and every redirect destination so you know which exact URL is supposed to be the final destination.
  • In a Search Console property you own, use URL Inspection on that destination and read its indexed URL status.
  • If the final URL is not indexed, use its Page indexing report reason to guide the next check. Don’t assume a redirect error’s cause without investigating the URL.

Map every redirect hop to identify the intended final URL

To identify the final URL, start with the URL that redirects and record each destination in order until you reach the address intended to serve the page. That sequence gives you a specific URL to inspect, rather than leaving you to guess whether Google indexed the source, an intermediate address, or the destination.

Google describes a redirect as moving an existing URL to a different location. Its guidance also distinguishes permanent redirects, which indicate the target for search results, from temporary redirects, which indicate the source. These are signals, not a guarantee about which URL Google will select in a particular chain. See Redirects and Google Search .

1
  1. Write down the starting URL. Keep the full address, including its protocol, host, path, and any query string. This is the URL a visitor, link, or other reference points to.

  2. Trace each destination in order. For each URL, record where it sends you next. If you manage the site, compare the sequence with the redirect rules in the relevant hosting or server configuration. A community reply recommends HTTPStatus.io for identifying redirect chains, but the supplied material doesn’t document that tool’s output or method; treat its result as a starting point, not a substitute for confirming the intended destination.

  3. Mark the intended final URL. Stop when you reach the address meant to serve the page, and write it separately from the source and intermediate URLs. If the chain does not lead to the destination you intended, resolve that uncertainty before using Search Console to assess the final URL.

Keep the sequence in a simple record, such as starting URL → next URL → intended final URL. For a longer chain, include every intermediate address rather than recording only the first and last. That makes it easier to match a status or reported issue to the URL it actually describes.

RelatedHow to Check Google Indexing When Results Don’t Match URL Inspection→

Inspect the exact final URL in Google Search Console

To find out whether the final URL is indexed, open URL Inspection in a Search Console property you own, enter the fully qualified final address, and read the indexed URL status for that address. Inspecting only the redirect source won’t answer whether the destination itself is indexed.

Google Search Console URL Inspection provides information about Google’s indexed version of a specific page. URL Inspection is accessed within a property and is available only for properties you own.

1
  1. Copy the intended final URL from your chain record. Use the exact address you marked as the destination, including the same protocol, host, path, and query string, if present.

  2. Enter that address in URL Inspection in a Search Console property you own. Confirm that the result is for the final URL you entered—not just the starting URL or an intermediate hop.

  3. Read the indexed URL status. If it says the page is indexed, Google reports that URL as indexed. If it reports a different state, note the status and use the page’s report details to decide what to check next.

The indexed URL report describes the most recently indexed version, not necessarily what the page serves now. Keep that distinction in mind when the page or its redirect behavior has changed; the live test is the separate check for the current fetch.

If you don’t own a Search Console property covering the site, you can’t use URL Inspection for this check. A search result or a site: query may be an indicator, but should not be treated as definitive proof of indexed URL status.

RelatedHow to Check a Referring Page’s Index Status and Backlink Access→

Use the live test without mistaking it for index evidence

Use the live test in an owned Search Console property when you already know the intended final URL and want to check its current fetch and indexability issues. Keep the live-test result separate from the indexed URL status: one checks the live page, while the other reports on Google’s indexed version.

1
  1. Start from the known final URL. Copy the destination you recorded in the redirect chain. Don’t use a live-test result to determine which destination you intended.

  2. Run the live test for that URL in the owned property. Review the issues it reports about the current fetch and indexability. Use those results to assess the live page, not to infer that Google has already added it to the index.

  3. Compare it with the indexed URL status. Keep the two results side by side in your notes. If they differ, you’re looking at different information: one concerns the live version; the other concerns the most recently indexed version.

ℹ️
Note
The live test fetches and examines a URL in real time and follows redirects. Use it only when you already know the intended destination. A live-test result is diagnostic, not proof that the URL is indexed.

If the live test reports an issue, use that information to investigate the current page. If the indexed URL status is the question, return to that status rather than treating a successful live fetch as confirmation of index inclusion.

RelatedHow to Audit Internal Links for Google Indexing→

Compare Google’s indexed URL with the redirect chain

Compare the URL whose indexed status you inspected with the source, intermediate addresses, and intended destination in your chain record. This helps you tell whether the status you have belongs to the final URL or to another address in the sequence.

Google says it tracks both a redirect source and its target. One URL becomes canonical and the other an alternate name; which one Google selects depends on signals that include whether the redirect is temporary or permanent. A permanent redirect indicates the target for search results, while a temporary redirect indicates the source, according to Google’s redirect guidance .

URL in your recordWhat to check
Starting URLIs it the address that sends visitors elsewhere, rather than the page you intend to serve?
Intermediate URLDoes it redirect again, or is it the intended destination? Record its position in the chain.
Final URLDoes the indexed URL status you inspected belong to this exact address?

The table helps organize the check; it doesn’t predict which URL Google will choose in a particular multi-hop chain. Google’s guidance says URL selection depends on signals such as whether a redirect is temporary or permanent, so it does not guarantee which URL will be selected for every chain.

If you own the relevant Search Console property, inspect the specific URLs you need to compare. Don’t read the status of the starting URL as the status of the final URL. If Google reports one URL as indexed while the final URL is not, record that distinction and use the relevant URL’s own report to guide further checks.

Use the Page indexing report to explain a missing final URL

If the final URL isn’t shown as indexed, check its Page indexing report reason before deciding that the redirect caused the problem. Google’s report lists reasons for non-indexing, and a non-indexed state does not necessarily mean there’s an error to fix.

The Page indexing report explains reasons Google reports for pages that are not indexed or have problematic indexing. Its “Redirect error” reason means Google experienced a redirect error; the report excerpt doesn’t specify the cause of an individual URL’s error.

1
  1. Open the Page indexing report for the site property. If the final URL appears in the report, note its exact status or reason. The report’s example list is not necessarily complete, so don’t assume an unlisted URL has a particular status; write down the exact reason rather than replacing it with an assumption about what happened.

  2. Inspect the specific final URL. Use URL Inspection in a Search Console property you own to review that address and its reported state. The Page indexing report describes categories of issues; the URL-level inspection gives information about the specific page.

  3. Choose a follow-up that matches the report. If the report says “Redirect error,” review the recorded chain and the redirect rules for the affected URL. If the reason indicates a non-indexed state that isn’t necessarily an error, use the reason’s description to decide whether it needs action. Don’t infer a cause the report doesn’t identify.

If the final URL is missing from the report, don’t treat that alone as proof of a particular indexing problem. Use URL Inspection for the individual address, and check that the page can be found through internal links or a sitemap when you’re responsible for the site. Google lists sitemaps and other discovery methods for informing it about pages.

Choose the next check with a hypothetical multi-hop example

For a hypothetical chain, use the final address as the URL to inspect, then let its reported status or reason determine what you check next. The example below assumes that the last address is the intended destination; it is not an observed test or evidence about a real site.

Assumed chain:

https://example.com/old → https://www.example.com/moved → https://www.example.com/article

1
  1. Confirm the assumed destination. In this example, the assumed final URL is https://www.example.com/article. If that is the address meant to serve the page, record it as the destination and keep the two preceding URLs as source and intermediate addresses.

  2. Inspect the final URL. Enter https://www.example.com/article in URL Inspection within a Search Console property you own. Read the indexed URL status for that exact address; don’t use a result for https://example.com/old as a substitute.

  3. Use the reported reason to select the next check. If the final URL is reported as indexed, the status answers the question for that URL. If it isn’t, review the specific reason in the Page indexing report and inspect the final URL for more detail. If the report says “Redirect error,” review the chain and its configured redirects rather than assuming a cause from the label alone.

  4. If you change a redirect, check the chain again. Confirm that it now leads to the intended final address, then inspect that exact address in Search Console again. If you’re changing the URL shown in search results, Google recommends a permanent server-side redirect when possible. A request for indexing, if you choose to make one, does not guarantee inclusion.

The result you’re trying to establish is narrow: whether Google reports the intended final URL as indexed. Keep the chain record, the indexed URL status, and any report reason separate. That gives you a clear next check without confusing a redirect’s source with its destination.

Content update: November 16, 2026.

Sources