● Live · scanning now
through the eyes of GPTBot, ClaudeBot, PerplexityBot.
Launching crawler checks, parsing machine-readable signals, and preparing generated fixes.
URL being scanned
your site
About 35s left
Idle
~35s remaining · auto-refreshing report
This site is difficult for AI tools to read right now.
The main areas needing attention are plain-text page access and sitemap.
Recommended 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.
Turn this scan into weekly monitoring.
Create a free workspace first, then unlock weekly monitoring for AI visibility changes after site, pricing, docs, sitemap, or crawler-rule updates.
Overall score
// score breakdown
8 checks
Public link
llmscan.dev/scan/N2QvTVbSGgESkyR48Qtkr
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Poor · 31/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/N2QvTVbSGgESkyR48Qtkr"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/N2QvTVbSGgESkyR48Qtkr/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 31/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 no canonical link tag was found.
Signal weight
Evidence
Recommendation
Next step: Serve a non-empty HTML homepage with a canonical link tag that points to the preferred public URL.The robots.txt file was found, but it contains formatting issues.
Signal weight
Evidence
Recommendation
Next step: Fix robots.txt syntax issues so each rule uses Field: value format, directives appear under a User-agent, and Sitemap entries use absolute URLs.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 exactly one h1 element that describes the page topic. Add missing semantic elements: main, article, nav, 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.Content-Signal directive not detected in headers, HTML metadata, or robots.txt.
Signal weight
Evidence
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
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
# RareRoles | Jobs You Won't Find on LinkedIn or Indeed > RareRoles: find jobs you won't find on LinkedIn or Indeed. Track applications and generate tailored resumes. 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://www.rareroles.com/- 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://www.rareroles.com/sitemap.xml # AI crawler access# Add explicit Allow rules for AI crawlers so public content permissions are clear.User-agent: GPTBot{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://www.rareroles.com/#organization", "name": "RareRoles | Jobs You Won't Find on LinkedIn or Indeed", "description": "RareRoles: find jobs you won't find on LinkedIn or Indeed. Track applications and generate tailored resumes.", "url": "https://www.rareroles.com/",# 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.