boldium.comscanned Jul 23, 2026 · 16:401.34s
Public AI visibility report

boldium.comAI visibilityNeeds Work

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

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

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

64/100
Needs Work
Download PDF
Go to fixesOverall position241 out of 1,158Leaderboard

// score breakdown

Points by check

8 checks

Crawlability20/20
Robots.txt7.5/15
llms.txt7.5/15
Sitemap10/10
Markdown support0/15
Semantic HTML8.6/10
Structured data5/10
Content signals5/5
3pass4warn1fail

Public link

llmscan.dev/scan/Vcwc1ERaM0BCO-BbSw3gk

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

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

Share your score

Post the public report with: “We scored 64/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://boldium.com/
finalUrl
https://boldium.com/
status
200

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

Signal weight

8/15
Warn

Evidence

robotsTxtUrl
https://boldium.com/robots.txt
exists
true
rawRobotsTxt
# https://contentsignals.org/ User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=yes # Allow everyone else User-agent: * Allow: / Sitemap: https://boldium.com/sitemap-index.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 exists but is missing one or more expected quality signals.

Signal weight

8/15
Warn

Evidence

llmsTxtUrl
https://boldium.com/llms.txt
present
true
accessible
true

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 index is valid and the checked child sitemap contains URL entries.

Signal weight

10/10
Pass

Evidence

sitemapUrl
https://boldium.com/sitemap-index.xml
sitemapUrls
[https://boldium.com/sitemap.xml, https://boldium.com/sitemap-index.xml]
robotsSitemapUrls
[https://boldium.com/sitemap-index.xml]

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://boldium.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 has some semantic HTML signals, but one or more title, metadata, heading, landmark, content, or link text checks need improvement.

Signal weight

9/10
Warn

Evidence

url
https://boldium.com/
quality
partial
score
86

Recommendation

Next step: Add missing semantic elements: article.

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://boldium.com/
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://boldium.com/
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
# Creative Agency | AI Products, Branding & Marketing | Boldium > Boldium helps leaders own their categories by crafting AI-powered products, branding, and marketing that are bold and trustworthy. 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://boldium.com/- Site type: web 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 AI crawlers so public content permissions are clear.User-agent: GPTBotAllow: / User-agent: ChatGPT-UserAllow: /
schema.jsonJSON
{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://boldium.com/#organization",      "name": "Creative Agency | AI Products, Branding & Marketing | Boldium",      "description": "Boldium helps leaders own their categories by crafting AI-powered products, branding, and marketing that are bold and trustworthy.",      "url": "https://boldium.com/",      "logo": "https://boldium.com/.netlify/images?url=https%3A%2F%2Fcdn.sanity.io%2Fimages%2Fabes57fd%2Fproduction%2F62bbaabb6503bc063c6ca1cffd854939ca10db37-864x864.webp%3Fw%3D1060%26h%3D1060%26auto%3Dformat&w=1060&h=1060&fit=cover&dpl=6a6242c9d89590000943eaa8"
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