Fix it

Crawled - currently not indexed: why Google skips a page, and what to change

Google read this page and decided not to add it to the index. That is a judgment about the page, so the fix is about the page: what it offers that others do not, and whether it should be indexed at all.

By Adem ÇakalPublished 5 sources
Short answer

Google crawled the page and did not index it. Its help page says this is common and not necessarily a problem, and for pages you care about it points you to URL Inspection to look for blocking or other issues. Google does not tell you the reason for each URL, so you work it out: first decide if the page deserves an index slot, then check what Google actually saw.

The difference from "discovered"

Here Google has already downloaded the page. If the last crawl date is empty instead, you are in the discovered, not crawled state, where the problem is access and timing. This page covers the case where the content was seen and passed over.

Should this page be indexed at all?

Answer this before touching any setting. Many URLs in this status are pages you would not miss.

  1. Does it answer a question a searcher would type, and does it answer it better or differently than the pages already in results?
  2. Does it contain information, data, a tool or a viewpoint that exists only here? Google's guidance asks whether content offers original information, reporting, research or analysis, and substantial value compared with other pages in results.
  3. Is it a variant of a page you already have (a tag page, a sort order, a print view)?
  4. Would you send a customer to it?

If the honest answer to the first two is no, indexing is not the fix. Merge it into a stronger page, redirect it, or leave it out on purpose. Google also warns against using extensive automation to produce content on many topics, and says generative text without manual oversight reflects little effort. That matters for template-built pages in particular.

Triage by page type

Page typeWhy it gets skippedWhat to change
Programmatic or template pageSame layout, a few swapped words; little beyond what sibling pages offerAdd a real asset per page (data, a tool, sourced examples). Cut pages that cannot get one.
Short blog postRestates what top results already sayAdd first-hand detail, a table or a worked example. Or merge into a longer guide.
Tag, category or date archiveList of links to content already indexed elsewhereUsually fine to leave unindexed. Keep out of the sitemap.
Paginated or filtered listingOverlaps page one of the same listAccept it, or consolidate. Do not chase indexing here.
Product or service page with little textNothing distinguishes it from the manufacturer's copy or neighboursWrite your own description, specs and use cases.
JavaScript-built pageMain text may be missing on first fetchCheck rendered HTML, then render on the server if needed.
Thank-you, login, cartNo search valueLeave unindexed.

This table is a way to form a hypothesis. Google does not publish per-URL reasons, so no row is a guarantee.

Check what Google saw: URL Inspection steps

  1. Inspect the URL and read the indexed view. Google notes this is the stored version, not a live test, so it shows what the crawl actually captured.
  2. Read the Crawl and Indexing fields. Page fetch should be successful, crawl allowed should be yes, indexing allowed should be yes. Compare the user-declared canonical with the Google-selected one.
  3. Run the live test and view the rendered page. Check that your main text, headings and links are present. A page that renders empty is a different problem from a page that renders fine and is judged unhelpful.
  4. Look for a soft 404. A page with almost no content, or an error page that returns status 200, can be treated as a soft 404.

A quick test of whether the text exists before any script runs:

curl -s https://example.com/your-page/ | grep -c "a distinctive sentence from your page"

A count of 0 means the sentence is built by JavaScript. Google's JavaScript guide says pages with a 200 status are queued for rendering and that server-side or pre-rendering is still a good idea. That applies to client-rendered setups in Next.js, Framer exports or custom React front ends. WordPress themes usually print text in the HTML, so look at content before rendering.

After a crawl, a page is judged on content and duplication, with three outcomes Crawled HTML fetched Rendered scripts run Judged value and overlap Indexed Crawled, not indexed (this status) Duplicate of another URL
Simplified from Google's JavaScript SEO and Page indexing documentation. Google does not publish the exact decision rules.

What to change first

Pick one page and change something a reader would notice, not the word count. Add a worked example, a table, a diagram, a short sourced section or a tool. Then link to the page from two or three related pages that are already indexed. After that, ask for indexing once and wait.

If many pages show the same status, fix the template, not each page. Example: if 300 location pages differ only by a city name, improving ten of them tells you more than resubmitting all 300.

Do not mass-delete or mass-noindex on a hunch. Export the list, group it by page type, and decide per group. Pages that get search traffic should never be touched on the basis of this status alone.

When the status lists a URL that should merge into another one, the answer is on the duplicate canonical page instead.

Questions people ask

Is Crawled - currently not indexed an error?

Google's help page says it does not index every page on the web, so the status is common and not necessarily a problem. It matters when the page is one you want to rank.

Will resubmitting the URL get it indexed?

Not by itself. Google says a request does not guarantee indexing and repeating it does not speed things up. If you did not change the page, Google will probably reach the same decision.

Can JavaScript rendering cause this status?

It can contribute. Google queues pages for rendering after crawling, and a page whose main text appears only after scripts run may look empty on the first pass. Server-side or pre-rendering removes that risk.

How long should I wait after improving the page?

Google says reprocessing takes days to weeks, depending on when it recrawls. Request indexing once for the improved URL, then check the Inspection result after a few weeks rather than daily.

Sources

  1. Search Console Help: Page indexing report, accessed 2026-11-12.
  2. Search Console Help: URL Inspection tool, accessed 2026-11-12.
  3. Google Search Central: Creating helpful, reliable, people-first content, accessed 2026-11-12.
  4. Google Search Central: Understand JavaScript SEO basics, accessed 2026-11-12.
  5. Google Search Central: Ask Google to recrawl your URLs, accessed 2026-11-12.