This site has a useful foundation, but important gaps still limit AI readability.
Key strengths include sitemap and structured data, while plain-text page access and content signals need attention.
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.
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 weeklyOverall score
// score breakdown
8 checks
Public link
llmscan.dev/scan/7dNl857rFjuKEl-I3GbbS
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Needs Work · 54/100A compact badge for footer, press, or trust sections that links visitors to this public report.
<a href="https://www.llmscan.dev/scan/7dNl857rFjuKEl-I3GbbS"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/7dNl857rFjuKEl-I3GbbS/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 54/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 contains AI crawler restrictions for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.
Signal weight
Evidence
Recommendation
Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access; serve a non-empty HTML homepage with a canonical link tag.robots.txt contains AI-crawler path blocks for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.
Signal weight
Evidence
Recommendation
Next step: Review AI crawler Disallow rules and keep only the paths that should be excluded from AI crawler access.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 is valid and contains URL entries.
Signal weight
Evidence
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: Avoid skipped heading levels so sections progress from h1 to h2 to h3 without gaps.Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.
Signal weight
Evidence
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
# Personal Finance Organisation & Secure Legacy Vault | SuccessionKeeper > Organise your financial world in one secure vault. Build a private roadmap for your primary nominee with wellbeing check-ins. Start your legacy today. 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://successionkeeper.com/- Site type: organization# robots.txt additions# Copy these blocks into the existing robots.txt file. Keep current rules unless a note calls out a conflicting Disallow. # AI crawler access# Add explicit Allow rules for blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://successionkeeper.com/#organization", "name": "Personal Finance Organisation & Secure Legacy Vault | SuccessionKeeper", "description": "Organise your financial world in one secure vault. Build a private roadmap for your primary nominee with wellbeing check-ins. Start your legacy today.", "url": "https://successionkeeper.com/", "logo": "https://successionkeeper.com/favicon.svg",# 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.