handsofflinks / discovered, currently not indexed
Discovered, currently not indexed. What it means for a backlink
Search Console is telling you it found the page carrying your link and then walked away. That one line, discovered but not indexed, is read as a failure of the link by almost everyone who sees it. It is not. The status belongs to the host page, and it records a decision Google already made about whether that page deserves storage.
This page works from a ledger of 413 placed links measured between 2026-06-25 and 2026-07-31. The measured order was always the same. Discovery came first, then a crawl, then indexing, and each stage could stop the sequence where it stood. A link whose host page landed on discovered but not indexed had already passed the first two stages and failed the third, which is a very different place to fail.
What the status actually records
Google runs a queue for URLs it knows about but has not yet crawled. A URL enters that queue when Google discovers it, usually by reading a link on a page it has already crawled, or from a sitemap. At that moment Search Console can show the URL as discovered, even though no request has been made for it yet. The literal description in Google's own documentation is that the URL was found but not yet crawled.
The full string you are reading is a later state. It means a crawl did happen, Google understood the page, and the page was then set aside rather than added to the index. It sits in a family of exclusion reasons that all describe a choice not to store a page, alongside duplicate without user-selected canonical, alternate page with proper canonical tag, and crawled but not indexed.
The distinction that matters for a backlink is this. A page never fetched cannot carry a link into the index, and a page fetched but declined also cannot. In the second case the failure happened after your link was read, which is why no amount of work on the link changes the outcome.
| Status in Search Console | What Google did | Was the anchor read |
|---|---|---|
| Discovered | Found the URL, queued it, has not fetched it | No |
| Discovered, currently not indexed | Fetched the host page and declined to store it | Yes, and discarded |
| Crawled, currently not indexed | Fetched and declined, same family, later wording | Yes, and discarded |
| Duplicate without user-selected canonical | Found the same content elsewhere and kept that copy | Yes, on the copy not kept |
| Indexed | Fetched, kept, and eligible to serve | Yes |
Read the wording of the status as a stage marker, not a verdict on quality. The names come from Google's URL inspection reporting, and the crawl and indexing overview documents linked in the disclosures below.
Why it cannot be fixed per link
Indexing is a property of the document, not of the links pointing at it. Google decides whether to keep a page by looking at that page and at the other pages on the same host, and your anchor is not part of that decision. The host page is one of thousands that Google may be evaluating on the same domain, and the comparison happens between those pages rather than between your link and anything else.
The practical consequence is blunt. If the host page is not in the index, the anchor it carries is not in the link graph, so nothing about your link is being evaluated at all. You are not watching a slow link. You are watching a page that failed a test you cannot enter.
DUPLICATION ON HOST
Profile, directory and forum placement pages are generated from a template. Thousands of near-identical pages compete for the same storage, and Google keeps a subset. The rest land on this status.
THIN CONTENT
A page with a name, an avatar and two lines of text gives a crawler almost nothing to keep. The page is fetched, understood as low value, and set aside without ceremony.
NO CRAWL DEMAND
Even a fetched page needs a reason to be refreshed. Pages nothing links to and no one searches for sit in the queue while more valuable pages on the same host are served first.
SITE LEVEL QUALITY
When a large share of a host sits on exclusion statuses, the pattern is about the host rather than any one URL. That is a signal about where you bought the placement, not about the anchor you asked for.
Each of those is a decision made about the host. None of them can be answered by editing a link you do not control, which is the whole reason this status produces so much wasted effort. The wider family of these exclusion reasons is tracked on backlinks not getting indexed.
How to read the status in your own report
The status is only available on a property you have verified, so in most cases you are reading it because you own the host, or because the host is your own profile page on a platform you joined. On a host you do not own there is no report to read, and you fall back on the checks that work from the outside.
- Confirm the status is attached to the host page rather than to your destination page. Your destination is the URL in the anchor, and it is a different property for inspection purposes.
- Check whether the status shows a last crawl date. If it does, Google fetched the page and the decision is already made.
- Fetch the page in a private window and look for near duplicates. A profile page whose content is a template plus a name is the classic candidate for this status.
- Compare the count of this status across the whole host with the count of indexed pages. A high ratio points at the host as the cause.
- Look at what else the host publishes. If the host has a few strong pages and thousands of generated ones, the generated ones lose the comparison and that is the answer.
Do not read this status as a penalty. Removal is a separate category with its own reporting. A page under this status was simply assessed and not kept, which is the ordinary outcome for a large share of any large site.
What a link buyer can actually do
You cannot fix a decision made about someone else's page. What you can do is change your own placement decisions, and the ledger supports exactly two actions that shift the odds.
Screen the host before the placement
The signal worth checking is whether the host page carries content that exists nowhere else. A page whose text is a template plus a name is a candidate for this status before you ever place a link on it. A page with an original paragraph, a real list or a genuine description is not. The same page type on two different hosts behaves differently, which is why the host matters more than the page type.
If you are placing links through an agency or a marketplace, the screening question is simply whether the host page would survive being read. The checks behind that question for a typical pipeline are set out on developer registry backlinks.
Replace rather than repair
A link on a host page that already carries this status is unlikely to change while you own nothing on that host. The honest move is to place the same anchor somewhere the page is unique and reachable, and to stop counting the old placement as live inventory. Chasing a fix means paying for effort against a decision that was never about you.
The checks that decide whether a placement was ever reachable are the ones in how to check if backlinks are indexed, and the route from a placement to a crawl sits in how to index backlinks.
The one legitimate lever that exists lives on a property you control. Requesting a recrawl through URL Inspection is documented as asking Google to recrawl a URL and is scoped to a verified property, so it resolves nothing for a host page you do not own. Where the page is yours, that request is the fastest honest action available and belongs to the crawl path question rather than the ranking question.
What the 413-link ledger showed
The pipeline behind this site measured 413 links between 2026-06-25 and 2026-07-31. Discovery consistently ran ahead of crawl, and crawl ran ahead of indexing, so a link could sit visible in one report and absent from another for weeks without anything being wrong. The status you are reading about describes the last stage rather than the first two.
Placements that reached the index
- A host page whose text is unique to that URL
- A host that already gets crawled on its own schedule
- A page with at least a few crawlable pages linking to it internally
- A page listed in the host's sitemap
- A URL that is stable and not built from a session token
Placements that stopped at this status
- A template page repeated thousands of times on one host
- A host where most URLs sit on the same exclusion status
- A page with no internal links pointing at it
- A page whose only distinct content is a name and a date
- A URL with no reason for anyone to search for it
None of the items in the right column is about the anchor text, the domain metric a marketplace displayed, or the price paid. Across the whole ledger, the channel and host page predicted the outcome and the link detail did not. The per channel breakdown sits on the channel comparison and the placements themselves are listed in the live links table.
What waiting does and does not change
Waiting is the right response when the host page is unique and useful, because the queue is served in priority order and a good page usually reaches the index eventually. The status is not permanent in the way a removal is, and ranking movements on the same host can pull a page back into consideration.
Waiting is pointless when the page is one of a large generated set. Nothing about the passage of time removes the duplicates that surround it, and the comparison that produced the status will produce it again on the next crawl. Recognising which of those two situations you are in is the whole decision.
Two links placed on the same day on two hosts often land weeks apart, and the gap tracks how often the crawler already visited each host rather than anything about the links. That pattern is why a timeline quoted by a vendor is worth nothing, and why the ledger's version of the question is covered in link velocity and the fetch mechanics in getting backlinks crawled faster.
Questions
Does this status mean my backlink was rejected?
No, it describes the host page rather than your link. Google fetched that page and chose not to keep a copy, so the anchor never entered the link graph.
Can I fix it for a link I do not own?
Not directly, because the decision belongs to a page and host you do not control. What you can do is check whether the host page is a near duplicate, thin or gated, and then decide whether keeping the placement is worth anything.
How long can a URL sit in this state?
No published limit and no countdown exists. A URL can wait indefinitely while higher value pages on the same host are served first, which is why a quoted timetable is never reliable.
Will resubmitting the host page move it?
No. A recrawl request needs a verified property, so a third party host page is out of scope, and repeating a submission does not change the judgement behind the status.
Is it worth buying an indexing service for this?
Treat any promise of guaranteed indexing as a claim about a channel that does not exist. What a legitimate service can do is help you get pages you own discovered. The market is examined in backlink indexing services.
Where to go next
If the host page carries this status, the remaining work is about placement choice rather than link repair. That is the honest boundary of what anyone can do for a link they do not own, and the pages below work in the same order the ledger's stages run.
Start with backlinks not getting indexed for the ranked causes, then checking whether backlinks are indexed for the exact probes, and how to index backlinks for the route from placement to index. If your question is about a delay rather than a refusal, the backlink index ETA calculator lays out the stages that can hold a link up.
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 between 2026-06-25 and 2026-07-31, not a sample of the wider web, and they predict nothing about any particular link. Every statement about Google on this page links to the Search Central page it was read from. Nothing on this page 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.