Checklist · AI search

AI Search Readiness Checklist

Search is becoming more conversational, multimodal, and agentic. This checklist helps you evaluate whether a website has the structural signals needed to be parsed, summarized, monitored, compared, and acted on by modern discovery systems.

Existence Compiler · 2026

The checklist

AI Overview readiness

Whether a generative answer surface can lift a clean, attributable answer from the page.

A clear "what is this?" answer near the top
What it is
A concise, self-contained definition placed high on the page.
Why it matters
Generative answer surfaces extract a short definition; a buried or implicit one is hard to lift.
What Existence Compiler checks
Existence Compiler checks for an early, extractable description and flags pages that bury their purpose.
FAQPage or QAPage schema where appropriate
What it is
Structured FAQ/Q&A markup that pairs questions with their answers.
Why it matters
It gives systems explicit question-to-answer pairs instead of inferring them from prose.
What Existence Compiler checks
Existence Compiler detects FAQPage/QAPage JSON-LD and recommends it when Q&A content exists.
Concise question/answer blocks
What it is
Short, focused answer blocks written around real questions.
Why it matters
Concise answers are easier to summarize and quote than long unbroken paragraphs.
What Existence Compiler checks
Existence Compiler looks for question-style headings paired with answer blocks.
Trustworthy metadata and source identity
What it is
A clear title and description, plus a stated identity for who publishes the page.
Why it matters
Answer systems weigh source clarity; anonymous or thin metadata is a weaker signal.
What Existence Compiler checks
Existence Compiler checks title, meta description, and the trust pages that establish identity.

AI Mode conversational depth

Whether the page can sustain a multi-turn, conversational exchange beyond the first answer.

Who it is for
What it is
An explicit statement of the intended audience.
Why it matters
Conversational search asks "is this for me?"; an explicit audience answers it directly.
What Existence Compiler checks
Existence Compiler checks for audience and purpose clarity.
Who it is not for
What it is
An honest statement of who the product is not for.
Why it matters
Boundaries help systems and people qualify fit and avoid mismatched recommendations.
What Existence Compiler checks
Existence Compiler rewards content that scopes its fit instead of overclaiming.
How it works
What it is
A plain description of how the product or service works.
Why it matters
Follow-up questions often probe mechanism; documented steps answer them.
What Existence Compiler checks
Existence Compiler checks for process and step content.
Use cases
What it is
Concrete scenarios where the product applies.
Why it matters
Use cases map a query's intent to your offering.
What Existence Compiler checks
Existence Compiler looks for use-case sections and pages.
Limits
What it is
A clear statement of what the product does not do.
Why it matters
Stated limits are a trust and defensibility signal for conversational systems.
What Existence Compiler checks
Existence Compiler treats explicit limitations as a positive clarity signal.
Alternatives / comparisons
What it is
Honest comparison to alternatives.
Why it matters
Comparative queries are common, and comparison content can be summarized into tables.
What Existence Compiler checks
Existence Compiler checks for comparison and feature content.
Follow-up questions
What it is
Content that anticipates and answers likely follow-ups.
Why it matters
AI Mode is multi-turn; depth sustains a conversation beyond the first answer.
What Existence Compiler checks
Existence Compiler measures conversational depth across the page's sections.

Information-agent monitorability

Whether an agent that watches for change can track the site over time.

RSS/Atom feed
What it is
A machine-readable feed of updates.
Why it matters
Agents that monitor for change poll feeds; without one, updates are invisible to them.
What Existence Compiler checks
Existence Compiler checks for a discoverable RSS/Atom feed.
sitemap <lastmod>
What it is
Accurate lastmod timestamps in the sitemap.
Why it matters
lastmod signals what changed and when; stale or missing values mislead crawlers.
What Existence Compiler checks
Existence Compiler checks the sitemap for lastmod presence and flags stale dates.
Changelog or updates page
What it is
A public, dated record of changes.
Why it matters
It gives monitors a single, parseable surface for what is new.
What Existence Compiler checks
Existence Compiler looks for a changelog or updates surface.
Visible published/modified dates
What it is
Human-visible dates on content.
Why it matters
Freshness signals help both readers and systems judge recency.
What Existence Compiler checks
Existence Compiler checks for visible date signals.
Stable URLs
What it is
URLs that do not churn.
Why it matters
Stable URLs let agents track an entity over time without losing it.
What Existence Compiler checks
Existence Compiler checks canonical URL consistency.

Multimodal asset clarity

Whether images, video, and documents carry enough metadata to be understood.

Descriptive image alt text
What it is
Alt text that describes the image's content.
Why it matters
Multimodal systems and assistive tech rely on alt text to interpret images.
What Existence Compiler checks
Existence Compiler measures image alt coverage.
Meaningful Open Graph image
What it is
An OG image that represents the page.
Why it matters
It controls link previews across social and chat surfaces.
What Existence Compiler checks
Existence Compiler checks for og:image and distribution-readiness signals.
Video metadata if video exists
What it is
Structured metadata for any video content.
Why it matters
Without metadata, video is opaque to discovery systems.
What Existence Compiler checks
Existence Compiler recommends VideoObject metadata where video is present.
Readable PDFs/documents if linked
What it is
Linked documents that are text-readable, not image scans.
Why it matters
Readable documents can be parsed and summarized; scans cannot.
What Existence Compiler checks
Existence Compiler flags linked assets and recommends readable formats.
Descriptive asset filenames
What it is
Filenames that describe the asset.
Why it matters
Descriptive names add weak but real context for crawlers.
What Existence Compiler checks
Existence Compiler recommends descriptive, non-opaque asset names.

Generative UI transformability

Whether the page's data can be re-rendered into summaries, cards, dashboards, or checklists.

Tables
What it is
Structured tabular data.
Why it matters
Tables convert cleanly into cards, summaries, and comparisons.
What Existence Compiler checks
Existence Compiler checks for tables and structured data blocks.
Ordered steps
What it is
Numbered, sequential instructions.
Why it matters
Ordered steps map to HowTo and step interfaces.
What Existence Compiler checks
Existence Compiler checks for step and sequence content.
Pricing/feature lists
What it is
Clear lists of features or plans.
Why it matters
Lists are easy to transform into comparison views.
What Existence Compiler checks
Existence Compiler checks for pricing, feature, and list signals.
Comparison blocks
What it is
Side-by-side comparison content.
Why it matters
Comparison data powers generative comparison cards.
What Existence Compiler checks
Existence Compiler checks for comparison structure.
Product/Offer/HowTo/ItemList schema
What it is
Schema.org types that describe structured entities.
Why it matters
Typed data is directly transformable by generative surfaces.
What Existence Compiler checks
Existence Compiler detects JSON-LD @types and recommends relevant ones.
Data that can become summaries, cards, dashboards, or checklists
What it is
Content shaped so it can be re-rendered into new interfaces.
Why it matters
Transformable data survives the shift from pages to generated interfaces.
What Existence Compiler checks
Existence Compiler scores transformability in its agentic readiness surface.

Action/contact/booking clarity

Whether a person or agent can find and take a clear next action.

Visible CTA
What it is
A clear primary call to action.
Why it matters
Agentic flows need an obvious action to surface or take.
What Existence Compiler checks
Existence Compiler checks for a visible CTA.
Contact path
What it is
A reachable way to make contact.
Why it matters
Contactability is a trust and action signal.
What Existence Compiler checks
Existence Compiler checks for a contact page or path.
Form or booking path
What it is
A form or booking flow where relevant.
Why it matters
It defines the concrete next action for people and agents.
What Existence Compiler checks
Existence Compiler checks for form and booking signals.
ContactPoint or relevant schema
What it is
Schema describing how to act or make contact.
Why it matters
Typed action and contact data is machine-actionable.
What Existence Compiler checks
Existence Compiler recommends ContactPoint and action schema where applicable.
Clear next step
What it is
An unambiguous next step on the page.
Why it matters
Ambiguous pages stall both people and agents.
What Existence Compiler checks
Existence Compiler checks for action clarity.

Classic AI/search basics

The structural fundamentals every discovery system still depends on.

Title/meta
What it is
A descriptive title and meta description.
Why it matters
They are the baseline of how a page is understood and previewed.
What Existence Compiler checks
Existence Compiler checks title and meta description.
Canonical
What it is
A canonical URL declaration.
Why it matters
It consolidates signals and prevents duplicate confusion.
What Existence Compiler checks
Existence Compiler checks the canonical tag.
robots.txt
What it is
A robots.txt that permits intended crawling.
Why it matters
A misconfigured robots file can hide a site from crawlers and agents.
What Existence Compiler checks
Existence Compiler checks robots.txt and AI-bot directives.
sitemap.xml
What it is
A sitemap listing the site's URLs.
Why it matters
It helps crawlers discover and prioritize pages.
What Existence Compiler checks
Existence Compiler checks for a sitemap and its contents.
llms.txt
What it is
A plain-text file describing the project for AI systems.
Why it matters
It gives AI a concise, authoritative summary to reference.
What Existence Compiler checks
Existence Compiler checks for llms.txt and can generate one.
schema.org JSON-LD
What it is
Structured data describing the page.
Why it matters
Typed data improves machine understanding.
What Existence Compiler checks
Existence Compiler detects JSON-LD and recommends relevant types.
Open Graph/Twitter cards
What it is
Social preview metadata.
Why it matters
It controls how links render when shared.
What Existence Compiler checks
Existence Compiler checks Open Graph and Twitter/X cards.
No accidental noindex
What it is
No unintended noindex directive.
Why it matters
An accidental noindex removes a page from search entirely.
What Existence Compiler checks
Existence Compiler detects noindex (meta tag or header) and flags it.

Passive trust/security signals

Publicly observable signals that a site is operated responsibly.

HTTPS
What it is
The site is served over TLS.
Why it matters
HTTPS is a baseline trust requirement.
What Existence Compiler checks
Existence Compiler checks HTTPS and certificate validity.
Security headers
What it is
Headers such as HSTS, CSP, and X-Content-Type-Options.
Why it matters
They harden the site and signal operational maturity.
What Existence Compiler checks
Existence Compiler's Security / Trust surface checks security headers.
Privacy/terms/contact pages
What it is
Standard trust pages.
Why it matters
Their presence is a basic credibility signal.
What Existence Compiler checks
Existence Compiler checks for trust pages.
SPF/DMARC where email/domain trust matters
What it is
DNS email-authentication records.
Why it matters
They reduce spoofing and reinforce domain trust.
What Existence Compiler checks
Existence Compiler checks SPF/DMARC at the DNS level (configured at the provider, not in app code).
security.txt if relevant
What it is
A security.txt disclosure contact.
Why it matters
It signals a responsible security posture.
What Existence Compiler checks
Existence Compiler checks for /.well-known/security.txt.

Disclaimer

This measures structural conditions. It does not guarantee rankings, traffic, citations, inclusion in AI Overviews, or outcomes from Google or any AI system.

Scan your site

Scan any public URL and discover if humans, search engines, and AI agents understand what your project does.

Scan your URL →

FreeNo accountNext step

See our methodology →View our baseline →

Keep reading

Methodology Baseline Limitations For agents MCP access Example report

Leer en español