Not Every Indexing Error Is Yours to Fix

Google Search Console makes far too many teams believe they have an indexing problem when they actually have a prioritization problem. The message I get most often from a new client’s marketing person is a screenshot: a column in Google Search Console, half of it green, the rest a stack of statuses that read like alarms: Crawled – currently not indexed, discovered – currently not indexed, and soft 404. The note underneath is almost always the same: How fast can we fix all of this?

My first answer usually surprises them. Most of that column is not a list of errors. It is Google telling you two very different things at the same time, and only one of them is a job for your developer.

For a professional practice, the distinction matters. A page Google does not index cannot be retrieved by AI answer engines either. When someone asks ChatGPT or Google’s AI who to hire, retrieval starts with the index. Knowing which statuses point to a technical block you can remove, and which reflect Google’s editorial judgment. I built meanderingSapien to help you understand exactly that.

The two kinds of “not indexed”

A page indexing status is just the checkpoint where a URL stopped moving through Google’s pipeline: found, crawled, judged, and sometimes indexed. Every status is one of two kinds. Some describe a block you put up by accident and can take back down. Others describe a decision Google made on purpose. Confusing the two is the most expensive mistake I see in this report. Sort the whole list into two columns, and the report stops being frightening.

Technical blocks

The first category includes blocks you created and can reverse. They prevent Google from indexing a page because of a technical instruction, an access issue, or a configuration problem:

• noindex tag preventing the page from being indexed.
• robots.txt rule blocking Googlebot from accessing the page.
• 404 or server errors stopping Google from retrieving the content.
• Duplicate pages without a canonical leave Google to guess which version to keep.

When I see one of these, I reach for the wrench. They are mechanical problems, and most are fixable in an afternoon. Once the block is removed, Google can evaluate the page on its own merits.

Google’s judgment

The second category is Google’s. These statuses are not technical faults or broken settings. They reflect Google’s own decisions about when, or whether, a page deserves an index slot:

• Discovered – currently not indexed: Google knows the URL exists but has not prioritized crawling it yet.
• Crawled – currently not indexed: Google fetched the page but decided it was not worth adding to the index.

In both cases, the page is technically reachable. The question is no longer whether Google can index it, but whether Google has enough reason to. The first group is where technical work pays off. The second is where I see teams spend weeks chasing fixes that were never going to change Google’s decision.

Where the page actually stopped

Before I touch anything, I want to know where in Google’s pipeline a URL stalled, because that answers a better question than “how do I fix this.” It answers “whose decision was this.”

Every status lands at one of five points:

• Discovery: Google knows the URL exists but has not scheduled a fetch.
• Crawl: Googlebot tries to fetch, and either succeeds, fails, or follows a redirect.
• Evaluation: Google reads the page and judges whether it is worth an index slot.
• Canonical: near-duplicate pages get grouped and one is chosen as the reference.
• Serving: a hard block, such as noindex, robots.txt, or a login wall, settles it regardless of quality.

Read a status against that sequence, and it tells you which column it belongs in before you have opened a single line of code.

The statuses that waste the most of your time

The statuses I spend the most time explaining are Discovered – currently not indexed and Crawled – currently not indexed. They are also the ones where I most often tell clients to stop looking for a technical fix.

Google has been open about what they mean. When its systems have real doubts about a site’s overall quality, they simply crawl and index less of it, and those two statuses are how that shows up. Some common triggers include: 

• Thin pages 
• Near-identical service pages
• Undifferentiated AI-generated content

However, not all AI-assisted writing counts, only the kind that adds nothing a dozen other pages already say, and none of that is a setting your developer can toggle.

So when a firm’s pages sit at Crawled – currently not indexed on their own merits – the real work is the content and authority underneath. You need to create pages distinctive enough to earn the slot, and enough credible mention of the firm elsewhere that Google treats the site as worth indexing in full. Your content gets you quoted in AI answers, which is where I would rather spend the budget anyway.

When Google overrules your canonical

Not every indexing decision is about whether a page gets into the index. Sometimes the more important question is which version of the page Google keeps there, canonicalization helps with that. Google groups pages that carry the same core content, then picks the version it judges most complete as the canonical. A rel=”canonical” you declare is a hint, so Google can overrule it.

For a firm with a stack of near-identical location or practice-area pages, that decision can have wider implications than rankings alone. The version Google ultimately treats as canonical is often the one other systems rely on as well. If that is not the page you intended to represent the topic, it is worth understanding why Google made a different choice. Near-duplicate pages competing for the same intent are one of the first things I look at when auditing a firm’s machine layer.

Check the report before you trust it

One last habit before you act on anything: confirm the number is real. It is surprisingly easy to lose time solving a problem that exists only in the report. The Page Indexing report has frozen on stale data for weeks at a stretch, more than once, showing counts that had not moved while the site underneath was fine. Google confirmed those episodes were reporting lags, and the per-URL live check in the URL Inspection tool stayed accurate the whole time.

So my rule is simple. My team does not open a ticket based on a status count that has not changed in three weeks. They check a specific URL in the URL Inspection tool first. More than once, that simple check has saved us from chasing a problem that wasn’t there.

Getting Indexed Is Just the Starting Point

Being indexed does not make a firm the answer to anything. It just makes the firm eligible to be. That is the machine layer of getting recommended: unglamorous, mostly invisible, and non-negotiable, because everything the content and authority work is meant to earn depends on the pages being retrievable in the first place. If you want the version that starts from the page, our free guide walks the same ground.

At meanderingSapien, I help professional practices separate the technical issues worth fixing from the signals that call for a different kind of work. If your Page Indexing report has turned into a list of questions, book a call to find solutions.

Frequently Asked Questions

What does “Discovered – currently not indexed” mean?

It means Google has found the URL but has not prioritized crawling it yet, often because a fetch looked likely to strain the site or the page was not worth the queue. It may be indexed later.

Should I use Google’s Indexing API to get a new page indexed faster?

Not for a normal page. Google scopes the Indexing API to job postings and livestream video pages only. A clean sitemap and some patience do more.

Should every page on my website be indexed?

No. The goal is to make sure the pages that represent your expertise and attract prospective clients are the ones Google chooses to keep.

I removed a noindex tag. Does asking Google to reindex actually help?

Yes. Once you have cleared a real block, requesting a recrawl in the URL Inspection tool can speed up how fast Google notices the change.