Invisible
kurakurabeer.com
Scanned Apr 20, 2026, 07:01 AM · 9.3s
Runtime Visibility
Runtime panel skipped
Requires at least 2 keyed LLM engines. Configure additional API keys (OpenAI, Perplexity, Gemini) to enable real-time citation testing.
Dimensions
Eight deterministic checks. Higher weight = bigger impact on the score.
Content Structure
5 / 20 · weight 20
fail3 issues ↓high
No definition-lead opener in the first 150 tokens
Open the homepage with '<Brand> is a <category> that <differentiator>' — this is the single biggest lever for AI citability.
medium
No 2–4 sentence summary paragraph above the fold
Add a 2–4 sentence paragraph immediately after the H1 summarising what the product is and who it serves.
medium
Some H2 topics are too short (<3 words)
Use exactly one H1, ensure the first H2 precedes any H3, and give every H2 a clear topic label (3+ words).
Citation Density
10 / 20 · weight 20
warn2 issues ↓high
External links exist but none hit the authoritative allowlist
Cite at least one .edu/.gov, Wikipedia, IETF/W3C spec, or tier-1 publication near your flagship claims.
high
Statistical claims are unsourced
Every % / 'X customers' / stat deserves an inline citation link to the origin study or publication.
Crawler Access
15 / 15 · weight 15
passno issuesSchema Markup
2 / 15 · weight 15
fail2 issues ↓critical
No valid Organization JSON-LD
Add <script type='application/ld+json'> with @type:Organization including name, url, logo, and sameAs (≥3 social profiles).
high
FAQ section exists but is not marked up as FAQPage JSON-LD
Wrap the FAQ with a FAQPage JSON-LD block so AI engines can lift the Q/A pairs verbatim.
llms.txt
0 / 10 · weight 10
fail1 issue ↓critical
No /llms.txt file found
Publish /llms.txt at the site root with '# <Project>' + a short summary + H2 sections linking to canonical doc URLs.
Entity Clarity
0 / 10 · weight 10
fail4 issues ↓medium
No clear self-identification in the opening paragraph
Open with 'We are ...' / 'Our mission is ...' / 'This is ...' — AI models need explicit entity framing.
low
No named author or byline visible
If the homepage surfaces editorial content, include an author byline (Person JSON-LD or 'By <Name>').
medium
No /about or /team page with credentials
Publish an About page listing founders, team, and credentials. AI engines heavily weight provenance.
low
Organization JSON-LD missing founder
Add 'founder': [{ @type: Person, name: ... }] to the Organization schema.
Off-site Authority (proxy)
0 / 5 · weight 5
fail1 issue ↓low
No social/authority footprint linked from header or footer
Add links to Wikipedia, LinkedIn company page, YouTube channel, or GitHub org so AI engines can cross-reference authority.
Freshness
0 / 5 · weight 5
fail1 issue ↓medium
No last-updated signal on homepage
Add <time datetime='YYYY-MM-DD'>Updated ...</time> or article:modified_time meta, or expose dateModified in Article JSON-LD.
Top 5 fixes
Prioritized by severity. Copy the Claude Code prompt to apply the fix yourself, or let AGNT patch it automatically.
- critical· llmstxtauto-fixable
No /llms.txt file found
Publish /llms.txt at the site root with '# <Project>' + a short summary + H2 sections linking to canonical doc URLs.
- critical· schemaauto-fixable
No valid Organization JSON-LD
Add <script type='application/ld+json'> with @type:Organization including name, url, logo, and sameAs (≥3 social profiles).
- high· citations
External links exist but none hit the authoritative allowlist
Cite at least one .edu/.gov, Wikipedia, IETF/W3C spec, or tier-1 publication near your flagship claims.
- high· schemaauto-fixable
FAQ section exists but is not marked up as FAQPage JSON-LD
Wrap the FAQ with a FAQPage JSON-LD block so AI engines can lift the Q/A pairs verbatim.
- high· structure
No definition-lead opener in the first 150 tokens
Open the homepage with '<Brand> is a <category> that <differentiator>' — this is the single biggest lever for AI citability.
Share this scan
No signup, no gates. The result page is public — link it anywhere.
AGNT Auto-fix
Stop losing to cited competitors.
AGNT patches robots.txt, llms.txt, schema, FAQ markup, and definition-lead openers across your site — automatically. You review the diffs, we ship the PRs.