If you run a blog or a small business site, you have probably opened Google Search Console, found the Page indexing report and seen two confusing labels: “Crawled – currently not indexed” and “Discovered – currently not indexed”. This guide is for bloggers and site owners who want to know what those labels actually mean, when they can be ignored, and what to do when an important page is stuck.
Contents
What Google says each status means
The two statuses sound similar but describe different points in Google’s process. Both appear in the Search Console Help documentation for the Page indexing report, in the list of reasons a page is not indexed.
| Status | Google’s description | What it suggests |
|---|---|---|
| Crawled – currently not indexed | The page was crawled by Google but not indexed. | Google fetched the page and chose not to add it to the index, at least for now. |
| Discovered – currently not indexed | The page was found by Google, but not crawled yet. | Google knows the URL exists but has not fetched it. The last crawl date in the report is empty. |
For the second status, Google explains that a planned crawl was rescheduled, which is why the last crawl date is empty. For the first, Google says the status is common and does not necessarily indicate an issue that needs attention, though it suggests using the URL Inspection tool to look for problems on pages you care about.
When you can safely ignore them
Google’s own wording is relaxed about non-indexed URLs. Its documentation says it is fine for a URL not to be indexed for the right reasons, that “not indexed” is not necessarily bad, and that you should not expect every URL on your site to be indexed. Duplicates and pages without meaningful information may be left out, as long as your key pages are indexed.
Enjoying this? Get our best tips by email
Practical SEO, link building and content strategies, straight to your inbox.
In practice, you can usually leave these statuses alone when the affected URLs are:
- Tag, archive, pagination or internal search result pages that you never meant to rank.
- URLs with tracking parameters or other variants of a page that is already indexed.
- Thin utility pages such as thank-you pages or login pages.
- Old URLs you plan to remove or redirect.
Also note that Google says sites with fewer than 500 pages probably do not need to use the Page indexing report heavily. If you have a 30-page business site and only one blog post is flagged, a calm check is enough; there is no need for a site-wide overhaul.
A practical triage workflow
Use this order when a page you actually want in search is flagged. It moves from cheap checks to larger changes.
1. Confirm the page matters
In Search Console, open the Page indexing report, scroll to the list of reasons and click the status. Look at the example URLs (the list is limited to 1,000 items). Sort them mentally into “I want this in search” and “I do not care”. Only the first group needs work.
2. Inspect the URL
Paste the URL into the search bar at the top of Search Console, or click the Inspect link beside it in the report. The result shows Google’s most recent stored version of the page, not the live one, and covers discovery, crawl and indexing, including the Google-selected canonical. Check whether the page is reported as available, whether the canonical Google chose matches the one you intended, and what the crawl details say.
Then click Test live URL. The live test fetches the page in real time and tells you whether it can be crawled and parsed. It does not check sitemaps, referring pages, canonical selection, duplicates, manual actions or quality guidelines, and passing it is not a promise of indexing. Use it to catch problems such as a noindex tag, a blocked resource or a page that renders empty.
3. Check for duplication and canonical confusion
Google’s canonicalization guidance says that without a declared preference, it picks the version it considers best to show users. Your signals are preferences, not commands. Redirects and rel="canonical" are strong signals; sitemap inclusion is a weak one. Ask yourself whether the flagged page is genuinely distinct from another page on your site, or whether it is a near copy, such as a location page where only the city name changes. If it is a near copy, either make it truly different and useful or consolidate it into one stronger page with a redirect or canonical.
4. Review quality honestly
Google says duplicates and pages lacking meaningful information may be left out. Read the page as a first-time visitor would. Does it answer a specific question better than what already exists? Does it add something original, such as clear steps, examples or your own data? Google does not say quality alone explains either status, but improving a weak page helps readers whatever Google decides.
5. Strengthen internal links
Pages buried deep or linked from nowhere give Google little reason to prioritise them. Link to the page from related posts and from a hub or category page, using descriptive anchor text. Our guide to smart internal linking covers how. It is sensible practice, though Google does not state that more links will move a page out of either status.
6. Keep your sitemap accurate
Submit a sitemap that lists only the canonical, indexable URLs you want found. Google’s URL Inspection help recommends a sitemap with <lastmod> values when you have many new or updated pages. Remove redirected, noindex and duplicate URLs from it so the file is a clean signal. For the basics, see our guide to sitemaps.
7. Request indexing once, then wait
After fixing real problems, click Request indexing on the inspection result. Requests go into a queue after a quick check for obvious errors, and you cannot request indexing if the live test shows the page is not indexable. Google’s help says a request does not guarantee inclusion and that processing can take anywhere from a day to a week or two. Treat that as Google’s general statement, not a promise for your page. The Page indexing report help also notes that it can take a week or so for Google to start crawling and indexing a new page.
8. Use Validate Fix for groups of pages
If you fixed a pattern affecting many URLs, open the issue details page and click Validate fix. Fix all instances first, because validation stops if Google finds even one remaining instance. Google says validation typically takes up to about two weeks but can take much longer. Do not click it again until validation has succeeded or failed. If it fails, use See details to find the offending URL, fix it and click Start new validation.
Common mistakes
- Clicking Request indexing repeatedly. Google caps requests per property per day without publishing the figure, and it never says repeat requests speed anything up. If the page has not changed, the request has nothing new to evaluate.
- Pressing Validate fix again and again. Google explicitly tells you to wait for the current validation to finish.
- Treating every flagged URL as an error. Many are duplicates or low-value pages you do not need indexed.
- Blocking or noindexing as a canonical fix. Google’s guidance says not to use robots.txt, the URL removal tool or noindex for canonicalization.
- Assuming a passing live test means indexing. It confirms the page can be fetched, nothing more.
If you are also seeing server errors, soft 404s or redirect problems in the same report, handle those first; our post on fixing crawl errors in Search Console walks through them.
Key takeaways
- “Crawled – currently not indexed” means Google fetched the page but did not index it; “Discovered – currently not indexed” means Google knows the URL but has not crawled it yet.
- Google says not every URL needs to be indexed, so start by deciding which flagged pages matter.
- Use URL Inspection and the live test to rule out technical blocks, then check duplication, quality, internal links and your sitemap.
- Request indexing once after a real change, and use Validate fix only after fixing all instances.
- Google does not guarantee indexing or give a timeline for these statuses, so be wary of anyone who does.
FAQ
Is “Crawled – currently not indexed” a penalty?
Google’s documentation does not describe it as a penalty. It says the status is common and does not necessarily indicate an issue needing attention. Manual actions are reported separately in Search Console.
How long until a flagged page gets indexed?
Google does not state a timeline for these statuses. Its help pages give general figures, such as a week or so for new pages and up to about two weeks for Validate fix, but also say these can take longer and that indexing is not guaranteed.
Why does Search Console say “Discovered” but never crawl my page?
Google says a planned crawl was rescheduled. It does not give detailed reasons in these pages, so check that your server responds reliably and that the page is linked internally.
