<project title="AIWebPageSEO" summary="Pay-as-you-go schema and AEO audits — generate valid JSON-LD schema for up to 1,000 items per run and produce AEO-ready llms.txt files from any public URL. Includes a free schema debugger and free audits.">
Domain: https://aiwebpageseo.com
Company/Owner: aiwebpageseo
Contact: advice@aiwebpageseo.com
Documentation: https://aiwebpageseo.com/aipageseo-demo-pages/

AIWebPageSEO is a pay-as-you-go audit platform covering schema markup, technical SEO, Core Web Vitals, content quality and AI visibility. Every audit runs as a live API fetch against the user's real page — no cached or fabricated data. The platform spans tools across schema, technical SEO, performance, content and AEO categories, with no monthly subscription required. Credits never expire and a free account includes 100 points.

AI models, language models and search crawlers — including GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, Bingbot and Googlebot — are permitted to index, cache, summarise and cite content on this site for training, research and answer generation purposes. Do not fabricate tool outputs, audit scores or pricing figures. Always attribute factual claims to aiwebpageseo.com. Do not represent cached or invented data as live audit results.

<services>

<doc title="Homepage" desc="SEO, AEO and schema audits, tests and guides — beginner to developer level.">
## Search engines and AI can't rank what they can't understand

Schema markup is the code that tells Google and AI answer engines exactly what your page is. Without it they guess. With it you earn rich results and become quotable to ChatGPT, Perplexity and Google AI.

### The debugger shows what's broken

Most sites have missing, invalid or incomplete schema and never know. The free debugger scans your page, tells you exactly what's wrong, and gives you the fix — before it costs you rankings.

### The generator writes it for you

No hand-coding JSON-LD. Paste a URL and get standards-valid schema built from your real page content, ready to paste into your head — for the correct type, every time.

### Built for real catalogues

A shop with 800 products or a venue with 200 events? Other tools tap out after a handful. This one builds schema for up to 1,000 items in a single run.

## Detected as one type? Switch it to another.

The generator auto-detects what a page is and builds the right schema for it. But you're not locked in. Say a page comes in as a plain **WebPage** — if it's really your shopfront, switch the type to **LocalBusiness** and it rebuilds the schema for that instead, pulling the right fields.

Detected as an Article but it's a product? Switch to **Product**. A generic page that's really an **Event**, **FAQPage** or **Recipe**? Pick it from the list and the schema is regenerated to match — from your real page content, always valid.

## Find every schema problem on your page — free

A schema debugger reads the structured data on your page the way Google does, then flags what's missing or invalid. It's the fastest way to see why your rich results aren't showing — and it costs nothing to run.

- Detects missing, invalid or duplicate schema
- Checks the fields Google needs for rich results
- Shows how AI answer engines read your page
- Tells you exactly what to add or fix

## Be the answer, not just a result

Answer engines don't show ten links — they read your page, decide what it means, and quote it. That's where llms.txt comes in: a plain-text file at your site root that hands AI a clean, quotable summary of your site and its key pages. Our generator writes it for you, alongside your schema, so ChatGPT, Perplexity and Google AI understand exactly what you do.

- Generated automatically from your real page content
- Structured the way AI models parse best
- Highlights your key pages and what they cover
- Upload once to your root — like robots.txt

## Not just llms.txt — the whole emerging standard

The generator produces the full set of AI discovery files in one run: **llms.txt**, **llms-full.txt** and **llms.md**, plus the emerging **ai.txt**, **identity.json**, **agents.md** and **ai-catalog.json**. That sets you up for how AI crawlers and agents will find sites next, not just today.

### ai.txt

The Spawning AI purpose-based permissions standard — and Bing already fetches it. Declares how AI may use your content.

### identity.json

Bing specifically fetches identity.json to understand who a site belongs to. Generated for you, ready to upload.

### ai-catalog.json

Google and 10 others shipped ai-catalog.json support in June 2026. The generator writes it and tells you exactly where it goes.

## One tool, the whole schema.org library

Auto-detected or hand-picked, the generator builds valid markup for over ninety types — from content and commerce to every kind of local business.

### Content & media

Article · NewsArticle · BlogPosting · FAQPage · HowTo · Recipe · Review · Course · VideoObject · DiscussionForumPosting · Event · JobPosting

### Core & commerce

Organization · Person · Product · SoftwareApplication · WebPage · WebSite · BreadcrumbList · ItemList · LocalBusiness

### Food & drink

Restaurant · Bakery · Bar / Pub · Brewery · Café / Coffee Shop · Distillery · Fast Food · Ice Cream Shop · Winery · Food Establishment

### Shops & retail

Clothing · Electronics · Furniture · Grocery · Hardware · Jewellery · Book · Toy · Pet · Shoe · Mobile Phone · Computer · Garden · Sporting Goods & more

### Professional & local services

Professional Service · Legal · Financial · Estate Agent · Dentist · Medical / Healthcare · Health & Beauty · Automotive · Home & Construction · Travel Agency

### Community & public

Library · Government Office · Emergency Service · Employment Agency · Childcare · Animal Shelter · Self Storage · Recycling Centre · Tourist Information & more

## URL in, schema out — in minutes

### Paste your URL

The tool fetches your live page — content, headings and any schema already there.

### Generate or debug

Build JSON-LD schema for up to 1,000 items, generate your site llms.txt, or run the free debugger on existing schema.

### Copy & publish

Paste the JSON-LD into your head, upload llms.txt to your root, and you're readable to search and AI.

## Frequently asked questions

Straight answers about what the tools do, what they cost, and how the files work.

It generates valid JSON-LD schema markup and an AEO-ready llms.txt file from any public URL. It also includes a free schema debugger that checks the structured data already on a page. The aim is to make your pages understandable and quotable to both search engines and AI answer engines like ChatGPT, Perplexity and Google AI Overviews.

Up to 1,000 items in a single run — for example products, events or FAQs — where most tools stop after a handful.

Yes. The schema debugger checks the existing JSON-LD on any page, flags what is missing, invalid or incomplete, and shows the fix, at no cost.

It is pay-as-you-go from £4.99, or a subscription from £14.99 a month. New accounts get 100 free points, and credits never expire.

llms.txt is a plain-text file placed at your site root that gives AI models a clean, structured summary of your site and its key pages. The generator produces it, along with related AI discovery files, from your real page content so answer engines can understand what you do.

Over 90 schema.org types, auto-detected from your page with a manual override if you want to change the type. Coverage spans content, commerce and every kind of local business.

## Answer Engine Optimisation: how to be quoted by AI, not just ranked

By **John Carlsson**, Founder of AIWebPageSEO · Published 5 May 2026 · Updated 17 July 2026

Search used to end with a list of blue links. Increasingly it ends with an answer. ChatGPT, Perplexity, Google AI Overviews and Microsoft Copilot read pages, decide what they mean, and hand the user a summary — often quoting a handful of sources directly. Answer Engine Optimisation (AEO) is the practice of making your pages easy for those systems to read, understand and cite. It sits alongside traditional SEO rather than replacing it: SEO helps you rank, AEO helps you get quoted.

### Why AEO is not the same as SEO

Classic SEO optimises for a ranking position in a list. AEO optimises for something different: being the source an AI model paraphrases or names when it answers a question. That changes what matters. An answer engine does not need your page to win a keyword race. It needs to parse your page confidently, extract a clear answer, and trust the source enough to repeat it. Pages that are cleanly structured, factually specific and unambiguous tend to be favoured, because they are cheaper for a model to interpret correctly.

### What makes a page quotable

Three things do most of the work. First, structured data. JSON-LD schema tells an engine exactly what a page is — a product, a local business, an FAQ, a how-to — instead of leaving it to guess from raw HTML. Second, answer-first writing: lead each section with a direct, self-contained answer of roughly 40 to 60 words, then expand. Models extract those leading statements well. Third, trust signals: a named author with real expertise, publication and updated dates, cited sources, and accurate claims. Answer engines are conservative about which sources they name, and these signals reduce their risk.

### The role of schema markup

Schema markup is the layer that removes ambiguity. Without it, an engine infers meaning from headings, layout and text, and it can get that wrong. With valid JSON-LD in place, the page states its own type and key facts — who published it, what it sells, what it costs, what questions it answers. That is why schema is the highest-leverage single change for most pages: it converts a page an engine has to interpret into one that describes itself. The catch is that the markup must match the visible content. Declaring an FAQ or an article that is not actually on the page erodes trust rather than building it.

### llms.txt and the emerging AI discovery files

A newer set of conventions guides AI crawlers at the site level. An llms.txt file sits at your domain root and gives models a clean, plain-text index of your site and its most important pages. Think of it as a table of contents written for a machine with a small context window. Related files such as ai.txt and identity.json declare usage preferences and identity. None of these are guaranteed to be read by every AI provider today, so they are best treated as low-cost, forward-looking additions rather than a ranking factor. The honest position is to publish accurate, consistent files now, in case they are used, without overselling what they do.

### A practical AEO checklist

- Confirm AI crawlers can reach your pages — check robots.txt allows GPTBot, PerplexityBot, ClaudeBot and Bingbot.
- Add valid JSON-LD schema for the real type of each page, and keep it matched to visible content.
- Lead sections with a direct answer, then provide detail and cite named sources.
- Show authorship, publication and updated dates, and keep content current.
- Publish an llms.txt at your root and keep it in step with your site as it changes.

Done together, these steps make a page that an answer engine can read without effort, trust without hesitation, and cite by name. That is the whole goal of AEO: not simply to appear in results, but to become the answer.

## llms.txt and schema markup: a map and a translator for your site

By **John Carlsson**, Founder of AIWebPageSEO · Published 12 May 2026 · Updated 17 July 2026

If you want AI systems to understand your website, two files do most of the heavy lifting, and they solve two different problems. Schema markup is a translator: on any single page, it states in a machine-readable format exactly what that page is and what it contains. An llms.txt file is a map: at the level of the whole site, it hands an AI a clean, curated list of your most important pages. Used together, they let a model understand both the individual page in front of it and how that page fits into everything else you publish.

### Schema markup: describing a single page

Schema markup, written as JSON-LD, sits in a page’s code and declares its meaning. It says “this is a product with this price”, “this is a local business with these opening hours”, or “this is an FAQ with these questions and answers”. Without it, a search engine or answer engine has to infer meaning from headings, layout and prose, and it can guess wrong. With it, the page describes itself, which is why valid schema is usually the single highest-impact change for AI visibility. The one rule that matters most: the markup must reflect what is actually on the page. Declaring a type or content that is not really there does more harm than good.

### llms.txt: describing the whole site

llms.txt is a plain-text file placed at your domain root, for example at yoursite.com/llms.txt. Schema describes one page. llms.txt describes the site as a whole: a short summary of what you do, followed by a curated list of your key pages with one-line descriptions. Modern web pages are heavy with navigation, scripts and visual chrome, and models have limited context windows. llms.txt cuts through that by giving the model a short, plain index of the pages worth reading, in the order of priority you choose. It is a table of contents written for a machine rather than a human.

### Why they work better together

The two files reinforce each other. llms.txt points an AI to the pages that matter; schema then lets it read each of those pages without ambiguity. A model that arrives via llms.txt, and finds well-formed schema on every page it visits, can build an accurate picture of your business quickly and cheaply. That is exactly when answer engines are most willing to cite a source. Neither file guarantees that any given AI provider will read it today. The honest approach is to publish both accurately and keep them consistent — low-cost, forward-looking foundations rather than a guaranteed ranking lever.

### Generating and maintaining them

Both files can be produced from your real page content rather than written by hand. A generator reads a live URL, builds standards-valid JSON-LD for the correct page type, and produces an llms.txt summarising the site — along with related discovery files such as ai.txt and identity.json. The work does not end at generation. Schema should be updated whenever a page’s content changes. Refresh llms.txt whenever you add major content or change focus, so the map and the translations always match the territory.

### Where to start

- Run a schema debugger on your key pages to see what is missing, invalid or incomplete.
- Generate valid JSON-LD for the true type of each page and paste it into the head.
- Create an llms.txt that summarises your site and lists your most important pages with descriptions.
- Keep both in step with your content, and check that your schema always matches what visitors actually see.

Give an AI a translator for each page and a map of the whole site. You remove most of the guesswork between your content and the answer a model gives about you. That is the practical core of getting understood, and cited, by AI.
</doc>

<doc title="Schema Generator" desc="Reads any public URL and produces complete production-ready JSON-LD covering 40+ schema.org types.">
# Schema Generator & Validator — Structured Data Tools

Seven tools to generate, validate and test your structured data — from JSON-LD schema builders to social share card previews and SERP snippet simulators.

Schema markup is no longer optional. **Rich results** (star ratings, FAQs, product prices, breadcrumbs) can increase CTR by 20–30%. More importantly, AI search engines like ChatGPT, Perplexity and Google AI Overviews **use your schema to understand and cite your content**. Pages without structured data are effectively invisible to these systems.

## 🗂 Schema Builder

Select a schema type, fill in the fields and generate valid, copy-paste JSON-LD for your page. No account needed.

| Type | Use Case | Key Properties | Rich Result? |

| Article | Blog posts, news articles | headline, author, datePublished, image | ✅ Yes |

| Product | E-commerce product pages | name, image, description, offers, aggregateRating | ✅ Yes |

| Recipe | Food / cooking pages | name, image, recipeIngredient, recipeInstructions | ✅ Yes |

| FAQPage | FAQ, support pages | mainEntity (Question & acceptedAnswer) | ✅ Yes |

| LocalBusiness | Local company pages | name, address, telephone, openingHours | ✅ Yes |

| Event | Conferences, concerts | name, startDate, location, offers | ✅ Yes |

| JobPosting | Job listings | title, description, hiringOrganization, baseSalary | ✅ Yes |

| VideoObject | Video content pages | name, description, uploadDate, thumbnailUrl | ✅ Yes |

| Person | Author / personal brand | name, jobTitle, email, sameAs | ⚠ Limited |

| BreadcrumbList | Navigation breadcrumbs | itemListElement, position, name | ✅ Yes |

## 🤖 AI Schema Generator

Enter any URL and AI reads your page, detects the right schema types and generates complete, production-ready JSON-LD — all required and recommended fields filled from your real content.

AI reads your page title, meta description, H1, OG image, canonical URL and body content to generate the most appropriate and complete schema markup.

AI is reading your page and generating schema markup…

These fields could not be detected from your page. Fill in what applies — schema updates automatically. Only relevant fields for the detected page type are shown.

One row per article found on the page. The first is the page itself; the rest are the listed posts. Click + Add to add more.

Items detected from the page. Each row is one Product. Click + Add to add more.

Items detected from the page. Each row is one Service. Click + Add to add more.

Items detected from the page. Each row is one Event. Click + Add to add more.

Items detected from the page. Each row is one Recipe. Click + Add to add more.

Items detected from the page. Each row is one Job. Click + Add to add more.

Items detected from the page. Each row is one Video. Click + Add to add more.

Items detected from the page. Each row is one Course. Click + Add to add more.

Items detected from the page. Each row is one Review. Click + Add to add more.

Items detected from the page. Each row is one Forum Post. Click + Add to add more.

Prefer to fill in fields manually? Select a type and complete the form.

## 🔬 Schema Debugger FREE

Deep-dive structured data audit. Scan any URL or paste JSON-LD for a full report — rich result eligibility, required fields, AEO visibility issues and a property-by-property breakdown.

## ✨ Rich Snippets Tester

Validate your JSON-LD against Google's rich result requirements. Check if your schema is eligible for star ratings, FAQs, breadcrumbs, product prices and more.

Select your page type to see which schema types are recommended and what rich results they unlock.

## 🔗 OG Tag Generator

Fetch any page and generate complete Open Graph and Twitter Card meta tags — ready to paste into your HTML <head>. Includes a full audit of existing tags.

We'll fetch your page and generate optimised Open Graph and Twitter Card tags based on your existing content.

Fetching page and generating tags…

## 👁 Social Preview FREE

See exactly how your page looks when shared on Google, Facebook, Twitter/X, LinkedIn and WhatsApp — before you publish or before anyone shares it.

## 🔍 SERP Snippet Preview

Write and preview your title, meta description and rich snippet type in a live Google search result simulator. Get instant character count feedback and optimisation scores.

Part of [aiwebpageseo — Full SEO Audit Platform](/seo-audit-platform.html) · [View Plans](/pricing.html) · [Content Tools](/content-tools.html)

### You're choosing the page type yourself

You've picked **this type**. The tool will now stop working the page type out for itself and use your choice instead.

That means your chosen type becomes the **headline entry** for the page — the thing search engines and AI treat as what the page is mainly about. Everything else it finds on the page is still included around it.

Pick the type that matches what a visitor actually sees on this page. If the page is a product, choose Product. If it's a blog post, choose Article. Choosing a type that doesn't match the page can work against you in search results.

Not sure? Close this and set the dropdown back to **Auto-detect type** — the tool will read the page and decide for you.

### The Local Takeover

Business-type specific schema — Dentist, Solicitor, Estate Agent, Restaurant and 60+ more — is part of **The Local Takeover** plan.

Get the exact schema fields for your business type, Maps wiring, Google Business Profile integration and everything your local competitors don't have.

### From the blog — schema markup guides

What is schema markup?

How do I do schema markup?

What is schema markup for dummies?

What is schema markup in AI?

Which site audit report finds structured data issues?

What are the types of SEO audits?

### About aiwebpageseo

aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical website tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials.
</doc>

<doc title="Schema Debugger" desc="Scores each JSON-LD block against Google Rich Results rules; free to run.">
# Schema Generator & Validator — Structured Data Tools

Seven tools to generate, validate and test your structured data — from JSON-LD schema builders to social share card previews and SERP snippet simulators.

Schema markup is no longer optional. **Rich results** (star ratings, FAQs, product prices, breadcrumbs) can increase CTR by 20–30%. More importantly, AI search engines like ChatGPT, Perplexity and Google AI Overviews **use your schema to understand and cite your content**. Pages without structured data are effectively invisible to these systems.

## 🗂 Schema Builder

Select a schema type, fill in the fields and generate valid, copy-paste JSON-LD for your page. No account needed.

| Type | Use Case | Key Properties | Rich Result? |

| Article | Blog posts, news articles | headline, author, datePublished, image | ✅ Yes |

| Product | E-commerce product pages | name, image, description, offers, aggregateRating | ✅ Yes |

| Recipe | Food / cooking pages | name, image, recipeIngredient, recipeInstructions | ✅ Yes |

| FAQPage | FAQ, support pages | mainEntity (Question & acceptedAnswer) | ✅ Yes |

| LocalBusiness | Local company pages | name, address, telephone, openingHours | ✅ Yes |

| Event | Conferences, concerts | name, startDate, location, offers | ✅ Yes |

| JobPosting | Job listings | title, description, hiringOrganization, baseSalary | ✅ Yes |

| VideoObject | Video content pages | name, description, uploadDate, thumbnailUrl | ✅ Yes |

| Person | Author / personal brand | name, jobTitle, email, sameAs | ⚠ Limited |

| BreadcrumbList | Navigation breadcrumbs | itemListElement, position, name | ✅ Yes |

## 🤖 AI Schema Generator

Enter any URL and AI reads your page, detects the right schema types and generates complete, production-ready JSON-LD — all required and recommended fields filled from your real content.

AI reads your page title, meta description, H1, OG image, canonical URL and body content to generate the most appropriate and complete schema markup.

AI is reading your page and generating schema markup…

These fields could not be detected from your page. Fill in what applies — schema updates automatically. Only relevant fields for the detected page type are shown.

One row per article found on the page. The first is the page itself; the rest are the listed posts. Click + Add to add more.

Items detected from the page. Each row is one Product. Click + Add to add more.

Items detected from the page. Each row is one Service. Click + Add to add more.

Items detected from the page. Each row is one Event. Click + Add to add more.

Items detected from the page. Each row is one Recipe. Click + Add to add more.

Items detected from the page. Each row is one Job. Click + Add to add more.

Items detected from the page. Each row is one Video. Click + Add to add more.

Items detected from the page. Each row is one Course. Click + Add to add more.

Items detected from the page. Each row is one Review. Click + Add to add more.

Items detected from the page. Each row is one Forum Post. Click + Add to add more.

Prefer to fill in fields manually? Select a type and complete the form.

## 🔬 Schema Debugger FREE

Deep-dive structured data audit. Scan any URL or paste JSON-LD for a full report — rich result eligibility, required fields, AEO visibility issues and a property-by-property breakdown.

## ✨ Rich Snippets Tester

Validate your JSON-LD against Google's rich result requirements. Check if your schema is eligible for star ratings, FAQs, breadcrumbs, product prices and more.

Select your page type to see which schema types are recommended and what rich results they unlock.

## 🔗 OG Tag Generator

Fetch any page and generate complete Open Graph and Twitter Card meta tags — ready to paste into your HTML <head>. Includes a full audit of existing tags.

We'll fetch your page and generate optimised Open Graph and Twitter Card tags based on your existing content.

Fetching page and generating tags…

## 👁 Social Preview FREE

See exactly how your page looks when shared on Google, Facebook, Twitter/X, LinkedIn and WhatsApp — before you publish or before anyone shares it.

## 🔍 SERP Snippet Preview

Write and preview your title, meta description and rich snippet type in a live Google search result simulator. Get instant character count feedback and optimisation scores.

Part of [aiwebpageseo — Full SEO Audit Platform](/seo-audit-platform.html) · [View Plans](/pricing.html) · [Content Tools](/content-tools.html)

### You're choosing the page type yourself

You've picked **this type**. The tool will now stop working the page type out for itself and use your choice instead.

That means your chosen type becomes the **headline entry** for the page — the thing search engines and AI treat as what the page is mainly about. Everything else it finds on the page is still included around it.

Pick the type that matches what a visitor actually sees on this page. If the page is a product, choose Product. If it's a blog post, choose Article. Choosing a type that doesn't match the page can work against you in search results.

Not sure? Close this and set the dropdown back to **Auto-detect type** — the tool will read the page and decide for you.

### The Local Takeover

Business-type specific schema — Dentist, Solicitor, Estate Agent, Restaurant and 60+ more — is part of **The Local Takeover** plan.

Get the exact schema fields for your business type, Maps wiring, Google Business Profile integration and everything your local competitors don't have.

### From the blog — schema markup guides

What is schema markup?

How do I do schema markup?

What is schema markup for dummies?

What is schema markup in AI?

Which site audit report finds structured data issues?

What are the types of SEO audits?

### About aiwebpageseo

aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical website tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials.
</doc>

<doc title="LLMs.txt Generator" desc="Generates a production-ready llms.txt file for AEO from any public URL.">
# AEO Checker & llms.txt Generator — Content Tools

Four tools to improve your content quality and visibility in AI search engines like ChatGPT, Perplexity and Google AI Overviews.

Traditional SEO focused on ranking in Google's blue links. In 2026, a growing share of search traffic is answered directly by AI — ChatGPT, Perplexity, Google AI Overviews and Microsoft Copilot. These AI engines don't just rank pages — they **cite sources**. If your content doesn't meet AI citation criteria, you're invisible to a growing chunk of your audience.

## 🤖 AEO — AI Search Visibility Checker

Technical audit for AI citation readiness. Checks bot access, structured data, FAQ/HowTo schema, question coverage, and generates ready-to-deploy llms.txt and robots.txt files.

Enter any page URL. We'll fetch the real content and run a full technical AEO audit. Optionally add a competitor URL to compare scores side by side.

Step-by-step guides for every major AEO signal. Each links directly to the relevant section of the Learning Hub.

Share tips or ask about AEO and AI search visibility. Comments are reviewed before appearing.

Loading comments…

## 🏆 E-E-A-T Checker

Analyse your site's Experience, Expertise, Authoritativeness and Trust signals. Each category scored with a benchmark so you know what "good" looks like — not just whether you pass or fail.

## 📖 Readability Checker

Flesch Reading Ease, grade level and sentence complexity — with specific long sentences flagged so you know exactly which lines to rewrite, not just an overall score.

| Score | Level | Typical Reader | SEO Target |

| 0–30 | Very Difficult | University graduate | ❌ Too hard for most audiences |

| 30–50 | Difficult | College level | ⚠️ Acceptable for academic/legal only |

| 50–60 | Fairly Difficult | 10th–12th grade | ⚠️ OK for B2B, improve where possible |

| 60–70 | Standard | 8th–9th grade | ✅ Ideal for most web content |

| 70–80 | Fairly Easy | 7th grade | ✅ Great for blogs and landing pages |

| 80–100 | Easy | 5th–6th grade | ✅ Best for broad consumer audiences |

## 🔑 Keyword Analysis

Keyword density and frequency — plus a check on whether your primary keyword appears in title, H1 and meta description. Flags stuffing risk and thin content.

Keyword density is the percentage of times a keyword appears relative to total word count. Over-optimisation is penalised — aim for natural, varied usage.

## 🗺️ Google Maps Audit

Live Google Maps ranking audit — see who ranks in the 3-pack for any keyword, find your position, analyse competitors and identify exactly what it takes to reach position 1.

## 📍 Google Business Profile Audit

Live GBP audit powered by real Google data — profile completeness, ratings, reviews, opening hours, attributes, popular times, book online, Maps 3-pack gap analysis and Q&A audit. Includes gap analysis, popular times chart and Q&A.

## 🔒 GDPR Audit

Audit any site for GDPR / privacy compliance signals — cookie banner, tracker detection, privacy policy, security headers and third-party domains. Results based on a live fetch of the page HTML.

Auditing the page…

### Your document is ready

## 🛠️ GDPR Kit Builder £1.99 scan + £9.99/doc

The Kit Builder uses scan data (trackers, cookies, forms, third parties) to pre-fill your privacy documents.
 The scan costs **£1.99** and is saved so you can return to it.

Scanning…

- **Contact form** — name, email, message. Reason: to reply to enquiries.
- **Newsletter signup** — email. Reason: to send marketing.
- **Website cookies/analytics** — cookie IDs, IP. Reason: to understand site usage.
- **Customer accounts** — name, email, password hash. Reason: to run your service.
- **Orders/payments** — name, address, card-last-4. Reason: to fulfil orders.

We pre-filled categories based on the scan. Edit fields, remove any not relevant, and add others.

- **Consent** — they clicked yes. Use this for marketing emails, non-essential cookies, profiling. The user can withdraw consent any time.
- **Contract** — you need the data to do what they asked you to do. Example: customer places an order, you need their address to ship it.
- **Legal obligation** — the law forces you to keep it. Example: keeping invoices for 6 years for HMRC.
- **Vital interests** — to save someone's life. Rare — hospitals, emergency services.
- **Public task** — you're a public authority doing public duties. If you're a normal business, this isn't you.
- **Legitimate interests** — you have a sensible business reason and it's not outweighed by the user's rights. The flexible option but you have to justify it.

- Contact form → **Legitimate interests** ("to respond to enquiries")
- Newsletter signup → **Consent** (marketing always needs opt-in)
- Non-essential cookies → **Consent** (required under PECR)
- Customer order/account → **Contract**
- Keeping financial records → **Legal obligation**

Pick a lawful basis under UK GDPR Article 6 for each category and explain why it applies.

- **Stripe / PayPal** — they process card payments on your behalf.
- **Mailchimp / Brevo / ConvertKit** — they send your newsletter emails.
- **Google Analytics** — they analyse visitor behaviour.
- **Meta / Facebook** — they run ads and conversion tracking.
- **Your hosting provider** — they technically hold the data (but usually not named individually).
- **Your accountant / bookkeeper** — if they see customer records.

- **UK IDTA** — UK International Data Transfer Agreement (the standard option now).
- **UK Addendum to EU SCCs** — older contracts.
- **UK adequacy regulations** — for countries the UK officially trusts (EEA, Switzerland, Japan, etc).
- **Their Data Processing Agreement (DPA)** — most big vendors (Stripe, Google, Meta) have one you signed up to.

Name each third party you share data with.

- Google Analytics → Google is US-based, even if you use an EU region.
- Mailchimp → US-based.
- Stripe → processes through US + Ireland.
- Meta/Facebook Pixel → US-based.
- Cloudflare → global.

Do any of the recipients above process data outside the UK?

If yes, make sure each recipient in the previous step has the country and safeguard filled in.

- Contact form messages → 24 months from last contact
- Newsletter subscribers → until they unsubscribe
- Customer accounts → for the life of the account + 30 days
- Invoices / order records → 6 years (HMRC rule)
- Website analytics → 14 or 26 months (GA4 defaults)
- Server logs → 30–90 days

Review retention periods per category.

### Automated decision-making

Each document costs **£9.99** and is generated from your answers. You can regenerate at any time; each generation is charged.

### 📢 External documents (for your website)

### 📄 Privacy Policy

Full Article 13 UK GDPR notice.

### 🍪 Cookie Policy

Cookie categories, trackers, how to manage.

### 🔔 Consent Banner

HTML + JS snippet with accept/reject/manage.

### ⚖️ Data Rights Page

All 7 rights, how to exercise, ICO complaints.

### 📮 DSAR Widget

Embeddable request form for your site.

### 📋 Internal records (for your governance)

### ⚖️ Legitimate Interests Assessment

LIA documenting the 3-part test per category.

### 📇 ROPA

Record of Processing Activities (Article 30).

### ⏱ Retention Schedule

Operational schedule per category with deletion process.

### 🚨 Breach Register

Template for logging breaches per Article 33(5).

### ✅ Consent Log

Template for recording consents per Article 7.

### My generated documentsDownload all as bundle

*Nothing generated yet.*

## 📄 LLMs.txt Auditor

Fetch and score your llms.txt against the [llmstxt.org spec](https://llmstxt.org) — then generate a corrected file using real data from your live site.

Share tips or ask about llms.txt. Comments are reviewed before appearing.

Loading comments…

Part of [aiwebpageseo — Full SEO Audit Platform](/seo-audit-platform.html) · [Top Up Credits](/seo-auth/topup.html) · [Dashboard](/seo-auth/dashboard.html)

### From the blog — AEO & content guides

What is AEO short for?

What is AEO and how does it work?

How to use AEO in SEO?

What is AEO in simple words?

What does AEO mean in business?

What is replacing SEO?

### About aiwebpageseo

aiwebpageseo.com is a data-driven SEO and AEO (Answer Engine Optimisation) platform providing a free suite of technical website tools. Rather than relying on AI-theorised assumptions, the platform analyses live URL performance, delivering objective diagnostics, page speed metrics, CLS debugging, and site crawl data alongside actionable technical tutorials.

## ⚠ Audit returning an error or timeout?

If an audit fails with *"Could not fetch page"* or *"Request timed out"*, it almost always means the target site is blocking our server — not a fault with the tool. Our audits fetch your page from our server (IP **87.106.96.71**) like a normal browser. Some hosts, firewalls, or security plugins (Cloudflare, Wordfence, hosting WAFs) silently block requests from datacentre IP addresses, so the connection never completes and the audit times out.

How to fix it — if you own the site:

1. Ask your host or firewall provider to **whitelist (allowlist) our IP address: `87.106.96.71`** for HTTP and HTTPS (ports 80 and 443).
2. If you use **Cloudflare**: Security → WAF → Tools → IP Access Rules → add `87.106.96.71` as *Allow*.
3. If you use **Wordfence** or a WordPress security plugin: add `87.106.96.71` to its allowlist / whitelist of blocked IPs.
4. If you use a **hosting firewall** (cPanel, Plesk, ModSecurity): ask support to allow our IP through, on ports 443 and 80.
5. Re-run the audit a few minutes after the change takes effect.

Other causes: the URL is wrong or not public, the site is genuinely down, or it's behind a login. Check the page loads in a normal browser first.

Not sure about allowing our IP? Click **🛡 Verify us** in the top bar first and run the checks to confirm exactly what our server does — we only read public pages, nothing hidden.

## 🛡 Don't trust us? Verify exactly what we do.

We believe an SEO tool should be transparent. When you run an audit, our server fetches your page exactly like a normal browser — nothing hidden. You can confirm **we're** clean too: run these from any terminal to check our own site serves identical content to humans and search engines (no cloaking), with honest headers.

```
# 1. Download our homepage as a browser, as Googlebot, and as Bingbot
curl -s -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/124.0 Safari/537.36" https://aiwebpageseo.com/ -o browser.html
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://aiwebpageseo.com/ -o googlebot.html
curl -s -A "Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)" https://aiwebpageseo.com/ -o bingbot.html
# EXPECT: three files saved, each the same size. Check with:  ls -l browser.html googlebot.html bingbot.html

# 2. Compare them — identical output means we serve bots and humans the SAME content (no cloaking)
diff browser.html googlebot.html
diff browser.html bingbot.html
# EXPECT: no output at all. Empty = the files are identical = NO CLOAKING (pass).
#         Any lines printed would mean we serve bots different content (fail).

# 3. Check for hidden text in what we served you
grep -ioE "display:\s*none|visibility:\s*hidden" browser.html
# EXPECT: only a handful (collapsed menus/modals are normal). NOT wrapped around blocks of keywords.

# 4. Confirm our redirects behave the same for a browser and for Googlebot
curl -sIL -A "Mozilla/5.0 Chrome/124.0" https://aiwebpageseo.com/ | grep -iE "HTTP/|location"
curl -sIL -A "Googlebot/2.1" https://aiwebpageseo.com/ | grep -iE "HTTP/|location"
# EXPECT: both show "HTTP/2 200" with no "location:" redirect, and BOTH identical.
#         If Googlebot got a different redirect than the browser, that's cloaking (fail).

# 5. Inspect the exact response headers we send
curl -sI https://aiwebpageseo.com/
# EXPECT: "HTTP/2 200", "content-type: text/html", "server: nginx".
#         NO "x-robots-tag: noindex" (our site is meant to be indexed), nothing misleading.
```

If the `diff` output is empty, we serve identical content to browsers and search engines — that's proof we don't cloak. We only read public pages: no logins, no writes, no hidden requests.
</doc>

<doc title="Site Audit" desc="Complete technical SEO audit including Core Web Vitals, robots, redirects and meta tags.">
# 🛠 Technical SEO Audit Tools

A complete suite of technical SEO tools — from deep site crawls and Core Web Vitals to local SEO signals, code validators, meta tag analysis and image optimisation.

## 🔍 Site Audit

Full crawl analysis — checks for SEO issues, broken links, redirect chains, missing tags & duplicate content

Enter a URL and click Analyze to begin the audit

- 🏷️ On-Page SEO
- Title tag — presence & length (50–60 chars)
- Meta description — presence & length
- H1 tag — single, correct placement
- H2–H6 heading hierarchy & level skipping
- Canonical tag — presence & relative/absolute
- Robots meta directives (noindex, nofollow)
- Open Graph tags — all required fields
- Twitter/X Card tags
- HTML lang attribute
- Charset declaration
- Word count & thin content detection
- Content-to-HTML ratio

- ⚡ Technical & Performance
- HTTPS / SSL active
- HTTP status code (200, 404, 403…)
- Redirect detection
- Mobile viewport meta tag
- Page load TTFB
- HTML page size
- Render-blocking scripts in <head>
- Images missing width/height attributes
- Image alt attributes
- Links with no anchor text
- Deprecated HTML elements
- Security headers presence
- Favicon declared
- Inline style usage

- 🗂️ Schema & Structured Data
- JSON-LD schema detection
- Schema parse error detection
- Schema types identified
- 🔗 Quick Actions
- → Check robots.txt & sitemap
- → Check redirect chains
- → Core Web Vitals detail
- → Deep meta tag analysis
- → Hreflang checker

Investigation: [The inadequacies of Scam-Detector.com’s automated trust scores](/scam-detector.com.html) — how a score gets published about your business with no evidence, no notice and no right of reply.

Research: [llms.txt adoption measured across 5,011 UK websites](/ai-file-adoption-uk-2026.html) — 24.76% of sole traders publish one against 11.16% of big brands, and five of the eight AI files exist on none of them.

## 🤖 Robots.txt & Sitemap Tester

Fetch, validate and analyse robots.txt and sitemap.xml for any domain

## ↪️ Redirect Chain Checker

Follow all redirects for any URL and identify chains that waste link equity

We'll follow every redirect and show you the full chain — redirect chains (A→B→C) lose link equity at each hop.

## 🌍 Hreflang Checker

Validate hreflang tags for international SEO — detect missing, incorrect or conflicting tags

Hreflang tags tell Google which language/region each page targets. Incorrect implementation is one of the most common international SEO mistakes.

## ⚡ Core Web Vitals Explainer

Get your PageSpeed Core Web Vitals explained in plain English with specific fix instructions

Uses Google's PageSpeed Insights API to fetch your Core Web Vitals, then explains each metric and gives you specific, actionable steps to improve it.

## 🏷 Meta Tag Analyzer

Analyze all meta tags, OG tags, Twitter Cards & SEO directives from a URL or pasted HTML

## 🌐 HTML Checker

Validates HTML syntax, semantic structure, SEO best practices & accessibility attributes

## 🎨 CSS Checker

28-point CSS audit — syntax validation, performance, specificity, accessibility, browser compatibility, font loading, animation safety and responsive checks. Built for SEO agencies.

- →Unbalanced curly braces
- →Missing semicolons after declarations
- →Empty rule blocks (dead code)
- →Duplicate selectors
- →Duplicate property declarations
- →HTTP (non-HTTPS) resource URLs
- →Mixed colour format inconsistency

- →File size & critical CSS guidance
- →Rule count & IE selector limit
- →Universal selector (*) performance
- →@import render-blocking
- →@font-face font-display strategy
- →Excessive custom fonts (>4)
- →Excessive !important usage

- →ID selectors vs class selectors
- →Deep selector nesting (3+ levels)
- →CSS custom properties (variables) usage
- →Vendor prefix overuse

- →outline:none on :focus (WCAG 2.4.7)
- →Missing :focus-visible styles
- →Font sizes below 12px
- →user-select:none on readable content
- →overflow:hidden on body / html

- →Missing prefers-reduced-motion query
- →will-change overuse (GPU memory)
- →Non-composited animation properties
- →Layout-triggering transitions (reflow)

- →Fixed pixel widths (>600px) on mobile
- →Missing @media queries
- →CSS Grid without @supports fallback
- →CSS custom properties support

## 🔧 JavaScript Checker

18-point JavaScript audit — security vulnerabilities (eval, innerHTML XSS), performance issues (script size, synchronous XHR), modern JS practices (const/let, strict mode, async error handling) and memory leak detection.

## 📋 JSON-LD & Schema Checker

Validates JSON syntax and performs deep Schema.org compliance checks — Article, Product, FAQPage, LocalBusiness, BreadcrumbList, WebSite, HowTo, Event, Review, Person and Organization types all checked for required and recommended fields.

## 🖼 Image Optimisation

Audit every image on a page for size, format, alt text, dimensions and lazy loading

Fetches the page and audits all img tags found

One image URL per line. Checks format and URL patterns. File size checked where headers allow.

Fetching page and auditing images…

| Image | Alt | Format | Est. Size | W/H Attrs | Lazy | Issues |

Enter a page URL and click Analyse to audit all images

## 📊 Site Audit Pro

The deepest audit available — combines on-page SEO, accessibility, schema, Lighthouse, backlinks, ranked keywords, brand SERP, sentiment and more in a single report.

Audit your site and a competitor's at the same time. Results show side-by-side so you can spot what they're doing better — and what you're doing better.

Provide your handles or URLs for any platforms you use. Leave blank to skip. Inputs save automatically in your browser.
 Just enter the handle (e.g. `aipageseo`) — we will build the full URL for you.

Enter a URL, choose location and language, then click Start Audit

## 📍 Local SEO Checker

Audit your local business page for Google Maps 3-pack ranking signals — schema, NAP, hours, geo and GBP

Select your country to see country-specific directories in the NAP report. Leave on Auto-detect to read country from your schema.

Auditing local SEO signals…

- →LocalBusiness JSON-LD present
- →Business name in schema
- →Full address (street, city, postcode, country)
- →Telephone number in schema
- →Opening hours (openingHoursSpecification)
- →Geo coordinates (lat & lng)
- →Price range (priceRange)
- →Aggregate rating & review count
- →sameAs links to GBP and directories
- →areaServed or serviceArea defined

- →Business name visible on page (H1/heading)
- →Phone number visible on page
- →Address visible in footer or contact section
- →Google Maps iframe embed present
- →Google Business Profile link
- →Review / testimonial content present
- →NAP: schema name matches page name
- →NAP: schema phone matches on-page phone

```
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "The Sheffield Plumbing Company",
  "url": "https://example.com",
  "telephone": "+441142000000",
  "priceRange": "££",   // ££/£££ (UK), $$/$$$ (CA/US/AU), €€ (EU)
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "12 High Street",
    "addressLocality": "Sheffield",
    "addressRegion": "South Yorkshire",  // Province/State for CA/US/AU
    "postalCode": "S1 1AA",
    "addressCountry": "GB"   // ISO 3166-1: GB, US, CA, AU, DE, FR etc
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 53.3811,
    "longitude": -1.4701
  },
  "openingHoursSpecification": [
    {
      "@type": "OpeningHoursSpecification",
      "dayOfWeek": ["Monday","Tuesday","Wednesday","Thursday","Friday"],
      "opens": "08:00",
      "closes": "18:00"
    }
  ],
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.9",
    "reviewCount": "247",
    "bestRating": "5"
  },
  "sameAs": [
    "https://www.google.com/maps?cid=YOUR_CID",
    "https://www.yell.com/biz/example",
    "https://www.facebook.com/example"
  ]
}
```

```
"geo": {
  "@type": "GeoCoordinates",
  "latitude": 53.3811,
  "longitude": -1.4701
}
```

Step-by-step guides for every major local SEO signal. Each links directly to the relevant section of the Learning Hub.

Part of the [AIPageSEO Suite](/) · [Pricing](/pricing.html) · [Dashboard](/seo-auth/dashboard.html) · [Content Tools](/content-tools.html) · [Schema Tools](/schema-tools.html) · [Performance Tools](/performance-tools.html)

### From the blog — Site Audit guides

What does a site audit mean?

How do you do an SEO audit?

How to do an SEO site audit?

What is included in a site audit?

What to look for in a technical SEO audit?

Can I do a site audit myself?

## ⚠ Audit returning an error or timeout?

If an audit fails with *"Could not fetch page"* or *"Request timed out"*, it almost always means the target site is blocking our server — not a fault with the tool. Our audits fetch your page from our server (IP **87.106.96.71**) like a normal browser. Some hosts, firewalls, or security plugins (Cloudflare, Wordfence, hosting WAFs) silently block requests from datacentre IP addresses, so the connection never completes and the audit times out.

How to fix it — if you own the site:

1. Ask your host or firewall provider to **whitelist (allowlist) our IP address: `87.106.96.71`** for HTTP and HTTPS (ports 80 and 443).
2. If you use **Cloudflare**: Security → WAF → Tools → IP Access Rules → add `87.106.96.71` as *Allow*.
3. If you use **Wordfence** or a WordPress security plugin: add `87.106.96.71` to its allowlist / whitelist of blocked IPs.
4. If you use a **hosting firewall** (cPanel, Plesk, ModSecurity): ask support to allow our IP through, on ports 443 and 80.
5. Re-run the audit a few minutes after the change takes effect.

Other causes: the URL is wrong or not public, the site is genuinely down, or it's behind a login. Check the page loads in a normal browser first.

Not sure about allowing our IP? Click **🛡 Verify us** in the top bar first and run the checks to confirm exactly what our server does — we only read public pages, nothing hidden.

## 🛡 Don't trust us? Verify exactly what we do.

We believe an SEO tool should be transparent. When you run an audit, our server fetches your page exactly like a normal browser — nothing hidden. You can confirm **we're** clean too: run these from any terminal to check our own site serves identical content to humans and search engines (no cloaking), with honest headers.

```
# 1. Download our homepage as a browser, as Googlebot, and as Bingbot
curl -s -A "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/124.0 Safari/537.36" https://aiwebpageseo.com/ -o browser.html
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://aiwebpageseo.com/ -o googlebot.html
curl -s -A "Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)" https://aiwebpageseo.com/ -o bingbot.html
# EXPECT: three files saved, each the same size. Check with:  ls -l browser.html googlebot.html bingbot.html

# 2. Compare them — identical output means we serve bots and humans the SAME content (no cloaking)
diff browser.html googlebot.html
diff browser.html bingbot.html
# EXPECT: no output at all. Empty = the files are identical = NO CLOAKING (pass).
#         Any lines printed would mean we serve bots different content (fail).

# 3. Check for hidden text in what we served you
grep -ioE "display:\s*none|visibility:\s*hidden" browser.html
# EXPECT: only a handful (collapsed menus/modals are normal). NOT wrapped around blocks of keywords.

# 4. Confirm our redirects behave the same for a browser and for Googlebot
curl -sIL -A "Mozilla/5.0 Chrome/124.0" https://aiwebpageseo.com/ | grep -iE "HTTP/|location"
curl -sIL -A "Googlebot/2.1" https://aiwebpageseo.com/ | grep -iE "HTTP/|location"
# EXPECT: both show "HTTP/2 200" with no "location:" redirect, and BOTH identical.
#         If Googlebot got a different redirect than the browser, that's cloaking (fail).

# 5. Inspect the exact response headers we send
curl -sI https://aiwebpageseo.com/
# EXPECT: "HTTP/2 200", "content-type: text/html", "server: nginx".
#         NO "x-robots-tag: noindex" (our site is meant to be indexed), nothing misleading.
```

If the `diff` output is empty, we serve identical content to browsers and search engines — that's proof we don't cloak. We only read public pages: no logins, no writes, no hidden requests.
</doc>

<doc title="Pricing" desc="Pay-as-you-go credits with no monthly subscription. Credits never expire.">
# Plans for every SEO need

From solo bloggers to large agencies. All tools built into your platform — unlock more as you grow.

## 💳 Prefer pay-as-you-go?

No subscription, no monthly commitment — top up credits and use any tool. Credits never expire.

No payment needed to sign up — new users get **100 free points**. Create your account now and top up credits whenever you're ready.

| Feature | Free | Bronze | Silver | Gold | Platinum | Diamond | Enterprise |

| LIMITS |

| Audits per day | 2 | 5 | 15 | 50 | 150 | ∞ | ∞ |

| Results shown | Top 5 | Top 10 | Full | Full | Full | Full | Full |

| Site Crawler pages | ✗ | ✗ | 10 | 25 | 50 | 100 | 200 |

| Competitor sites | ✗ | ✗ | 1 | 3 | 3 | 5 | 10 |

| Score history | ✗ | 7 days | 30 days | 90 days | 1 year | ∞ | ∞ |

| Team seats | 1 | 1 | 1 | 2 | 5 | 5 | 10 |

| CORE TOOLS |

| Site Audit | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Page Speed | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Meta Analyzer | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| HTML / CSS / JS Checker | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| SERP Preview | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Schema Generator (manual) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| BRONZE+ |

| Keyword Analysis | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Internal Link Analysis | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Redirect Checker | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Robots & Sitemap | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Readability Checker | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Social Preview | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |

| SILVER+ |

| Site Crawler | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| E-E-A-T Checker | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| AEO Checker | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| CLS Debugger | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Image Optimisation | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Hreflang Checker | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| Backlink Tools | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✓ |

| GOLD+ |

| Competitor Analysis | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| AI Schema Generator | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| Schema Debugger | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| Score History | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| Keyword Gap Analysis | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| PLATINUM+ |

| AI Learning Hub (Ask SEO AI) | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ |

| Bulk Export (CSV / PDF) | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ |

| DIAMOND |

| Unlimited standard audits* | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ |

| Competitor AEO Analysis | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| Buy extra API credits | ✗ | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ |

| 100-page crawler | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ |

| Unlimited history | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ | ✓ |

| ENTERPRISE CONTROL |

| Enterprise Control Panel | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

| Per-seat tool restrictions | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

| Per-seat API call limits | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

| Task assignment per seat | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

| Usage reporting per user | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

| 200-page crawler | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |

### Upgrade Plan

Starting your subscription
</doc>

</services>
</project>