www.framer.comscanned Jul 28, 2026 · 10:077.67s
Public AI visibility report

www.framer.comAI visibilityNeeds Work

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

Key strengths include AI guidance file and plain-text page access, while sitemap and homepage access need attention.

Recommended next step

publish a valid XML sitemap at /sitemap.xml and reference it from the crawler policy file so crawlers and AI systems can discover important URLs.

Turn this scan into weekly monitoring.

Send yourself a magic link that opens a workspace already watching this domain for weekly AI visibility changes.

Unlock monitoringView AI Optimization docs

Overall score

63/100
Needs Work
Download PDF
Go to fixesOverall position267 out of 1,258Leaderboard

// score breakdown

Points by check

8 checks

Crawlability10/20
Robots.txt7.5/15
llms.txt15/15
Sitemap0/10
Markdown support15/15
Semantic HTML5.7/10
Structured data5/10
Content signals5/5
3pass4warn1fail

Public link

llmscan.dev/scan/IPT-vI0-PYTSa8m5qZGjh

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Needs Work · 63/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/IPT-vI0-PYTSa8m5qZGjh
<a href="https://www.llmscan.dev/scan/IPT-vI0-PYTSa8m5qZGjh"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/IPT-vI0-PYTSa8m5qZGjh/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
63/100

Share your score

Post the public report with: “We scored 63/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://buildinframe.com/
finalUrl
https://www.framer.com/@soubhagya/
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.

The robots.txt file was found, but it contains formatting issues.

Signal weight

8/15
Warn

Evidence

robotsTxtUrl
https://www.framer.com/robots.txt
exists
true
rawRobotsTxt
User-Agent: * Allow: / Disallow: /api-proxy Disallow: /*?budget= Disallow: /*&budget= Disallow: /*?region= Disallow: /*&region= Disallow: /*?skill= Disallow: /*&skill= Disallow: /*?language= Disallow: /*&language= Disallow: /*?tab= Disallow: /*&tab= Disallow: /experts/*?referrer= Disallow: /experts/*&referrer= Disallow: /*?sort= Disallow: /*&sort= Disallow: /*?query= Disallow: /*&query= Content-Signal: ai-train=yes, search=yes, ai-input=yes Sitemap: https://www.framer.com/sitemap.xml Sitemap: https://www.framer.com/marketplace/sitemap.xml

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

Signal weight

15/15
Pass

Evidence

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

No accessible XML sitemap was found for this site.

Signal weight

0/10
Fail

Evidence

sitemapUrl
https://www.framer.com/sitemap.xml
sitemapUrls
[https://www.framer.com/sitemap.xml, https://www.framer.com/marketplace/sitemap.xml]
robotsSitemapUrls
[https://www.framer.com/sitemap.xml, https://www.framer.com/marketplace/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 returns markdown content when requested with Accept: text/markdown, giving AI systems a cleaner text representation with less navigation chrome to parse.

Signal weight

15/15
Pass

Evidence

url
https://www.framer.com/@soubhagya/
acceptHeader
text/markdown
status
200

The homepage has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

6/10
Warn

Evidence

url
https://www.framer.com/@soubhagya/
quality
partial
score
57

Recommendation

Next step: Add a title tag between 10 and 70 characters. Add a meta description between 50 and 160 characters. Add missing semantic elements: main, footer.

Structured data was found, but it is missing core Organization or WebSite schema, contains invalid JSON-LD, or only uses non-JSON-LD formats.

Signal weight

5/10
Warn

Evidence

url
https://www.framer.com/@soubhagya/
quality
partial
hasStructuredData
true

Recommendation

Next step: Prefer valid JSON-LD and include Organization or WebSite schema.org types in valid JSON-LD for clearer AI interpretation.

AI content usage signals detected via Content-Signal robots.txt directives.

Signal weight

5/5
Pass

Evidence

url
https://www.framer.com/@soubhagya/
hasContentSignals
true
hasContentSignalHeader
false

Recommendation

Next step: Consider adding Content-Signal HTTP header, AI-specific head meta tags, robots noai/noimageai 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
# www.framer.com > Framer Web Designer & Plugin Developer @ BuildinFrame | Taking Clients 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.framer.com/@soubhagya/- Site type: breadcrumb list
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.framer.com/@soubhagya/#organization",      "name": "Framer Community",      "description": "Framer Web Designer & Plugin Developer @ BuildinFrame | Taking Clients",      "url": "https://www.framer.com/@soubhagya/",      "logo": "https://www.framer.com/creators/seo/community-install-ios-180.png",
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.

Related scans

Similar AI visibility reports

Browse leaderboard