Indexing problems: detect and fix

Indexing problems appear when Google knows a URL but does not show it in results or decides to exclude it because of a technical, quality, or duplication signal. The most reliable place to start is the Pages report in Google Search Console and separating what is normal from what affects the business. Not every non-indexed page is a problem: a URL with noindex can be fine if it is an internal page, but a blocked commercial category does require action. The plan is to identify the exact status, validate the cause, and apply the right fix: remove blocks, adjust the canonical, improve content, strengthen internal linking, and request a new review. At Growth Digital we treat this analysis as a technical audit: first we prioritize URLs with organic value, then we act on the patterns that stop Google from processing them correctly.

What an indexing problem is

An indexing problem appears when Google knows a URL (or should know it) and does not include it in its index, or leaves it out because of a signal from you: noindex, robots.txt, canonical, or redirect. Indexed does not mean well ranked. It means it can be shown. Without an index there is no ranking.

If even the homepage does not appear when you search your brand, the diagnosis is different: the website is not on Google. This page is about specific URLs excluded in Search Console, not "Google is down today."

How to see it: the Pages report

In Search Console, Pages (formerly Coverage) groups indexed and non-indexed URLs by reason. The total number of excluded URLs is almost never the problem: filters, parameters, and legal thank-you pages can and should stay out. Prioritize services, categories, landings, and articles that should attract customers.

Inspect an important URL: whether it is on Google, which canonical it chose, and when it crawls it. The site: operator gives orientation; it is not an audit. How to read the rest of the panel: use Search Console.

noindex and robots.txt

noindex (meta or HTTP header) asks Google not to show the page. It is correct for carts, internal search, or test environments. It is a mistake if a commercial landing inherited it from staging.

robots.txt does not remove from the index by itself; it blocks crawling. If you block /services/ or CSS, Google does not understand the page well. Review Disallow, make sure the sitemap does not list blocked URLs, and check the rendered HTML, not only the CMS editor.

Canonical and duplicates

The canonical indicates the preferred version. If it points to another URL, Google usually excludes yours. Typical conflict: sitemap and menu to one address, canonical to another (www, trailing slash, parameters, language).

Nearly identical pages ("plumber in [town]" with the same text) dilute the signal. Either make them genuinely different, or consolidate them. You do not need to "empty" the report: you need business URLs to point to one clear version.

Crawled or discovered, not indexed

Discovered - currently not indexed: Google knows it exists (sitemap or link) and has not visited it yet, or does not prioritize it. Internal links near the homepage are often missing, or there are too many low-value URLs. Crawl budget: what crawl budget is.

Crawled - currently not indexed: it already saw it and did not choose it. Almost always quality: thin text, duplicate, or worse than another of your URLs on the same topic. Forcing "request indexing" without improving the pattern rarely changes the verdict.

A plan to recover only what matters

Export statuses, cross them with the URLs that sell, and group by cause. High: services and landings. Medium: supporting articles. Low: filters and parameters. Success is not "more indexed pages"; it is that the ones that should be indexed are.

Fix the cause (remove noindex, align canonical, improve content, link from a strong page). Validate with inspection and request indexing for a priority handful, not a thousand URLs. Measure by group: status that disappears, URL that becomes indexed, impressions that return. If after several crawls nothing changes, return to quality and duplicates before insisting.

A poorly closed migration or a preproduction noindex can knock out an entire directory. There, technical SEO work saves blind changes.

Technical data and signals that affect crawling and indexing

Google Search Console statuses should be read as diagnostic signals, not as an automatic error list. A page with noindex may be correctly excluded, while a crawled-but-not-indexed page may need content improvements, internal links, or differentiation from duplicates. I would use this section as a technical checklist: validate access, directives, canonical, sitemap, quality, and crawl priority. If an important URL fails on more than one signal, fix the strongest contradiction first. For example, there is no point expanding content if the page itself declares noindex or points as canonical to another URL.

Status or signal	What it means	What I would check first
Noindex	Google receives an instruction not to include the page in the index.	Meta robots, HTTP headers, and CMS configuration.
Blocked by robots.txt	Google may have limited crawl access to a path or resource.	Disallow rules, sitemap, and affected critical paths.
Alternate canonical	The page declares or Google chooses another URL as the main version.	Declared canonical, internal links, and URL included in the sitemap.
Discovered - currently not indexed	Google knows the URL but has not crawled or prioritized it yet.	Internal linking, depth, sitemap, and volume of new URLs.
Crawled - currently not indexed	Google visited the URL but decided not to add it to the index for now.	Quality, duplication, search intent, and internal signals.

Conclusion

In short: recover the pages Google ignores by starting with an ordered diagnosis, not isolated changes. Indexing problems are fixed when you understand whether the URL is blocked, duplicated, poorly canonicalized, weakly linked, or simply does not add enough value versus other pages. I would always prioritize URLs with real impact and work by patterns, because one technical cause can affect dozens of pages. When Search Console stops being an alarm and becomes a roadmap, indexing goes from a vague problem to a measurable, controllable process.

Frequently asked questions about indexing problems: detect and fix

What does 'Discovered - currently not indexed' mean in Search Console?

It means Google knows the URL, usually because it appears in a sitemap or was found through links, but has not crawled it yet or has not prioritized it. It does not necessarily imply a serious error, though it is worth reviewing if it affects important pages. Check whether the URL is well linked internally, appears in a clean sitemap, and is not part of a mass of low-value pages. If the page has value, improve its internal signals and request inspection when it is ready.

Why does Google index some pages and not others?

Google decides which pages to add to its index based on access, technical signals, duplication, quality, and relevance. It may index a main category and leave out very similar variants, thin pages, or poorly linked URLs. It can also exclude pages with noindex, a canonical pointing elsewhere, or crawl blocks. Analyze the concrete status in Search Console and do not assume every page must be indexed. A healthy site usually has intentionally excluded pages and priority pages correctly indexed.

Does internal duplicate content slow indexing?

Yes, it can slow it when several URLs offer very similar content and Google sees no clear reason to index them all. In that case the search engine may choose a different canonical version, exclude variants, or leave pages crawled but not indexed. It often happens with filters, parameters, repeated landings, pagination, or very similar product pages. The fix depends on the case: consolidate with a canonical, redirect, improve differential content, or remove URLs from the sitemap. Each indexable page should have a clear intent and its own value.

How long does Google take to reindex after a fix?

There is no fixed timeline, because it depends on the site's crawl frequency, the importance of the URL, internal linking, and how clear the fix is. A heavily linked page may be reviewed sooner than a deep or isolated URL. After fixing noindex, canonical, robots.txt, or content, validate the URL in Search Console and request indexing for priority pages. Then monitor the Pages report and check whether the status changes. If it does not, review quality, duplication, and internal signals again.

Need a marketing team?

Let’s talk and grow your business