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.

www.realtek.com - 35/100 Poor

expand

Grade

Poor

Most AI systems struggle to read this site. Start with the highest-weight failures below.

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 breakdown3 passed · 11 failed

✓

AI agent manifest

/llms.txt found (2446 bytes).

25 / 25

⌄

✓

Full-content AI feed

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

10 / 10

⌄

Structured data

No JSON-LD structured data found on the homepage.

0 / 15

⌄

Readable content ratio

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

4 / 15

⌄

Crawler-visible content

358 chars server-rendered, 0 H1, 2 H2, 0 substantial paragraph(s). Add more structured content to improve this score.

5 / 10

⌄

AI crawler permissions

robots.txt exists but defines no rules for AI agents (GPTBot, ClaudeBot, etc.).

0 / 10

⌄

Page index

/sitemap.xml exists but does not look like valid XML.

0 / 10

⌄

Social and citation metadata

No OpenGraph tags found.

0 / 10

⌄

Page identity signals

title: 7 chars, description: missing. Longer, descriptive values improve this score.

2 / 10

⌄

Canonical authority

No <link rel="canonical"> tag found.

0 / 5

⌄

✓

Accessibility and speed

HTTPS confirmed, responded in 324ms.

5 / 5

⌄

Attribution schema

No author, publisher, Person, or Organization found in JSON-LD structured data.

0 / 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 11 outstanding issues, with the reason each one matters and the exact fix. Copy it into Claude, ChatGPT, Cursor, or any coding agent working on www.realtek.com.

# AI readiness fixes for www.realtek.com

Audit by AI Web Readiness (https://aiwebreadiness.com) on 2026-08-12. Full report: https://aiwebreadiness.com/report/rfj6UWmMWf
Current score: 35/100 (Poor). 3 of 14 checks at full marks.

## Your task

You are working on the website https://www.realtek.com. 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 95 weighted points on the table across these 11 issues. Fixing all of them scores 100/100. If you only have time for the top 3, that alone is worth 36 points and takes the score to roughly 60/100.

---

## Issues to fix (11)

### 1. Structured data (15 points available)

**What the scan found:** No JSON-LD structured data found on the homepage.

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

### 2. Readable content ratio (11 points available, currently scoring 4 of 15)

**What the scan found:** 358 chars of text, 0.4% 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.

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

**What the scan found:** robots.txt exists but defines no rules for AI agents (GPTBot, ClaudeBot, etc.).

**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:** /sitemap.xml exists but does not look like valid XML.

**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. Social and citation metadata (10 points available)

**What the scan found:** No OpenGraph tags found.

**Why it matters:** OpenGraph tags supply the headline and summary agents use when citing or previewing your content. Missing tags force agents to improvise, often poorly.

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

### 6. Page identity signals (8 points available, currently scoring 2 of 10)

**What the scan found:** title: 7 chars, description: missing. Longer, descriptive values improve this score.

**Why it matters:** Your title and meta description are the first signals an agent reads to classify what a page is about. Thin or missing values hurt both discoverability and citation accuracy.

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

### 7. Attribution schema (8 points available)

**What the scan found:** No author, publisher, Person, or Organization found in JSON-LD structured data.

**Why it matters:** Structured author, publisher, Person, or Organization data tells AI citation engines who created the content and who stands behind it, directly influencing whether you get credited.

**How to fix it:** Add an author or publisher entity to your JSON-LD. For a business, include an Organization block with name, url, and logo. For content pages, add an author field with a Person type containing name and optionally sameAs links to authoritative profiles (LinkedIn, Wikipedia, official bio page). This is what citation engines use to attribute quotes and facts to you.

### 8. 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.

### 9. 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.

### 10. Crawler-visible content (5 points available, currently scoring 5 of 10)

**What the scan found:** 358 chars server-rendered, 0 H1, 2 H2, 0 substantial paragraph(s). Add more structured content to improve this score.

**Why it matters:** Checks whether your page delivers real content in the raw HTML. Sites that render entirely in JavaScript are largely invisible to AI crawlers that do not execute scripts.

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

### 11. Canonical authority (5 points available)

**What the scan found:** No <link rel="canonical"> tag found.

**Why it matters:** A canonical tag tells agents which URL is the definitive version of a page, preventing your authority from being split across duplicates or parameter variants.

**How to fix it:** Add <link rel="canonical" href="https://yourdomain.com/page-url"> to the <head> of every page, pointing to the preferred URL. This should be an absolute URL. Most CMS platforms can add this automatically. It is especially important for pages accessible via multiple URLs or with query parameters.

---

## 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://www.realtek.com/llms.txt

```
# Realtek

> Pages and resources from www.realtek.com.

## Key Pages
- [News](https://www.realtek.com/Article/News?lang=en-GB&app_id=18)
- [%7BProductHitsTextLink%7D](https://www.realtek.com/%7BProductHitsTextLink%7D)
- [%7BHomeBannerLink%7D](https://www.realtek.com/%7BHomeBannerLink%7D)
- [%7BhomeNewsLink%7D](https://www.realtek.com/%7BhomeNewsLink%7D)
- [%7Bfooterlink%7D](https://www.realtek.com/%7Bfooterlink%7D)
- [Index](https://www.realtek.com/Article/Index?menu_id=1153&lang=en-GB)

## 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** (25 pts): /llms.txt found (2446 bytes).
- **Full-content AI feed** (10 pts): /llms-full.txt found (2446 bytes).
- **Accessibility and speed** (5 pts): HTTPS confirmed, responded in 324ms.

---

## When you are done

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

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

⌄