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 20 weighted checks, each representing a signal that AI agents use when reading, classifying, or citing a website. Each check is a pass, partial, or fail, and the points add up to a score out of 100. The checks cover indexability (10 pts), /llms.txt (10 pts), structured data (9 pts), robots.txt AI permissions (8 pts), and further signals totalling 100 core points, plus four optional bonus checks.

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.

sushinow.ae - 80/100 Good - AI Web Readiness

expand

Grade

Good

Solid foundation. A few targeted fixes will push you to excellent.

Score

Passed

Partial

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

This report was produced with an earlier scoring model. Rescan to see the current 20-check score, which is not directly comparable.

Page-level checks used the homepage plus 3 inner pages: /menu/, /order/, /review/

Check breakdown10 passed · 7 partial · 1 failed

✓

AI agent manifest

/llms.txt found (1374 bytes).

14 / 14

⌄

✓

llms.txt quality

Has a title, a summary, 5 sections, 12 links, links on your own domain.

8 / 8

⌄

✓

Full-content AI feed

/llms-full.txt found (3423 bytes).

4 / 4

⌄

✓

Structured data

5 JSON-LD block(s) with rich types: restaurant, postaladdress, menu, contactpoint, orderaction. Counted across the homepage and 3 inner pages.

9 / 9

⌄

✓

Attribution schema

Found an Organization or Person entity, a name, a url, logo, or sameAs, author or publisher on content. Counted across the homepage and 3 inner pages.

5 / 5

⌄

✓

Q&A schema

FAQPage schema found with 6 Question(s). LLMs cite structured Q&A heavily. Counted across the homepage and 3 inner pages.

4 / 4

⌄

Readable content ratio

2349 chars of text, 12.5% text-to-HTML ratio. Improving content density would raise this score. Averaged over 4 pages (homepage first): 6.5, 0, 3, 3.5 of 7.

3.5 / 7

⌄

Crawler-visible content

2349 chars server-rendered, 1 H1, 3 H2, 12 substantial paragraph(s). Averaged over 4 pages (homepage first): 7, 2, 5, 4 of 7.

4.5 / 7

⌄

✓

AI crawler permissions

Explicitly allows 10 AI agent(s): gptbot, claudebot, anthropic-ai, perplexitybot....

8 / 8

⌄

Page index

Valid sitemap with 4 URL entries and no <lastmod> dates. More URLs and <lastmod> dates raise this score.

4 / 6

⌄

Social and citation metadata

Present: og:title, og:description, og:image, og:site_name. Averaged over 4 pages (homepage first): 4, 3.5, 0, 0 of 4.

2 / 4

⌄

Page identity signals

title: 71 chars, description: 212 chars. Note: the title is long enough to be truncated and the description is long enough to be truncated. Titles of 40-70 and descriptions of 50-160 characters score full marks. Averaged over 4 pages (homepage first): 4, 1.5, 1.5, 1.5 of 5.

2 / 5

⌄

Canonical authority

Canonical: https://sushinow.ae/. Averaged over 4 pages (homepage first): 3, 0, 0, 0 of 3.

1 / 3

⌄

✓

Accessibility and speed

HTTPS confirmed, homepage downloaded in 184ms.

3 / 3

⌄

✓

Content feed

Feed advertised via <link> tag: https://sushinow.ae/feed.xml

2 / 2

⌄

Semantic structure

Issues: heading levels skip a step. Averaged over 4 pages (homepage first): 3, 1.5, 3, 3 of 4.

2.5 / 4

⌄

Agent discovery endpoints

No agent discovery documents found (MCP server card, A2A agent card, API catalog, agents.json, or OpenAPI description).

0 / 4

⌄

✓

Content freshness

4 date signal(s) found. Most recent: 12-Oct-2026.

3 / 3

⌄

Fix this with AI

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

# AI readiness fixes for sushinow.ae

Audit by AI Web Readiness (https://aiwebreadiness.com) on 2026-10-12. Full report: https://aiwebreadiness.com/report/QCUpkq18hp
Current score: 80/100 (Good). 10 of 18 checks at full marks.

## Your task

You are working on the website https://sushinow.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 20.5 points on the table across these 8 issues. Fixing all of them reaches 100/100. If you only have time for the top 3, that alone is worth 10.5 points and takes the score to 90/100.

---

## Issues to fix (8)

### 1. Agent discovery endpoints (4 points available)

**What the scan found:** No agent discovery documents found (MCP server card, A2A agent card, API catalog, agents.json, or OpenAPI description).

**Why it matters:** A growing share of AI traffic comes from agents that act on a service, not only read it, for example by calling an API or starting a task for a user. These files are how such agents discover what your service can do and how to use it. If you run an API or an agent, publishing them makes you usable by other AI systems. A purely informational site does not need them.

**How to fix it:** Publish at least one machine-readable discovery document that applies to you, for example /.well-known/mcp.json for an MCP server, /.well-known/agent-card.json for an A2A agent, /.well-known/api-catalog for your APIs, or /openapi.json for a REST API. Two or more earn full marks.

### 2. Readable content ratio (3.5 points available, currently scoring 3.5 of 7)

**What the scan found:** 2349 chars of text, 12.5% text-to-HTML ratio. Improving content density would raise this score. Averaged over 4 pages (homepage first): 6.5, 0, 3, 3.5 of 7.

**Why it matters:** AI crawlers read pages under strict size and time limits. A page that is mostly code, trackers and layout markup gives them very little real content for the effort and tends to be deprioritised or truncated. A page with a healthy amount of readable text is quick to process and easy to summarise, which makes it more likely to be understood correctly and used as a source.

**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,000 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.

### 3. Page identity signals (3 points available, currently scoring 2 of 5)

**What the scan found:** title: 71 chars, description: 212 chars. Note: the title is long enough to be truncated and the description is long enough to be truncated. Titles of 40-70 and descriptions of 50-160 characters score full marks. Averaged over 4 pages (homepage first): 4, 1.5, 1.5, 1.5 of 5.

**Why it matters:** The title and description are the first things a search engine or an AI agent reads to decide what a page is about and whether it is relevant to a question. Missing or vague ones make the page harder to classify, and overlong ones get truncated in search results and citations. A clear, specific title and description improve how often your page is chosen and how accurately it is described.

**How to fix it:** Write a descriptive <title> tag of 40-70 characters that clearly names the page and your brand. Add a <meta name="description"> of 50-160 characters that summarises what the page offers. Longer values get truncated. Both should be unique per page, specific rather than generic, and written for humans.

### 4. Crawler-visible content (2.5 points available, currently scoring 4.5 of 7)

**What the scan found:** 2349 chars server-rendered, 1 H1, 3 H2, 12 substantial paragraph(s). Averaged over 4 pages (homepage first): 7, 2, 5, 4 of 7.

**Why it matters:** Many AI crawlers do not run JavaScript. If your site builds its content in the browser, those crawlers receive an almost empty page and conclude that there is nothing here, even though a human visitor sees a full site. Delivering content in the initial HTML, through server rendering or static generation, is what makes it visible to the widest range of search engines and AI tools.

**How to fix it:** Ensure your pages use server-side rendering (SSR) or static generation so content appears in the raw HTML response. If you use React, Next.js, or similar frameworks, enable SSR or SSG. At minimum your H1, primary heading structure, and first few paragraphs of content should be present without JavaScript.

### 5. Page index (2 points available, currently scoring 4 of 6)

**What the scan found:** Valid sitemap with 4 URL entries and no <lastmod> dates. More URLs and <lastmod> dates raise this score.

**Why it matters:** A sitemap is the list of pages you want found. It lets crawlers discover content that internal links might not surface and tells them which pages have changed recently, so updates are picked up faster. Without one, discovery depends on crawlers following links, and pages that are deep in your site, new or poorly linked can be missed for a long time.

**How to fix it:** Create a valid XML sitemap listing your important pages with <loc> and <lastmod> entries, serve it at /sitemap.xml, and add a line 'Sitemap: https://yourdomain.com/sitemap.xml' to your robots.txt. Most CMS platforms generate this automatically.

### 6. Social and citation metadata (2 points available, currently scoring 2 of 4)

**What the scan found:** Present: og:title, og:description, og:image, og:site_name. Averaged over 4 pages (homepage first): 4, 3.5, 0, 0 of 4.

**Why it matters:** OpenGraph tags are the headline, summary and picture that others see when your page is shared, previewed or cited. AI assistants and link-preview systems use them to describe your page quickly and consistently. When they are missing, the tool has to improvise from the page body, and the result is often an awkward title, a wrong summary or no image at all.

**How to fix it:** Add OpenGraph meta tags to your page <head>: og:title (your page title), og:description (a 1-2 sentence summary), og:image (a representative image URL), and og:site_name (your brand name). Each tag present adds to your score. These same tags are used by social platforms when your content is shared.

### 7. Canonical authority (2 points available, currently scoring 1 of 3)

**What the scan found:** Canonical: https://sushinow.ae/. Averaged over 4 pages (homepage first): 3, 0, 0, 0 of 3.

**Why it matters:** The same page is often reachable at several addresses, such as with and without www, with tracking parameters, or through old links. The canonical tag tells search engines and agents which address is the real one so that your authority is gathered in one place. A missing tag splits that authority, and a wrong one can tell search engines to drop your pages in favour of an address that does not exist.

**How to fix it:** Add <link rel="canonical" href="https://yourdomain.com/page-url"> to the <head> of every page. Use an absolute URL on your own domain that returns a 200 and matches the page itself. Never point it at a staging, old, or unrelated domain.

### 8. Semantic structure (1.5 points available, currently scoring 2.5 of 4)

**What the scan found:** Issues: heading levels skip a step. Averaged over 4 pages (homepage first): 3, 1.5, 3, 3 of 4.

**Why it matters:** Agents cannot see your design. They read the structure of the markup to work out what the page is about, which part is the main content and how it is organised. Clean headings and landmarks let them extract the right text and skip navigation and footers. A page built from anonymous containers is much harder to interpret, so its content is more likely to be misread or left out.

**How to fix it:** Use exactly one <h1> per page and do not skip heading levels (h1, h2, h3 in order). Wrap primary content in <main>. Set <html lang='en'> (or your language). Add <meta name='viewport' content='width=device-width, initial-scale=1'>. Give meaningful images an alt attribute.

---

## 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 https://sushinow.ae/llms.txt

```
# Sushi Now

> Enjoy fresh handcrafted sushi rolls, nigiri, sashimi, cooked favorites, vegetarian options, boba, and iced coffee. Browse the menu and order online.

## Key Pages
- [Menu](https://sushinow.ae/menu/)
- [Order](https://sushinow.ae/order/)

## 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:

- **AI agent manifest** (14 pts): /llms.txt found (1374 bytes).
- **llms.txt quality** (8 pts): Has a title, a summary, 5 sections, 12 links, links on your own domain.
- **Full-content AI feed** (4 pts): /llms-full.txt found (3423 bytes).
- **Structured data** (9 pts): 5 JSON-LD block(s) with rich types: restaurant, postaladdress, menu, contactpoint, orderaction. Counted across the homepage and 3 inner pages.
- **Attribution schema** (5 pts): Found an Organization or Person entity, a name, a url, logo, or sameAs, author or publisher on content. Counted across the homepage and 3 inner pages.
- **Q&A schema** (4 pts): FAQPage schema found with 6 Question(s). LLMs cite structured Q&A heavily. Counted across the homepage and 3 inner pages.
- **AI crawler permissions** (8 pts): Explicitly allows 10 AI agent(s): gptbot, claudebot, anthropic-ai, perplexitybot....
- **Accessibility and speed** (3 pts): HTTPS confirmed, homepage downloaded in 184ms.
- **Content feed** (2 pts): Feed advertised via <link> tag: https://sushinow.ae/feed.xml
- **Content freshness** (3 pts): 4 date signal(s) found. Most recent: 12-Oct-2026.

---

## When you are done

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

Click the box to select all · 10,578 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.

⌄