"Discovered – currently not indexed" means Google knows your page exists but hasn't crawled it yet; "Crawled – currently not indexed" means Google crawled it and decided not to add it to the index — for now. Neither is a penalty, and neither is an error you can "fix" with one setting. They're Google's way of saying your page hasn't yet earned a place in its index, usually because of crawl priority (for "discovered") or perceived value and duplication (for "crawled"). This guide explains every common indexing status in Search Console, the real reasons behind each, and the step-by-step process to get pages indexed — including what we did when it happened to our own blog.
Key takeaways
- "Discovered – currently not indexed" means Google knows the URL but hasn’t crawled it (a crawl-priority issue); "Crawled – currently not indexed" means it was crawled but not judged worth indexing yet (a value issue).
- Neither is a penalty, and neither has a one-click fix.
- Rule out noindex tags, robots.txt blocks, wrong canonicals and error status codes first, then link to the page from your strongest indexed pages.
- Requesting indexing helps after the page is fixed; repeating the request daily doesn’t raise priority.
- Our own audit found 12 of 17 posts indexed; the other five were crawl-priority cases on a young domain.
It happened to us, too: a real indexing audit
In October 2026 we ran a URL Inspection check across every post on this blog. Of 17 articles, 12 were "Submitted and indexed". The other five were split across three statuses:
| Status in Search Console | Posts | What it told us |
|---|---|---|
| Submitted and indexed | 12 | Healthy |
| URL is unknown to Google | 2 | Google hadn't even discovered them yet — the newest posts |
| Discovered – currently not indexed | 2 | Known, but crawl was deferred |
| Crawled – currently not indexed | 1 | Crawled, judged not (yet) worth indexing |
Our sitemap was registered, fetched daily, and had zero errors — so this wasn't a technical blocker. It was crawl priority on a young domain. Two things we found and fixed are worth copying: our sitemap was stamping every static page with "modified today" on every fetch (which teaches Google to ignore your modification dates), and older posts were linked only from page 2 of the blog listing — one click deeper than they needed to be. Both are now fixed. The lesson is that "not indexed" is usually a prioritization signal, and prioritization responds to signals you control.
Every indexing status in Search Console, explained
| Status | What it means | Usual cause | What to do |
|---|---|---|---|
| Discovered – currently not indexed | Google knows the URL but hasn't crawled it | Low crawl priority, young site, many URLs, slow server | Strengthen internal links; request indexing; improve server speed |
| Crawled – currently not indexed | Crawled, not added | Thin or near-duplicate content; low perceived value | Make the page clearly unique and substantial; link to it from strong pages |
| Duplicate without user-selected canonical | Google thinks another URL is the main version | Parameter URLs, http/https or www variants, near-identical pages | Set a canonical tag; consolidate duplicates |
| Alternate page with proper canonical tag | Correctly pointing elsewhere | Working as intended | Nothing — unless the canonical is wrong |
| Excluded by 'noindex' tag | You told Google not to index it | Leftover noindex from staging or a plugin setting | Remove noindex if the page should rank |
| Blocked by robots.txt | Crawling disallowed | An over-broad Disallow rule | Fix robots.txt |
| Page with redirect | The URL redirects elsewhere | Normal after a migration | Make sure internal links point to the final URL |
| Not found (404) / Soft 404 | Page missing, or looks empty | Deleted pages; "no results" pages returning 200 | Redirect or restore; return proper 404s |
Why "Discovered – currently not indexed" happens
Google crawls with a budget. On a large, authoritative site that budget is generous; on a new or small site, Google discovers URLs (through sitemaps and links) faster than it chooses to crawl them. The most common reasons a discovered page sits in the queue:
- The site is young or has little authority. Google crawls less often until it trusts the site's content is worth fetching.
- The page is weakly linked. A URL that appears only in the sitemap — or only on page 3 of an archive — signals low importance.
- Server response is slow or errors appear. Google throttles crawling when a server struggles, to avoid overloading it.
- Too many low-value URLs. Filter, tag and parameter pages competing for the same budget dilute it.
Why "Crawled – currently not indexed" happens
This one is a quality decision. Google fetched the page and concluded it doesn't add enough to its index right now. Typical reasons: the page is short or generic, it closely resembles other pages on your site or elsewhere, or it lacks signals of importance (few internal links, no external links). It's also common for brand-new pages to sit here briefly and then get indexed on a later crawl. The fix is almost never technical — it's making the page more clearly valuable and more clearly important within your site.
The step-by-step fix
1. Find every affected page — not just the ones you notice
Search Console's Pages report lists URLs by status, but it's sampled and lags behind. The more reliable approach is to inspect your URLs directly. Clicktics' De-Indexed Pages report does this automatically: it builds your URL list from your sitemap plus Search Console, checks each page with Google's URL Inspection API, and shows Google's own reason for every page that isn't indexed — including pages that were indexed and quietly dropped out.

The impressions column is the triage signal. A page that earned 61 impressions last month and zero now is an urgent loss; a page that never had impressions is a lower-priority "get it indexed" task.
2. Rule out the technical blockers
For each affected URL, confirm in Search Console's URL Inspection tool: is it allowed by robots.txt? Is there a noindex tag? Does the canonical point to itself? Does it return a 200 status? Any "no" here is the real answer and must be fixed first — no amount of content work overrides a noindex tag.
3. Strengthen internal links to the page
This is the most underrated lever. Link to the unindexed page from pages that are already indexed and receive traffic — ideally from within the body text, with descriptive anchor text. Make sure it's reachable within two or three clicks from your homepage. For a blog, that means a listing that shows all posts without deep pagination, and related-post links between articles.
4. Make the page earn its place
For "crawled – not indexed" especially: add what makes the page uniquely useful — original data, screenshots, worked examples, a direct answer to the question in the first paragraph. Remove or merge near-duplicate pages that compete with it.
5. Submit and verify
Once the page is fixed, ask Google to crawl it. In Search Console that's URL Inspection → "Request indexing", one URL at a time. Clicktics' Index Links feature lets you submit pages from your dashboard and then verifies the result: each URL stays "processing" until Google's URL Inspection API confirms it's indexed, so you're not guessing whether a request worked.

An honest note on how submission works: Google officially documents its Indexing API for job-posting and livestream pages. Many SEOs use it more broadly and report faster crawls, but Google doesn't guarantee indexing for any submission method. What you can rely on is the verification — knowing for certain which pages are in and which aren't. Our Index Links setup guide walks through connecting a Google service account, including the two Google APIs that both need to be switched on.
6. Keep your sitemap honest
Only list URLs you want indexed (no redirects, no noindex pages, no parameter duplicates), and only update a page's lastmod date when its content actually changes. A sitemap that claims everything changed today trains Google to ignore its dates.
7. Be patient, then re-check
After fixes, give Google one to four weeks. Re-inspect the URLs then. If a page is still "crawled – not indexed" after genuine improvements and strong internal links, consider whether it should exist as a separate page at all — merging it into a stronger page is sometimes the right answer.
Which unindexed pages should you fix first?
If dozens of pages aren't indexed, don't try to fix them all at once. Prioritize:
- Pages that make money — product, service, pricing and key landing pages. One indexed product page is worth more than ten indexed tag archives.
- Pages that used to be indexed and earned impressions. A page that dropped out after earning traffic is a direct loss; recovering it is usually faster than indexing something new.
- Pages other sites link to. External links make a page more likely to be indexed and more valuable once it is.
- Fresh, substantial content you've just published and linked from strong pages.
And deliberately leave some pages unindexed. Thin tag pages, internal search results, filter combinations and near-duplicate variants often shouldn't be in Google's index at all. Adding noindex to genuinely low-value pages can help Google spend its crawl attention on the pages you care about.
What not to do
- Don't request indexing for the same URL every day. Repeated requests don't raise priority; fixing the page and its internal links does.
- Don't mass-produce thin pages to "get more indexed". More low-value URLs make crawl priority worse for the whole site.
- Don't pay for "guaranteed indexing" services. Nobody outside Google can guarantee indexing, and some of these services use spammy link networks.
- Don't remove important pages from your sitemap because they aren't indexed yet. The sitemap should list every page you want indexed.
- Don't change URLs to "reset" a page. A new URL starts from scratch and loses any signals the old one had.
How long does indexing take?
For an established site, new pages often appear within a few days. For a young site, a few weeks is common, and some pages wait longer. There's no fixed timeline, because it depends on crawl priority — which is exactly why the steps above focus on raising it. The quickest measurable signal that things are improving is the number of your submitted URLs moving to "Indexed" week over week.
Don't forget the opposite problem: pages falling out
Getting indexed is half the job. Pages also drop out — after a site migration, a CMS update that added noindex, a redirect loop, or a quality reassessment. Because nothing alerts you, sites often discover de-indexing only when traffic or leads fall. That's the reason the De-Indexed Pages report runs a daily scan: a page that leaves Google's index shows up the next day, with Google's reason, instead of at the end of the quarter.
Frequently asked questions
What does "Discovered – currently not indexed" mean?
Google has found the URL (usually via your sitemap or a link) but hasn't crawled it yet. It's a crawl-priority status, common on new or low-authority sites. Strengthen internal links, make sure your server is fast, and request indexing for the most important pages.
How do I fix "Crawled – currently not indexed"?
Make the page more clearly unique and valuable, consolidate near-duplicates, and link to it from your stronger indexed pages. Then request indexing and re-check after a couple of weeks.
Does "Request indexing" in Search Console work?
It asks Google to recrawl the URL soon; it doesn't guarantee indexing. It's most effective after you've fixed whatever was holding the page back.
Can a sitemap alone get my pages indexed?
A sitemap helps Google discover pages, but discovery isn't indexing. Pages need to be reachable through internal links and judged worth indexing — a sitemap can't do that part for you.
How do I know if a page was de-indexed?
Inspect it with Search Console's URL Inspection tool, or use a monitor that checks your pages automatically. Clicktics' De-Indexed Pages report checks your sitemap and Search Console URLs daily and flags any page that drops out, with Google's reason.
Stop guessing which pages Google has
Indexing problems are invisible until they cost you traffic. Clicktics shows you which pages are in Google's index, which fell out and why, and lets you submit and verify pages from one dashboard — alongside rank tracking, Search Console data and full visitor analytics. Try every feature free for 14 days — no card needed.
Start your 14-day free trial → or read the Index Links setup guide.
Tomás García
Tomás García writes for the Clicktics blog about session replay, analytics engineering, and building privacy-first products that agencies love. Reach the team at [email protected].