Why your location pages are not indexed: Discovered and Crawled, currently not indexed
In Google Search Console, “Discovered – currently not indexed” means Google has found your location page URL but has not crawled it yet, so it is queued. “Crawled – currently not indexed” means Google did crawl the page and chose not to index it, which is almost always a quality or duplication judgement rather than a technical fault. For templated city and town pages, a pile of pages sitting in that second status is Google’s quality filter working as intended, not a bug you can resubmit your way out of. The fix is to strengthen or consolidate the pages, hold the thin ones back, and let each one earn indexation on its own merits.
This guide is for anyone running location pages at any scale, whether that is six town pages for a boiler repair business or a few hundred service-area pages across a region. It explains exactly what each Search Console status means, why local pages land in the not-indexed pile so often, and the honest sequence for getting them indexed. Written by Stephen Evans, who builds the Townsmith Local Pages Engine. Published 3 July 2026.
What is the difference between Discovered and Crawled, currently not indexed?
These two statuses appear in the Search Console Page indexing report under “Why pages aren’t indexed”. They look similar and people often treat them the same, but they describe two completely different stages and they call for different responses.
- Discovered – currently not indexed. Google knows the URL exists, usually from your sitemap or an internal link, but it has not crawled the page yet. Google’s own report describes this as the page being “found by Google, but not crawled yet”, often because crawling it then “was expected to overload the site”, so the crawl was rescheduled. This is a scheduling signal, not a verdict. The page has not been judged. (Source: Search Console Page indexing report help, accessed 3 July 2026.)
- Crawled – currently not indexed. Google fetched the page, read the content, and decided not to put it in the index. The report states the page “was crawled by Google but not indexed” and adds “no need to resubmit this URL for crawling”. This is a verdict. It usually means the page is too thin, too similar to your other pages, or does not add anything a searcher could not get elsewhere. (Source: Search Console Page indexing report help, accessed 3 July 2026.)
The short version: Discovered is a queue, Crawled is a decision. If your location pages are mostly in Discovered, Google has not got to them yet. If they are mostly in Crawled, currently not indexed, Google has looked and is not impressed.
A two-row reference for the two statuses
| Search Console status | What it actually means | What it tells you to do |
|---|---|---|
| Discovered – currently not indexed | URL is known but not yet crawled. A crawl-scheduling signal, often deferred to avoid overloading your server. No quality judgement has been made. | Wait, and remove anything blocking efficient crawling. Make sure the page is actually worth crawling when Google arrives. |
| Crawled – currently not indexed | Page was crawled and read, then left out of the index. A quality or duplication judgement. Google says there is no need to resubmit. | Strengthen, consolidate, or remove the page. Resubmitting changes nothing on its own. |
Why do location pages end up not indexed so often?
Local page sets are unusually prone to both statuses, and the reason is built into how most of them are made. A typical batch is one template repeated across a town list, with the town name swapped in and the body text otherwise near-identical. From Google’s side that produces dozens of pages that are technically different URLs but say almost the same thing. There is little reason to index the eleventh page when it adds nothing the first ten did not.
Google is explicit that indexing is conditional. Its documentation on how Search works states “Indexing isn’t guaranteed; not every page that Google processes will be indexed” and that “Indexing also depends on the content of the page and its metadata”. The same page adds that “Google doesn’t guarantee that it will crawl, index, or serve your page, even if your page follows the Google Search Essentials”. (Source: Google Search Central, In-Depth Guide to How Google Search Works, accessed 3 July 2026.) Indexation is earned per page on quality and uniqueness. It is not a switch you flip by submitting a sitemap.
The common local triggers for the Crawled, currently not indexed verdict are worth naming plainly:
- Near-duplicate bodies where only the town name and a map pin change between pages. This is the same problem covered in the guide to duplicate content on location pages, and it is the single most frequent cause.
- Pages built for towns the business has no real connection to, with no jobs done there, no local detail, and nothing a resident would recognise.
- Thin pages that are mostly a heading, a paragraph of generic service copy, and a contact form, with no substance specific to the area.
- A whole batch published at once, so Google sees a sudden spike of similar low-substance URLs and treats the set with suspicion.
A boiler repair firm covering Uckfield, Lewes and Crowborough does not need three pages that read identically with the town swapped. It needs three pages that each say something true and specific about working in that town, or it needs one strong page that covers the area honestly. If you are still deciding how many to publish at all, the guide on how many location pages to build works through that question before you write a line.
Will resubmitting or requesting indexing fix it?
No. Resubmitting will not fix a quality verdict. If a page is sitting in “Crawled – currently not indexed”, Google has already seen it and decided against it. Google says in plain terms that there is “no need to resubmit this URL for crawling”. Hitting Request Indexing again, regenerating the sitemap, or pinging the URL does not change the underlying judgement. It just asks Google to look at the same page and reach the same conclusion.
The “Request indexing” button has a real use, but it is the last step, not the first. It is for telling Google to re-look after you have materially changed a page so the verdict can actually differ. Requesting indexing on an unchanged thin page is the SEO equivalent of resubmitting the same essay and hoping for a better mark. This is also why bulk recovery does not work as a button-press. If a large set has been demoted, the honest path is the one in the scaled content recovery guide: fix the substance, prune what cannot be fixed, then re-request page by page.
How do you actually get location pages indexed?
Treat indexation as something each page earns, in this order. None of these steps is a trick, and none of them guarantees indexing, because nothing does. They raise the odds by removing the reasons Google declined in the first place.
- Audit which pages are affected and how. Open the Search Console Page indexing report, click into “Discovered – currently not indexed” and “Crawled – currently not indexed”, and export the URL lists. Separate the queue problem (Discovered) from the quality problem (Crawled). They need different work.
- Consolidate or strengthen. For each Crawled-not-indexed page, decide honestly: can this page carry real, area-specific substance, or is it a near-duplicate that should fold into a stronger page? Strengthen the ones with a genuine reason to exist. Consolidate or remove the rest. Fewer strong pages beat many weak ones every time.
- Hold the thin ones back. Do not publish a page until it clears a real quality bar. A page that would land in the not-indexed pile is better kept as a draft than shipped, because shipping it adds to the low-substance signal across your whole set.
- Request indexing only after the page earns it. Once a page genuinely says something a searcher in that town would value, then use Request Indexing for that single URL, and check back in the index-coverage report over the following days.
This is exactly the discipline the Townsmith quality score is built to enforce before anything reaches Google. Every page the engine builds is scored from 0 to 100 on substance and uniqueness, server-side, with no AI and no external calls. Pages below the threshold are held back automatically rather than published, so the thin pages that land in “Crawled – currently not indexed” never ship in the first place. You can read how the scoring works in the quality score documentation, and see the broader hold-back behaviour on the features page.
To be clear about what that score is and is not: it is an internal quality gate that mirrors the kinds of judgement Google makes. It does not guarantee indexing or rankings, because no tool can. What it does is stop you shipping the pages most likely to be declined, which is the part that is actually in your control.
What about the technical asides, canonical tags and crawl speed?
Two technical points come up constantly alongside these statuses, and both deserve one honest sentence rather than a rabbit hole.
Canonical tags. If near-identical location pages each canonicalise to one another or to a parent, Google will index only the canonical and leave the rest out, which can show up as not-indexed, so check that each page you genuinely want indexed declares itself as its own canonical.
Crawl speed and TTFB. A slow time to first byte makes Googlebot crawl more cautiously and is a common reason genuinely useful pages linger in “Discovered – currently not indexed”, so a fast, reliable server helps Google get through your queue, though it will never persuade Google to index a thin page.
Crawl budget is mostly a concern for very large sites, and even there Google has said it only wants to crawl high-quality content, so making low-quality pages load faster does not earn more crawling. For a handful of town pages, crawl budget is rarely the real issue. The real issue is almost always substance.
Is there a special trick for AI search or AI Overviews here?
No. There is no separate route into AI Overviews or AI Mode for pages that Google has declined to index. A page has to be indexed and eligible to appear in normal results before it can be surfaced in an AI answer, so the work is the same: be genuinely useful and earn indexation. There is no AI-only schema, no llms.txt shortcut, and no chunking trick that gets a thin page indexed. Good people-first content is the optimisation, and after you publish you can monitor pickup in both the index-coverage report and the newer Generative AI performance report in Search Console. Building real topical depth across your area, rather than swapping town names, is also the foundation for AI visibility, which the guide to topical authority for local businesses covers in full.
Common questions about location pages not being indexed
Why are my location and city pages not indexed when my service pages are fine?
Because service pages tend to be individually written and distinct, while location pages are usually a template repeated across a town list. Distinct pages clear the quality bar. Near-duplicate town pages trip it. The pattern you are seeing is Google indexing the unique pages and declining the repetitive ones, which is the quality filter doing its job.
How long does Discovered, currently not indexed take to clear?
There is no fixed time, and Google says it cannot predict or guarantee when or whether a URL will be crawled or indexed. Discovered pages can move within days or sit for weeks. If they have sat for a long time, the most useful thing you can do is make sure the page is genuinely worth crawling when Google reaches it, and that your server responds quickly, rather than repeatedly requesting indexing.
Does deleting thin location pages help the rest of the site?
Often, yes. Removing or consolidating pages that were never going to be indexed reduces the volume of low-substance URLs Google associates with your site, which can help the remaining strong pages. This is the core idea behind recovering from a scaled-content problem: fewer, better pages, with the dead weight pruned rather than left to drag.
Will the Townsmith plugin guarantee my pages get indexed?
No, and you should be wary of anything that claims it can. Townsmith builds real, editable location pages, scores them for substance, holds the thin ones back, and outputs clean schema, all server-side. That removes the most common reasons Google declines a page. Indexing itself is always Google’s decision, made per page on quality and uniqueness. Townsmith complements your existing SEO setup, whether that is Rank Math, Yoast, AIOSEO or SEOPress, rather than replacing it. You can read how the scoring gate works in the quality score documentation.
Figures and Google documentation references on this page are current as of 3 July 2026. Re-check the Search Console help pages and Google Search Central documentation before acting, as Google updates both.