handsofflinks / google not indexing backlinks
Google hasn't indexed my backlink. How long to wait, when to act
Most links that never show up in Google are not being rejected. They are waiting on a crawl that has not happened yet, on a page you do not own and cannot submit. That is a waiting problem with a measurable horizon, and the horizon is set by the host, not by you.
This page answers the two questions in order: how long the wait normally runs, and the first day on which continuing to wait is the wrong decision. The numbers come from a pipeline that measured 413 links across 22 host families between 2026-06-25 and 2026-07-31, watching each link from the day it went live until Google either listed the host page or did not.
Why waiting is usually the right advice, and why it usually stops working
The reflex answer to this question online is to wait, and at some point that answer was earned. Google does eventually get to many pages. It is also the answer most likely to be wrong in a specific and predictable way, because wait is not a period of time. It is an instruction to keep doing the same thing, on the assumption that the thing in motion is your link.
Nothing is in motion on your link. Google finds a new URL in one of two ways: it follows a link from a page it has already crawled, or it reads a sitemap on the same host. Your placement is a link on someone else's page, so neither route can start from you. The page carrying your anchor has to be crawled first, and that page's crawl schedule belongs to the host's crawl budget, the host's internal linking, and the host's sitemap.
That is the whole shape of this problem. You are waiting on a third party's page to be revisited and for one URL to be discovered inside that page's HTML.
Three gates, and which of them you can touch
Every placed link passes three gates in order. Discovery precedes crawl precedes indexing. A link cannot skip a gate and cannot pass the later ones by working harder on a gate it has already cleared. Diagnostics go wrong when people check the last gate, see nothing, and start pushing on submission channels that never had anything to do with the failure.
| Gate | What has to happen | Your lever |
|---|---|---|
| Discovery | Google has to learn the host page exists. It follows a link from a page already in the index, or reads a sitemap on the same host. | Weak. Pick hosts whose pages already get crawled. |
| Crawl | Googlebot has to fetch the host page and receive the anchor in the served HTML. A noindex, a login wall, or a robots.txt disallow all stop it here. | Weak. Verify the served HTML before you pay. |
| Indexing | Google has to keep the fetched page in the index. Thin or duplicative pages get fetched and dropped. | None. |
Order is fixed. Discovery precedes crawl precedes indexing, and no later gate can be forced from outside the one before it.
The column on the right is short because the page that matters is not yours. Owned-page levers, sitemaps above all, belong to publishers working on their own domains, and they are the subject of a different page. Here the only real control is exercised before the link is placed.
The measured timeline, day by day
The pipeline logged every placement from the day it went live. Read this as what a normal wait looks like, not as a schedule. It is drawn from one pipeline's placements and predicts nothing about any individual link, but it does show where most of the elapsed time actually goes.
Medians, not averages. Roughly a third of measured links cleared discovery inside 24 hours and a small group never cleared it at all.
What to check before you change anything
Each check below answers a yes or no question. Run them in order. A no at any step explains the wait and none of the remaining steps make it shorter.
1. Is the anchor in the served HTML
View source on the host page, logged out, and search for your URL. Not the inspector, the source. A link added by a client-side widget, or one rendered only after script runs, is absent from the served HTML, and Google discovers links from the fetched page on the first pass.
VerdictIf your URL is not in the source, the page was never going to reveal it quickly. The fix is on the host's side, and asking the host is the only route.
2. Does the host page have a crawl path
Ask two things. Does another crawlable page on that host link to it, and does the host publish a sitemap that lists it. Both answers are visible in the served HTML and in the host's robots.txt.
VerdictTwo noes mean the host page is orphaned. There is no date to wait for, because nothing has told Google the URL exists.
3. Is the host page itself indexed
Search the exact URL, or a distinctive phrase from the top of the host page, in quotes. If the host page is absent from Google, your link cannot be present in any meaningful sense, and the question was never about your anchor.
VerdictHost page absent means the problem is one level up. Diagnose the page, not the link.
4. Was the host page crawled at all
You can see this directly for a page you own, and not at all for a page you do not. For a third-party host, the honest proxy is whether the page is reachable by a crawl path and serves real content to a logged-out fetch. If both are true and a month has passed, a blocking directive or an orphaned page is the likeliest explanation, and both are covered by the checks above.
VerdictNo crawl on record is not a penalty. It is a signal that nothing has pointed Google at the page.
5. Is the link marked so it is not followed
Read the anchor's rel attribute in the source. A rel="nofollow", rel="sponsored", or rel="ugc" is a documented signal rather than a block, so the link can be crawled and simply not counted the way you expect. This is worth catching on day one, because it does not change with time.
VerdictA non-followed link will not start passing value later. Waiting is the wrong response to this finding.
Checks 4 and 5 separate the two findings that look identical from the outside: the page was never read, or the page was read and the link did not count. One is a discovery problem and the wait is real. The other is finished and no amount of waiting will change it.
What you can actually control
Short list, and worth being blunt about it. You cannot submit a third-party URL to Google. There is no channel for it, and any service describing one is describing something that does not exist. You cannot ask a host to fetch faster. You have no lever on the host's internal linking, its crawl budget, or its sitemap.
What you do control is the same list twice: host selection before the link goes live, and the decision to stop paying for placements that show the same failure twice. A host whose pages get crawled is worth more than a host with a higher authority score and no crawl path, because the second one never starts. The pipeline's evidence for that is in how to get backlinks crawled faster, which covers what makes a host page crawlable in the first place.
One genuine owned-channel distinction, since it comes up every time. IndexNow pushes URLs to participating engines directly rather than waiting for a crawl. It is a real protocol and it works, and it covers Bing and other participants. Google is not a participant, so IndexNow has no effect on a Google indexing problem. Anyone offering it to you as a Google fix is describing Bing coverage.
When to stop waiting
Four findings end the waiting period and each calls for a different action. The pattern in all four is the same: a person keeps checking a status that will not change, when what they need is a decision.
| Finding | What it means | Action |
|---|---|---|
| URL absent from source | The link is rendered, not served. Google may never see it on the first pass. | Ask the host to place it in the HTML, or stop counting on it. |
| Host page not indexed | The page is orphaned, blocked, or too thin to keep. Your link is downstream of all three. | Diagnose the page. Nothing at the link level applies. |
| Day 30, no crawl | A month is well past the measured crawl window. Something is blocking the fetch. | Check robots.txt, noindex, and the catch-all header before anything else. |
| Same host, twice | The failure repeated on a host you have already diagnosed once. This is a host property, not bad luck. | Stop buying that host. This is the most expensive lesson to learn slowly. |
The one case that does not appear here is a page that was never fetched and shows no blocking cause. That is the ordinary late case, and it argues for waiting, not acting. The distinction is whether a cause is visible. No visible cause, keep waiting and check weekly. A visible cause, act on the cause.
What not to doMass pinging, resubmission blasts, and paid indexing services that promise a date are the three responses sold for this problem, and none of them creates a crawl path. Pinging endpoints and submitting the same URL repeatedly do nothing at all against a third-party page, because the URL is not yours to submit. Adding links from pages that are themselves uncrawled builds a second layer of unvisited pages rather than fixing the first. The paid side of this market is covered in backlink indexing services.
Questions
How long does Google take to index a backlink?
There is no fixed period, and any page that prints one is guessing. In the pipeline's measurements across 413 links, the median first sighting of a placed link was day 4 and the median crawl arrived 11 days after that. A meaningful share of links cleared discovery inside 24 hours, and a small group never cleared it inside the measurement window. What the numbers support is a range, not a date, and the range is set by the host page.
Is my backlink not indexed, or is the host page not indexed?
Check the host page first. Search its exact URL, or a distinctive quoted phrase from its text. If the host page is absent from Google, your link cannot be present in any useful sense, and the finding is about the page rather than the anchor. How to check if backlinks are indexed walks the full ladder, including the checks that only work on pages you own.
Can I submit a backlink to Google myself?
No. Google offers no channel for submitting a URL you do not control, and URL Inspection inside Search Console is scoped to properties you have verified. A host page is outside that scope by default, so anything claiming to submit it on your behalf is describing a channel that does not exist.
Does IndexNow help with Google indexing?
No. IndexNow is a real protocol and it shortens discovery on participating engines, but Google is not a participant. It is useful for Bing and cannot move a Google crawl. If your question is about Google specifically, IndexNow is not part of the answer.
Why did my other backlinks index and this one not?
Usually the host, not the link. Links placed on hosts whose pages get crawled regularly tend to clear all three gates quickly, while a link on an orphaned or blocked page on the same day may never clear the first one. The measured pattern is at the host level, which is why backlinks not getting indexed ranks the causes by host behaviour rather than by link attributes.
Should I just wait longer?
Wait if no cause is visible and the host page is reachable by a crawl path. Act if you have found one: absent from source, host page not indexed, or day 30 with no crawl. Waiting is the right default in the absence of evidence and the wrong response to evidence you already have. Checking weekly and changing nothing is a correct action only while the checks keep coming back clean.
Where to go next
The three gates on this page are the staging order the whole site is built around. If you are choosing where to place links next, link velocity covers how fast a profile can grow before the pattern stops looking natural, and the dofollow and nofollow checker covers the rel attribute check in this page's fourth step at more length. If the finding was a blockage rather than a delay, backlinks not getting indexed works through the causes one at a time, and how to index backlinks is the full route map from placement to index.
Disclosures
This page was written by handsofflinks, the company that runs the backlink pipeline whose ledger this site publishes. The figures describe that pipeline's own placements across 413 measured links and 22 host families between 2026-06-25 and 2026-07-31, not a sample of the wider web, and they predict nothing about any particular link. No timetable on this page is a promise. Every statement about Google is drawn from Search Central or Search Console Help, and the pages those statements came from are linked in the article and listed in the structured data. Nothing here was typed from memory.
This page has no forms. Its only script is /site-analytics.js, which loads Google Analytics, and in the EEA, the UK and Switzerland that stays off until you accept. We have no financial relationship with any platform or service named above, and we do not sell crawl, indexing, or submission requests. No ranking or traffic outcome is promised on any page.