Blog / Technical SEO /

Fixing ‘Crawled – currently not indexed’

Google visited your page. It looked around. It left without adding it to the index. Frustrating, and Search Console files it under “Crawled – currently not indexed” without telling you why.

That status is a clue, not a command to hammer the request-indexing button. Start by checking that the page is accessible, useful and distinct. Confirm the canonical URL, internal links, sitemap status and content quality. Then improve what’s genuinely weak and give Google time to recrawl. There’s no guaranteed fix and no indexing timeline.

What the status means

“Crawled – currently not indexed” means Google has crawled the URL but has not currently indexed it. It differs from “Discovered – currently not indexed”, where Google knows about the URL but has not crawled it yet. Search Console statuses can change as Google processes pages.

The report does not provide a single diagnosis. A URL may be excluded because the page is very similar to others, offers limited value, has unclear canonical signals or is part of a site with crawl or quality issues. The cause varies, so don’t assume every URL with this status has the same problem.

First confirm that the status applies to the intended URL. Check trailing slashes, protocol, hostname, parameters and canonical tags. A page may point to another URL as canonical, or a duplicate version may be the one shown in the report.

Check technical access

Load the page as a visitor and inspect its status code. It should return the intended content rather than an error, redirect chain, login wall or soft 404. Confirm that robots.txt and meta robots directives do not block indexing, and that the canonical points to the preferred URL.

Use URL Inspection to see the tested page information, including the last crawl and Google’s reported canonical where available. The live test can confirm current accessibility, but it does not guarantee indexing. Check whether JavaScript is needed to render the main content and whether Google can access the resources required.

Look at the XML sitemap and internal links. A sitemap can help discovery, but inclusion does not force indexing. Pages should also have meaningful links from relevant sections of the site. An orphan page with no path for users or crawlers deserves an information-architecture review.

Assess whether the page should be indexed

Ask what distinct value the URL provides. Does it answer a useful question, contain original information or support a real customer task? Is it a filtered page, a print view, a thin tag archive or a near-copy of another URL? Some pages should not be indexed; focus on those you deliberately want searchers to find.

Compare the page with the site’s other content. If several URLs answer the same question, choose a primary resource and consolidate where appropriate. I wouldn’t create near-duplicates to target slightly different keyword phrasing. If a page depends on product or location data, check that the information is current and specific enough to help.

Improve the page with substance: correct facts, clearer explanation, useful comparisons, better navigation or original evidence. Do not add generic paragraphs just to reach a word count. If no meaningful improvement is available, consider whether the page is necessary.

Use indexing requests sparingly

After making a substantial change, request indexing through Search Console if the URL is eligible. Repeated requests do not guarantee a faster crawl or a different indexing decision. Give Google time to revisit the page and monitor the status.

For many URLs, fix the underlying template or data issue rather than submitting each URL manually. If a sitemap, canonical or internal linking problem affects a group, address the shared cause. Then inspect representative pages.

Look at the wider site

If many important pages share the status, examine the site’s overall quality and technical setup. Check for accidental noindex rules, canonical conflicts, duplicate templates, server errors, excessive low-value URLs and recent migrations. Use crawl data and server logs where available.

Don’t panic-delete pages or assume a manual penalty. Check Search Console for manual actions and security issues, but a no-index status can occur without either. Keep a log of changes and compare with the date of the last crawl.

A practical investigation order

I treat each URL as a small diagnosis, not a checklist to tick blindly. First compare the inspection result with the live page: does Googlebot receive a successful response, and does the rendered content include the main text? Check robots rules, a noindex directive and the canonical target. Then search your own site for close duplicates, including parameter versions, print pages or an older URL that still attracts internal links. If two pages serve the same need, decide whether one should be consolidated or whether both deserve clearer, distinct purposes.

Next look at discovery. Is the page linked from a relevant category or article, or does it appear only in a sitemap? A sitemap can help discovery, but it does not make a page valuable or guarantee indexation. Review whether the page answers a real need and whether it adds something beyond the pages already available. Make a focused improvement, update internal links if needed, and request indexing once after the page is ready. Then allow time and monitor the inspection result. Repeatedly submitting an unchanged URL does not reveal Google’s reasoning.

Pick one affected URL and inspect its canonical, content and internal links. What evidence can you find before you request indexing again?