www.tryprofound.comscanned May 27, 2026 · 12:590.72s
Public AI visibility report

www.tryprofound.comAI visibilityNeeds Work

This site has a useful foundation, but important gaps still limit AI readability.

Key strengths include AI guidance file and sitemap, while plain-text page access and page structure 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 weekly

Overall score

43/100
Needs Work
Go to fixesOverall position318 out of 491Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt7.5/15
llms.txt15/15
Sitemap10/10
Markdown support0/15
Semantic HTML0/10
Structured data0/10
Content signals0/5
2pass2warn4fail

Public link

llmscan.dev/scan/_TeiRXel5n37lwKobt1IM

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Needs Work · 43/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/_TeiRXel5n37lwKobt1IM
<a href="https://www.llmscan.dev/scan/_TeiRXel5n37lwKobt1IM"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/_TeiRXel5n37lwKobt1IM/badge.png"
    alt="LLM Scan AI visibility score badge"
    width="460"
    height="120"
    style="width: 260px; max-width: 100%; height: auto;"
  />
</a>
Open badge
L
LLM Scan
Needs Work
Score
43/100

Share your score

Post the public report with: “We scored 43/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 is reachable, but the requested URL redirects before reaching the homepage and robots.txt contains AI crawler restrictions for GPTBot, ChatGPT-User, ClaudeBot, Claude-Web, PerplexityBot, and Google-Extended.

Signal weight

10/20
Warn

Evidence

url
https://tryprofound.com/
finalUrl
https://www.tryprofound.com/
status
200

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

8/15
Warn

Evidence

robotsTxtUrl
https://www.tryprofound.com/robots.txt
exists
true
rawRobotsTxt
User-Agent: * Allow: / Allow: /llms.txt Disallow: /admin Sitemap: https://www.tryprofound.com/sitemap.xml

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 was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15
Pass

Evidence

llmsTxtUrl
https://www.tryprofound.com/llms.txt
present
true
accessible
true

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

Signal weight

10/10
Pass

Evidence

sitemapUrl
https://www.tryprofound.com/sitemap.xml
sitemapUrls
[https://www.tryprofound.com/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://www.tryprofound.com/
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 HTML is missing important title, metadata, structure, content, or link text signals.

Signal weight

0/10
Fail

Evidence

url
https://www.tryprofound.com/
quality
poor
score
43

Recommendation

Next step: Shorten the meta description to 160 characters or fewer. Use exactly one h1 element and move secondary section titles to h2-h6. Avoid skipped heading levels so sections progress from h1 to h2 to h3 without gaps. Add missing semantic elements: nav.

No JSON-LD, Microdata, or RDFa structured data was found on the page.

Signal weight

0/10
Fail

Evidence

url
https://www.tryprofound.com/
quality
none
hasStructuredData
false

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

0/5
Fail

Evidence

url
https://www.tryprofound.com/
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 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
# Profound | Optimize Your Brand's Visibility in AI Search > Profound helps brands gain visibility in AI-generated answers, optimize their presence in LLM-based answer engines, and stay competitive in the zero-click world. 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.tryprofound.com/- Site type: website
robots.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 blocked AI crawlers; remove or narrow conflicting Disallow rules if your crawler target requires precedence.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://www.tryprofound.com/#organization",      "name": "Profound | Optimize Your Brand's Visibility in AI Search",      "description": "Profound helps brands gain visibility in AI-generated answers, optimize their presence in LLM-based answer engines, and stay competitive in the zero-click world.",      "url": "https://www.tryprofound.com/",      "logo": "https://www.tryprofound.com/favicons/favicon-light.svg",
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.