Read public material
The crawler reads the submitted public URL and a small set of public discovery files such as robots.txt, sitemap and llms.txt.
Method
AI-Ready is a public-page snapshot. It checks what AI systems can read, what evidence they can trust and which fixes should come first.
How it works
The crawler reads the submitted public URL and a small set of public discovery files such as robots.txt, sitemap and llms.txt.
The audit checks whether the site explains the business, services, contacts, policies and source evidence clearly enough.
The report groups the most useful findings into a snapshot, limitations and practical next steps.
What we check
Can the page be reached, read as text and understood without hidden context?
Do headings, URLs, key pages and discovery files help AI find the important material?
Can the site explain what it does, who it serves and what action a visitor should take?
Are contacts, policies, authorship, source notes and correction paths visible?
Are public files or pages available for systems that need concise, cited context?
Which small set of changes would reduce guessing and make the site easier to explain?
AI-readiness vs SEO
SEO often focuses on search visibility, keywords, technical indexing and traffic. Those can matter, but they are not the whole problem.
AI-readiness asks whether public evidence is clear enough for an AI system to read, cite, trust and explain without inventing missing facts.
How to read the score
A higher score means the audit found stronger public readability, structure and trust signals. It does not certify quality, rankings, traffic, sales or inclusion in AI answers.
The report summary explains what matters most before the numbers.
Score areas point to where the site is thin, unclear or missing evidence.
A shallow public audit cannot prove private facts, legal compliance or business performance.
Source and trust signals
AI-readable sources are public pages or files that summarize what the site is, what it offers and which claims are supported. They do not replace the website; they make the evidence easier to inspect.
Discovery files show what can be crawled and where important pages live.
Concise public AI notes can describe services, policies, sources and answer boundaries.
Structured data can help machines recognize organization, website and page context.
Contacts, policies, authorship and correction paths help separate evidence from unsupported claims.
Limits
The audit does not guarantee search ranking, AI answer placement, traffic, sales or leads.
It is a public AI-readiness snapshot, not legal advice, full SEO analysis or vulnerability testing.
The audit reads public material. It cannot verify private documents, internal data or claims that are not visible.
The standard audit is intentionally shallow so it stays fast, safe and easy to interpret.
Why Fix Pack exists
Many findings are simple to understand but still need careful writing, file drafts and developer-ready tasks. Fix Pack is the handoff layer after the audit.
Open Fix PackA short explanation of what changed and why it matters.
Concrete tasks for pages, metadata, source files and trust signals.
Review-ready drafts for files or page sections that make public evidence clearer.
FAQ
No. It checks visible public evidence and explains what can be understood from that evidence.
No. Scores are useful for prioritizing fixes, but they do not guarantee ranking, traffic, sales or AI inclusion.
Usually public pages, discovery files, schema.org, llms.txt if present, contact paths, policies and visible service explanations.
It turns findings into owner-facing notes, developer tasks and draft AI-readable materials for review.
AI-Ready
Start with one public URL. Use the report as a map for what AI can read and what deserves the first fix.