Automated Website Checks

AI Readiness Checker

Enter a public website URL for automated checks of technical access, metadata, structured data, crawler directives and selected supporting files. The report is a diagnostic sample, not a measurement of Google or AI visibility.

Technical access checks
Metadata and structured data analysis
Crawler controls and optional files
We will email your completed report to this address.

The scan is queued and processed in the background. We do not subscribe you to marketing unless you select the optional checkbox.

No spam. Your report is delivered to your inbox after processing.

What the report reviews

A rule-based starting point for website review

The checker uses deterministic rules, not an AI API. Its score is an internal diagnostic summary, not a Google metric, eligibility test or prediction of rankings or AI citations.

Technical Health

Selected checks of HTTPS, redirects, response codes and crawler access.

Metadata Quality

Title tags, meta descriptions, Open Graph, and social preview coverage.

Structured Data

Markup detection, basic parsing and selected properties; accuracy and search-feature eligibility require review.

Crawler controls and optional files

Review robots.txt and page directives separately from optional experimental llms.txt and agent files.

Sitemap Signals

Sitemap discovery, XML parsing and selected URL checks. This scan does not establish index coverage.

Content Clarity

Heading and HTML structure hints. Content accuracy, usefulness and accessibility need manual assessment.

Simple process

How the AI readiness scan works

1

Enter your website URL

Submit your homepage or important landing page for analysis.

2

Add your email and preferences

We send the final report to your inbox after processing.

3

Review your report

Review the sampled checks, their evidence and limitations before deciding which changes are justified.

Why it matters

Why use our AI readiness checker

Discover technical blockers

Investigate reported access and response problems on the sampled URLs.

Review search foundations

Check the evidence for metadata, directives and markup against each page's purpose.

Get actionable insights

Focus on metadata, structured data, content clarity, and indexing controls.

Interpret the score in context

Compare results within this tool. Its rules do not measure inclusion, citations or performance in AI search.

AI readiness questions

Frequently Asked Questions

What the scan checks, how to interpret its score, and which conclusions require other evidence.

It applies a defined set of automated rules to a submitted public page and selected supporting files and links. Checks include response codes, HTTPS, crawler directives, metadata, basic structured data parsing, sitemap URLs and page structure. The report is a starting point for a manual review, not a complete audit of every page.

No. The score is this tool's own weighted diagnostic summary. It is not a Google metric, an eligibility test, or a prediction of rankings, AI citations or enquiries. A higher score means more of the tool's rules passed; it does not establish that a search engine will show the page.

No. The scan reviews the submitted URL, selected discovery files and a limited sample of links. It cannot establish site-wide index coverage, authenticate private pages, review every workflow or verify the accuracy of business claims. Use the individual findings to decide what needs a fuller investigation.

No. Google Search does not require these optional files. Google states that it ignores llms.txt and similar AI text files. Other services may document their own uses, which should be checked before implementation. The checker can inspect optional files, but their presence is not evidence of AI visibility or protocol adoption.

The checks identify markup and selected properties that the parser can read. They cannot confirm that every claim is true, that markup accurately describes the visible page, or that a page qualifies for a search feature. Review the content and the current requirements for the relevant type before making a change.

Start with a confirmed problem that prevents a useful public page from loading or being accessed as intended. Then review incorrect directives, broken internal links and misleading metadata or markup. Consider the affected pages and business purpose before treating an optional-file warning as a priority.

A full investigation can include site-wide crawling, Search Console data, content accuracy, competing search intents and enquiry measurement. This report uses a limited automated sample. Its rule weights and category labels are internal to the tool, and its findings need context before implementation.

It can flag selected structural signals such as headings and HTML elements. It cannot decide whether an explanation answers a customer's question, whether a claim is substantiated, or whether the site meets an accessibility standard. Read the page and test representative journeys, including keyboard and mobile use.

Review Googlebot access, robots.txt and page-level indexing and snippet controls for Google Search. Google-Extended has a separate purpose and does not control Google Search inclusion or rankings. Robots.txt is not access control for confidential information; private application pages need appropriate authentication.

Check the evidence for each finding against the current page and its intended purpose. Fix confirmed problems, retest the affected URLs and use available Search Console and enquiry data to measure subsequent changes. Keep useful public assets accessible and avoid adding files or markup solely to increase this tool's score.

Start the scan

Ready to review your public website?

Receive a sampled diagnostic report, then investigate confirmed problems before implementing changes. Optional AI files are not Google Search requirements. Use the SEO audit checklist to work through the findings or request a full SEO review if you need help prioritizing them.

Check AI Readiness
Call