This site is difficult for AI tools to read right now.
Key strengths include content signals, while homepage access and crawler policy need attention.
Recommended next step
remove AI crawler Disallow: / rules or replace them with narrower path-level restrictions for private content only.
Overall score
What happens next
Monitor this score as your site changes
Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.
// score breakdown
8 checks
Public link
llmscan.dev/scan/7Zu9t0ISzkm7udHufLb33
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Poor · 20/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/7Zu9t0ISzkm7udHufLb33"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/7Zu9t0ISzkm7udHufLb33/badge.png"
alt="LLM Scan AI visibility score badge"
width="460"
height="120"
style="width: 260px; max-width: 100%; height: auto;"
/>
</a>Share your score
Post the public report with: “We scored 20/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
The homepage is reachable, but robots.txt blocks GPTBot, ClaudeBot, and Google-Extended from crawling the site.
Signal weight
Evidence
Recommendation
Next step: Remove AI crawler Disallow: / rules or replace them with narrower path-level restrictions for private content only.robots.txt explicitly blocks GPTBot, ClaudeBot, and Google-Extended from the whole site.
Signal weight
Evidence
Recommendation
Next step: Remove AI crawler Disallow: / rules or add narrower Allow/Disallow rules if AI crawlers should be able to discover public content.The llms.txt file exists but is missing one or more expected quality signals.
Signal weight
Evidence
Recommendation
Next step: Publish /llms.txt as text or markdown with more than 200 characters, markdown headings, and at least one absolute URL.The sitemap.xml file could not be parsed as valid XML.
Signal weight
Evidence
Recommendation
Next step: Regenerate sitemap.xml with valid XML and a sitemap <urlset> or <sitemapindex> root element.The homepage returned HTML when requested with Accept: text/markdown, so the server appears to ignore markdown content negotiation.
Signal weight
Evidence
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
Evidence
Recommendation
Next step: Add missing semantic elements: article, footer. Add visible body copy after script and style removal so the page has at least 200 words.No JSON-LD, Microdata, or RDFa structured data was found on the page.
Signal weight
Evidence
Recommendation
Next step: Add JSON-LD structured data with Organization or WebSite schema so AI systems can identify the site owner or website entity.AI content usage signals detected via Content-Signal robots.txt directives.
Signal weight
Evidence
Recommendation
Next step: Consider adding Content-Signal HTTP header, AI-specific head meta tags, robots noai/noimageai directive so AI systems can consistently discover content usage preferences across robots.txt, HTTP headers, and HTML metadata.What happens next
Keep watching this score
Scores move when sites and models change. This one was measured once, on Aug 24, 2026.
// generated fixes
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 packageNot 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
# bidout.lol > Pay to rank. Higher bid wins. New spots start at $1. 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://bidout.lol/- Site type: website# 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://bidout.lol/sitemap.xml # AI crawler access# Add explicit Allow rules for blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://bidout.lol/#organization", "name": "bidout.lol", "description": "Pay to rank. Higher bid wins. New spots start at $1.", "url": "https://bidout.lol/",# 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.What happens next
Monitor this score as your site changes
Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.
Related scans