The citelayer® Dashboard
Use the dashboard to move from a status summary to the actual response or local data behind it. A green card is useful only within the feature it checks.
Run and read a scan
- Open the AI Scanner and run the checks.
- Read the explanation for each warning or failure.
- Open the affected endpoint or page and compare its body with the expected output.
- After a fix, run the relevant check again.
Follow the feature screens
- Schema: configured identity and output ownership.
- llms.txt and Markdown: scope, exclusions and response diagnosis.
- Bot Analytics: logged crawler activity, referrals and blind spots.
- WebMCP: context discovery, Abilities availability and Read-only mode.
- Store add-ons: license/settings state and platform capabilities.
Keep measurements separate
The site scanner, per-page editor checklist and blindspot content score use different inputs. Bot totals count matching requests; referral totals count recognized arrival events. None is a citation leaderboard. See score methodology and analytics limits.
When the browser differs from the dashboard
A static file, cache layer, WAF, SEO provider or server rule can serve a response different from the plugin generator. Inspect the public endpoint from a fresh request and use diagnosis rather than assuming saved settings describe what every visitor receives.
Next step
Continue with the quick start checklist, or check the common questions. For a reproducible problem, send the plugin versions, affected URL, expected result and actual response through Support. Do not include passwords, license keys or customer details.
Reviewed 6 October 2026 against citelayer® Free 1.13.5, WooCommerce add-on 1.2.19 and EDD add-on 1.2.1. Features depend on the active components and settings on your site.