Why Google Is Not Indexing My Page: "Crawled" and "Discovered – Currently Not Indexed"

Open the Page indexing report in Google Search Console and you'll usually find two large groups of URLs under "Why pages aren't indexed": Crawled – currently not indexed and Discovered – currently not indexed. They sound alike. They point to different problems, and the fixes are different too.

What the two statuses mean

Discovered – currently not indexed

Google knows the URL exists, from a sitemap or a link, but hasn't crawled it yet. Google's own explanation is usually that it planned to crawl the URL but rescheduled, often because crawling the site was expected to overload the server. In practice it also shows up when Google doesn't see enough value in the URL to prioritise it.

This is mostly a crawl priority problem.

Crawled – currently not indexed

Google fetched the page and decided not to index it, at least for now. Google says the URL may or may not be indexed in the future and that you don't need to resubmit it.

This is mostly a quality or duplication problem. Google saw the content and wasn't convinced.

Mixing them up is the most common mistake. Asking for more crawls of a "Crawled – currently not indexed" page doesn't help, because Google has already seen it.

Fixing "Discovered – currently not indexed"

Common causes

• Weak internal linking. The URL is only in the sitemap, or only linked from deep paginated pages.
• Too many low-value URLs. Faceted navigation, tag archives, session parameters and near-duplicate pages compete for crawl attention.
• Slow or unreliable server. If responses are slow or return errors, Google reduces how much it crawls.
• A brand-new site. New domains have little crawl history, so Google moves cautiously.

Fixes

1. Link the page from somewhere Google crawls often. Your homepage, main category pages, a "latest posts" block or a relevant, popular article.
2. Reduce crawl waste. Use robots.txt to keep crawlers out of parameter variations and internal search results. Keep noindex for pages that need to be crawlable but shouldn't be indexed. Remember that a robots.txt block stops Google from seeing a noindex tag, so don't combine both on the same URL.
3. Clean your sitemap. Only canonical, indexable 200 URLs, with accurate lastmod dates. Google ignores priority and changefreq, but it does use lastmod when it's consistently accurate. Check yours with the sitemap validator.
4. Improve server response. Look at the Crawl stats report in Search Console for response time and host status problems.
5. Create more discovery signals. External links and other legitimate signals give Googlebot more reasons to fetch the URL. This is where an indexing service can help, because the issue really is getting the crawl.

Fixing "Crawled – currently not indexed"

Common causes

• Thin content. Short pages that add nothing beyond what's already indexed elsewhere.
• Near-duplicates. Product variants, location pages with only the city name changed, tag pages that repeat category pages.
• Low perceived usefulness. Pages that exist for search engines rather than people, such as auto-generated pages or boilerplate-heavy templates.
• Canonical confusion. Signals point different ways, for example the canonical tag says one URL while internal links and the sitemap say another.
• Rendering problems. The main content only loads through JavaScript that fails or times out during rendering, so Google sees an almost empty page.
• Timing. Sometimes it's just recent. Pages can move out of this status on their own after a re-crawl.

Fixes

1. Make the page clearly worth indexing. Add original information, answer the question better than the pages already ranking, and remove boilerplate that hides the real content.
2. Consolidate duplicates. Merge near-identical pages, redirect the extras with 301s, or canonicalise them to the strongest version.
3. Align your signals. The canonical tag, internal links, sitemap entries and hreflang should all point at the same URL.
4. Check the rendered HTML. Use URL Inspection's live test and view the rendered page. If the main content is missing, fix the rendering.
5. Strengthen internal links. Links from relevant, indexed pages tell Google this page matters on your site.
6. Then request a re-crawl. After a substantial change, Request indexing in Search Console (or an indexing service for many URLs) makes sense, because now there's something new to evaluate.

Rule out the basics first

Before you dig into quality, rule out mechanical blockers. They're quicker to find and quicker to fix:

• A noindex meta tag or X-Robots-Tag header left over from staging
• A canonical tag pointing to a different URL
• A robots.txt rule blocking the path
• A non-200 status code, a redirect chain, or a soft 404
• The wrong URL version in your sitemap (http vs https, www vs non-www, a trailing slash mismatch)

The indexability checker tests status, robots directives and canonicals in one go. The robots.txt tester shows which rule, if any, blocks a given URL.

A triage order that works

1. Confirm the current status. Reports can lag behind, so check the specific URL with URL Inspection or the index checker.
2. Rule out mechanical blockers.
3. If it says Discovered: work on crawl priority (internal links, sitemap, crawl waste, discovery signals).
4. If it says Crawled: work on the page (content, duplication, canonicals, rendering).
5. Request a re-crawl only after you've changed something meaningful.
6. Give it time, and re-check after a week or two.

For a full list of setup checks on a new site, see the indexing checklist for a new website.

Where QuickIndexx helps, and where it doesn't

QuickIndexx is useful when the problem is getting crawled, as with "Discovered – currently not indexed" pages and new URLs. We push URLs through discovery channels and show when the crawler visits. If no crawl happens within 24 hours, the credit goes back. For "Crawled – currently not indexed", the fix is on the page itself, and we'd rather tell you that than sell you submissions that won't change Google's decision. See pricing for plans.