The homepage resolves, connects, returns HTTP 200 OK, exposes a canonical URL, and is not blocked by robots.txt.
Signal weight
20/20
Pass
Evidence
- url
- https://vaultaire.app/
- finalUrl
- https://vaultaire.app/
- status
- 200
Public AI visibility report
vaultaire.appAI visibilityNeeds Work
This site has a useful foundation, but important gaps still limit AI readability.
Key strengths include homepage access and crawler policy, while plain-text page access and sitemap 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
67/100
Needs Work// score breakdown
Points by check
8 checks
Crawlability20/20PASS
Robots.txt15/15PASS
llms.txt15/15PASS
Sitemap0/10FAIL
Markdown support0/15FAIL
Semantic HTML7.1/10WARN
Structured data10/10PASS
Content signals0/5FAIL
4pass1warn3fail
Public link
llmscan.dev/scan/Od8-ewbrFd5a9gjLTDg25
Signals checked
8 AI visibility signals
Fix bundle
4 copy-ready files
Share badge
Needs Work · 67/100Add a polished proof badge
A compact badge for footer, press, or trust sections that links visitors to this public report.
Embed codellmscan.dev/scan/Od8-ewbrFd5a9gjLTDg25
<a href="https://www.llmscan.dev/scan/Od8-ewbrFd5a9gjLTDg25"
target="_blank"
rel="noopener"
>
<img
src="https://www.llmscan.dev/scan/Od8-ewbrFd5a9gjLTDg25/badge.png"
alt="LLM Scan AI visibility score badge"
width="460"
height="120"
style="width: 260px; max-width: 100%; height: auto;"
/>
</a>L
LLM Scan
Needs Work
Score
67/100
Share your score
Post the public report with: “We scored 67/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
robots.txt allows crawler access and includes Sitemap references.
Signal weight
15/15
Pass
Evidence
- robotsTxtUrl
- https://vaultaire.app/robots.txt
- exists
- true
- rawRobotsTxt
- User-agent: * Allow: / # Explicitly allow GPTBot User-agent: GPTBot Allow: / # Explicitly allow ClaudeBot User-agent: ClaudeBot Allow: / # Explicitly allow Google-Extended User-agent: Google-Extended Allow: / # Explicitly allow CCBot User-agent: CCBot Allow: / # Explicitly allow Bytespider User-agent: Bytespider Allow: / # Explicitly allow PerplexityBot User-agent: PerplexityBot Allow: / # Explicitly allow OAI-SearchBot User-agent: OAI-SearchBot Allow: / # Explicitly allow ChatGPT-User User-agent: ChatGPT-User Allow: / # Explicitly allow bingbot User-agent: bingbot Allow: / # Explicitly allow Amazonbot User-agent: Amazonbot Allow: / # Explicitly allow coccocbot User-agent: coccocbot Allow: / Sitemap: https://vaultaire.app/sitemap.xml
The llms.txt file was found and includes the expected text, length, heading, and URL signals.
Signal weight
15/15
Pass
Evidence
- llmsTxtUrl
- https://vaultaire.app/llms.txt
- present
- true
- accessible
- true
No accessible XML sitemap was found for this site.
Signal weight
0/10
Fail
Evidence
- sitemapUrl
- https://vaultaire.app/sitemap.xml
- sitemapUrls
- [https://vaultaire.app/sitemap.xml]
- robotsSitemapUrls
- [https://vaultaire.app/sitemap.xml]
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://vaultaire.app/
- 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
7/10
Warn
Evidence
- url
- https://vaultaire.app/
- quality
- partial
- score
- 71
Recommendation
Next step: Avoid skipped heading levels so sections progress from h1 to h2 to h3 without gaps. Add missing semantic elements: article.Valid JSON-LD structured data was found with core Organization or WebSite schema.org types.
Signal weight
10/10
Pass
Evidence
- url
- https://vaultaire.app/
- quality
- good
- hasStructuredData
- true
Content-Signal directive not detected in headers, HTML metadata, or robots.txt.
Signal weight
0/5
Fail
Evidence
- url
- https://vaultaire.app/
- 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 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
llms.txtMarkdown
# Vaultaire — Private iPhone Photo Vault, End-to-End Encrypted > Vaultaire: The local-first encrypted vault for iOS. Protect your files with pattern-based security. No accounts, no data tracking, pure privacy by design. 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://vaultaire.app/- Site type: software applicationrobots.txtTXT
# 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 AI crawlers so public content permissions are clear.schema.jsonJSON
{ "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://vaultaire.app/#organization", "name": "Vaultaire — Private iPhone Photo Vault, End-to-End Encrypted", "description": "Vaultaire: The local-first encrypted vault for iOS. Protect your files with pattern-based security. No accounts, no data tracking, pure privacy by design.", "url": "https://vaultaire.app/",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.