Recovery Playbooks
Crawled – Currently Not Indexed in Search Console: WordPress Fix Checklist
Classify affected WordPress URLs, fix canonical and internal linking problems, improve thin posts, and know when to request indexing.
Last reviewed: June 8, 2026
Crawled – currently not indexed in Search Console means Google reached the URL but did not add it to the index at the time reported. For WordPress sites, the cause is rarely one single switch. It can be thin article variants, weak internal linking, duplicated archive paths, stale sitemap entries, canonical mismatch, or pages that are technically reachable but not useful enough to keep.
This checklist is for WordPress site owners, agencies, and headless frontend teams reviewing real affected examples from Search Console. It assumes the URL returns 200 and is not blocked by robots.txt or noindex. If the page is blocked, fix that first.
Key takeaways
- This status is not always an error. Google can crawl a page and still choose not to index it.
- Fix examples, not totals. Start with 10 affected URLs and classify each one by template, content type, canonical signal, and internal links.
- For programmatic WordPress content, quality and uniqueness matter more than publishing volume.
Step 1: classify the affected URLs
Export or copy a sample from Search Console and group the URLs before making changes:
- Real articles: posts that should be indexed and receive search traffic.
- Pagination: archive pages such as
/blog?page=8or/?page=12. - Code sample paths: URLs that came from examples, plugin routes, REST routes, or copied snippets.
- Near-duplicate articles: posts with the same structure, same intro shape, and only a function name changed.
- Old or invalid URLs: routes that now return 404, redirect, or should never have been linked.
This matters because each group needs a different fix. Do not request indexing for everything. That often wastes crawl attention and leaves the root problem untouched.
Step 2: inspect the page Google saw
Use URL Inspection for a representative affected page. Check these fields:
- last crawl date
- whether crawling was allowed
- whether indexing was allowed
- user-declared canonical
- Google-selected canonical
- rendered HTML screenshot and loaded resources when available
If the canonical selected by Google is different from the page you care about, fix canonical and internal link consistency before rewriting the article. If Google saw an empty shell or a broken render, fix rendering before content.
Step 3: improve articles that deserve indexing
For real WordPress articles, rewrite around the searcher’s problem instead of the function name. A weak article titled WordPress rest_url Example often competes with official references. A stronger article answers an operational question:
- when to use the function
- what failure it prevents
- what a complete implementation looks like
- which mistakes cause production bugs
- how to validate the change after deployment
Use concrete sections: symptoms, cause, fix, validation, common mistakes, and related internal reading. Thin code examples are easy to crawl and easy to ignore. Troubleshooting pages with real decision criteria are harder to replace.
Step 4: reduce low-value URL discovery
WordPress and headless frontends can accidentally expose many URLs that do not need indexing. Review:
- archive pagination that has no search demand
- sample endpoints rendered as clickable links
- REST route examples that resolve against the public domain
- old slugs without useful redirects
- tag, category, author, and date archives with duplicate content
If a URL should not exist, return a clean 404 or remove the internal link that exposes it. If it should consolidate into another page, use a targeted redirect. If it is a valid supporting URL but not a search landing page, consider whether it needs to be in the sitemap at all.
Step 5: strengthen internal links
Google should not discover important articles only through a sitemap. Link priority articles from the homepage, archive, related reading blocks, and topically relevant posts. Use descriptive anchors that match the problem, not vague labels such as “read more”.
<a href="/blog/wordpress-admin-ajax-returns-minus-one-nonce-checks">
admin-ajax.php returns -1 nonce troubleshooting
</a>For a small site, internal links are one of the clearest signals you control. If a page has zero meaningful internal links, it is harder to argue that it is important.
When to request indexing
Request indexing only after a substantial fix: the page now has stronger content, correct canonical signals, clean rendering, and better internal links. If you changed only a typo or waited a day, let normal crawling handle it.
Related reading
If the affected examples are caused by a short sitemap, start with Search Console sitemap shows fewer pages than WordPress. If the examples are mostly redirect URLs, use the Page with redirect in Search Console guide.
