Google Search Console for beginners can feel alarming the first time you open the Page indexing report and see thousands of URLs listed as “not indexed.” Most of those statuses are harmless, and the scary-sounding ones usually have a clear cause. This guide explains what each common status means, how to fix “Discovered – currently not indexed” step by step, and which messages you can safely ignore.
Quick Answer: “Discovered – currently not indexed” means Google knows your URL, from a sitemap or a link, but hasn’t crawled it yet. For a few new pages it often clears on its own. If it persists, strengthen internal links, confirm nothing blocks Google, check server health, and remove junk URLs. “Crawled – currently not indexed” is different: Google read the page and chose not to index it, which usually points to thin or duplicate content.
Key Takeaways
- “Discovered” and “Crawled” mean different things: Discovered is a crawl-priority problem, while Crawled is a page-value problem.
- Getting crawled doesn’t guarantee indexing, and indexing isn’t guaranteed for every page on any site.
- Many “excluded” statuses are normal, such as redirects, correct canonicals, and noindex tags you added on purpose.
- The Request Indexing button has a small daily limit, so use it for a few important pages, and use Validate Fix for batches.
- The report lags real life, so a URL shown as “discovered” may already have been crawled.
Where to Find the Report
Open Search Console, go to Indexing, then Pages, and scroll to “Why pages aren’t indexed.” Click any reason to see affected URLs, then use the “Inspect any URL” bar at the top to check one page in detail.
Two cautions help beginners. First, the report shows only a sample of URLs per status, up to 1,000, so don’t treat it as a complete list. Second, it updates with a delay, so check a page with URL Inspection before assuming a problem is current.
Discovered vs Crawled: The Difference That Matters
These two statuses sit at different stages, and they need different fixes.
| Discovered – currently not indexed | Crawled – currently not indexed | |
|---|---|---|
| What it means | Google knows the URL but hasn’t fetched it | Google fetched the page but didn’t index it |
| Last crawl date | Empty | Shown |
| Main issue | Crawl priority or capacity | Page value, duplication, or quality |
| Where to look first | Internal links, server health, URL clutter | The page itself |
A page can move from Discovered to Crawled before it’s indexed, which means the bottleneck has shifted from crawling to content evaluation.
How to Fix “Discovered – Currently Not Indexed”
Start by confirming it’s a real problem, then work through these checks in order. A small number of Discovered URLs right after you publish is normal. Google’s help says it often reschedules a crawl to avoid overloading a site, and for small sites the cause is usually crawl priority, not a hard capacity limit.
- Inspect the URL and confirm it still has no crawl date.
- Rule out blocks. In WordPress, check Settings, then Reading, and make sure “Discourage search engines from indexing this site” is unchecked. Also check for noindex tags and robots.txt rules.
- Submit your sitemap under Sitemaps in Search Console. Your SEO plugin’s sitemap is often at sitemap_index.xml.
- Add internal links from pages Google already crawls, such as navigation, hub pages, and related-post blocks.
- Check server health in Settings, then Crawl stats. Slow or unreliable hosting can make Google crawl less.
- Remove clutter: thin pages, tag archives, and parameter URLs that dilute your important pages.
How to Fix “Crawled – Currently Not Indexed”
Because Google already read the page, improve the page rather than resubmitting it. Google’s guidance says such a page may or may not be indexed later and there’s no need to keep requesting it.
Common causes on small sites are thin or near-duplicate pages, weak internal linking, and publishing many new URLs at once. Improve thin pages with genuinely useful detail, merge overlapping pages into one stronger page and redirect the rest, link to the page from relevant posts, and noindex or remove low-value URLs. Then use Validate Fix and wait.
Other Common Statuses
Some statuses need action and many don’t, so check before you fix anything.
| Status | Usually a Problem? | First Fix |
|---|---|---|
| Excluded by “noindex” tag | Only if the page should rank | Remove noindex (check your SEO plugin and WordPress settings), then request indexing |
| Soft 404 | Yes, for pages that should exist | Add real content, or return a proper 404 or 410 |
| Not found (404) | Not if the page is gone on purpose | Fix broken internal links or add a redirect |
| Duplicate without user-selected canonical | Usually yes | Add a self-referencing canonical to the main version |
| Duplicate, Google chose different canonical than user | Check it | Make sure your canonical points to the right page |
| Alternate page with proper canonical tag | Usually no | Confirm the canonical points to the preferred page |
| Page with redirect | Usually no | Nothing, if the redirect is intentional |
| Blocked by robots.txt | Only if unintended | Review your robots.txt rules |
Ignore statuses that simply confirm your own settings, such as redirects, canonicals, and noindex tags you added on purpose.
A Five-Minute Weekly Routine
A short routine beats occasional panic. Once a week, check the Pages report for new problem statuses, confirm your sitemap shows “Success,” and scan the Performance report for queries bringing visitors. Our Google Analytics 4 guide covers the matching traffic check, and our Shopify SEO guide shows how Search Console fits an online store.
Common Mistakes
The most common mistake is clicking Request Indexing repeatedly, which doesn’t fix underlying causes. Others include deleting pages without checking whether they matter, panicking over statuses that are normal, and publishing many thin pages at once. Also remember WordPress sites often have an SEO plugin controlling noindex and sitemaps, as covered in our guide to the best WordPress plugins for small business websites.
Frequently Asked Questions
Q1. How long does “Discovered – currently not indexed” take to fix?
For a few new pages, it often clears within days or weeks without action. If it stays for a long time, work through internal links, server health, and URL clutter.
Q2. Should I keep clicking Request Indexing?
No. The tool has a small daily limit and doesn’t fix root causes. Use it sparingly for important pages and rely on Validate Fix for batches.
Q3. Is “Crawled – currently not indexed” a penalty?
No. It means Google evaluated the page and chose not to index it, often because it’s thin, duplicated, or poorly linked.
Q4. Does every page on my site need to be indexed?
No. Redirects, duplicates with correct canonicals, and intentional noindex pages are normal. Focus on pages you want to rank.
Q5. Why does my WordPress site have pages excluded by noindex?
Check Settings, then Reading, for the “Discourage search engines” option, then your SEO plugin’s per-page and sitewide settings.
Conclusion
Google Search Console for beginners is easier once you separate harmless statuses from real problems. Treat “Discovered – currently not indexed” as a crawl-priority issue and “Crawled – currently not indexed” as a page-quality issue, fix the cause instead of resubmitting, and ignore statuses that just reflect your own settings. A five-minute weekly check will catch most real problems early.
