My new answer pages say "crawled — currently not indexed". What does that mean?
It means the page was fetched and then not stored. That is a quality and duplication judgment far more often than a technical one. On answer hubs the usual causes are near-duplicate pages, pages that add nothing beyond what an existing page already says, and thin pages published in bulk. Changing crawl settings will not move it. Changing the page will.
Three states, three different problems
The states get conflated and they have almost nothing to do with each other.
- Discovered — currently not crawled. The URL is known but has not been fetched. This is a priority and capacity signal: your site is not being crawled as aggressively as you are publishing. Internal linking and publishing pace matter here.
- Crawled — currently not indexed. The page was read and judged not worth storing. This is about the content, full stop.
- Indexed but ranking nowhere. The page is stored and losing to better pages. That is a competition problem, not an indexation one.
The bulk-publish signature
The pattern to look for: a batch of pages published on the same day, of which a fraction gets indexed and the rest sits in crawled-not-indexed indefinitely. That is not random. It is the system storing the pages that add something and declining the ones that restate what it already has, including what it already has from you.
If your batch was generated from a keyword list rather than a deduplicated question list, expect this outcome. It is the visible consequence of the planning shortcut.
What to actually change
- Merge the near-duplicates. Usually the single highest-yield fix.
- Add real information gain. A distinction, a formula, a failure mode — something no other page on the topic states.
- Link it from a hub and from siblings. An unlinked page is a weaker candidate for storage.
- Reduce boilerplate share. If your template contributes more text than the answer does, the unique portion of the page is small.
- Slow the publishing pace. A steady cadence gets evaluated more favorably than a periodic dump, and it also matches what your review capacity can support.
Patience, and its limit
New pages sometimes sit for weeks before being indexed, so acting on day three is premature. But if a page has been linked, submitted and stable for well over a month and remains unindexed, waiting longer is not a strategy. Rewrite it or merge it.
The uncomfortable version of this diagnosis: unindexed pages are feedback. Treat a large unindexed batch as a message about the content system that produced it, not as a technical ticket — which is why we build the planning and dedup stages into content automation before the drafting stage, and why the answer hub is built question-first.
Topics: indexation · search console · diagnostics · scaled content
Have a version of this question about your own business?
The useful answer usually depends on which systems you run and how they're connected. That's a conversation, not a blog post.