Crawled or Discovered, Currently Not Indexed: What Each Means
What Search Console's "Crawled" and "Discovered - currently not indexed" statuses mean, which pages to ignore, and how to fix the ones that matter.
You open Google Search Console, go to the Page indexing report, and find a long list of pages under "Crawled - currently not indexed" or "Discovered - currently not indexed". Some of them are pages you care about. This guide is for business owners and whoever runs their website. It explains what each status means, which pages you can safely ignore, and what actually fixes the rest.
In short: "Discovered" means Google knows the URL but hasn't crawled it yet. "Crawled" means Google fetched the page and chose not to index it, for now. First check the page with URL Inspection, which is more current than the report. Then rule out technical blocks: noindex, a different Google-selected canonical, duplicate URL versions, soft 404s, or a firewall challenge served to Googlebot. If the page is technically fine, the fix is usually better internal links and more distinct, useful content, not repeated "Request indexing" clicks.
What the two statuses mean
Google's Page indexing report help defines them like this:
| Status | Google's definition | What it usually points to |
|---|---|---|
| Discovered - currently not indexed | Found by Google but not crawled yet. Typically Google wanted to crawl it, but expected that doing so would overload the site, so it rescheduled the crawl. | Crawl priority: weak internal links, a slow or struggling server, or a very large number of low-value URLs |
| Crawled - currently not indexed | Crawled but not indexed. It may or may not be indexed in the future; no need to resubmit it for crawling. | Value or duplication: Google didn't see enough reason to add this page to its index |
Neither status is an error or a penalty. Google is also clear that you shouldn't expect every URL on a site to be indexed, only the canonical pages. A blog with tag pages, feeds and filtered URLs will always have some of these.
Step 1: Triage, because many URLs don't need fixing
Export the list and sort it into two groups before doing anything.
Usually fine to leave alone:
- Feed URLs (
/feed/), comment feeds and RSS - Tag, author and date archives on a blog
- Paginated pages (
/page/2/) - URLs with tracking or filter parameters (
?utm_source=,?sort=) - Old test pages, attachment pages or thin search-result pages
Worth investigating:
- Service and product pages
- Location pages
- Blog posts you wrote to bring in visitors
- Your homepage or contact page (if these are listed, start here)
Tip: If most of the list is the first group, there's nothing to fix. You may want to stop linking to or listing some of these URLs, but that's tidying, not a repair.
Step 2: Check the page with URL Inspection
The Page indexing report is a periodic summary and can lag behind. The URL Inspection tool shows the latest status Google has for a URL, and its Test live URL button checks how Google sees the page right now.
Paste a page that matters and look at:
- Page indexing status. It may already be indexed since the report was generated.
- Crawl allowed? / Indexing allowed? These reveal robots.txt blocks and noindex.
- User-declared canonical vs Google-selected canonical. If they differ, Google is treating your page as a duplicate of another URL.
- View tested page. The screenshot and HTML show what Googlebot actually received.
Step 3: Rule out technical causes
Work through these for each important page:
- Noindex. A
noindexrobots meta tag or anX-Robots-TagHTTP header keeps a page out of the index. SEO plugins and site builders sometimes add it to whole sections. - Robots.txt. A disallow rule stops crawling. Our guide to robots.txt mistakes covers the common ones.
- Canonical conflicts. If the Google-selected canonical is a different URL, check Google's guide to specifying a canonical URL. Make the canonical tag, internal links and sitemap all point to the same version.
- Duplicate URL versions.
httpandhttps,wwwand non-www, trailing slash or none, and parameter variants can all serve the same content. Redirect the extra versions to one. - Soft 404s. A page that says "nothing here" or has almost no content but returns HTTP 200 can be treated as a soft 404. Google's HTTP status codes documentation explains this. Return a real 404 or 410 for pages that are gone, and add real content to pages that should stay.
- Firewall or CDN challenges. Bot protection that shows a "Checking your browser" page or a captcha to Googlebot means Google crawls the challenge, not your content. View tested page reveals this. Allow verified Google crawlers rather than whitelisting a user-agent string; Google explains how to check that a request really comes from Googlebot.
- JavaScript-only content. If the main text only appears after scripts run, check the rendered HTML in the live test. See why your React site might be invisible to Google.
Step 4: Give Google a reason to crawl and index it
If the page passes every technical check, the problem is usually priority and value.
For "Discovered":
- Link to the page from your menu, homepage or related pages. Pages that nothing links to (orphan pages) are a classic cause.
- Keep your XML sitemap clean: only canonical, indexable URLs that return 200. Our guide to XML sitemaps for small business sites explains why.
- If you have thousands of low-value URLs (filters, calendars, parameters), cut them down so Google's crawling goes to the pages that matter.
- Check server response times. A slow or error-prone server makes Google crawl more cautiously.
For "Crawled":
- Make the page clearly distinct. Location pages that differ only by the town name, or product pages copied from the manufacturer, give Google little reason to index another copy.
- Answer the visitor's question fully on the page, with details only you can provide: your process, photos, the area you serve, what is and isn't included.
- Merge thin pages covering the same topic into one stronger page and redirect the others.
- Link to it from related, already-indexed pages with descriptive anchor text.
What doesn't help
- Clicking Request indexing over and over. Google's help says a request doesn't mean the page will be indexed, and there's a daily limit. Use it once after a real fix.
- Paid "indexing services". They can't change Google's assessment of the page, and some rely on spammy links.
- Resubmitting the same sitemap daily. It doesn't change priority.
- Panicking about every URL. Some pages are meant to stay out.
Key takeaways
- Discovered = not crawled yet (priority). Crawled = fetched but not chosen (value or duplication).
- Triage first: feeds, tags, pagination and parameters can usually be left alone.
- Use URL Inspection and its live test before trusting the report.
- Rule out noindex, robots.txt, canonical conflicts, duplicates, soft 404s and firewall challenges.
- Then strengthen internal links and make each page distinct and useful.
If you'd rather see all of this in one place, the free one-page SEO scan on seo.lordevo.com checks a page's canonical tag, robots meta, X-Robots-Tag, robots.txt rules and sitemap. The paid Full SEO Audit crawls up to 50 pages and builds an indexability matrix for each one, covering status, robots, canonical, sitemap and internal links, and flags canonical chains, orphan pages and soft 404s. Our guide on how to read an SEO audit shows what to do with the results.
FAQ
How long until a fixed page gets indexed? Google says new content can take a few days to be indexed, and it can be longer. No one can promise a date.
Can "Crawled - currently not indexed" pages hurt my site? Not directly. A large share of low-value URLs can make crawling less efficient, which is why triage matters.
Should I delete the pages? Only if they have no value to visitors. Otherwise improve, merge or link to them.