SEO · AEO · GEO Analyzer
The dnsverifier.com SEO / AEO / GEO Analyzer audits any page across three pillars at once: SEO (Search Engine Optimization — title, meta, canonical, headings, Open Graph, robots.txt, XML sitemap), AEO (Answer Engine Optimization — FAQ schema, question-style headings, direct-answer copy, semantic HTML for featured snippets and voice), and GEO (Generative Engine Optimization —
llms.txt, AI-crawler access for ChatGPT / Claude / Perplexity / Gemini, structured-data entity grounding, author E-E-A-T and freshness so your content gets cited). It returns a 0–100 score per pillar with live SERP & social previews, a full meta / link / script inventory, and copy-paste fixes. Results stream live.Frequently asked questions
- What is the difference between SEO, AEO, and GEO?
- SEO (Search Engine Optimization) is the classic discipline of ranking in Google/Bing results — titles, meta tags, canonical URLs, headings, structured data, sitemaps, and links. AEO (Answer Engine Optimization) optimizes for direct answers: featured snippets, voice assistants, and the answer boxes that lift a single passage to the top — it rewards FAQ schema, question-style headings, and concise direct-answer copy. GEO (Generative Engine Optimization) optimizes to be cited by generative AI engines like ChatGPT, Perplexity, Claude, and Google's AI Overviews — it depends on letting AI crawlers in (robots.txt, llms.txt), clear entity grounding via schema.org, named authorship (E-E-A-T), freshness, and citable facts.
- How does the GEO score work — does blocking AI crawlers hurt it?
- GEO measures whether generative engines can both access and confidently cite your content. The analyzer checks /llms.txt, your robots.txt rules for the major AI crawlers (GPTBot, OAI-SearchBot, ClaudeBot, PerplexityBot, Google-Extended, Applebot-Extended, CCBot and more), structured-data richness, Organization/sameAs entity identity, author/E-E-A-T signals, freshness dates, and citation density. If your robots.txt blocks answer-engine crawlers, the AI-access check flags it — those engines can't crawl you, so they won't cite you. That may be intentional; the tool surfaces the trade-off rather than forcing a choice.
- What is llms.txt and why does it matter for GEO?
- llms.txt is an emerging convention (llmstxt.org): a plain-text file at your site root that tells AI crawlers what the site is, which pages are canonical, and what is safe to cite — the AI-era equivalent of robots.txt + sitemap.xml. The analyzer checks whether /llms.txt exists and counts it as a positive GEO signal because it makes your content easier for generative engines to summarize accurately.
- Does this audit run JavaScript / render the page like Googlebot?
- No — it fetches the server-rendered HTML and parses it directly (it does not execute client-side JavaScript). For server-rendered and statically-generated sites this matches what crawlers index first. For single-page apps that inject content with JavaScript, the word-count and content checks may under-report; the fix is to server-render or pre-render critical content, which is also what crawlers prefer.
- Which checks affect the score and which are informational?
- Each pillar score is a weighted percentage: a passing check earns full weight, an 'Improve' (warn) earns half, and a 'Fail' earns zero. Purely observational items (like images when a page has none) are marked Info and excluded from scoring. The overall score blends the three pillars (SEO 40%, AEO 30%, GEO 30%) and maps to an A+ to F grade.
- How does this compare to Ahrefs, Semrush, SEOptimer, or metatags.io?
- Those are excellent commercial suites (some paid, some freemium). This is a free, single-page, no-signup audit that adds the AEO and GEO pillars most classic SEO tools don't cover yet — explicit AI-crawler access analysis, llms.txt detection, and answer-engine readiness — alongside the standard on-page metadata, structured-data, SERP/social previews and full meta/link/script inventory you'd expect from a tag inspector.