Get a complete SEO + GEO report in about 30 seconds
A full audit across 9 SEO dimensions and 9 GEO dimensions — 60+ checks in total — with a fix list ranked by impact.
JSON-LD Schema Studio
Five GEO-ready templates. Fill in the fields and get deployable markup. Prefill from your latest audit, then validate structure and completeness before you ship.
Article
Output
Click "Generate JSON-LD" to see the markup here.
Deployment rules (read before shipping)
- Place the snippet inside the page's
<head>. Use one matching type per page — do not stack multiple types. - No fabricated data. Dates, headlines and answers must match the visible page. AI can verify this, and mismatches hurt rankings.
- Do not ship template placeholders. Generic boilerplate has no GEO value.
- Always validate. A single JSON punctuation or bracket error makes the block unreadable to AI.
JSON-LD validator
Audit history
Results are stored in your browser's localStorage and never uploaded. The latest 30 audits are kept so you can track score changes before and after fixes.
Recent audits
How this works
What the audit measures, how scores are calculated, and how to turn the results into fixes.
1. What problem does this solve?
Traditional SEO gets you found and ranked in search results. GEO (Generative Engine Optimization) gets you understood, trusted and cited by AI answer engines. This tool audits both tracks and returns a prioritized action list.
SEO dimensions
- Crawlability & indexing (robots.txt, sitemap, noindex, redirects)
- URL structure (HTTPS, canonical, parameters, path depth)
- Titles, descriptions & keywords (title tag, meta description, overlap)
- Heading structure (single H1, H2 sections, hierarchy)
- Content quality (word count, paragraphs, keyword density)
- Mobile & baseline compatibility (viewport, lang, charset, alt text)
- Link structure (internal links, anchor text, outbound sources)
- Performance & UX (response time, page size, compression, CWV estimate)
- Social sharing (Open Graph, Twitter Card)
GEO dimensions
- JSON-LD structured data (presence, validity, type match, fields, consistency, stacking)
- Answer-first structure (filler openers, extractable first sentence, question subheads)
- Semantic precision (hedging language, subjective superlatives)
- Verifiable information density (numbers, years, percentages, standards)
- Self-contained answers (FAQ block, link dependency)
- Structured evidence (lists, tables, paragraph length, table of contents)
- Authority signals (published date, byline, citations)
- Content differentiation (original data, generic filler)
- AI citation readiness (paragraph length, definition density, key takeaway)
2. How scoring works
Why weight GEO higher? AI answers are a new acquisition channel, and structured data is the standard technical entry point for GEO, so the return per hour is usually higher than more content work. To favour SEO instead, change the 0.45 / 0.55 coefficients in analyze() inside lib/analyzer.js.
| Score | Grade | What it means |
|---|---|---|
| 90 - 100 | Excellent | Meets the bar for priority AI citation |
| 75 - 89 | Good | Solid foundation; close the gaps to move up quickly |
| 60 - 74 | Fair | Clear gaps remain; work through the action list |
| 40 - 59 | Weak | Key elements missing; AI cannot read or trust the page reliably |
| 0 - 39 | Critical | Blocking issues; fix immediately |
3. Recommended workflow
- Foundation (highest SEO priority): fix crawling, indexing, duplicate URLs and mobile basics. Start with the Crawlability & Indexing, URL Structure and Mobile & Baseline Compatibility dimensions.
- Technical layer (highest GEO priority): generate and deploy JSON-LD in Schema Studio. This is usually the fastest win.
- Content layer (the core of GEO): rewrite key pages to lead with the conclusion, back it with structured evidence, and use specific data. Focus on Answer-First Structure, Semantic Precision and Verifiable Information Density.
- Authority layer: build relevant backlinks for SEO and earn mentions across authoritative sources for GEO.
- Measure and iterate: re-audit after changes and compare results in History.
4. FAQ
- Why did the fetch fail?
- Common causes: a typo in the domain, the site is not publicly reachable, a timeout, or bot protection returning 403/503. Switch to "Paste HTML" to audit offline.
- How accurate is the Core Web Vitals score?
- It is a server-side estimate based on response time, document size, compression and lazy loading. It is not a substitute for real LCP, CLS or INP measurements. Use PageSpeed Insights or field data for exact numbers.
- Does the audit modify my site?
- No. It is read-only: it fetches the page, robots.txt and sitemap.xml, and writes nothing.
- Does it support JavaScript-rendered pages?
- No. It analyzes the HTML returned by the server, not the DOM after JavaScript runs. Client-side rendered sites will score lower, which is expected and is itself a signal worth acting on.