Free Tool

Agentic Readiness Check

See whether your site is ready for AI agents and AI search. This checks the signals Google's Lighthouse "Agentic Browsing" category looks at (llms.txt, WebMCP) plus the ones it leaves out (AI-crawler access, content visible without JavaScript). Runs server-side, no browser extension needed.

How the check works

When you enter a URL, Gridlok fetches your page, your robots.txt, and your llms.txt from our server, then reads them the same way an AI crawler would. It does not run JavaScript, because most AI crawlers do not either. Every signal is checked against the raw HTML your server returns, not a rendered browser view.

travel_explore

Crawler access

Can AI bots like GPTBot and OAI-SearchBot reach your pages at all, or does robots.txt block them?

html

Readable content

Is your text in the HTML the server sends, or hidden behind JavaScript that crawlers never run?

data_object

Machine signals

Structured data, llms.txt, and WebMCP tools that help agents understand and use the page.

Frequently asked questions

Q. What is agentic readiness?

Agentic readiness is how easily AI agents and AI search tools can read, understand, and act on your site. It covers whether crawlers can reach your pages, whether your content lives in the raw HTML, and whether you expose machine-readable signals like structured data, llms.txt, or WebMCP tools.

Q. What does this tool check?

It runs six checks: an llms.txt file, WebMCP tools, AI-crawler access in robots.txt, whether your content is in the raw HTML rather than JavaScript-only, structured data (JSON-LD), and basic title and description tags. It reads your page the way an AI crawler does, server-side, with no browser or extension needed.

Q. How is this different from Chrome's Lighthouse Agentic Browsing audit?

Lighthouse runs inside Chrome and needs a special build with experimental flags to show its agentic audits. This tool runs on a server and reads your raw HTML directly, so anyone can use it without installing anything. It also checks two things Lighthouse leaves out: whether AI crawlers are blocked in robots.txt, and whether your content survives with JavaScript turned off.

Q. Do I really need an llms.txt file?

Not strictly. llms.txt is an unofficial proposal, and no major AI company has confirmed that it reads the file. It is cheap to add and does no harm, so the tool flags a missing one, but you should treat it as optional rather than essential.

Q. What is WebMCP?

WebMCP is an experimental browser standard that lets a page expose tools an AI agent can call directly, such as a search box or a contact form the agent can fill in. It is very new, so most sites will not have it yet, and a missing WebMCP setup is not a problem for normal SEO.

Q. Why does my content need to be in the raw HTML?

Most AI crawlers do not run JavaScript. If your text only appears after scripts load in a browser, those crawlers see an almost empty page. Content that is already present in the HTML your server sends is readable by every crawler, which is why this check matters more than the trendier ones.

Q. Will passing every check get my site cited by ChatGPT?

No tool can promise that. These checks remove the technical blockers that stop AI systems from reading you in the first place. Whether you then get cited still depends on having content worth citing and trust signals across the rest of the web. Treat a clean result as clearing the runway, not guaranteeing takeoff.

Want the full picture?

Read how the Lighthouse Agentic Browsing score actually works, what each audit checks, and why 4/4 is the real ceiling.

Read the Guide menu_book