SXO, AEO, and AIO Scores Are Now in Every Audit

Q: What Do SXO, AEO, and AIO Mean?

SXO (Search Experience Optimization) is the intersection of SEO and user experience — it measures whether users want to click your result and stay once they arrive. A page can rank well and still have a poor SXO score if it loads slowly, lacks a mobile viewport, or truncates titles in search results.

Q: Which Plan Includes SXO, AEO, and AIO Scores?

SXO, AEO, and AIO scores are included automatically on the Starter plan ($5/mo) and above. They run concurrently with every call — no additional query parameters, no separate API calls, and no extra usage counted against your monthly quota. Free plan users see in the response with an upgrade link.

Q: How Do You Improve SXO, AEO, and AIO Scores?

Each score has distinct levers. The array in the API response tells you exactly which ones failed — here are the highest-impact fixes for each:

The SEO landscape has fractured. In 2024, the question was "will my page rank on Google?" In 2026, the questions are:

Will it appear in AI-generated answers (ChatGPT, Perplexity, Gemini)?
Will Google pull it into a featured snippet or voice result?
Does it provide a good enough experience that users actually stay?

Standard SEO scores don't answer those questions. So we added three new ones.

What's New

Every /audit call on a paid plan now returns three additional scoring objects alongside your existing SEO score. Each object contains a numeric score (0–100), a letter grade, a checks array with individual results, and a plain-English summary you can display directly in a UI or pass to a reporting workflow. The three new scores run concurrently with the existing audit — no additional API calls, no extra usage counted against your monthly quota.

{
  "score": 74,
  "grade": "B",
  "audit": { ... },
  "sxo": {
    "sxo_score": 81,
    "sxo_grade": "A-",
    "checks": [ ... ],
    "summary": "Strong search experience — fast, mobile-ready, and UX-optimised."
  },
  "aeo": {
    "aeo_score": 52,
    "aeo_grade": "C+",
    "checks": [ ... ],
    "summary": "Limited answer engine optimisation — add FAQ schema and structure content as direct answers."
  },
  "aio": {
    "aio_score": 68,
    "aio_grade": "B",
    "checks": [ ... ],
    "summary": "Good AI readiness with some gaps in fact density or accessibility signals."
  }
}

All three scores are included automatically on Starter plan and above. Free plan users see _extended_gated in the response.

What Do SXO, AEO, and AIO Mean?

SXO (Search Experience Optimization) is the intersection of SEO and user experience — it measures whether users want to click your result and stay once they arrive. A page can rank well and still have a poor SXO score if it loads slowly, lacks a mobile viewport, or truncates titles in search results.

AEO (Answer Engine Optimization) measures your eligibility for featured snippets, People Also Ask boxes, and voice search results. It looks at structured content signals like FAQ schema, question-phrased headings, and short answer paragraphs that search engines extract for "position zero" placements.

AIO (AI Optimization) measures whether your content can be discovered, parsed, trusted, and cited by large language models like ChatGPT, Perplexity, and Gemini. It covers signals like AI bot access in robots.txt, server-side rendering, fact density, and author credibility markers that retrieval systems weight when choosing what to cite.

SXO — Search Experience Optimization

SXO measures whether users want to click your result and stay once they arrive. It's the intersection of SEO and UX, and Google has been leaning on page experience signals since Core Web Vitals became a ranking factor.

10 checks including:

Page speed — response time scored <1s (excellent) to >3s (fail)
Mobile viewport — is the page actually responsive?
HTTPS — required for modern search and browser trust
Compression — gzip/brotli reduces TTFB and improves crawl budget
Render-blocking scripts — synchronous <script> tags in <head> delay LCP
CTR signals — title length (30–65 chars) and meta description length (120–165 chars) optimised for click-through
Navigation — <nav> element as a UX and structural signal
DOM complexity — >3,000 DOM nodes hurt layout performance
Breadcrumbs — UX and structured navigation signals for SERP display

A page can rank well and still have a poor SXO score — slow load, no mobile viewport, titles truncated in search results. That gap is what SXO surfaces.

AEO — Answer Engine Optimization

AEO covers your eligibility for featured snippets, People Also Ask boxes, and voice search answers. These are the "position zero" placements that get clicks without a traditional organic result.

8 checks including:

FAQ / HowTo schema — FAQPage and HowTo JSON-LD are the primary triggers for accordion-style rich results
Question-phrased headings — H2/H3 headings that end in ? directly map to PAA box queries
Answer-first content — does the opening paragraph deliver a direct, factual answer?
Short answer format — paragraphs of 20–60 words are the sweet spot for snippet extraction
Structured lists — ordered and unordered lists are heavily favoured for step-by-step snippets
Data tables — semantic <table> elements with <th> headers for comparison snippets
Rich schema types — Article, Product, Recipe, Event, Review schema for rich result eligibility
Definition patterns — "X is Y" sentence structures for definition snippets

Most sites focus on traditional SEO and ignore the content formatting signals that determine snippet eligibility. AEO makes those visible.

AIO — AI Optimization

AIO measures whether your content can be discovered, read, trusted, and cited by large language models. This matters because AI-generated answers (in ChatGPT, Perplexity, Claude, Gemini) increasingly drive qualified traffic — and the pages they cite are the ones that trained them or that their retrieval systems can access and parse.

10 checks including:

AI bot access — are GPTBot, ClaudeBot, PerplexityBot, Google-Extended, and CCBot allowed in robots.txt?
llms.txt — the emerging standard for giving LLM crawlers structured guidance about your content
Server-side rendering — AI crawlers typically don't execute JavaScript; your content must be in the HTML
Fact density — numbers, percentages, dates, and proper nouns per 100 words; LLMs prefer information-dense content
Reading ease — Flesch score; simpler prose is more likely to be accurately reproduced in AI answers
Chunk-friendly sections — sections of 50–300 words are optimal for RAG (retrieval-augmented generation) chunking
Author / E-E-A-T signals — JSON-LD author, meta author tag, byline elements; AI systems weight credibility signals
Content freshness — dateModified in JSON-LD or OG tags; stale content is downranked by retrieval systems
Semantic HTML — <article>, <section>, <main> — AI crawlers use these to distinguish content from boilerplate
Entity consistency — brand name present in content for unambiguous entity attribution

How It Differs from GEO

We already have GEO (Generative Engine Optimization) as a separate endpoint. Here's how they relate:

	GEO (`/geo/audit`)	AIO (in `/audit`)
Focus	Deep entity, freshness, and structured data analysis	Content accessibility and format for LLM systems
Depth	26 checks across 5 weighted categories	10 targeted checks per audit
Included in	Basic plan and above	Starter plan and above
Call	Separate endpoint	Bundled with every audit

GEO is a deep-dive. AIO is a fast signal you get on every audit without an extra API call.

Which Plan Includes SXO, AEO, and AIO Scores?

SXO, AEO, and AIO scores are included automatically on the Starter plan ($5/mo) and above. They run concurrently with every /audit call — no additional query parameters, no separate API calls, and no extra usage counted against your monthly quota. Free plan users see _extended_gated in the response with an upgrade link.

Plan	Price	SXO / AEO / AIO
Free	$0	Not included
Starter	$5/mo	Included
Basic	$15/mo	Included
Pro	$39/mo	Included
Ultra	$99/mo	Included

How Do You Improve SXO, AEO, and AIO Scores?

Each score has distinct levers. The checks array in the API response tells you exactly which ones failed — here are the highest-impact fixes for each:

To improve your SXO score:

Compress images and enable gzip/brotli to reduce response time below 1 second
Add a <meta name="viewport"> tag for mobile responsiveness
Move render-blocking <script> tags to the bottom of <body> or add defer
Keep page titles between 30–65 characters and meta descriptions between 120–165 characters

To improve your AEO score:

Add FAQPage JSON-LD schema with question-and-answer pairs
Rephrase H2/H3 headings as questions ending in ?
Write opening paragraphs as direct, factual 20–60 word answers
Use numbered lists for step-by-step content and <table> elements for comparisons

To improve your AIO score:

Allow AI crawlers in robots.txt: User-agent: GPTBot / Disallow: (blank)
Add an llms.txt file at your domain root with structured content guidance
Ensure your content renders server-side — not client-side via JavaScript
Add author JSON-LD, a byline element, and dateModified to every page

Availability

SXO, AEO, and AIO scores are included automatically in every /audit response on Starter ($5/mo) and above. No query parameters, no separate calls, no extra usage counted.

Free plan users see _extended_gated in the response with an upgrade link.

curl https://seoscoreapi.com/audit?url=https://yoursite.com \
  -H "X-API-Key: YOUR_KEY"

The response will include sxo, aeo, and aio objects if you're on a paid plan.

Using the Scores in Practice

For site owners: All three scores have a letter grade (A+ to F) and a plain-English summary. Look at the checks array for specific fixes.

For developers building SEO tools: You can surface these as separate tabs or progress bars in your UI. Each check includes name, status (pass/warning/fail/info), score, max, and detail.

For agencies: Run audits on client sites and filter checks by status: "fail" across all three categories. The most common pattern we see: strong traditional SEO (good meta, structured data) but weak AIO (blocking AI crawlers, no llms.txt, no author signals).

What's Next

We're working on:

SXO trend tracking — monitoring how SXO score changes over time alongside traditional SEO score
AEO opportunity detection — identifying queries where you rank but have no FAQ/HowTo schema
AIO crawler simulation — showing you what GPTBot actually sees when it crawls your page

These will ship to Starter and above as they're ready.

If you're not yet on a paid plan, upgrade here to start seeing SXO, AEO, and AIO scores on your next audit.

Frequently Asked Questions

What do SXO, AEO, and AIO mean?

SXO (Search Experience Optimization) measures UX and page experience signals. AEO (Answer Engine Optimization) measures eligibility for featured snippets and People Also Ask boxes. AIO (AI Optimization) measures whether LLMs like ChatGPT and Perplexity can discover, parse, and cite your content. Each score is 0–100 with a letter grade, and all three are returned in a single /audit call.

How do these differ from a standard SEO score?

The standard SEO score covers technical fundamentals — meta tags, structured data, crawlability, and on-page basics. SXO, AEO, and AIO go further: SXO adds UX performance signals, AEO adds answer-format content checks, and AIO adds AI crawler accessibility signals that traditional audits never measured. A page can have a strong SEO score and still fail AIO if it blocks AI bots in robots.txt or has no author attribution.

Which plan includes these scores?

SXO, AEO, and AIO scores are included on the Starter plan ($5/mo) and above. They are bundled into every /audit response automatically — no extra API calls, no additional parameters, and no separate usage counted against your monthly quota. Upgrading from the free plan immediately unlocks all three scores on your next audit.

What checks does AEO look for?

AEO checks for FAQPage and HowTo JSON-LD schema, question-phrased H2/H3 headings, answer-first opening paragraphs, short 20–60 word answer blocks, ordered/unordered lists, data tables with header rows, rich schema types (Article, Product, Recipe), and definition-pattern sentence structures. Most sites fail on FAQ schema and question headings — these two fixes alone often add 10–15 AEO points.

How do you improve each score?

For SXO: improve page speed, add a mobile viewport tag, and defer render-blocking scripts. For AEO: add FAQPage schema, rephrase headings as questions, and write short direct-answer paragraphs. For AIO: unblock AI crawlers in robots.txt, add an llms.txt file, ensure server-side rendering, and add author JSON-LD. Each score's checks array identifies exactly which signals failed so you know where to start.