Worked example · real public signals · 20 Nov 2026

What the free check actually returns.

A worked example on a real public site, using the same nine signals as the free check. It shows the format and depth of the evidence. Every row below records only what the fetched responses contained — nothing is inferred or invented.

Site checked: https://tailwindcss.com/
Snapshot: 20 Nov 2026, UTC.
Method: the public homepage and six conventional paths (/llms.txt, /llms-full.txt, /robots.txt, /sitemap.xml, /sitemap_index.xml, /sitemap-index.xml) were fetched once with a desktop user agent. A 404 at a conventional path is an observation, not proof a site cannot be read — some sites use different filenames or restrict crawlers deliberately. Findings can change; this is a neutral snapshot, not a comment on the product.

Result: 3 of 9 signals in place

3 / 9

One further signal (Open Graph) is partial: two of the three required tags are present. Partial signals do not count towards the score.

SignalResultEvidence from the live responses
/llms.txt with real contentGapGET /llms.txt returned HTTP 404; /llms-full.txt also returned HTTP 404 (Next.js 404 pages).
Named AI-crawler rules in robots.txtGapGET /robots.txt returned HTTP 404, so no User-agent rules for AI crawlers (for example GPTBot, ClaudeBot or PerplexityBot) and no Sitemap: line were present.
Organisation and offering structured dataGapThe homepage HTML (877,958 B) contains no application/ld+json block.
Descriptive title and meta-descriptionIn place<title>Tailwind CSS - Rapidly build modern websites without ever leaving your HTML.</title>; one <meta name="description"> (“Tailwind CSS is a utility-first CSS framework for rapidly building modern websites without ever leaving your HTML.”).
Exactly one H1In placeOne <h1> element in the homepage HTML: “Rapidly build modern websites without ever leaving your HTML.”
Reachable XML sitemap linked from robots.txtGap/sitemap.xml, /sitemap_index.xml and /sitemap-index.xml all returned HTTP 404, and /robots.txt was not reachable to declare a sitemap.
One canonical URL per pageGapNo rel="canonical" link element was found in the homepage HTML.
Open Graph tagsPartialog:title, og:description and og:image are present; og:url is absent. The check requires the core share tags including og:url.
Useful text in the HTML, not only JavaScriptIn placeThe main copy (“Rapidly build modern websites without ever leaving your HTML.”) appears directly in the returned HTML.

The three gaps I would fix first

  1. Publish /llms.txt and /robots.txt. A short markdown index of the pages you want assistants to read and quote, plus a real robots.txt that states your crawl preferences and a Sitemap: line. Cheap, static, no dependency.
  2. Add a real XML sitemap at a conventional path. Generate and serve the sitemap, then declare it from robots.txt so crawlers and agents can discover it from the locations they check by convention.
  3. Add the missing template tags. Organization and SoftwareApplication (or another relevant type) JSON-LD, a rel="canonical", and og:url — small edits that usually apply site-wide from one template.

Get the same evidence for your site

The free check verifies these nine signals against your live pages and returns the top three measurable gaps with the evidence, by email, with no obligation. Request a free check → Or run the two-minute self-check first; it stays in your browser and sends nothing.

The €19 Audit Pack adds the ranked fix report, draft llms.txt, structured-data block and a before/after re-check. The €49 tier adds a small tested MCP server for your public docs and FAQ. See the offer →

Ready to order? Order the €19 pack → · Order the €49 pack + MCP server →