Skip to content
Reference

Citelayer® Dashboard Overview — WordPress AI Visibility Settings

6 min read

The Citelayer® dashboard gives you a single place to enable, disable, and configure every protocol the plugin offers. No hunting through multiple menus — everything lives under one roof.

Accessing the Dashboard

You reach the dashboard in two ways:

  • Admin menu: Go to Settings → Citelayer (options-general.php?page=citelayer).
  • Plugins list: Click the “Settings” action link directly next to the plugin entry in your Plugins list.

Both paths take you to the same place.

Dashboard Tabs

The dashboard organizes everything into nine tabs. Each tab controls a specific area of the plugin:

  • Dashboard — Overview of active features and plugin detection status
  • Schema — Organization schema configuration
  • llms.txt — LLM instruction file settings
  • UCP — UCP Discovery toggle
  • WebMCP — WebMCP endpoint and health check
  • Markdown — Markdown endpoint scope and signal headers
  • Compatibility — SEO plugin detection and mode selection
  • Settings — General plugin settings
  • License — License key management

Here is what each tab does and what you configure there.

Dashboard Tab

This is your at-a-glance overview. The Active Features counter shows exactly which protocols are currently enabled. If you have three out of five features running, you see that immediately.

Below the counter, the Plugin Detection status tells you whether Citelayer® has detected any SEO plugins on your site. If it finds one, you see the plugin name and its family label. If it finds plugins from multiple families, you see a conflict warning here as well. For full details on how detection works, see SEO Plugin Compatibility.

Schema Tab

Configure your Organization schema output here. You set the structured data fields that describe your site to machines:

  • knowsAbout — Topics and subjects your organization covers
  • expertise — Areas of professional expertise
  • Social media profiles — Twitter, LinkedIn, Facebook, Instagram, and GitHub URLs

Citelayer® uses these values to build a complete Organization schema block and serves it via the REST API. The more accurate your entries, the richer the structured data output.

llms.txt Tab

Control your llms.txt file from this tab. You get two settings:

  • Enable / Disable — Toggle the llms.txt endpoint on or off.
  • Compatibility mode — Choose how Citelayer® interacts with your SEO plugin’s llms.txt output (Enhance or Replace). This setting only appears when an SEO plugin is detected.

When disabled, the /llms.txt endpoint returns a 404 response.

UCP Tab

A single toggle controls UCP Discovery. Enable it, and Citelayer® registers the UCP endpoint. Disable it, and the endpoint is not registered at all — no leftover routes, no unnecessary processing.

WebMCP Tab

Manage your WebMCP endpoint here with two features:

  • Enable / Disable — Toggle the WebMCP context endpoint.
  • Health Check — Run an AJAX-based check that verifies whether your .well-known/mcp/context.json endpoint is reachable from the outside. Click the button, and the plugin sends a request to your own endpoint and reports success or failure. Use this to confirm that server-level redirects or security plugins are not blocking the path.

Markdown Tab

The Markdown tab has the most configuration options of any feature. You control:

  • Enable / Disable — Toggle the Markdown endpoints.
  • Scope mode — Choose between Sitemap (automatically includes all URLs in your XML sitemap) and Manual (you pick exactly which content to expose).
  • Post type selection — Select which post types (posts, pages, custom types) generate Markdown output.
  • Exclude IDs — Enter specific post or page IDs to exclude from Markdown generation, even if their post type is enabled.
  • Content-Signal headers — Set the HTTP headers that accompany your Markdown responses: ai-train, search, and ai-input. These signal to crawlers how you permit your content to be used.

Compatibility Tab

This tab shows you exactly what Citelayer® has detected on your site. You see every active SEO plugin, grouped by family. For example, if you run both Rank Math (free) and Rank Math Pro, they appear together under the “rankmath” family label.

For each feature that can conflict (Schema and llms.txt), you toggle between Enhance mode and Replace mode. The v3.1 “Locked Compat View” with family grouping makes it clear at a glance which plugins belong together and what mode each feature uses.

Read the full explanation of modes, families, and conflicts in SEO Plugin Compatibility.

Settings Tab

General plugin settings live here. These are global options that affect Citelayer® as a whole rather than individual features.

License Tab

Enter your license key here. The license system is prepared for premium addon licensing — when premium features become available, this is where you activate them. The tab shows your current license status and expiration date.

Feature Toggles: What “Disabled” Actually Means

When you disable a feature in Citelayer®, the plugin does not just hide the output. The endpoint either returns a 404 response or is not registered at all. No route exists. No code runs. No resources are consumed.

This is a deliberate design choice. A disabled feature behaves as if it was never installed. You do not need to worry about leftover routes or phantom endpoints responding to requests when you turn something off.

Conflict State Banner

If Citelayer® detects SEO plugins from multiple different families — for example, Rank Math and Yoast running at the same time — a red banner appears at the top of every admin page. Not just the Citelayer® dashboard. Every page.

This banner is non-dismissable. You cannot click it away. It stays visible until you resolve the conflict by deactivating one of the conflicting SEO plugins. While the conflict exists, the affected features (Schema and llms.txt) pause their output entirely.

This aggressive warning exists for a reason: running two competing SEO plugin families simultaneously causes unpredictable schema output and duplicate structured data. Citelayer® refuses to guess which one you want and instead tells you to choose.

For the full breakdown of conflict states and resolution steps, see SEO Plugin Compatibility.

WebMCP Health Check

The WebMCP tab includes a one-click health check. When you click the button, Citelayer® fires an AJAX request that attempts to reach your .well-known/mcp/context.json endpoint. The result tells you one of two things:

  • Reachable — The endpoint responds correctly. Crawlers and tools can access your WebMCP context.
  • Not reachable — Something blocks the path. Common causes include security plugins blocking .well-known paths, server-level redirect rules, or caching layers stripping the response.

Run this check after initial setup and again after any server configuration change. It takes less than a second and saves you from discovering problems through missing data weeks later.

Each tab in the dashboard corresponds to a dedicated documentation page with deeper technical detail:

New Tabs in v1.4.3

Citelayer® v1.4.3 expands the dashboard with three new tabs:

Bot Analytics

This tab tracks AI crawler activity on your site. Four sub-tabs organize the data: Overview, Top Bots, Crawler Logs, and CSV Export.

The Bot Analytics dashboard answers questions like “Is GPTBot crawling my site?” All data stays on your server — no external tracking.

AI Referrals

Tracks when real human visitors arrive from AI platforms like ChatGPT, Perplexity, and Claude. Shows total referral volume, top sources, and a paginated event log.

AI Readiness Scanner

Runs an automated audit of your site’s AI visibility. Checks structured data, robots.txt, llms.txt, Content-Signal Headers, and (WooCommerce) product feed status. Score from 0 to 100.