What is AI web readiness?

AI web readiness measures how well a website can be discovered, parsed, and cited by AI agents and large language models. It covers signals like /llms.txt, structured data, robots.txt AI crawler permissions, server-side rendering, and OpenGraph metadata.

What is /llms.txt and why does it matter?

/llms.txt is a plain text file placed at the root of a website that tells AI agents what the site is about, what it offers, and which pages to prioritize. Without it, AI agents have to guess your site's structure and purpose. It is the most impactful single change you can make for AI visibility.

How is the AI readiness score calculated?

The score is calculated across 14 weighted checks, each representing a signal that AI agents use when reading, classifying, or citing a website. Points are awarded on a pass/partial/fail basis, then normalized to a 0-100 scale. The checks cover /llms.txt (25 pts), structured data (15 pts), content readability (15 pts), and 11 additional signals.

Is AI readiness the same as SEO?

They overlap but are distinct. Traditional SEO optimizes for search engine crawlers and ranking algorithms. AI readiness optimizes for large language models and AI agents that read, summarize, and cite content directly. Many SEO best practices (structured data, fast load times, clear content) also help AI readiness, but AI-specific signals like /llms.txt have no SEO equivalent.

Which AI crawlers does the tool check for?

The tool checks for explicit permissions in robots.txt for GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, Google-Extended, anthropic-ai, cohere-ai, and meta-externalagent, among others.

Is this tool free to use?

Yes, AI Web Readiness is completely free to use. No account or sign-up is required. Simply enter a URL and get a full report in seconds.

broba.ae - 40/100 Fair - AI Web Readiness

expand

Grade

Fair

Agents can find you, but key signals are missing. Worth a focused pass.

Score

Passed

Failed

Not sure where to start?

Get a free 15-minute session with an AI visibility expert. We'll walk through your results and prioritise the fixes that move the needle fastest.

Book a free call →

No obligation · 15 min · Free

Check breakdown5 passed · 9 failed

AI agent manifest

No /llms.txt found (status 404).

0 / 25

⌄

Full-content AI feed

No /llms-full.txt found (status 404).

0 / 10

⌄

Structured data

2 JSON-LD block(s) found (types: restaurant, postaladdress, website). Adding richer schema types would improve this score.

7 / 15

⌄

Readable content ratio

824 chars of text, 3.0% text-to-HTML ratio. Improving content density would raise this score.

9 / 15

⌄

✓

Crawler-visible content

824 chars server-rendered, 1 H1, 1 H2, 3 substantial paragraph(s).

10 / 10

⌄

AI crawler permissions

No /robots.txt found (status 404).

0 / 10

⌄

Page index

No /sitemap.xml at root (status 404).

0 / 10

⌄

✓

Social and citation metadata

Present: og:title, og:description, og:image, og:site_name.

10 / 10

⌄

✓

Page identity signals

title: 73 chars, description: 198 chars.

10 / 10

⌄

✓

Canonical authority

Canonical: https://broba.ae/

5 / 5

⌄

Accessibility and speed

Site is not served over HTTPS.

0 / 5

⌄

✓

Attribution schema

Found "publisher" entity in JSON-LD. AI citation engines can attribute this content.

8 / 8

⌄

Q&A schema

No FAQPage or HowTo schema found. Adding structured Q&A can significantly increase AI citations.

0 / 7

⌄

Content feed

No RSS or Atom feed detected. A content feed signals an actively updated site that agents should re-index.

0 / 6

⌄

Fix this with AI

A complete brief covering all 9 outstanding issues, with the reason each one matters and the exact fix. Copy it into Claude, ChatGPT, Cursor, or any coding agent working on broba.ae.

# AI readiness fixes for broba.ae

Audit by AI Web Readiness (https://aiwebreadiness.com) on 2026-08-08. Full report: https://aiwebreadiness.com/report/Js7wluMX4M
Current score: 40/100 (Fair). 5 of 14 checks at full marks.

## Your task

You are working on the website http://broba.ae. An automated audit measured how well this site can be discovered, parsed, and cited by AI agents and LLM-powered search engines. The issues it found are listed below, ordered by how many points each is worth.

Work through them in order, highest value first. For each issue, make the change in this site's codebase or CMS using the stack and conventions already in use. Where a fix needs copy, facts, or URLs you cannot verify from the existing site, ask me rather than inventing them.

There are 87 weighted points on the table across these 9 issues. Fixing all of them scores 100/100. If you only have time for the top 3, that alone is worth 45 points and takes the score to roughly 71/100.

---

## Issues to fix (9)

### 1. AI agent manifest (25 points available)

**What the scan found:** No /llms.txt found (status 404).

**Why it matters:** An /llms.txt file tells AI agents exactly what your site is, what it offers, and which pages to prioritize. Without it, agents have to guess.

**How to fix it:** Create a plain text file at /llms.txt in your site root. It should start with a # Title line, a short > description, and a list of your key pages as markdown links. Use the draft generated below as your starting point. It is ready to deploy as-is.

### 2. Full-content AI feed (10 points available)

**What the scan found:** No /llms-full.txt found (status 404).

**Why it matters:** An /llms-full.txt file gives agents your complete site content in one place, so they can understand you without crawling page by page.

**How to fix it:** Create /llms-full.txt at your site root containing the full text of your most important pages, concatenated in order. Each page should be separated by a clear heading. Many static site generators and CMS platforms have plugins that generate this automatically.

### 3. AI crawler permissions (10 points available)

**What the scan found:** No /robots.txt found (status 404).

**Why it matters:** Checks whether your robots.txt explicitly addresses AI agents like GPTBot, ClaudeBot, and PerplexityBot. Silence is ambiguous; explicit rules build trust and control.

**How to fix it:** Add explicit rules for AI crawlers to your /robots.txt file. To allow all AI agents: add "User-agent: GPTBot", "User-agent: ClaudeBot", "User-agent: PerplexityBot", "User-agent: Google-Extended", and "Allow: /" under each. To block specific agents, use "Disallow: /" instead. Each additional agent addressed improves your score.

### 4. Page index (10 points available)

**What the scan found:** No /sitemap.xml at root (status 404).

**Why it matters:** A valid sitemap.xml gives agents a reliable, complete map of your site so no important page gets missed during indexing.

**How to fix it:** Create a valid XML sitemap at /sitemap.xml listing all your important pages with <loc> entries. Most CMS platforms (WordPress, Webflow, Squarespace) generate this automatically. For custom sites, use a sitemap generator tool or library. Submit it to Google Search Console once created.

### 5. Structured data (8 points available, currently scoring 7 of 15)

**What the scan found:** 2 JSON-LD block(s) found (types: restaurant, postaladdress, website). Adding richer schema types would improve this score.

**Why it matters:** JSON-LD tells agents what type of entity you are, what you do, and how your content relates to the wider web. It is the vocabulary of machine understanding.

**How to fix it:** Add a <script type="application/ld+json"> block to your homepage <head>. At minimum include @context, @type (e.g. Organization, WebSite, or Article), name, url, and description. For higher scores add richer types like BreadcrumbList, Article, or Product on the relevant pages. Google's Structured Data Markup Helper is a good starting point.

### 6. Q&A schema (7 points available)

**What the scan found:** No FAQPage or HowTo schema found. Adding structured Q&A can significantly increase AI citations.

**Why it matters:** FAQPage and HowTo schema mark up content in the exact format LLMs use to answer questions. Pages with this schema are cited at significantly higher rates.

**How to fix it:** On any page that contains questions and answers, add a FAQPage JSON-LD block with Question and Answer entities. Each Question needs a name (the question text) and an acceptedAnswer with a text property. For step-by-step content, use HowTo schema instead. Google's Rich Results Test can validate your implementation.

### 7. Readable content ratio (6 points available, currently scoring 9 of 15)

**What the scan found:** 824 chars of text, 3.0% text-to-HTML ratio. Improving content density would raise this score.

**Why it matters:** Measures how much of your page payload is actual text versus markup, scripts, and boilerplate. Low ratios signal bloated or ad-heavy pages that agents deprioritize.

**How to fix it:** Reduce inline scripts and styles, remove unused third-party widgets, and ensure your main content is substantial. Aim for at least 1,500 characters of visible body text and a text-to-HTML ratio above 10%. Moving scripts to external files and deferring non-critical CSS both help significantly.

### 8. Content feed (6 points available)

**What the scan found:** No RSS or Atom feed detected. A content feed signals an actively updated site that agents should re-index.

**Why it matters:** An RSS or Atom feed signals that your site publishes content regularly and gives agents and aggregators a reliable stream to re-index as you update.

**How to fix it:** Create an RSS or Atom feed at /feed.xml or /rss.xml listing your most recent content with title, link, description, and pubDate per item. Add a <link rel="alternate" type="application/rss+xml" href="/feed.xml"> tag to your <head> so agents can discover it automatically. WordPress, Ghost, and most CMS platforms generate this by default.

### 9. Accessibility and speed (5 points available)

**What the scan found:** Site is not served over HTTPS.

**Why it matters:** Agents skip sites that are slow or served over plain HTTP. This check confirms your site is on HTTPS and responds within 3 seconds.

**How to fix it:** Ensure your site is served over HTTPS with a valid SSL certificate. Most hosting providers offer this free via Let's Encrypt. For speed, enable HTTP/2, compress responses with gzip or Brotli, serve images in modern formats (WebP/AVIF), and use a CDN. Target a Time to First Byte (TTFB) under 500ms.

---

## Ready-to-deploy /llms.txt

This draft was generated from the site's own metadata and links. Review the wording, correct anything inaccurate, then save it as a plain text file at the site root so it resolves at http://broba.ae/llms.txt

```
# Broba Boba

> Brewed for the crew with milk boba, fruit boba, sparkling boba, refreshing tea drinks, and handcrafted boba favorites.

## Key Pages
- [Home](http://broba.ae/)

## About
This file follows the /llms.txt convention, which provides AI agents and language models with a structured map of this site. Learn more at https://llmstxt.org.
```

---

## Already passing, do not regress

These signals are already at full marks. Preserve them while making the changes above:

- **Crawler-visible content** (10 pts): 824 chars server-rendered, 1 H1, 1 H2, 3 substantial paragraph(s).
- **Social and citation metadata** (10 pts): Present: og:title, og:description, og:image, og:site_name.
- **Page identity signals** (10 pts): title: 73 chars, description: 198 chars.
- **Canonical authority** (5 pts): Canonical: https://broba.ae/
- **Attribution schema** (8 pts): Found "publisher" entity in JSON-LD. AI citation engines can attribute this content.

---

## When you are done

Deploy the changes, then rescan broba.ae at https://aiwebreadiness.com to confirm the score moved. The report tracks the delta between scans automatically.

Click the box to select all · 8,106 characters

/llms.txt draft

Ready-to-deploy file. Drop it in your site root so AI agents can find a structured map of what you offer.

⌄