Advanced SEO Audit

Advanced Technical SEO Audit, Core Web Vitals (INP) & GEO/AEO Compliance Engine

Advanced SEO Audit & GEO/AEO Compliance Engine is an enterprise-grade technical SEO scanner, Core Web Vitals (INP) diagnostic tool, and Generative Engine Optimization (GEO) benchmarking engine for BrowserMesh. It unifies traditional technical crawling (canonicals, robots.txt, hreflang reciprocity, Soft 404s) with modern AI search citability, RFC 9309 bot permissions, client-side hydration parity, and Schema.org 2026 deprecation linting.

The cloud-native, next-generation alternative to Screaming Frog SEO Spider ($259/yr), Semrush Site Audit, Ahrefs Site Audit, and Google Lighthouse CLI.

📑 Quick Navigation Table of Contents

• 🤝 Perfect Companion Ecosystem Pairing
• 🎯 Target Audience & Industry Solutions
• 🚀 Key Features & Capabilities
• 📊 Output Data Contract (Pristine 15 Top-Level Fields)
• 📊 Industry Benchmark Comparison
• ❓ Frequently Asked Questions (FAQ)

🤝 Perfect Companion Ecosystem Pairing

Advanced SEO Audit pairs seamlessly with other BrowserMesh professional audit plugins:

• accessibility-auditor: Covers the entire DOM accessibility and legal compliance surface — WCAG 2.1 & 2.2 AA/AAA, European Accessibility Act (EAA) requirements, live computed color contrast (4.5:1 / 3:1), 24px target sizing, sticky focus obstruction (F110), and HTML5 landmarks.
• image-seo-auditor: Specializes in deep media optimization — descriptive alt text heuristics, modern formats (AVIF/WebP), responsive <picture> tags, Google Image Sitemaps, and layout shift dimensions.
• competitor-on-page-comparison: Provides head-to-head multi-URL competitive analysis — keyword density, content gap extraction, and entity n-gram tokenization.

Together, these companion plugins deliver a complete, 360-degree digital performance and technical compliance suite.

🎯 Target Audience & Industry Solutions

• Technical SEO Directors & Digital Agencies: Audit client domains at scale. Identify complex canonical loops, hreflang syntax errors (en-UK trap), render-blocking resources, and client-side hydration mismatches before they cause ranking drops.
• Generative Search Strategists & Content Teams: Optimize websites for AI synthesis engines (Google AI Overviews, ChatGPT Search, Perplexity AI, Claude Citations). Measure brand citability using Princeton University research heuristics and structure content with atomic Answer Nuggets.
• Web Architects & Performance Engineers (Next.js, Nuxt, Remix, Shopify, WordPress): Ensure SPAs and headless websites maintain strict rendering parity between server-rendered raw HTML and client-hydrated DOM. Eliminate LCP hero lazy-loading and excessive DOM complexity that degrades INP.
• E-Commerce & Enterprise Site Owners: Protect organic visibility by ensuring dedicated AI search crawlers (OAI-SearchBot, Claude-SearchBot, PerplexityBot) are permitted while safeguarding proprietary data from training scrapers.

🚀 Key Features & Capabilities

1. 2026 Generative Engine Optimization (GEO) & AEO Engine

• Princeton University Citability Model: Evaluates pages using empirical heuristics proven to increase LLM source citation likelihood by +30% to +40% (quantitative statistics density, expert quotations, authoritative outbound links, and HTML <table> data matrices).
• Answer Nuggets Readiness: Detects structured conversational question subheadings (What, Why, How, Compare, vs, Cost) paired with atomic 40–80 word direct answer definitions placed within the first 100 words.
• Machine-Readable Standard (/llms.txt & /llms-full.txt): Auto-discovers and validates the Answer.AI standard site map at the root domain, validating markdown structure and byte size limits (< 500KB).
• Web MCP Discovery: Inspects client-side tool discovery interfaces for autonomous web agents.

2. AI Crawlers & Web Bots Permission Matrix (RFC 9309 Compliant)

• Search vs Training Separation: Strictly decouples AI Search bots from AI Model Training scrapers. Sites that block training scrapers (GPTBot, ClaudeBot) for copyright protection are never penalized in SEO scoring as long as real-time search crawlers are allowed.
• 12+ AI Bot Catalog:
  • Search Bots: OAI-SearchBot (ChatGPT Search), Claude-SearchBot (Anthropic Search), PerplexityBot (Perplexity AI).
  • Training Bots: GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Meta-ExternalAgent, Bytespider, CCBot, Diffbot.
• RFC 9309 Rules Engine: Applies longest matching prefix precedence and equal-length Allow tie-breakers.

3. Core Web Vitals 2026 & Anti-Pattern Diagnostics

• Interaction to Next Paint (INP): Permanent Core Web Vital replacing FID ($\le 200$ms Good baseline). Isolates render-blocking scripts in <head> (excluding HTML5 type="module") and excessive DOM complexity (> 2,500 nodes).
• LCP Hero Lazy-Loading Anti-Pattern: Detects top-fold banner/hero images marked with loading="lazy" (which delays LCP discovery by 1,000–2,500ms) and flags missing fetchpriority="high".
• Cumulative Layout Shift (CLS): Flags images, videos, and dynamic embeds missing explicit width and height attributes or CSS aspect-ratio.
• Modern Image Adoption: Computes the exact adoption percentage of next-generation WebP, AVIF, and SVG image formats.

4. Technical SEO, Canonicals & BCP 47 Hreflang Linter

• Canonical Status Taxonomy: Classifies canonical tags into self_referencing, mismatch, missing, multiple, cross_domain, and invalid. Flags relative canonical anti-patterns (/page instead of https://...).
• Hreflang BCP 47 Linter: Validates ISO 639-1 language and ISO 3166-1 country codes. Flags the colloquial en-UK trap (suggesting en-GB), underscore separator errors (en_US -> en-US), missing self-reference tags, and missing x-default global fallbacks.
• Soft 404 Detection: Heuristically flags HTTP 200 OK responses served on empty error shells, missing product grids, or thin pagination templates.
• Client-Side Hydration Parity: Compares raw HTTP response HTML against fully hydrated Playwright DOM across 7 core SEO tags (Title, H1, Meta Description, Canonical, Meta Robots, Internal Links, Structured Data) to flag js_dependent and critical_mismatch risks.

5. Structured Data 2025/2026 Deprecations Linter

• 2025/2026 Deprecations Awareness: Detects deprecated schemas including FAQPage (fully deprecated by Google on May 7, 2026), HowTo (mobile deprecated), Course Info, Claim Review, Estimated Salary, and Special Announcement.
• High-Value Schemas: Validates required entity fields for Product, Article, Organization (sameAs array), and LocalBusiness.
• Cycle-Safe JSON-LD Unroller: Non-recursive traversal handling complex @graph arrays and circular references safely.

6. Calibrated 0–100 Health Scoring Engine

• Multi-Category Base (100 Points): Technical (25), On-Page (20), Content Quality & E-E-A-T (20), Mobile & Core Web Vitals (15), Structured Data (10), AI Search & GEO (10).
• Hard Severity Ceiling Caps: Fatal errors cap the maximum attainable score:
  • HTTP Failure (4xx/5xx): Hard Cap = 0 (Grade F)
  • Soft 404 Error State: Hard Cap = 45 (Grade F)
  • Accidental Noindex: Hard Cap = 49 (Grade F)
  • Missing Title & H1: Hard Cap = 55 (Grade D)
  • Insecure Plain HTTP: Hard Cap = 65 (Grade C)
  • Critical Hydration Mismatch: Hard Cap = 70 (Grade C)

📊 Output Data Contract (Pristine 15 Top-Level Fields)

Every audited URL yields a structured JSON object strictly conforming to the 15 top-level fields contract, designed to trigger all advanced visual features in scraper_frontend:

{
  "url": "https://example.com/guide/seo",
  "title": "The Complete SEO and AEO Optimization Guide 2026",
  "score": 97,
  "grade": "A+",
  "status": "optimal",
  "statusCode": 200,
  "loadTimeMs": 420,
  "issuesCount": 1,
  "categories": {
    "technical": 25,
    "onPage": 20,
    "contentQuality": 20,
    "mobileUx": 12,
    "structuredData": 10,
    "aiSearchGeo": 10
  },
  "technicalSeo": {
    "indexable": true,
    "isSoft404": false,
    "canonical": {
      "url": "https://example.com/guide/seo",
      "status": "self_referencing"
    },
    "robotsDirectives": ["index", "follow", "max-image-preview:large"],
    "sitemapFound": true,
    "redirects": { "isRedirect": false, "hops": 0 },
    "protocol": { "isHttps": true, "hsts": false },
    "renderParity": { "status": "parity_verified", "missingInRawHtml": [] },
    "htmlSizeKb": 84.5,
    "mixedContentLinksCount": 0
  },
  "onPageSeo": {
    "titleLength": 49,
    "titleStatus": "optimal",
    "descriptionLength": 137,
    "descriptionStatus": "optimal",
    "headings": {
      "h1Count": 1,
      "h1Text": "The Complete SEO and AEO Optimization Guide 2026",
      "h2Count": 4,
      "h3Count": 3,
      "h4Count": 0,
      "totalHeadings": 8,
      "hierarchyValid": true,
      "questionHeadingsCount": 3,
      "majorHeadingsOutline": [
        "What is Generative Engine Optimization?",
        "How do Answer Nuggets Work?",
        "Why Core Web Vitals Matter"
      ]
    },
    "images": {
      "total": 6,
      "missingAlt": 0,
      "missingDimensions": 0,
      "modernFormatPercent": 100,
      "formatBreakdown": { "webp": 4, "avif": 2, "png": 0, "jpg": 0, "svg": 0, "other": 0 }
    },
    "links": {
      "internalCount": 24,
      "externalCount": 5,
      "brokenInternalCount": 0,
      "emptyAnchorCount": 0,
      "insecureExternalCount": 0,
      "nofollowCount": 1
    },
    "socialTags": {
      "ogComplete": true,
      "twitterCardComplete": true,
      "hasOptimalOgDimensions": true,
      "ogTitle": "The Complete SEO and AEO Optimization Guide 2026",
      "ogDescription": "Learn how to optimize for AI and search in 2026.",
      "ogImage": "https://example.com/og-banner.jpg",
      "twitterCard": "summary_large_image",
      "twitterTitle": "The Complete SEO and AEO Optimization Guide 2026",
      "twitterImage": "https://example.com/og-banner.jpg"
    },
    "structuredData": {
      "detectedTypes": ["Article", "Organization"],
      "totalBlocks": 1,
      "hasSyntaxError": false,
      "deprecatedTypes": [],
      "eligibleRichResults": ["Article", "Organization"]
    },
    "coreWebVitals": {
      "lcpCandidate": "https://example.com/hero.webp",
      "heroLazyLoaded": false,
      "missingDimensionImages": 0,
      "renderBlockingScriptsCount": 0,
      "renderBlockingCssCount": 1,
      "renderBlockingScripts": [],
      "renderBlockingStylesheets": ["https://example.com/styles.css"],
      "domNodeCount": 620
    }
  },
  "contentAndEeat": {
    "wordCount": 1250,
    "readingTimeMinutes": 7,
    "readingEaseScore": 68,
    "textToHtmlRatioPercent": 18,
    "contentDepth": "comprehensive",
    "keywordAlignment": { "titleInH1": true, "titleInDescription": true },
    "authorFound": true,
    "authorName": "Jane Doe",
    "dates": {
      "published": "2026-01-15T08:00:00Z",
      "modified": "2026-10-20T12:00:00Z",
      "isFresh": true
    },
    "contactOrAboutLinksFound": true
  },
  "aiSearchGeo": {
    "llmsTxtFound": true,
    "llmsTxtUrl": "https://example.com/llms.txt",
    "aiCrawlerAccess": {
      "searchBots": {
        "OAI-SearchBot": "allowed",
        "Claude-SearchBot": "allowed",
        "PerplexityBot": "allowed"
      },
      "trainingBots": {
        "GPTBot": "blocked",
        "ClaudeBot": "blocked"
      }
    },
    "citabilityScore": 92,
    "citabilityMetrics": {
      "statisticsCount": 14,
      "quotesCount": 2,
      "tablesCount": 1,
      "answerNuggetsCount": 3
    },
    "answerReadiness": "high"
  },
  "issues": [
    {
      "id": "lcp-hero-missing-high-priority",
      "category": "mobileUx",
      "severity": "info",
      "points": 3,
      "title": "Hero Image Missing fetchpriority=\"high\"",
      "description": "Top-fold hero image does not declare fetchpriority=\"high\".",
      "fix": "Add fetchpriority=\"high\" to your primary LCP hero image element.",
      "location": "https://example.com/hero.webp"
    }
  ],
  "recommendations": [
    "1. [MOBILEUX] Add fetchpriority=\"high\" to your primary LCP hero image element."
  ]
}

📊 Industry Benchmark Comparison

❓ Frequently Asked Questions (FAQ)

1. What is Generative Engine Optimization (GEO) and how does it differ from traditional SEO?

Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO) are the practices of structuring webpage content so that Large Language Models (Google AI Overviews, ChatGPT Search, Perplexity AI, Claude) can accurately parse, extract, and cite your content. This engine evaluates your content against the Princeton University GEO research model, auditing quantitative statistics, expert quotations, HTML data tables, and 40–80 word direct Answer Nuggets placed under interrogative subheadings.

2. Why does this engine decouple AI Search crawlers from AI Model Training scrapers?

Content publishers often wish to protect their copyrighted editorial assets from foundation model pre-training scrapers (GPTBot, ClaudeBot, Google-Extended) while remaining fully discoverable on AI-powered search engines (OAI-SearchBot, Claude-SearchBot, PerplexityBot). This engine evaluates both categories independently under RFC 9309 rules—ensuring you receive zero SEO penalty for blocking training bots as long as search indexers remain allowed.

3. How does the Princeton University Citability Model work?

Empirical research from Princeton University demonstrated that pages featuring quantitative statistics density, verified expert attributions, authoritative outbound references, and structured <table> markup achieve a +30% to +40% increase in generative engine citation likelihood. This engine measures these exact metrics to generate an objective Citability Score (0–100).

4. How does Interaction to Next Paint (INP) impact SEO and Core Web Vitals?

Interaction to Next Paint (INP) permanently replaced First Input Delay (FID) as an official Google Core Web Vital in March 2024. Pages with poor responsiveness (> 200ms) risk algorithmic demotion in mobile search results. This engine audits INP risk factors directly, isolating render-blocking scripts in <head>, excessive DOM complexity (> 2,500 nodes), and unoptimized long-task triggers.

5. What is Client-Side Hydration Parity and why does it matter for Next.js/Nuxt sites?

Search engines crawl the raw server HTTP HTML response before initiating client JavaScript hydration. If critical metadata (canonical URL, title, H1, meta robots, schema markup) is absent or contradictory in the initial server HTML and only generated after client hydration, search crawlers may index the unhydrated shell or drop rankings. This engine compares raw server HTML directly against hydrated Playwright DOM to guarantee 100% parity.

6. Why are FAQPage and HowTo Schema.org rich results flagged as deprecated?

Google Search Central officially deprecated FAQPage rich results on May 7, 2026, eliminating accordion dropdowns in search results. Similarly, HowTo rich snippets were deprecated on mobile devices in late 2023. This engine flags these deprecated schemas so webmasters avoid wasting crawl budget on obsolete markup and instead optimize content as on-page Q&A Answer Nuggets for LLM retrieval.

7. How do Hard Severity Ceiling Caps prevent health score inflation?

Traditional SEO tools calculate health scores using flat ratios, often awarding 90+ scores to broken pages with hundreds of passing minor checks. This engine applies strict ceiling caps for critical technical flaws: HTTP 4xx/5xx errors cap the score at 0 (Grade F), Soft 404s cap at 45 (Grade F), accidental noindex directives cap at 49 (Grade F), and missing Title + H1 caps at 55 (Grade D).

8. Can I audit an entire website using an XML Sitemap?

Yes! Simply provide an XML Sitemap URL (e.g. https://example.com/sitemap.xml or compressed .xml.gz). The engine automatically decompresses gzipped files, recursively expands <sitemapindex> child sitemaps, and concurrently audits up to your configured page threshold with deduplication and unified reporting.