check whether a backlink is indexed in Google

To check whether a backlink is indexed in Google, inspect the page that contains the link, not the destination receiving it. The central question is whether Google has indexed that linking page. A link being visible in a browser only proves that the page and link are currently accessible; it does not establish what Google has stored in its index.

The best method depends on ownership and scale. Search Console offers detailed indexed information for a URL in a property under the operator's control. External backlink pages usually fall outside that boundary. Public search checks can help with those URLs, but Google explicitly says search operators are constrained by indexing and retrieval limits. A careful audit therefore records the method, the URL variant, and whether the result is positive, negative, or inconclusive.

Define the object being checked

A backlink record contains at least two URLs:

Linking URL: the page where the hyperlink appears.
Target URL: the page to which the hyperlink points.

Indexation checks belong against the linking URL. Before interpreting any index signal, open that page and confirm that the intended target is still linked. This separates two different failures: a missing link and a page that is not represented in Google's index.

URL normalization also matters. Keep the full protocol, hostname, path, parameters when relevant, and trailing slash exactly as delivered. Google's documentation notes that www and non-www host forms are not equivalent queries. If a canonical URL is available through owned-property inspection, compare it with the submitted URL rather than treating every URL variant as a separate indexed document.

Technical comparison of six methods

Method	What it actually checks	Access boundary	Best use	Main limitation
1. Specific `site:` query	Search results associated with a domain, URL, or URL prefix	Public	Quick evidence for an external linking URL	Results are not exhaustive; absence is inconclusive
2. URL Inspection indexed report	Google's indexed version and page-indexing details	URL must be in the current Search Console property	Detailed status for owned pages	Not available for arbitrary third-party backlink pages
3. URL Inspection live test	Whether the current page appears accessible and potentially indexable	URL must be in the property	Checking a fix or current fetch conditions	It does not say that the live page is indexed
4. URL Inspection API	Programmatic inspection of the indexed version	Authorized Search Console property	Repeatable checks for owned URL lists	Indexed version only, with per-site and per-project quotas
5. Google Indexing API	Update or removal notifications for eligible page types	Authorized eligible content	`JobPosting` or `BroadcastEvent` pages embedded in `VideoObject`	It is not an ordinary-page index checker
6. List-based index service	A list-oriented status workflow	Depends on the service	Reviewing many external linking URLs consistently	Results still need method-aware interpretation

1. Specific `site:` query

Run a query using the full linking URL or the narrowest useful URL prefix:

site:https://support.google.com/webmasters/answer/9012289

Google says a specific query may help determine whether a URL is indexed and served. It also says an indexed URL can appear for a related site: query, but appearance is not assured. The operator does not necessarily return every indexed URL under a prefix, so it cannot provide a complete indexed-page count.

Treat a matching result as useful public evidence. Treat no result as "not confirmed by this method," not as final proof of exclusion. Recheck the exact hostname, protocol, path, and slash form before escalating the finding.

2. URL Inspection indexed report

For a page inside a verified Search Console property, URL Inspection provides information about Google's indexed version. The report can show an overall index status, crawl information, and Google's selected canonical. This makes it the most diagnostic option in this comparison when the property is available.

The ownership boundary is decisive for backlink auditing. Search Console requires the complete URL to sit inside the currently opened property. A backlink on an unrelated publisher's site cannot simply be entered into the auditor's own property. That is why public or bulk methods remain relevant for external placements.

Also distinguish "URL is on Google" from visible placement for every search. Google describes that status as eligibility to appear, not a promise that the URL will appear in a particular result.

3. URL Inspection live test

The live test examines the current page rather than the stored indexed version. It can help after changes to access controls, indexing directives, or page delivery. Its result answers whether the Google inspection crawler can access the page for indexing and whether detectable conditions permit indexing.

It does not answer whether the page is already indexed. Google notes that the live test does not cover every indexing issue and cannot predict canonical selection. Keep live and indexed results in separate columns; combining them turns an indexation audit into an indexability audit.

4. URL Inspection API

The URL Inspection API sends a POST request to:

https://searchconsole.googleapis.com/v1/urlInspection/index:inspect

The request supplies inspectionUrl, siteUrl, and an optional language code. The inspected URL must be under the Search Console property named by siteUrl, and authorization requires a supported Search Console OAuth scope.

The API currently returns only information about the version in Google's index. It cannot run the live test. Google publishes URL Inspection quotas of 2,000 queries per day and 600 per minute per site, alongside per-project limits of 10,000,000 per day and 15,000 per minute. A large-site workflow should prioritize URLs and handle quota responses rather than assuming that one unrestricted full-catalog pass is available.

5. Google Indexing API

The Google Indexing API is often confused with URL Inspection, but it serves a different purpose. Google limits it to pages containing JobPosting or livestreaming BroadcastEvent data embedded in a VideoObject. Its update and delete calls notify Google about eligible URLs.

Notification metadata reports whether Google received a notification. Google explicitly says that this metadata does not report when a URL was indexed or removed. It must not be presented as an index-status endpoint for ordinary articles, product pages, backlink pages, or general site inventories.

6. List-based index service

External backlink inventories create a practical gap: they may contain many URLs, while Search Console inspection is property-bound. A list workflow can preserve one row per linking URL and one result per run. Use a check Google index in bulk workflow to process the linking URLs, then retain uncertain rows for targeted review.

The output should remain evidence, not a substitute for diagnosis. Keep the original linking URL, normalized URL, result, check method, and observation date. If a row conflicts with a public result, inspect URL variants and avoid rewriting a negative observation as certainty.

A defensible backlink indexation workflow

Export linking URLs. Exclude target URLs from the inspection column.
Deduplicate exact variants. Preserve a mapping back to every backlink record.
Confirm the link exists. Verify the linking page and intended destination before checking index status.
Separate owned and external pages. Use Search Console indexed inspection only where the URL belongs to an accessible property.
Choose a method by volume. A specific site: query suits a small public spot check; API or list workflows suit repeatable sets within their access boundaries.
Label uncertainty. A missing site: result is not exhaustive evidence. A live-test pass is not an indexed verdict.
Review canonical information where available. The inspected URL and Google-selected canonical may differ.
Document the decision. Record whether the next action is technical diagnosis, URL correction, recheck, or no change.

For a focused explanation of linking-page checks, use the backlink indexation guide.

Reading conflicting results

Conflicts often reflect different questions. A live test can report that a current page is accessible while the indexed report still reflects an older version. A specific site: query can omit a URL because operator results are non-exhaustive. The URL Inspection API can report indexed-version data but cannot reproduce the live test.

Use this order:

Identify whether each result describes public search output, the indexed version, the live page, or an API notification.
Confirm that every method used the same URL variant.
Give owned-property indexed data its proper diagnostic weight without confusing eligibility with appearance.
Mark unresolved external-page disagreements as inconclusive and preserve the evidence.

FAQ

Can Search Console inspect any backlink page?

No. The URL must belong to the currently opened Search Console property. A third-party publisher URL normally requires a public or external list-checking method.

Does no `site:` result mean the backlink page is not indexed?

No. Google says site: results are not exhaustive and that an indexed URL is not assured to appear for a related query. A miss is an inconclusive signal.

Is the live URL test an index check?

No. It tests the current page for access and potential indexability. The indexed report describes Google's stored version; the two results answer different questions.

Can the URL Inspection API test the live page?

No. Google's API documentation states that only the indexed version is currently available through the endpoint.

Can the Google Indexing API check ordinary backlink pages?

No. It is restricted to eligible JobPosting and livestreaming BroadcastEvent pages, and notification status does not report index status.