Crawlability and Core Web Vitals
Robots, sitemaps, canonicals, hreflang, render budget, and CWV scored for every top template, with the issues that block schema from being discovered.
What it actually is
I crawl your site with RankLabs configured to emulate both Googlebot and the major AI engine fetchers. Then I score the things that block discovery: robots.txt rules, sitemap accuracy, canonical chains, hreflang clusters, JS rendering vs raw HTML schema delivery, and Core Web Vitals across the same template set the schema audit covers.
Marketers run Lighthouse, hand you a CWV score, and stop there. The question that matters for schema work is different: is the JSON-LD in the initial HTML response, or is it injected client-side after hydration? Most AI engine fetchers don't execute JavaScript. If your schema only appears post-hydration, the scan tells you which engines see nothing and which templates the gap shows up on.
Deliverables
- Crawl report flagging robots, canonical, sitemap, and hreflang issues by URL
- JS-rendered vs raw-HTML schema delivery analysis per template
- Core Web Vitals scored across mobile and desktop for the same template set
- AI engine fetcher accessibility check (ChatGPT, PerplexityBot, ClaudeBot, GoogleBot, GoogleOther)
- Crawl budget analysis for sites over 10K URLs
What breaks without it
If the crawler can't reach the schema, none of the schema work matters. I've seen sites where every PDP has clean JSON-LD, the validator passes, and AI engines still ignore the entity, because the schema is loaded by a tag manager script three seconds after first paint. The schema technically exists. To anything that fetches without rendering JS, it doesn't.
The other recurring failure: a robots.txt rule blocking a path the marketing team forgot they added during a 2022 launch. Six templates worth of schema invisible to every engine. Found in eight minutes. Fixed in one line.
How it fits the Audit
Crawlability findings often reorder the roadmap. There's no point scoring revenue impact on a Product schema fix if the page is canonical-pointed at a parent collection that never resolves. This artifact catches the upstream blockers before they pollute the impact model.
The full Audit breakdown
- 01componentSchema graph auditOpen
- 02componentAI visibility scanOpen
- 03currentCrawlability and Core Web Vitalsyou are here
- 04componentRevenue impact per fixOpen
- 05component90-day remediation roadmapOpen
Stop pouring budget into a broken foundation.
If your SEO retainer hasn’t compounded, your AI citations have stalled, or your last technical audit ended in a deck nobody read, that’s not a content problem. It’s an engineering problem. The same engineer who diagnoses ships the fix.