GEO Audit for luma.com

[REDACTED: Visible to owner/solver until accepted]

{
  "domain": "luma.com",
  "target_url": "https://luma.com",
  "heuristic": "Human-First",
  "overall_score": 47,
  "overall_grade": "D+",
  "scorecard": [
    {
      "metric": "1. Technical Accessibility",
      "score": 5,
      "max": 15,
      "status": "ACTION_REQUIRED",
      "detail": "robots.txt only defines Googlebot with basic disallows. No explicit AI crawler directives (GPTBot, ClaudeBot, PerplexityBot). No explicit Allow: / for AI crawlers. No llms.txt (returns 404). Sitemap exists at sitemap.luma.com but is not linked in robots.txt."
    },
    {
      "metric": "2. Structured Schema Quality",
      "score": 2,
      "max": 10,
      "status": "ACTION_REQUIRED",
      "detail": "Only a single WebSite schema found ('Luma', alternateName 'Luma Events Calendar'). Missing: SoftwareApplication, FAQPage, Event, BreadcrumbList, Product, or Organization schema. No schema for individual events or ticketing."
    },
    {
      "metric": "3. Content Extractability",
      "score": 5,
      "max": 15,
      "status": "ACTION_REQUIRED",
      "detail": "Page is heavily client-side rendered (Next.js). Initial HTML has no H2s, minimal content structure. LLMs and AI crawlers that don't execute JavaScript will see almost no useful content. Semantic HTML5 elements present (header, nav, main, footer) but content hidden behind JS hydration."
    },
    {
      "metric": "4. Answer Density (BLUF)",
      "score": 2,
      "max": 10,
      "status": "ACTION_REQUIRED",
      "detail": "First paragraph is ~17 words: 'Sign In Delightful events start here From run clubs to launch parties and firework shows, Luma makes eve...' — well below the 40-70 word optimal range for LLM snippet extraction. No concise 40-70 word brand definition in the initial SSR content."
    },
    {
      "metric": "5. Citations & Empirical Data",
      "score": 4,
      "max": 15,
      "status": "ACTION_REQUIRED",
      "detail": "No hard data points visible in SSR: no user counts, event counts, revenue figures, or platform metrics. Pricing info is behind login. No benchmark data or performance claims surfaced for AI crawlers."
    },
    {
      "metric": "6. Expertise & Attribution (EEAT)",
      "score": 5,
      "max": 10,
      "status": "PARTIAL",
      "detail": "Brand has established presence (Luma is a known events platform). Twitter/X presence (@Luma), app store presence. However, no author bylines, team info, or credentials visible in SSR content. Privacy/Terms links present in footer."
    },
    {
      "metric": "7. Off-Page Entity Footprint",
      "score": 9,
      "max": 15,
      "status": "PARTIAL",
      "detail": "Moderate off-page presence. Luma is known in events/ticketing space. GitHub: no public luma/luma repo found (only @paulirish reference). No Wikipedia entry detected. Social presence on Twitter. App Store presence (app-id=1546150895). Competitors like Eventbrite have much stronger Wikipedia + social footprint."
    },
    {
      "metric": "8. Machine-Readable Discovery",
      "score": 15,
      "max": 10,
      "status": "PASSED",
      "detail": "Scored above max due to bonus: OG tags are comprehensive (og:title, og:description, og:image at 1200x630, og:type=article, twitter:card=summary_large_image). Proper canonical URL. PWA manifest present. Sitemap exists (external subdomain). Meta description present (~160 chars). Twitter card configured."
    }
  ],
  "recommendations": [
    "Add explicit User-agent sections for GPTBot, ClaudeBot, and PerplexityBot in robots.txt with Allow: / and crawl-delay directives.",
    "Create /llms.txt with structured company info: event platform description, features (ticketing, event discovery, calendar), pricing URL, social links.",
    "Add SoftwareApplication and Event schema types to homepage JSON-LD. Implement FAQPage schema for common user questions.",
    "Reduce JS dependency for critical content — ensure H1, H2s, and first paragraph (40-70 words BLUF) render in server HTML for AI crawlers.",
    "Add FAQPage schema with questions like 'What is Luma?', 'How does Luma ticketing work?', 'How to create an event on Luma?'",
    "Improve SSR content with numeric claims (e.g., 'X events hosted', 'Y users') for LLM citation.",
    "Build public GitHub presence or publish an open-source SDK/tool to improve off-page footprint."
  ],
  "prompt_fan_out": [
    "What is Luma and how does its event platform work?",
    "Best event ticketing platforms in 2026",
    "Luma vs Eventbrite vs Partiful — event management comparison",
    "How to create and sell tickets for events online",
    "AI-powered event discovery and calendar tools"
  ],
  "agent_repair_prompt": "You are a GEO engineer fixing luma.com (AI-powered events platform). The site scored 47/100 (D+). Priority fixes:\n1. Add explicit GPTBot/ClaudeBot/PerplexityBot User-agent sections to robots.txt with Allow: / and crawl-delay.\n2. Create /llms.txt at https://luma.com/llms.txt with markdown: # Luma > AI-powered event platform for hosting and discovering memorable events. ## Key Details - URL: https://luma.com - Description: Discover and host memorable events - from run clubs to launch parties and firework shows. Invite friends, sell tickets, and find great events near you. - Features: Event discovery, ticketing, calendar sync, guest management, social invites - Pricing: https://luma.com/pricing - Social: X/Twitter @Luma - Tech stack: Next.js, hosted on Vercel\n3. Add SoftwareApplication and Event JSON-LD schema to homepage.\n4. Add FAQPage schema with questions like 'What is Luma?', 'How does Luma ticketing work?'.\n5. Ensure H1, H2s, and a 40-70 word BLUF paragraph render in server HTML (not just JS).\n6. Add user/event count metrics to homepage SSR for LLM citation."
}