voicetopost.appscanned May 26, 2026 · 16:420.39s

Public AI visibility report

voicetopost.appAI visibilityAI-Ready

This site is in strong shape for AI discovery and readability.

Key strengths include homepage access and crawler policy, while plain-text page access needs 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 weekly

Overall score

85/100

AI-Ready

Go to fixes Overall position15 out of 491Leaderboard

// score breakdown

Points by check

8 checks

Crawlability20/20PASS

Robots.txt15/15PASS

llms.txt15/15PASS

Sitemap10/10PASS

Markdown support0/15FAIL

Semantic HTML10/10PASS

Structured data10/10PASS

Content signals5/5PASS

7pass0warn1fail

Public link

llmscan.dev/scan/vX8dihVGRR97coytlkJnE

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

AI-Ready · 85/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/vX8dihVGRR97coytlkJnE

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

Open badge

LLM Scan

AI-Ready

Score

85/100

Share your score

Post the public report with: “We scored 85/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 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://voicetopost.app/
finalUrl: https://voicetopost.app/
status: 200

robots.txt allows crawler access and includes Sitemap references.

Signal weight

15/15

Pass

Evidence

robotsTxtUrl: https://voicetopost.app/robots.txt
exists: true
rawRobotsTxt: User-agent: * Allow: / Disallow: /api/ Disallow: /checkout Disallow: /auth Sitemap: https://voicetopost.app/sitemap.xml # AI crawler access User-agent: GPTBot Allow: / User-agent: ChatGPT-User Allow: / User-agent: ClaudeBot Allow: / User-agent: Claude-Web Allow: / User-agent: PerplexityBot Allow: / User-agent: Google-Extended Allow: / User-agent: * Crawl-delay: 10

The llms.txt file was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15

Pass

Evidence

llmsTxtUrl: https://voicetopost.app/llms.txt
present: true
accessible: true

The sitemap.xml file is valid and contains URL entries.

Signal weight

10/10

Pass

Evidence

sitemapUrl: https://voicetopost.app/sitemap.xml
sitemapUrls: [https://voicetopost.app/sitemap.xml]
robotsSitemapUrls: []

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://voicetopost.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 a valid title, meta description, heading structure, semantic landmarks, substantial body copy, and descriptive anchor text.

Signal weight

10/10

Pass

Evidence

url: https://voicetopost.app/
quality: good
score: 100

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

Signal weight

10/10

Pass

Evidence

url: https://voicetopost.app/
quality: good
hasStructuredData: true

AI content usage signals detected via Content-Signal HTTP headers, AI metadata hints.

Signal weight

5/5

Pass

Evidence

url: https://voicetopost.app/
hasContentSignals: true
hasContentSignalHeader: true

Recommendation

Next step: Consider adding AI-specific head meta tags, robots noai/noimageai directive, Content-Signal robots.txt directive so AI systems can consistently discover content usage preferences across robots.txt, HTTP headers, and HTML metadata.

// 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

# Voice to Post: AI content generator for founders, coaches and experts > Record a voice note or paste raw ideas. AI extracts your insights and writes posts that sound like you, not like a robot. Try free, no login required. 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://voicetopost.app/- Site type: organization

robots.txtTXT

schema.jsonJSON

{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://voicetopost.app/#organization",      "name": "Voice to Post: AI content generator for founders, coaches and experts",      "description": "Record a voice note or paste raw ideas. AI extracts your insights and writes posts that sound like you, not like a robot. Try free, no login required.",      "url": "https://voicetopost.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.