Status and Discovery Analytics

Cybermaps connects configuration, filesystem state, public delivery, and request observations in one operational view.

Sitemap Status

Sitemap Status validates the current public sitemap URL and every advertised child.

AI Discovery Status

Each publication reports:

  • enablement;
  • format maturity and adoption statement;
  • intended delivery mode;
  • local owned-file state;
  • observed public delivery;
  • HTTP status and media type;
  • required profile or headers;
  • parseability; and
  • the last static reconciliation.

Status probes include X-Cybermaps-Diagnostic: 1 and are filtered from analytics to keep crawler observations clean.

Discovery Analytics

Recording is opt-in. A registered endpoint request reaching PHP can create a privacy-minimal observation even when its User-Agent is unrecognized.

If the self-reported User-Agent matches the crawler registry, the row is additionally marked recognized and stores the normalized signature, category, and anonymized IPv4 /24 or IPv6 /64 network identifier.

Unrecognized endpoint rows store no IP address or User-Agent. Ordinary content-page rows are limited to recognized crawlers. Admin requests are ignored.

Analytics coverage

The Request Log represents endpoint traffic and recognized content requests observed by WordPress. Physical files and CDN-served requests can be combined with external server analytics when a complete cross-layer traffic picture is required.

Controls

Discovery Analytics includes:

  • 30-day endpoint and content summaries;
  • alias grouping by endpoint ID;
  • recognized signature and category breakdowns;
  • recent Request Log rows;
  • recording enablement;
  • retention from 1 to 365 days;
  • bounded CSV export; and
  • clear-history controls.

Disabling recording preserves existing history.

Request limiting

Recognized crawler requests enter a local minute-window limiter keyed by crawler ID, endpoint cost tier, and minute.

Public REST search uses a separate 60-second transient keyed by an installation-salted, one-way identifier derived from the request IP. The raw IP and query text are not stored in that transient.