This report has been viewed 331 times • Share your own site's results at cite-met.com
This report was scored with our older rules. Rescan to see the current result.
Your C.M.E.T. Score
Critical Issues Found. Only 2/10 points scored. Bots likely cannot read your content.
How AI answer engines read this page
Visitors see the rendered page. Right now, answer engines are reading much less of it.
✨ Beautiful, interactive experience with full JavaScript rendering
<div id="root"></div><!-- IMPORTANT: DO NOT REMOVE THIS SCRIPT TAG OR THIS VERY COMMENT! -->
⚠️ Limited static HTML - AI may miss your content
Why this matters for citability
ChatGPT, Claude and Perplexity don't document that their crawlers run JavaScript, so content that only appears after scripts run may be missed. Google renders JavaScript.
When the important content only appears after the browser runs that JavaScript, a crawler that doesn't run it can land on a near-empty <body> and have little to read. The more of your content that ships as static HTML, the more an engine can cite, reference, or recommend it.
Core Fundamentals
Static HTML Content
Worth 5 points • 0.0/5 scored
AEO (Answer Engine Optimization)
AI Crawler Requirements
Worth 2 points • 0.0/2 scored
SEO (Search Engine Optimization)
Traditional Search Requirements
Worth 3 points • 2.3/3 scored
Why "Fix my SEO" prompts rarely move this score
You might be tempted to ask Cursor, Lovable, or Bolt to "Fix my SEO." That alone usually isn't enough, because citability is set by your build and serving setup, not just by page code.
How the page gets rendered
AI builders generate source code (React/Vue/Svelte). Whether an answer engine sees real content depends on how that code is rendered and served.
Keeping routes and sitemaps in sync
Simply adding a sitemap.xml file isn't enough. As you add new pages, the sitemap has to keep up so engines can discover every route.
Hard-coding this once tends to drift into broken links and stale indexing, so generate it from your routes in your build. The Sitemap check (CM-203) looks for it. We check your sitemap, but we don't write it.
Staying interactive after pre-render
To be both interactive (for users) and readable as static HTML (for bots), you need the right hydration setup.
Your framework does this: Next.js, Astro, Nuxt and TanStack Start send the HTML first, then hydrate it in the browser. cite-met serves what your build outputs and adds only its measurement scripts.
🛠️ Developer Resources
Want to fix this manually? Here's everything you need to get started.
