AI can barely see this site. · roasted Aug 30, 2026
THE ROAST
Your event listing page is an H3 graveyard with zero Event schema—LLMs see 80+ event names but can't parse dates, times, or locations, so they literally can't tell a concert from a farmers market 💀
Film festival page probably has all the juicy details (dates! location! ticket info!) but zero Event schema, so AI systems can't scrape, compare, or recommend it—it's just decorative text 🎬📍❌
Blog hub with no BlogPosting or NewsArticle schema means your editorial content reads as 'generic webpage text' to LLMs instead of structured journalism—zero author attribution, zero publication date parsing 📝🚮
About page probably explains your mission, history, and what you do, but you have ZERO Service schema, so AI asks 'wait, what does Visit KC actually DO?' and makes something up 🤷💭
A whole page dedicated to deals and experiences with likely ZERO Product/Offer schema—LLMs can't extract pricing, validity dates, or redemption info, so your promotions are invisible to AI deal aggregators 💸❓
WHAT IS BROKEN
[CRITICAL] Visit KC has zero Service schema despite being a tourism board with clear service offerings (event listings, travel guides, attractions, accommodations coordination), yet LLMs have no structured way to understand what Visit KC actually provides.
[WARNING] Organization schema exists but lacks critical LocalBusiness attributes like address, telephone, email, and operational hours—crucial for a destination marketing organization that should be contactable.
[CRITICAL] The site has zero FAQ schema despite obvious FAQ content opportunities (visitors likely ask 'What's there to do in KC?' 'When are events?' 'What's KC famous for?' 'Where to stay?'), leaving structured FAQ data completely untapped.
[CRITICAL] Event pages (198 total pages) lack Event schema markup—each event listed should have @type: Event with name, description, startDate, location, image, but nothing is marked up, making event discovery impossible for AI.
[CRITICAL] Blog/article pages (visible in crawl: /articles/, /blog/) have no NewsArticle or BlogPosting schema, so LLMs treat them as generic text rather than structured editorial content with authors, publish dates, and editorial authority.
