handsofflinks / check if backlinks are indexed
Verification ladder, first-party measurement
How to check if backlinks are indexed
A backlink that loads in your browser is not yet a backlink Google has. Checking takes a ladder of tests, from a quick site search up to reading the served HTML of the linking page, and each rung tells you something the one below can't. The weakest rung is a search operator. The strongest is Google's own Links report, and for pages you don't own, the raw response the server sends.
Rung one, a site search for the linking URL
Google documents the site operator as a way to find search results from a particular domain, URL, or URL prefix. So a search for the exact linking URL that returns the page is a sign Google has indexed it. A search that returns nothing proves less than people think. Google says search operators are bound by indexing and retrieval limits and points to the URL Inspection tool as more reliable for debugging. The inurl operator shows up in a lot of guides, but Google's search operators documentation doesn't list it, so treat it as folk knowledge rather than a documented check.
Rung two, URL Inspection for a page you own
If you own the linking page, URL Inspection provides information about Google's indexed version of a specific page and lets you test whether a URL might be indexable. Read the result carefully. It describes the most recently indexed version, not what's live right now, and it shows the last time the page was crawled by Google along with the URL Google picked as canonical. Run a live test when you want the current state, because that mode fetches and examines the URL in real time. Two limits matter for backlink audits. The URL must be in the currently opened property, so you can't inspect someone else's page that links to you. And there's a daily limit of inspection requests for each property, with a separate cap on live tests. Even a clean result isn't a guarantee the page will appear in Search results.
Rung three, the Links report
The Links report is the only rung that answers the question from Google's side for pages you don't control. It shows which sites contain the most backlinks to your site and which of your pages get the most links from elsewhere. Finding the linking host there means Google crawled a page on it and associated the link with you. Not finding it means less. Google says the report isn't a comprehensive list of every link on your site, its tables are capped in length so large sites see a truncated view, and it includes links found over time that may have since been removed, or a page may no longer exist.
Free tool
Classify the status of one backlink
Open the page that carries your link with view-source (not the rendered DOM), paste that HTML below, and type the URL you expect it to link to. The tool walks the same ladder the ledger uses and returns one status with the reason. Everything runs in your browser; nothing is sent anywhere.
Build the check links
Enter the page that links to you and your own domain. The three links open the places that answer whether Google has that page and that link. Nothing is fetched here.
Classify one backlink from its served HTML
The status taxonomy this ledger uses
| Status | Rows | Share | What it means | Tool can return it |
|---|---|---|---|---|
| LIVE | 232 | 56.2% | Page answers 200, the anchor to the target is in the served HTML, and no noindex is set; eligible to be crawled. | yes |
| LIVE-NO-CRAWL-PATH | 99 | 24.0% | The link is live but nothing indexed links to the page and the host publishes no sitemap for it, so crawlers have no route in. | no |
| INERT-SANDBOX-HOST | 28 | 6.8% | The page serves but sits on a host search engines do not crawl (permaweb gateways), so the link never enters the graph. | no |
| DEAD-NOINDEX | 14 | 3.4% | A robots meta tag or X-Robots-Tag header on the page says noindex; the page is dropped and the link on it counts for nothing. | yes |
| NO-LINK | 13 | 3.1% | The page is live but the served HTML carries no anchor whose href resolves to the target. | yes |
| DUPLICATE | 9 | 2.2% | A second build of a source and target pair the ledger already holds; counted so the totals stay honest. | no |
| DEAD-REP-GATED | 4 | 1.0% | The host hides or strips the link until the account clears a reputation threshold it never reached. | no |
| FAILED | 4 | 1.0% | The publish step never completed, so no page exists to check. | no |
| DEAD-404 | 3 | 0.7% | The page answers 4xx or 5xx, so there is nothing for a crawler to index. | yes |
| LIVE-NOT-SERVER-RENDERED | 3 | 0.7% | The target appears only inside script or JSON on the page; the anchor is created client-side, which raw HTML crawls do not see. | yes |
| DEAD-ROBOTS-BLOCKED | 2 | 0.5% | robots.txt on the host disallows the page path, so the link is never fetched. | no |
| PENDING-VERIFY | 2 | 0.5% | Built inside the window but not yet re-fetched for verification when the ledger was cut. | no |
| Total | 413 | 100.0% | All ledger rows, 2026-06-25 to 2026-07-31. |
Exact integers from the public ledger: 413 attempts, 2026-06-25 to 2026-07-31. The classifier above can return the five statuses marked yes; the other seven need a crawl, a robots.txt read or a second build to tell apart.
Rung four, the served HTML of a page you don't own
For a page you don't own, the strongest evidence you can gather yourself is what the server actually sends. Fetch the linking page with a plain HTTP client, not a browser, and paste the served HTML, the status code and any X-Robots-Tag header into the classifier above. Here's what the checks look for and why.
- Status. With a success response Google considers the content for processing, including indexing. Google doesn't index URLs that return a 4xx status code, and already indexed URLs that start returning one are removed. Content from a 5xx response is ignored, and indexed URLs on it are kept for a while and then dropped. A page that returns a success code but reads like an error or is empty can be reported in Search Console as a soft 404.
- The anchor itself. Google can only crawl your link if it's an a element with an href. A span with a click handler or a bare URL in text is not a link to Google. Links inserted by JavaScript are crawlable as long as they use that same HTML markup, but only after rendering, which is why the tool asks for server-sent HTML rather than the DOM you see in devtools.
- Rel tokens. Google tells publishers to mark links that are advertisements or paid placements with rel sponsored, recommends marking user-generated content links such as comments and forum posts with rel ugc, and describes nofollow for cases where the publisher would rather Google not associate the site with, or crawl the linked page from, theirs. Read the tokens on your anchor at the dofollow nofollow checker.
- Robots directives. A noindex directive tells Google not to show the page in search results, and nofollow tells it not to follow the links on the page. Both can arrive in a meta tag or in the X-Robots-Tag HTTP response header, so paste the headers too.
- Robots.txt. A disallow rule doesn't keep the page out. Google says robots.txt is not a mechanism for keeping a web page out of Google, and a page that's disallowed in robots.txt can still be indexed if linked to from other sites. What disallow does is hide the directives, because when Google can't fetch the page any information about indexing or serving rules will not be found and will therefore be ignored. Google's advice for a page you want out is to block indexing with noindex or password-protect the page.
- Rendering. Google renders the page and runs any JavaScript it finds using a recent version of Chrome, but on app-shell sites the initial HTML does not contain the actual content and Google needs to execute JavaScript first. Rendering happens once Google's resources allow, in a queue separate from crawling. A link that exists only after rendering is weaker evidence than one in the raw HTML.
Why a live link is not yet a counted link
Every check above can pass and the link can still sit outside Google's index. Discovery is the missing rung. Google finds pages when it extracts a link from a known page to a new page or reads a submitted sitemap, and Googlebot crawls the web by accessing URLs found in previously crawled pages. A fresh profile page on a host where nothing links to new profiles has no path in. A sitemap helps, but it doesn't guarantee that all the items in your sitemap will be crawled and indexed, and Google says plainly that it doesn't guarantee that it will crawl, index, or serve your page. So the ledger behind this site records a crawl path as its own check, separate from the served-HTML checks, and a link with no path is labelled LIVE-NO-CRAWL-PATH rather than LIVE. That label is the largest bucket after LIVE in the audited ledger. Those rows passed every check a typical index checker runs and still had nothing pointing at them.
What the ledger statuses mean
Each row in the ledger carries one of the labels below. Per-status counts are recomputed from the audited ledger copy, and the homepage prints the three headline buckets, 232 live, 130 undiscoverable and 51 failed, where every count sits next to its denominator. The right-hand column names the rung on this page that would catch each case.
| Status | What the row records | Rung that catches it |
|---|---|---|
| LIVE | Served success status, anchor present in server-sent HTML with a real href, rel read off the served page, and a confirmed crawl path | All four |
| LIVE-NO-CRAWL-PATH | Passes every served-HTML check but no indexed page or sitemap reaches it | None of the markup checks, only rung one on the host and the sitemap probe |
| LIVE-NOT-SERVER-RENDERED | Anchor appears only after JavaScript runs, absent from the raw HTML | Rung four, anchor check |
| INERT-SANDBOX-HOST | Host publishes the asset on a domain that carries no signal to search | Rung one on the host |
| DEAD-NOINDEX | Robots meta or X-Robots-Tag carries noindex | Rung four, directives |
| DEAD-ROBOTS-BLOCKED | Path disallowed in robots.txt, so directives on the page can't be read | Robots.txt read by hand |
| DEAD-404 | Linking page returns a client error | Rung four, status |
| DEAD-REP-GATED | Host hides the link until the account earns reputation | Rung four, anchor check |
| NO-LINK | Domain appears in the page but not inside an a element with an href | Rung four, anchor check |
| DUPLICATE | Same target already recorded on the same host | Ledger only |
| FAILED | Publish call did not return a page | Rung four, status |
| PENDING-VERIFY | Published, not yet re-fetched | Not yet checked |
Sitemap lines on the six publishing hosts
One crawl-path signal you can read for any host is its robots.txt. Google says the file controls which files crawlers may access on your site and may carry Sitemap lines, where the sitemap URL must be a fully-qualified URL. Across a fixed probe sample of six of the hosts this pipeline has published to, docs.rs, pkg.go.dev, telegra.ph, mataroa.blog, njump.me and zenodo.org, robots.txt read as Googlebot carries a Sitemap line on 33.3 percent of the six hosts probed, recomputed from the probe on 2026-09-06. A host without one isn't undiscoverable, links still work as discovery, but the sitemap rung is missing for anything you publish there.
Questions people ask about indexed backlinks
- Does a backlink count if the page is live but not indexed?
- Google says pages are discovered when Google extracts a link from a known page to a new page. Until the linking page has been crawled, Google hasn't seen the link on it. The place that association shows up is the Links report, which lists which sites contain the most backlinks to your site.
- Can I run URL Inspection on a page that links to me?
- Not unless you own it. The URL must be in the currently opened property, so third-party pages are out. Use the site search and the served-HTML checks instead.
- Is a site search a reliable index check?
- No. Google says search operators are bound by indexing and retrieval limits, so a miss doesn't prove the page is absent.
- Does a robots.txt disallow mean the link is dead?
- Not on its own. A page that's disallowed in robots.txt can still be indexed if linked to from other sites. But Google can't read the page, so it won't see the anchor on it either.
- How long until Google indexes the backlink?
- Google publishes no timetable and this page won't invent one. Its own statement is that it doesn't guarantee that it will crawl, index, or serve your page. For what you can do about a link with no path in, read how to index backlinks.
Where these checks come from
Every statement about Google on this page links to the Search Central or Search Console Help page it was read from, on 2026-09-06. The one figure, the share of hosts with a Sitemap line, was recomputed in code from a first-party robots.txt probe of the six hosts and validated before the page was built. Nothing on the page was typed from memory. The status labels are the ones the ledger uses when it re-fetches each published link and reads the served HTML.
No ranking or traffic outcome is promised on any page.
Ledger figures are the operator's own history with this method across 16 of his own sites over 37 days and are not a forecast of any buyer's results.
What to do next
If the checks put your link in LIVE-NO-CRAWL-PATH, the question changes from whether Google has it to how Google could find it. How to index backlinks covers that, host by host. If the anchor is there but the rel tokens are the worry, the dofollow nofollow checker reads them off pasted markup.