WordPress diagnosis guide

Public crawl evidence versus WordPress evidence.

The public response is what visitors and search engines received. The WordPress record can explain how that response was produced, but it should never replace the public observation.

Get access →Explore workspace ↗
Complete evidence✦Explicit boundaries✦Verifiable outcomes
01

What the public crawl proves

  • Delivered status, redirects, HTML, metadata, headings, links, schema, and assets
  • Public-edge cache and response evidence
  • The discovery route and captured source context
  • The configured crawl coverage—not private unpublished inventory
02

What WordPress can explain

  • Post status, type, language, template, and modification record
  • Explicit SEO fields versus excerpts and rendered fallbacks
  • Referenced attachment metadata
  • Whether a public symptom is shared by a CMS template or record type
03

Why read-only matters

Diagnosis and mutation should have different permissions. A connected audit can make the repair path precise without giving the crawler authority to edit production content.

Continue exploring
Product

Connect the public defect to the WordPress record behind it.

Join public crawl evidence to a read-only WordPress snapshot for clearer diagnosis of templates, translations, metadata, posts, and referenced media.

Open →Solution

See the delivered page and the CMS cause side by side.

Audit a WordPress site from the public edge, then enrich selected crawl evidence with a read-only CMS snapshot for clearer fixes.

Open →SEO check

Missing or derived meta descriptions

Separate truly missing meta descriptions from CMS excerpts, theme fallbacks, empty SEO fields, and derived visible copy.

Open →
Self-service SaaS

Connect a site and run the workflow yourself.

Get the full technical SEO toolkit on every plan. Choose the number of websites you need and use the same crawling, investigation, and verification workflow.

Get access →