Search Console Crawled, Not Indexed on WordPress: What To Fix
Crawled, not indexed is not one single bug. It can come from duplicate pages, weak content, soft 404 behavior, canonical confusion, render problems, internal link gaps, or a page Google simply does not think is worth indexing yet.
Use this when important WordPress blog posts, service pages, location pages, or WooCommerce pages show Crawled, not indexed in Search Console.
Quick answer
Start with evidence, not a plugin setting. The first useful checks are: Confirm the page returns 200 and is not blocked by noindex. Check the canonical tag and make sure it points to the clean public URL. Compare the page to similar indexed pages and improve unique value. Keep every change small enough to reverse.
Fast diagnosis map
Use this map before changing production. It helps separate a real platform issue from a cached page, stale setting, or missing handoff.
| Signal | What it means | Useful next check |
|---|---|---|
| Duplicate title | Check access, users, or ownership first | Check status and noindex |
| Thin body | Look for a configuration, plugin, or data mismatch | Fix canonical |
| Wrong canonical | Inspect the layer most likely to be hidden from the normal UI | Improve unique answer |
| No internal links | Prove whether the problem is still active | Add internal links |
What to check first
- Confirm the page returns 200 and is not blocked by noindex.
- Check the canonical tag and make sure it points to the clean public URL.
- Compare the page to similar indexed pages and improve unique value.
- Add internal links from relevant live pages, not only from the sitemap.
- Check rendered HTML if the site is a React app, headless frontend, or heavily cached page.
Run a focused check
These commands or fields give you a useful starting point. Adapt paths, IDs, and privacy handling to the site before running anything on production.
curl -sSI https://example.com/blog/example-post
curl -sS https://example.com/blog/example-post | grep -Ei 'canonical|noindex|title|description'
curl -sS https://example.com/sitemap.xml | grep 'example-post'
Safe fix order
Do the work in this order so each result can be verified. If a step fails, stop and capture the evidence before making a broader change.
- Check status and noindex
- Fix canonical
- Improve unique answer
- Add internal links
- Resubmit sitemap
Verification checklist
The fix is not done when the warning disappears. Confirm the result from the visitor side, admin side, and reporting side.
- The canonical URL and sitemap URL match.
- The page has enough original, helpful content to stand alone.
- The rendered HTML includes title, meta description, body content, and links.
- A related indexed page links to the URL naturally.
Mistakes to avoid
- Do not judge the result by the homepage only.
- Do not clear every cache layer until you know which layer affects the symptom.
- Do not delete evidence before copying filenames, timestamps, versions, and affected URLs.
- Do not make privacy or crawler decisions without writing down the business reason.
- Do not leave temporary debug settings, test accounts, or broad permissions in place.
When HandL WP should help
Bring in help when the issue affects leads, checkout, ads, malware risk, search visibility, or a client production site. HandL WP can trace the problem through WordPress, hosting, tracking, cache, and Search Console, then verify the business workflow after the technical fix.
If this is active on a production site, fix WordPress indexing issues.