luma.comscanned May 26, 2026 · 13:500.41s
Public AI visibility report

luma.comAI visibilityNeeds Work

This site has a useful foundation, but important gaps still limit AI readability.

Key strengths include crawler policy and structured data, while AI guidance file and plain-text page access need attention.

Recommended next step

publish an AI guidance file as text or markdown with more than 200 characters, markdown headings, and at least one absolute URL.

Why monitor after one scan?

AI visibility changes when teams ship new pages, edit pricing or docs, update sitemaps, or change crawler rules. Weekly monitoring catches those silent regressions before answer engines and agents start reading stale or broken signals.

Monitor weekly

Overall score

41/100
Needs Work
Go to fixesOverall position346 out of 491Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt15/15
llms.txt0/15
Sitemap0/10
Markdown support0/15
Semantic HTML5.7/10
Structured data10/10
Content signals0/5
2pass2warn4fail

Public link

llmscan.dev/scan/ojDhilOQokCbyqphyn6p6

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Needs Work · 41/100

Add a polished proof badge

A compact badge for footer, press, or trust sections that links visitors to this public report.

Embed codellmscan.dev/scan/ojDhilOQokCbyqphyn6p6
<a href="https://www.llmscan.dev/scan/ojDhilOQokCbyqphyn6p6"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/ojDhilOQokCbyqphyn6p6/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>
Open badge
L
LLM Scan
Needs Work
Score
41/100

Share your score

Post the public report with: “We scored 41/100 for AI-readability.”

Download fixes

Grab generated files and implementation notes for the highest-impact gaps.

Rescan weekly

Save this domain to catch regressions after content, sitemap, or robots changes.

Monitor weekly

// signal breakdown

8 signals AI systems depend on

The homepage is reachable, but the requested URL redirects before reaching the homepage.

Signal weight

10/20
Warn

Evidence

url
https://lu.ma/
finalUrl
https://luma.com/
status
200

Recommendation

Next step: Serve a non-empty HTML homepage with a canonical link tag that points to the preferred public URL.

robots.txt allows crawler access.

Signal weight

15/15
Pass

Evidence

robotsTxtUrl
https://luma.com/robots.txt
exists
true
rawRobotsTxt
User-agent: Googlebot Disallow: /social-share Disallow: /in/ Disallow: /company/ Disallow: /session-*

Recommendation

Next step: Add Sitemap directives to robots.txt so crawlers can find canonical sitemap files.

No llms.txt file was found for this site.

Signal weight

0/15
Fail

Evidence

llmsTxtUrl
https://luma.com/llms.txt
present
false
accessible
false

Recommendation

Next step: Publish /llms.txt as text or markdown with more than 200 characters, markdown headings, and at least one absolute URL.

No accessible XML sitemap was found for this site.

Signal weight

0/10
Fail

Evidence

sitemapUrl
https://luma.com/sitemap.xml
sitemapUrls
[https://luma.com/sitemap.xml]
robotsSitemapUrls
[]

Recommendation

Next step: Publish a valid XML sitemap at /sitemap.xml and reference it from robots.txt so crawlers and AI systems can discover important URLs.

The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.

Signal weight

0/15
Fail

Evidence

url
https://luma.com/
acceptHeader
text/markdown
status
200

Recommendation

Next step: Add content negotiation for Accept: text/markdown on the homepage and return a markdown representation with Content-Type: text/markdown. Keep the HTML response for regular browser requests.

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

6/10
Warn

Evidence

url
https://luma.com/
quality
partial
score
57

Recommendation

Next step: Expand the title tag to at least 10 characters. Add missing semantic elements: main, article. Add visible body copy after script and style removal so the page has at least 200 words.

Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.

Signal weight

10/10
Pass

Evidence

url
https://luma.com/
quality
good
hasStructuredData
true

Content-Signal directive not detected in headers, HTML metadata, or robots.txt.

Signal weight

0/5
Fail

Evidence

url
https://luma.com/
hasContentSignals
false
hasContentSignalHeader
false

Recommendation

Next step: Add the standard directive 'Content-Signal: ai-train=no, search=yes, ai-input=yes' to robots.txt, HTML metadata, or HTTP headers so AI systems can discover content usage preferences.

// generated fixes

Downloadable fix files

Preview the generated files below. Enter your email to reveal the full fixes, download the bundle, or copy the agent-ready implementation prompt.

Done-for-you

Agency package

Not sure how to ship the technical fixes? Book a call and we can help turn this report into implemented updates.

Fix planning from your scan

Implementation guidance

AI visibility monitoring

llms.txtMarkdown
# Luma > Discover and host memorable events effortlessly with Luma. Invite friends, sell tickets, and find great events happening near you. This llms.txt file summarizes the public, canonical resources that AI assistants and crawlers should use to understand this site. ## Site Overview - Canonical URL: https://luma.com/- Site type: web site
robots.txtTXT
# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # Sitemap discovery# Add this top-level directive so search and AI crawlers can discover the canonical sitemap.Sitemap: https://luma.com/sitemap.xml # AI crawler access# Add explicit Allow rules for AI crawlers so public content permissions are clear.User-agent: GPTBot
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://luma.com/#organization",      "name": "Luma",      "description": "Discover and host memorable events effortlessly with Luma. Invite friends, sell tickets, and find great events happening near you.",      "url": "https://luma.com/",      "logo": "https://luma.com/apple-touch-icon.png",
head metaHTML
# Content-Signal recommendations Use these directives to make AI-use preferences explicit for compliant crawlers and AI systems. They are advisory signals, so keep them aligned with robots.txt, terms, and access controls. ## Recommended values - ai-train=no: AI model training, fine-tuning, and dataset creation.- search=yes: AI search indexing, snippets, and discovery.- ai-input=yes: AI answer grounding, retrieval, and generated-response context.