Cybermaps on Cybermaps — Advanced WordPress Sitemaps & AI Discovery

Features

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps 5.0 is a dedicated discovery engine for WordPress. It combines an advanced sitemap system, machine-readable AI publications, automated catalogs, Schema.org knowledge data, static delivery, crawler logs, and professional content reports in one focused plugin.

Every capability described here ships in Cybermaps Core.

One discovery engine across the entire site

Cybermaps uses one shared eligibility decision for XML sitemaps, AI publications, RAG chunks, IndexNow submissions, and Content Intelligence.

That decision brings together:

AI Search Creates More Ways for Great Websites to Be Discovered

Wed, 27 May 2026 00:00:00 +0000

AI search is expanding the path between a question and a website.

Google describes AI Mode and AI Overviews as systems that can issue multiple related searches across subtopics and data sources, then build a response with supporting links. That creates more opportunities for useful, specialized pages to become part of a person’s research journey.

The sites best positioned for that environment have two strengths:

excellent conventional search foundations; and
information that machines can retrieve and understand efficiently.

Cybermaps strengthens both.

Getting Started

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps is a specialist sitemap, machine-publication, delivery-diagnostics, crawler-analytics, and content-intelligence plugin.

It is an outstanding fit for sites using Genesis or Mai Theme SEO controls and also respects supported Yoast SEO, Rank Math, and All in One SEO indexability signals.

Requirements

WordPress 7.0 or newer
PHP 8.2 or newer
Permission to manage WordPress plugins and Cybermaps settings

Cybermaps Core includes the complete feature set documented on this website.

Installation

Install and activate Cybermaps.
Open Cybermaps → Overview.
Configure Sitemaps and save.
Configure AI Publishing and save.
Open Sitemap Status and validate the public sitemap.
Open AI Discovery Status and inspect intended delivery, owned-file state, public response, media type, and parseability.
Enable recording under Discovery Analytics → Data Controls only if PHP-side request observations are useful for the site.
Create a first completed run under Reports to establish a content baseline.

Primary administration surfaces

The five settings tabs are:

The Static File Engine

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps can serve its discovery layer through WordPress or materialize eligible publications as physical files. The Static File Engine gives operators a practical way to match publication strategy to server behavior and performance goals.

Three delivery modes

Mode	Files written	Ideal use
`off`	Dynamic routes	Conventional WordPress request handling
`well_known`	Five origin-root well-known targets	Reliable canonical delivery on nginx and OpenLiteSpeed
`all`	Eligible sitemaps, discovery files, localized LLMS, and RAG chunks	Maximum physical delivery and minimal runtime work

The default well_known mode solves an important infrastructure problem: OpenLiteSpeed and some nginx configurations serve /.well-known/ before WordPress. Cybermaps places those canonical files where the web server expects to find them.

Turn Content Findings into a Growth Plan

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps replaces hours of manual inventory work with a repeatable content-planning system.

Each finding connects a URL to a literal measurement and a saved rule. That makes it easy to sort the site into practical work queues, estimate effort, assign owners, and explain why the work matters.

Establish a useful baseline

Configure thresholds that match the site’s content model, then run Content Intelligence.

The default post policy begins with:

300 minimum words;
a 365-day review age; and
media review enabled.

The default page policy begins with 150 minimum words. Each content type can be tuned for the site before establishing the first baseline.

A Token-Budgeted Briefing for AI Retrieval

Wed, 27 May 2026 00:00:00 +0000

Websites can contain far more information than a retrieval system can use in one context window.

llms.txt offers a concise map to important resources. llms-full.txt can expose the complete eligible corpus. Cybermaps adds a third option: /llms-tldr.txt, a site briefing assembled to a configurable approximate token budget.

The middle path between a map and a corpus

A short resource map is efficient, but the client must retrieve additional pages to obtain the details. A full corpus carries the details, but a large website may exceed the context available to the retrieval step.

ADP and the Discovery Registry

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps ADP is the site’s machine-readable discovery manifest: a compact starting point that helps retrieval systems identify the publications, catalogs, feeds, actions, and search interfaces available on the website.

It is powered by the same Core registry that drives the rest of the discovery system.

One registry powers everything

Each fixed publication records:

canonical path and aliases;
media type and format;
route handler;
enablement setting;
static publication target;
maturity and adoption information;
throttle tier; and
human-readable label and description.

Routing, static publication, status validation, analytics classification, discovery indexes, and generated documentation consume that shared metadata.

Professional Report Presentation

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps reports are built to be delivered.

Add your professional identity, select a presentation style, and transform a technical content inventory into a clear document that helps clients understand the opportunity and approve the next phase of work.

Presentation controls

Each HTML report can include:

prepared-by name;
prepared-by URL;
professional logo;
client-facing site name; and
Swiss, Minimal, Monochrome, Midnight, or Cyberbrand presentation.

The same completed run can also be exported as CSV for project management and JSON for automation or archival use.

Publication Eligibility

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps\SEO\PublicationEligibility provides one final decision reused by sitemaps, AI publications, RAG chunks, IndexNow, and Reports.

Decision inputs

Cybermaps evaluates:

WordPress publication state, public object type, password protection, URL, and site visibility.
Genesis and Mai Theme noindex, canonical, and redirect signals.
Supported Yoast SEO, Rank Math, and All in One SEO signals.
Cybermaps global and per-resource exclusions.
Surface-specific inclusion controls.

An off-resource canonical or redirect makes the resource ineligible. The final result includes explicit reason keys and source signals.

Sitemaps

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps builds a configurable sitemap index and provider inventory from eligible WordPress resources.

Core output

Numbered post-type and taxonomy children
Author, archive, and miscellaneous URL providers
Google News output when enabled
Optional RSS 2.0 output
Image and video extensions
External sitemap references
Dynamic ETag and 304 Not Modified responses
Browser-readable XSL preview

The default index is /sitemap.xml. Internal children are chunked at 2,000 URLs.

External sitemap references

Cybermaps references an external sitemap; it does not copy or claim ownership of the file.

Smarter Sitemap Metadata

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps treats a sitemap as managed discovery infrastructure.

The engine combines standard priority and change-frequency controls with image, video, News, RSS, HTML, and browser-readable output. Publisher presets make it easy to establish practical priority patterns across different site sizes and content types.

Shared eligibility keeps every surface aligned

Before a resource reaches a sitemap, Cybermaps evaluates:

publication state and public visibility;
password protection;
canonical URL and redirects;
global and per-resource exclusions;
Genesis and Mai Theme SEO settings; and
supported Yoast SEO, Rank Math, and All in One SEO signals.

The same decision is reused by machine publications, RAG chunks, IndexNow submissions, and Content Intelligence.

Budgeted Site Briefing 0.2 Draft

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps experimental proposal · deterministic output · configurable token budget

Purpose

/llms-tldr.txt gives a publisher a middle path between a short link-oriented llms.txt file and a complete site corpus.

It assembles a compact briefing from eligible WordPress content, follows a stable publisher-controlled order, includes complete resource entries, and accounts for the entire output under a configured approximate token budget.

The goal is straightforward: expose more useful site knowledge in one retrieval while keeping the publication practical for context-limited systems.

Machine Publications

Mon, 01 Jan 0001 00:00:00 +0000

The Endpoint Registry keeps routing, media types, static targets, enablement, throttling, status validation, analytics, and advertised publications synchronized.

Fixed publications

Canonical path	Classification	Purpose
`/.well-known/ai.json`	Vendor extension	Primary discovery manifest
`/.well-known/ai-discovery`	Vendor extension	Registry-backed publication index
`/llms.txt`	Community proposal	Site map with short literal extracts
`/llms-full.txt`	Optional vendor extension	Complete literal stored-content corpus
`/llms-tldr.txt`	Optional experiment	Deterministic budgeted briefing
`/knowledge-graph.json`	Schema.org-based vendor endpoint	Configured identity and relationship graph
`/feed.json`	JSON Feed 1.1	Recent content
`/ai-sitemap.xml`	Vendor extension	Machine-oriented content inventory
`/ai-usage.json`	Vendor extension	Publisher-authored usage assertions
`/ai-actions.json`	Vendor extension	Publisher-authored action links
`/skill.md`	Vendor extension	Publisher-authored site guide
`/.well-known/api-catalog`	RFC 9727 representation	Public REST API catalog

The manifest and discovery index have /ai.json and /ai-discovery aliases. Usage and action publications have corresponding well-known aliases.

Static File Engine

Mon, 01 Jan 0001 00:00:00 +0000

Dynamic WordPress handlers are the functional baseline. The Static File Engine optionally materializes the same output.

Modes

Mode	Behavior
`off`	Writes no files; supported requests use WordPress when routed to PHP
`well_known`	Writes five origin-root well-known copies while AI Publishing is enabled; default
`all`	Also writes eligible sitemap, web-root discovery, localized LLMS, and RAG output

The retired enable_static_engine boolean is not a runtime fallback. static_engine_mode is the only mode setting.

Status and Discovery Analytics

Mon, 01 Jan 0001 00:00:00 +0000

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.

Reports

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps Reports turns the WordPress content inventory into a repeatable optimization and client-delivery workflow.

Content Intelligence runs

For published public post types except attachments, a run records:

stable resource key and WordPress object ID/type;
title and URL;
stored modified time;
literal visible word count;
media presence;
indexability and reasons; and
SHA-256 content hash.

The run also preserves its rules, rule hash, baseline run ID, counts, snapshot hash, timestamps, and terminal state.

Robots, Identity, and External Services

Mon, 01 Jan 0001 00:00:00 +0000

Robots output

Cybermaps supports global and per-bot directives, append or takeover mode, crawl delays, and links to configured sitemap and discovery publications.

Robots directives and machine-readable usage values communicate publisher preferences. They do not technically or legally enforce compliance.

robots.txt remains dynamic in every Static File Engine mode.

Identity output

Configured Organization or Person JSON-LD is emitted on the front page only when required identity data exists. Optional VideoObject output is separate.

REST API and WP-CLI

Mon, 01 Jan 0001 00:00:00 +0000

All REST routes use the cybermaps/v1 namespace.

REST routes

Route	Access
`GET /discovery`	Public while AI Publishing is enabled
`GET /llms-tldr`	Public while AI Publishing and the experimental briefing are enabled
`GET /search`	Public while AI Publishing is enabled
`GET /urls`	`X-Cybermaps-Secret`
`GET /status`	`X-Cybermaps-Secret`
`GET /audit-latest`	`X-Cybermaps-Secret`
`GET /audit-run?run_id=N`	`X-Cybermaps-Secret`
`POST /purge`	WordPress authentication and `manage_options`

Secret-protected and maintenance responses are private and no-store.

Public search uses bounded WordPress text matching and eligibility filtering. The result limit is restricted to 1–100. It does not use embeddings or semantic similarity.

Extension API 2.0

Mon, 01 Jan 0001 00:00:00 +0000

Cybermaps\Core\ExtensionAPI::get_instance() exposes a narrow public boundary.

Capabilities

endpoints() registers validated metadata for an implemented extension endpoint.
eligibility() returns the same final publication decision used by Core.
audits() provides read-only access to completed audit runs.

The readiness action is:

cybermaps_extension_api_ready

Endpoint registration errors are rejected without preventing Core from loading.

Deliberate boundaries

Extension API 2.0 does not expose:

Core’s service container;
Core settings ownership;
filesystem ownership records;
route callbacks;
audit mutation;
licensing; or
an updater.

An extension uses its own namespace, options, tables, routes, assets, lifecycle, generated files, and uninstall behavior.

Lifecycle, Security, and Troubleshooting

Mon, 01 Jan 0001 00:00:00 +0000

Lifecycle

Activation provisions Core schema and schedules required work.

Deactivation unschedules work and attempts an ownership-safe static purge.

Uninstall removes persistent Core data only when Delete data on uninstall was explicitly enabled.

Administration security

Administrative actions require manage_options and nonces. Request values are sanitized and output is escaped for its context.

Static writes use WP_Filesystem. Cybermaps does not overwrite or delete a target whose current content differs from its recorded ownership hash.

LLMS-TLDR 0.2

Mon, 01 Jan 0001 00:00:00 +0000

/llms-tldr.txt is an optional experimental Cybermaps publication for testing deterministic, token-budgeted site briefings.

It is not part of the llms.txt proposal, an IETF standard, an MCP resource, an Agent Skill, a search index, or an AI-generated summary.

Stable order

Configured pinned resource IDs in publisher order
Configured content-type order
Stored modified time descending
WordPress object ID ascending

Literal extraction

Each candidate contains the title, public URL, content type, valid stored modification time, and a fixed-length literal extract.