skoda.co.uk — AI Site Grade

Analysis

Skoda.co.uk: Full AI crawler access, but a cold-knowledge gap on the EV pivot and no structured AI surface

The most striking finding is that skoda.co.uk gives every major AI crawler full, unrestricted 200 access with identical content to a browser — yet has no llms.txt, no AI-specific robots.txt directives, and its Organization schema omits the "Simply Clever" tagline and EV positioning that the brand is known for in cold LLM knowledge.

Crawler Access

All 11 tested AI bots (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, Bytespider, Applebot-Extended, anthropic-ai, Perplexity-User) receive a 200 status with 455KB of identical HTML — no UA-based blocking, no JS shell, no Cloudflare challenge. The site runs on Azure (via x-azure-ref header, cdn.skoda-auto.com CDN) with HSTS and X-Frame-Options set. The robots.txt is a single User-agent: * with Disallow: (empty, meaning allow all) and a sitemap pointer — no AI-bot rules at all. The /llms.txt returns a 404 error page (248KB of HTML/CSS/JS). The sitemap index contains 12 sub-sitemaps covering ~1,400+ URLs including web pages, apps (retailers, stock, chargemap, manuals, visualizer), suggesting a mature but non-AI-optimized information architecture.

Cold-Knowledge Gap

The LLM knows Skoda UK as a value-for-money, practical family car brand with the "Simply Clever" tagline (ice scraper in fuel cap, umbrella in door), strong reliability ratings, and the Octavia/Fabia/Kodiaq as key models. The actual site, however, leads heavily on the electric transition: the homepage hero is the all-electric Epiq, followed by Elroq and Enyaq EVs. The "Simply Clever" phrase does not appear anywhere in the homepage text, meta description, or schema. The Organization schema lists founding date (1895), address, and social links — but no slogan, description, or knowsAbout fields that would anchor the brand's distinctive value proposition for AI knowledge graphs.

Schema Posture

Product pages (e.g., Enyaq SE L) use Vehicle schema with enginePower, torque, fuelType, offers.price — solid structured data for individual models. The FAQ pages (/discover/faqs and /electric-hybrid-cars/faq) correctly implement FAQPage with Question/Answer entities, making them strong candidates for AI answer extraction. However, the range overview page (/new-cars/range) contains only 19 words of visible text and a single BreadcrumbList schema — no ItemList, no Vehicle collection, no comparison data. The homepage has no WebSite or SearchAction schema. The awards page (/awards) lists 8 recent What Car? and Parkers wins but has no Review or AggregateRating schema to make those awards machine-readable.

External Signals

The site references awards from What Car?, Parkers, Auto Express, Carwow, Fleet News, and The Car Expert — all credible UK automotive sources. DNS records show VW Group MX servers and MarkMonitor nameservers, confirming the corporate VW Group infrastructure. Social links point to Facebook, Instagram, X (Twitter), and YouTube. No Reddit threads or independent review aggregator citations were found in search, meaning AI models pulling external signals will rely heavily on the site's own content and general automotive press — neither of which strongly communicates the "Simply Clever" differentiation that the cold LLM already associates with the brand.

Findings

1. No llms.txt file for AI crawlers Medium

   The site returns a 404 for /llms.txt, missing the opportunity to provide a curated AI-friendly summary of key pages and brand information.

   What to change: Create an llms.txt file at the root listing key pages (homepage, model range, FAQs, awards) with brief descriptions.

2. Organization schema omits slogan and description High

   The homepage's Organization schema lacks 'slogan', 'description', and 'knowsAbout' fields, failing to communicate the 'Simply Clever' tagline and EV focus to knowledge graphs.

   What to change: Add 'slogan': 'Simply Clever', a 'description' summarizing the brand's EV transition, and 'knowsAbout' referencing electric models.

3. Cold LLM knowledge does not reflect EV-heavy site content High

   LLMs recall Skoda as a value family brand with 'Simply Clever' features, but the site leads with electric models (Epiq, Elroq, Enyaq) — a gap that could cause AI-generated summaries to misrepresent the brand's current focus.

   What to change: Add structured data (e.g., 'slogan', 'description') and an llms.txt to explicitly communicate the EV pivot to AI crawlers.

4. Car range overview page has minimal text and no collection schema High

   The /new-cars/range page contains only 19 words of visible text and a single BreadcrumbList schema, making it nearly invisible to AI crawlers for understanding the model lineup.

   What to change: Add descriptive text for each model and implement ItemList or VehicleCollection schema to list all models with key specs.

5. Awards page lacks Review or AggregateRating schema Medium

   The awards page lists 8 wins from What Car? and Parkers but has no structured data to make these awards machine-readable for AI knowledge graphs.

   What to change: Add AggregateRating or Review schema for each award, including the awarding organization and year.

6. Homepage missing WebSite and SearchAction schema Medium

   The homepage does not include WebSite schema with SearchAction, reducing its ability to appear in AI-powered search result features like site links or search boxes.

   What to change: Add WebSite schema with SearchAction pointing to a search endpoint (e.g., /search?q={search_term_string}).

7. Robots.txt has no AI-bot-specific directives Low

   The robots.txt allows all bots with a single wildcard rule, missing the chance to guide AI crawlers to priority pages or manage crawl rate.

   What to change: Add explicit rules for AI bots (e.g., GPTBot, ClaudeBot) to prioritize key pages like model ranges and FAQs.

8. FAQ pages are well-structured but not surfaced in llms.txt Medium

   The FAQ pages use correct FAQPage schema with Q&A pairs, making them ideal for AI answer extraction, but they are not listed in any AI-friendly surface like llms.txt.

   What to change: Include FAQ page URLs in the llms.txt file with brief descriptions.

9. Limited external signal diversity for AI models Low

   Web searches for Skoda UK reviews and brand reputation returned no results from Reddit or independent aggregators, meaning AI models rely heavily on the site's own content and general press.

   What to change: Encourage customer reviews on third-party platforms and engage in community forums to build external signals.

What's working

• All major AI crawlers receive full 200 access — Every tested AI bot (GPTBot, ClaudeBot, etc.) gets a 200 status with identical HTML to a browser, ensuring content is fully indexable.
• Product pages use correct Vehicle schema with detailed specs — Individual model pages (e.g., Enyaq SE L) include Vehicle schema with engine power, torque, fuel type, and pricing, making them rich for AI extraction.
• FAQ pages correctly implement FAQPage schema — Both /discover/faqs and /electric-hybrid-cars/faq use FAQPage with Question/Answer entities, making them strong candidates for AI answer extraction.
• Sitemap index covers 1,400+ URLs across 12 sub-sitemaps — The sitemap index includes sub-sitemaps for web pages, retailers, stock, chargemap, manuals, and visualizer, ensuring broad crawl coverage.
• LLM cold knowledge associates Skoda with 'Simply Clever' and reliability — LLMs recall Skoda UK as a value-for-money, practical family car brand with the 'Simply Clever' tagline and strong reliability ratings, providing a positive baseline.
• Awards page lists wins from credible UK automotive sources — The site references awards from What Car?, Parkers, Auto Express, Carwow, Fleet News, and The Car Expert, which are authoritative in the UK market.
• Site runs on Azure with HSTS and X-Frame-Options — The site uses Azure infrastructure with security headers (HSTS, X-Frame-Options), ensuring reliable and secure delivery.