link.mescanned Jul 5, 2026 · 11:010.20s
Public AI visibility report

link.meAI visibilityPoor

This site is difficult for AI tools to read right now.

Key strengths include sitemap, while homepage access and crawler policy need attention.

Recommended next step

update the User-agent: * the crawler policy file rules so the public homepage is not covered by a Disallow rule.

Turn this scan into weekly monitoring.

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

Overall score

21/100
Poor
Download PDF
Go to fixesOverall position1,140 out of 1,169Leaderboard

// score breakdown

Points by check

8 checks

Crawlability0/20
Robots.txt0/15
llms.txt0/15
Sitemap10/10
Markdown support0/15
Semantic HTML5.7/10
Structured data5/10
Content signals0/5
1pass2warn5fail

Public link

llmscan.dev/scan/dPryQeD5e8bD1G0_82P8s

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

Poor · 21/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/dPryQeD5e8bD1G0_82P8s
<a href="https://www.llmscan.dev/scan/dPryQeD5e8bD1G0_82P8s"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/dPryQeD5e8bD1G0_82P8s/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
Poor
Score
21/100

Share your score

Post the public report with: “We scored 21/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 robots.txt blocks general crawlers from accessing it.

Signal weight

0/20
Fail

Evidence

url
https://link.me/matteos_2025
finalUrl
https://link.me/matteos_2025
status
200

Recommendation

Next step: Update the User-agent: * robots.txt rules so the public homepage is not covered by a Disallow rule.

robots.txt blocks all crawlers from the whole site.

Signal weight

0/15
Fail

Evidence

robotsTxtUrl
https://link.me/robots.txt
exists
true
rawRobotsTxt
# We allow everything from the root # and then set noindex on our backends for paths that we want to Disallow # to prevent this list from being too complex and long User-agent: Applebot Allow: / User-agent: baiduspider Allow: / User-agent: Bingbot Allow: / User-agent: Discordbot Allow: / User-agent: facebookexternalhit Allow: / User-agent: Googlebot Allow: / User-agent: Googlebot-Image Allow: / User-agent: Google-InspectionTool Allow: / User-agent: ia_archiver Allow: / User-agent: LinkedInBot Allow: / User-agent: msnbot Allow: / User-agent: Naverbot Allow: / User-agent: Screaming Frog SEO Spider Allow: / User-agent: seznambot Allow: / User-agent: Slurp Allow: / User-agent: teoma Allow: / User-agent: TelegramBot Allow: / User-agent: Twitterbot Allow: / User-agent: Yandex Allow: / User-agent: Yeti Allow: / User-agent: SnapchatAdsBot Allow: / User-agent: SemrushBot Allow: / User-agent: Pinterestbot Allow: / User-agent: * Disallow: / Sitemap: https://link.me/sitemap.xml Sitemap: https://link.me/users-sitemap.xml

Recommendation

Next step: Replace the global Disallow: / policy with narrower path-level rules if public content should be discoverable by crawlers.

No llms.txt file was found for this site.

Signal weight

0/15
Fail

Evidence

llmsTxtUrl
https://link.me/llms.txt
present
false
accessible
false

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

10/10
Pass

Evidence

sitemapUrl
https://link.me/sitemap.xml
sitemapUrls
[https://link.me/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://link.me/matteos_2025
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

6/10
Warn

Evidence

url
https://link.me/matteos_2025
quality
partial
score
57

Recommendation

Next step: Shorten the meta description to 160 characters or fewer. Add missing semantic elements: main, article, nav. Add visible body copy after script and style removal so the page has at least 200 words.

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://link.me/matteos_2025
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.

Content-Signal directive not detected in headers, HTML metadata, or robots.txt.

Signal weight

0/5
Fail

Evidence

url
https://link.me/matteos_2025
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
# Check out Matteo Silva (@matteos_2025) on Linkme > Discover Matteo Silva on LinkMe: Quality first, street-ready fits second. At Matteo , every hoodie and tee is built to last, with ethical sourcing and bold design at the core. Shop the collection—bold, versatile, you 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://link.me/matteos_2025- Site type: profile page
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://link.me/matteos_2025#organization",      "name": "Check out Matteo Silva (@matteos_2025) on Linkme",      "description": "Discover Matteo Silva on LinkMe: Quality first, street-ready fits second. At Matteo , every hoodie and tee is built to last, with ethical sourcing and bold design at the core. Shop the collection—bold, versatile, you",      "url": "https://link.me/matteos_2025",      "logo": "https://link.me/icon.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