Install CYBERMAPS, review the suggested configuration, and see what it publishes for your site.

Requirements and installation

Use WordPress 7.1 or later and PHP 8.2 or later. PHP 8.3+ is recommended.

Free and available now. WordPress.org listing awaiting approval.

Get the plugin ZIP from the CYBERMAPS downloads page. In WordPress, go to Plugins → Add New → Upload Plugin, choose the ZIP, then install and activate CYBERMAPS.

The plugin is free and available to install now. The WordPress.org listing is awaiting approval; the downloads page shows which installation options are currently available.

Configure your first publications

Choose one sitemap owner. Disable overlapping sitemap output in other plugins before letting CYBERMAPS take over its routes.
Open CYBERMAPS → Overview → Quick Setup and answer the three short steps.
Select Finish setup to apply the preset, then expand See settings applied for the receipt.
Fine-tune public content eligibility, schema, and AI Publishing in their workspaces.
Open Sitemap Status and AI Discovery Status. Test the public URLs and their headers.
Open Reports and save a content report. Review content, potential-orphan, and click-depth findings, make a useful improvement, and run another report to compare the findings.

Keep the editorial tools you use. If your theme already handles titles and schema, you may not need a full SEO suite. Cybermaps disables WordPress’s native sitemap provider when it initializes and registers its own sitemap routes. Choose one public sitemap owner and coordinate overlapping output from other SEO plugins before activation. Review overlapping schema settings as well.

How it works

Cybermaps adds one top-level administration area with seven primary tabs:

Page	What it controls
Overview	Site inventory, feature status, publication links, and operational shortcuts
XML Sitemaps	XML, News, RSS, media, external URL, Content Discovery Strategy, caching, redirect, robots-link, translation, IndexNow, WebSub, and Static File Engine settings
HTML Sitemap	Shortcode availability plus an interactive builder, generated shortcode, examples, and attribute reference
AI Publishing	The publication master switch, LLMS output, discovery manifests, feeds, chunks, actions, usage policy, custom AI instructions, and crawler/robots policy
Schema	Organization, LocalBusiness, or Person identity, contact and location details, social profiles, hours, contact points, and service catalogs
Reports	Content and local internal-link measurements, saved reports, focused action lists, report themes, agency branding, and AI Discovery Publication Reports
Advanced	Delivery and performance controls, managed or self-managed Cloudflare OAuth plus a one-time-token fallback, headless and media-CDN URL rewriting, private REST secret, static cleanup, uninstall behavior, and configuration exchange

Debugging is a separate submenu, with expiring diagnostic logging, redacted support bundles, runtime and optimization status, and public delivery checks.

Quick Setup

Quick Setup is an optional three-step survey launched from Overview:

Your website: choose the closest website type for a matching content profile and sitemap preset.
Your priorities: choose basic AI discovery and either crawler activity with IP anonymization or lightweight delivery.
About you: enter a public identity type, name, short introduction, and optional logo or photo.

Finish setup applies the site-wide preset and displays a summary with an expandable settings receipt. Viewing or leaving the survey changes nothing. Activity insights enable 30-day logging with IP anonymization and dynamic delivery; logged-in observations retain the WordPress user ID as described in Diagnostics and crawler analytics. Lightweight delivery disables logging and selects full static publication. Multisite always keeps dynamic delivery.

Custom content-group adjustments, crawler policies, AI usage permissions, detailed AI features, identity contacts and catalogs, credentials, route slugs, and reports remain in their normal workspaces. Turning AI discovery off also disables WebSub because it depends on the Discovery Hub. The server validates and sanitizes the preset and checks the content, environment, and destination fingerprints before applying it. There is no saved completion state or recurring setup notice.

The apply request accepts only the documented answer keys and scalar types, with bounded identity text and a nonnegative media ID. The server reconstructs the preset from those answers, reruns the non-mutating configuration preview, and compares the environment, content, and destination hashes before it writes anything. The browser does not send a configuration document for WordPress to trust or replay. Identity names use WordPress text sanitization; introductions use textarea sanitization so line breaks survive. Unsupported choices and unknown fields are rejected before the preset is built.

The Crawler & Robots Policy workspace is shown directly within AI Publishing. Its category rows provide bulk controls for every crawler currently listed in that group; individual rows stay collapsed until an administrator chooses Customize.

Cybermaps also provides three dedicated diagnostic pages:

Sitemap Status lists the advertised sitemap inventory, estimated URL coverage, explicit item exclusions, configured delivery mode, and direct links for public inspection.
AI Discovery Status checks each registered fixed-path publication’s enablement, expected format, public HTTP status, media type, parseability, and delivery path. It distinguishes Configured settings, Advertised generated metadata, and Publicly verified live HTTP results.
Discovery Analytics combines endpoint activity, crawler-like content visits, unidentified request patterns, the detailed Request Log, retention, CSV export, and clear-history controls.

The standard WordPress Dashboard includes a five-row CYBERMAPS: Recent PHP-Observed Requests widget with a direct link to the full analytics view.

AI Discovery Status and the AI Discovery Publication Report make bounded GET requests to enabled publications at the configured public base URL. They send the expected Accept media type, X-Cybermaps-Diagnostic: 1, and a Cybermaps health-check User-Agent. The API Catalog receives an additional HEAD check for its required Link header. A bounded number of publications also receive secondary HEAD, OPTIONS, and conditional GET checks for protocol and cache behavior. All of these probes carry the diagnostic marker.

Results are validated locally and cached briefly. A separately hosted Frontend Base URL receives these requests when configured; no probe data is sent to Cybermaps. A failed loopback request or local validation limit leaves delivery unverified rather than proving that public delivery is broken.

On multisite, Network Admin adds a Cybermaps page with an optional centralized /sitemap-network.xml index. It lists the Cybermaps sitemap for each public site where the plugin is active.

For each publishable public post type, the classic editor and block editor expose Cybermaps controls for sitemap exclusion, AI exclusion, intent, sitemap priority, and change frequency. WordPress attachment rows are excluded from the shared publication-type inventory. A translation panel is available when translation integrations are enabled.

Optional MCP connections

Cybermaps works on its own. For MCP clients, open AI Publishing → Model Context Protocol, follow the install/activate link for MCP Adapter by WordPress.org (0.7.0+), then select Enable Cybermaps MCP (read-only) and save. Installing the adapter alone does not enable the integration. The panel shows the endpoint and connection instructions. See MCP setup and 7.x migration for supported authentication, a dedicated Subscriber account and client reconnection.