Weekly LLM Coverage Monitor (max 12 weeks) iWeekly automated check: how each AI platform's citation score for your site changes over time. CXO: a drop on one platform = something changed in crawler access, content depth or structured data. Web: a sustained rise = your AI citation improvements are taking effect.
Baseline from this week's scan — trend line will form after the next weekly snapshot.
📡
Signal history is building
Weighted score trend will appear after the first scan completes.
AI platform snapshot — this week iWeekly automated check of how many AI platforms cite your site and with what quality. Runs every Monday. CXO: use this to track visibility trends over time.
Coverage Score iNumber of search-first AI platforms actively citing your site (ChatGPT, Gemini, Perplexity, Grok). Claude is excluded — it does not use live web search in the same way. CXO: 0/4 = no sourced presence in AI answers. Web: fix bot access and structured data to increase coverage.
AI platforms citing you
AI Visibility Score iWeighted composite across all monitored LLMs (0–100). Higher = more consistent AI-sourced presence week over week. CXO: use trend to measure the impact of content changes.
0–100 composite
Platform Dependency iOver-reliance risk on a single AI platform (0–1). CXO: above 0.5 = if that one platform changes its algorithm, your AI visibility collapses. Web: diversify structured data and content distribution across platforms.
over-reliance risk
Content Reach i% of monitored AI platforms where your content appears. CXO: 100% = all monitored platforms pick up your content. Content + Web: add more content types (news, docs, case studies) to reach more platforms.
platforms covering you
Per-LLM breakdown
| LLM |
Sources iNumber of URLs this LLM uses as sources when describing your company. Web: more sources = better citation coverage. |
Channels iTypes of content cited (blog, product page, about, press…). Content: more channel types = better signal breadth. |
Weighted iQuality-adjusted score: source count × channel diversity × citation depth. Higher = this LLM cites you more reliably. |
|
|
|
|
|
📡
Weekly LLM signals not yet available
Signal Monitor runs weekly. Data will appear after the first weekly snapshot.
Knowledge vs citation
AI knowledge check: .
Citation readiness: · average .
Knowing your company ≠ citing your website. AI platforms can have perfect knowledge of your brand but still not cite you as a source — citation requires live technical signals: bot access, structured data, llms.txt, and content depth.
Fixable Issues iIssues ranked by score impact — fixing the top item gives the biggest VCL gain. CXO: check weekly if high-impact issues remain open. Web: start with Quick-win effort issues — same score gain, less work. Content: focus on issues tagged L4, L6, L8.
iPoints added to your VCL score if this issue is fixed. CXO: prioritise issues with the highest number. Web/Content: combine with effort — a +12 Quick-win beats a +15 that takes months.
·
Effort: iHow much work the fix requires. Quick win = under 1 hour, usually a config or tag change. Medium = 1–4 hours, code or content update. Hard = requires dev sprint or content strategy. Web: Quick wins first. CXO: delegate Hard items to sprint planning.
Detailed fix instructions will appear here including specific code changes, content updates, configuration changes and validation steps to resolve this issue.
✅
No issues yet
After the first scan a prioritised list of fixable issues will appear here.
Competitor benchmark iScore benchmark against detected domains in your industry and country. This is not a full competitor audit. CXO: negative delta = that benchmark domain leads your AI discoverability score. Click + to inspect layer-level differences where data is available.
Auto-detected benchmark · 3 included
L1 Gateway iBot access — 0 = AI crawlers blocked by robots.txt. CXO: score 0 blocks all layers below. Web: fix robots.txt first.
L2 SSR iServer-side rendering — low = content injected by JS, invisible to AI crawlers. Web: content must be in HTML, not client-side JS.
L3 Indexability iCanonical tags, hreflang, noindex flags. Web: missing or duplicate canonicals reduce this score.
L4 Content iClarity of what you do, for whom, what problems you solve. Content: add structured homepage copy, FAQs and answer-style pages.
L5 Tech SEO iSitemap, HTTPS, mobile viewport, performance. Web: verify sitemap.xml is submitted and includes all key pages.
L6 On-Page iOpen Graph, meta tags, internal links, image alt. Web + Content: add og:title, og:description; fix missing alt text.
L7 Citation iWhether AI platforms cite you as source. CXO: revenue gap layer — low = zero presence in AI answers. Content: add llms.txt, answer pages. Web: fix bot access and structured data.
L8 SEO Activity iContent freshness and sitemap updates. Content: publish or update pages regularly so the site does not look stale to AI crawlers.
L1 Gateway iBot access — 0 = AI crawlers blocked by robots.txt. CXO: score 0 blocks all layers below. Web: fix robots.txt first.
L2 SSR iServer-side rendering — low = content injected by JS, invisible to AI crawlers. Web: content must be in HTML, not client-side JS.
L3 Indexability iCanonical tags, hreflang, noindex flags. Web: missing or duplicate canonicals reduce this score.
L4 Content iClarity of what you do, for whom, what problems you solve. Content: add structured homepage copy, FAQs and answer-style pages.
L5 Tech SEO iSitemap, HTTPS, mobile viewport, performance. Web: verify sitemap.xml is submitted and includes all key pages.
L6 On-Page iOpen Graph, meta tags, internal links, image alt. Web + Content: add og:title, og:description; fix missing alt text.
L7 Citation iWhether AI platforms cite you as source. CXO: revenue gap layer — low = zero presence in AI answers. Content: add llms.txt, answer pages. Web: fix bot access and structured data.
L8 SEO Activity iContent freshness and sitemap updates. Content: publish or update pages regularly so the site does not look stale to AI crawlers.
Layer detail available after next weekly scan.
🏆
Competitors not yet discovered
Competitors are auto-detected after the first scan based on your industry and country.
EU AI Act — Preliminary Exposure Assessment
Risk tier iEU AI Act risk classification based on your industry and AI use. CXO: LIMITED = standard transparency obligations. HIGH = strict conformity assessment required before any AI deployment.
EU jurisdiction iWhether your company falls under EU AI Act regulation. CXO: EU jurisdiction = compliance required by August 2026. Non-EU = voluntary compliance, but increasingly expected by EU partners and customers.
Based on industry classification · · refreshes weekly
Key obligations iSpecific compliance steps required for your risk tier under the EU AI Act. CXO: these are legal actions your team must take before deploying or using AI systems in the EU.
Recommended next step iThe single most important compliance action for your risk tier right now. CXO: assign this to your legal or compliance owner with an August 2026 deadline. Web/Content: check if this step requires a technical or content change on your site.
This is an automated preliminary assessment based on industry classification. It does not constitute legal advice. Consult qualified EU AI Act counsel for compliance decisions.
⚖️
Assessment pending
EU AI Act assessment will appear after the next weekly scan.
⚖️
No scan data yet
Run your first scan to get your EU AI Act preliminary assessment.
AI Visibility Score — VCL trend iScore trend across all scans. CXO: a dropping trend = competitors are improving faster. Web: click any scan date to see the full snapshot and identify which layer dropped.
Baseline starts from a zero baseline week. Real trend will form with the next scans.
📈
No scan yet
Score trend will appear after the first scan completes.
Score by layer — trend iHow each of the 8 layers changed over time. Web: identify the layer that is deteriorating to prioritise your next fix. Content: watch L4 and L8 for content freshness drops.
Baseline starts from a zero baseline week. Real trend will form with the next scans.
📊
No scan yet
Layer trend will appear after the first scan completes.
📅
No scan history yet
Each scan is stored as a separate snapshot. History will appear after multiple scans.
