domisol.appscanned Aug 17, 2026 · 11:021.48s

Public AI visibility report

domisol.appAI visibilityAI-Ready

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

Key strengths include homepage access and AI guidance file, while crawler policy and page structure need attention.

Recommended next step

fix the crawler policy file syntax issues so each rule uses Field: value format, directives appear under a User-agent, and Sitemap entries use absolute URLs.

Overall score

91/100

AI-Ready

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Monitor changes

Download PDF

Go to fixes Overall position42 out of 2,155Leaderboard

// score breakdown

Points by check

8 checks

Crawlability20/20PASS

Robots.txt7.5/15WARN

llms.txt15/15PASS

Sitemap10/10PASS

Markdown support15/15PASS

Semantic HTML8.6/10WARN

Structured data10/10PASS

Content signals5/5PASS

6pass2warn0fail

Public link

llmscan.dev/scan/LluKJw5RHfenX8D2jmgDP

Signals checked

8 AI visibility signals

Fix bundle

4 copy-ready files

Share badge

AI-Ready · 91/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/LluKJw5RHfenX8D2jmgDP

<a href="https://www.llmscan.dev/scan/LluKJw5RHfenX8D2jmgDP"
  target="_blank"
  rel="noopener"
>
  <img
    src="https://www.llmscan.dev/scan/LluKJw5RHfenX8D2jmgDP/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

91/100

Share your score

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

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

Signal weight

8/15

Warn

Evidence

robotsTxtUrl: https://domisol.app/robots.txt
exists: true
rawRobotsTxt: # DomiSol — robots policy # Public marketing site: every page is fair game for general crawlers. # ── Content Signals (contentsignals.org / AIPREF draft) ────────────── # Machine-readable statement of how this content may be used, applied to # every crawler in the `*` group below. It makes explicit the same # posture the per-agent Allow lines already imply: we WANT DomiSol read, # indexed, cited, AND used as grounding by AI answer engines, and we're # fine with it feeding model training (we already Allow CCBot, # Google-Extended and anthropic-ai further down). # search = appear in search indexes → yes # ai-input = used as grounding for AI answers/RAG → yes # ai-train = used to train / fine-tune AI models → yes # To withdraw training consent later, change to `ai-train=no` (and add # the matching Disallow lines for the training crawlers below). The # directive sits as the FIRST line of the group so simple parsers that # read only the line after `User-agent:` still see it. User-agent: * Content-Signal: search=yes, ai-input=yes, ai-train=yes Allow: / Disallow: /api/ # Cloudflare-injected paths (email obfuscation, challenges, analytics # beacons). They aren't pages, they're infrastructure endpoints — and # Cloudflare sometimes returns 404 for the email-protection one, # which Google then reports as a coverage error against the property. # Disallowing here removes them from Search Console's crawl queue. Disallow: /cdn-cgi/ # Major search engines: explicit allow + reasonable crawl rate. User-agent: Googlebot Allow: / User-agent: Googlebot-Image Allow: / User-agent: Bingbot Allow: / User-agent: DuckDuckBot Allow: / User-agent: YandexBot Allow: / User-agent: Baiduspider Allow: / # ── AI assistants / answer engines — explicitly welcome ────────────── # These all already fall under `User-agent: *` above, so this section # changes no behaviour. It exists to make intent UNAMBIGUOUS: DomiSol # WANTS to be read, indexed, and cited by AI answer engines — that's # the whole point of /llms.txt and the FAQPage JSON-LD across the site. # Listing each agent also gives one obvious place to flip a bot to # Disallow later if it ever misbehaves. # # Two kinds of agent are listed: # * index/crawl bots — build the engine's searchable corpus # * *-User / live-fetch bots — fetch a page in real time when a user # asks the assistant about it; blocking these means the assistant # can't open our links even when a user explicitly requests it. # OpenAI — ChatGPT / SearchGPT User-agent: GPTBot Allow: / User-agent: OAI-SearchBot Allow: / User-agent: ChatGPT-User Allow: / # Anthropic — Claude User-agent: ClaudeBot Allow: / User-agent: anthropic-ai Allow: / User-agent: Claude-Web Allow: / User-agent: Claude-User Allow: / User-agent: Claude-SearchBot Allow: / # Perplexity User-agent: PerplexityBot Allow: / User-agent: Perplexity-User Allow: / # Google — Gemini / AI Overviews grounding. Google-Extended is NOT a # crawler; it's the token that decides whether Gemini & Vertex AI may # use content Googlebot already fetched. Allowing it is required to be # eligible for citation in Gemini answers. User-agent: Google-Extended Allow: / # Apple Intelligence User-agent: Applebot-Extended Allow: / # Microsoft Copilot rides the Bing index — Bingbot is allowed above. # Common Crawl — open corpus many models train on; broad presence. User-agent: CCBot Allow: / # Amazon User-agent: Amazonbot Allow: / # Meta AI User-agent: meta-externalagent Allow: / # Block well-known mass-scrape / archival LLM bots that don't respect # bandwidth. (Comment any of these out if you want them indexed.) User-agent: AhrefsBot Disallow: / User-agent: SemrushBot Disallow: / User-agent: MJ12bot Disallow: / User-agent: PetalBot Disallow: / User-agent: DotBot Disallow: / # Sitemaps — Astro's @astrojs/sitemap integration generates this at build time. Sitemap: https://domisol.app/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 was found and includes the expected text, length, heading, and URL signals.

Signal weight

15/15

Pass

Evidence

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

The sitemap index is valid and the checked child sitemap contains URL entries.

Signal weight

10/10

Pass

Evidence

sitemapUrl: https://domisol.app/sitemap-index.xml
sitemapUrls: [https://domisol.app/sitemap.xml, https://domisol.app/sitemap-index.xml]
robotsSitemapUrls: [https://domisol.app/sitemap-index.xml]

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://domisol.app/
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

9/10

Warn

Evidence

url: https://domisol.app/
quality: partial
score: 86

Recommendation

Next step: Shorten the meta description to 160 characters or fewer.

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

Signal weight

10/10

Pass

Evidence

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

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

Signal weight

5/5

Pass

Evidence

url: https://domisol.app/
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.

What happens next

Keep watching this score

Scores move when sites and models change. This one was measured once, on Aug 17, 2026.

Watch weekly

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

# Free online solfa editor (and jianpu) · DomiSol > DomiSol is a free online solfa editor — and jianpu editor — for writing d r m f s l t or 1 2 3 in your browser. Play it back, arrange SATB, share a link, export PDF. Free during beta. 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://domisol.app/- Site type: software application

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. # Crawl-rate guidance

schema.jsonJSON

{  "@context": "https://schema.org",  "@graph": [    {      "@type": "Organization",      "@id": "https://domisol.app/#organization",      "name": "Free online solfa editor (and jianpu) · DomiSol",      "description": "DomiSol is a free online solfa editor — and jianpu editor — for writing d r m f s l t or 1 2 3 in your browser. Play it back, arrange SATB, share a link, export PDF. Free during beta.",      "url": "https://domisol.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.

What happens next

Monitor this score as your site changes

Weekly checks catch robots, sitemap, schema, and content regressions before AI systems stop reusing your pages.

Watch weekly

domisol.appAI visibilityAI-Ready

Points by check

Add a polished proof badge

8 signals AI systems depend on

Downloadable fix files

Similar AI visibility reports