Patchy presence
6 of 10 checks passing · 2 warnings · 2 fails
The score combines ten structural signals AI engines use to decide whether to cite you. Each band points to a different intervention.
0–39
AI engines cannot reliably surface your brand. Foundational structural work needed before targeted GEO investment makes sense.
40–59
AI engines find you sometimes. Critical signals are missing or noisy. Targeted fixes can lift you into reliable citation range fast.
60–74
You appear in some answers but lose to competitors on key prompts. The structural foundation is there — sharpen it.
75–89
You are reliably citable across the major AI engines. Remaining work is fine-tuning entity disambiguation and content depth.
90–100
Strong AI readiness across all ten structural signals. You are in the top tier of citation candidates for your category.
Pass
Organization schema with 11 sameAs pointers. Full entity-graph tier.
Recommendation Schema coverage is comprehensive.
Add JSON-LD for Organization, WebSite and the right entity type per template (Article, Product, Service, FAQPage). Wire sameAs links to your verified profiles. Validate with Schema.org and Google's Rich Results test.
Effort 1–2 days · template-level fix
Pass
All 5 major AI crawlers are explicitly or implicitly allowed.
Recommendation Keep this policy. Re-check whenever robots.txt is edited.
Update robots.txt to explicitly allow GPTBot, ClaudeBot, PerplexityBot, OAI-SearchBot and Google-Extended on the paths you want cited. Remove blanket Disallow rules that catch AI crawlers as collateral.
Effort 1 hour · single config change
Pass
Person schema present with 2 sameAs pointers.
Recommendation Author entity well-formed. Keep author pages crosslinked from articles and ensure each contributor has the same sameAs treatment.
Add Person JSON-LD on every article and author page, with sameAs pointers to LinkedIn, Wikidata, and (where applicable) Wikipedia. Author entities recognized in the Knowledge Graph strengthen the entire domain's citation candidacy.
Effort Half day · template + author profile copy
Fail
No Wikipedia article matches the brand.
Recommendation Pursue Wikipedia coverage if the brand is notable enough. Do NOT author your own — find an editor.
Wikipedia notability is earned, not bought. Citable maps your independent secondary sources, drafts a neutral encyclopedic article, and shepherds it through editor review. Without notable third-party coverage we will tell you and decline.
Effort 4–8 weeks · earned media required
Fail
No matching Wikidata entity found.
Recommendation Create a Wikidata entry for the brand and link it from your Organization schema sameAs array.
Create or claim your Wikidata entity, then connect every verified profile (Crunchbase, LinkedIn, Companies House, ISNI, X, your own /about). Each verified sameAs link is a citation foothold for AI engines.
Effort 1 day · Wikidata authoring + verification
Warning
Recognized but ambiguous: score 13.42943382263184, type Organization, Thing.
Recommendation Add or strengthen `sameAs` references to Wikipedia/LinkedIn/Crunchbase. Submit corrections via Google Knowledge Panel suggestions.
Knowledge Graph entry follows from the upstream signals: schema, sameAs network, Wikipedia/Wikidata, and consistent NAP across the web. Fix those first; the Knowledge Panel typically follows within weeks.
Effort Downstream of other fixes · weeks
Pass
Most recent dateModified is 0 days old. Top RAG-recency tier.
Recommendation Hold this cadence. Refreshing core pages every 60 days protects against Perplexity's citation decay.
Add dateModified to Article/WebPage JSON-LD and a visible 'Last updated' line on every content page. Refresh the visible timestamp and the schema field every 60 days on top pages. Highest-ROI rewrite for Perplexity and ChatGPT search.
Effort Ongoing · 60-day refresh cadence
Warning
12 stat-bearing patterns detected. Below the 19-statistic threshold Princeton research correlates with 2× citation rate.
Recommendation Add specific statistics, expert quotes, and authoritative source citations to top-traffic articles. Target 19+ data points per long-form piece.
Rewrite top-traffic articles to include 19+ specific data points, 3+ named source citations, and at least 2 attributed expert quotes. Princeton GEO research: citing authoritative sources lifts visibility 40%; adding statistics lifts it another 37%.
Effort 1–2 weeks · content rewrite
Pass
Detected on 2 of 3 trust-seed platforms: LinkedIn company, GitHub org.
Recommendation Strong presence. Adding the third profile would maximise the third-party citation correlation (0.664 vs 0.218 for backlinks).
Claim and complete profiles on Trustpilot, LinkedIn company, and GitHub org (or the trust-seed platforms relevant to your category — G2, Capterra, ProductHunt, Crunchbase). Third-party mention volume correlates 0.664 with AI citation; backlinks correlate just 0.218.
Effort 1 day · profile claim + content
Pass
/llms.txt present with 837 non-empty lines (hedge in place).
Recommendation Hedge in place. Not a current ranking signal — no major LLM vendor documents consuming external llms.txt files as of 2026. Keep it maintained if cheap; do not over-invest. The real Share of Answer levers are schema, entity, extractability, crawler access, and third-party citations.
Hedge signal — not consumed by ChatGPT, Perplexity, Gemini, Claude, or AI Overviews as of 2026 (Google explicitly debunked it as a ranking factor in May 2026). If your CMS can auto-generate /llms.txt at the root from your sitemap and meta descriptions, ship it as a cheap hedge. Do not author it manually or pay a vendor to manage it. See /journal/does-llms-txt-matter-2026 for the full Citable position.
Effort Minutes if auto-generated · do not invest more
Share
Public permalink with grade and all ten signals. No login, no gate, indexable — built for LinkedIn and X.
Ready to fix this
Score-adjacent
Closest to your score — click any to see the full scorecard.
citable.agency
67/100
shopify.com
62/100
semrush.com
69/100
pipedrive.com
71/100
example.com
59/100
fernandoangulo.com
73/100