IndexingWordPress
Indexing failure path
WordPress Discovered — Currently Not Indexed
Discovered currently not indexed often means Google found the URL but has not treated it as worth crawling yet. On WordPress sites, the cause commonly sits in crawl priority, internal linking, sitemap-only pages, weak archives, or unstable server response.
TRIGGERS / WHEN
When this usually appears
- after launching many new URLs
- after submitting sitemap-only pages
- after publishing thin archive pages
- after migration or URL structure changes
- after slow hosting or cache problems
ROOT PATHS / WHY
Where the failure often sits
- low crawl priority
- deep or missing internal links
- too many weak sitemap URLs
- tag or archive bloat
- slow or unstable response
- similar templates competing for attention
- new URLs with no supporting links
FIRST PASS
Checks closest to the symptom
internal-link depth
sitemap-only URL patterns
server response and cache state
GSC crawl and discovery timing
archive footprint
priority links from hubs and templates
SPRINT OUTPUT
Fix or implementation-ready path
- identify why URLs are discoverable but low priority
- fix safe sitemap, link, template, or response issues
- separate URLs to strengthen from URLs to prune
- hand off a crawl-priority cleanup path
VERIFICATION
The change needs a second measurement
- GSC URL Inspection
- crawl sample
- sitemap review
- server response checks
- internal-link crawl
USEFUL INPUT
What helps reproduce it
- affected URL examples
- GSC discovery state
- sitemap URL
- what changed recently
- WordPress and GSC access
SCOPE BOUNDARY
What this path does not promise
- mass URL submission
- backlinks
- content calendar
- ranking guarantee
- sitewide redesign
RELATED FAILURE PATHS
Continue only when the symptom crosses a layer
START / Indexing
Have the URL and one exact symptom?
The remaining technical context can stay collapsed unless it helps reproduce the failure.