Publish factual identity and service catalogs, and configure crawler preferences.

How it works

A named identity can appear as homepage JSON-LD when the homepage is indexable, and in the Knowledge Graph when AI Publishing is enabled. Supported primary types are Organization, LocalBusiness, and Person, with validated Schema.org subtypes.

Supported fields include:

entity name, description, and image;
international postal address, latitude, and longitude;
phone and email;
social-profile sameAs URLs;
customer-support, technical-support, and sales contact points;
opening hours; and
one or more Schema.org OfferCatalog structures.

Catalogs can be entered manually or derived from a bounded selection of published direct child pages. The parent and each emitted child must be public, unprotected pages eligible for that output. Knowledge Graph catalogs also honor AI exclusions and Content Discovery Strategy publication choices; homepage schema uses schema indexability. The bounded candidate selection can produce fewer than 50 offers after exclusions.

Normalized identity data is limited to 12 catalogs, 50 offers per catalog, 200 offers overall, 20 social profiles, 12 contact points, and four opening-hour ranges per day. Catalog and identity changes invalidate discovery caches and schedule static reconciliation.

The Knowledge Graph also publishes a WebSite with the Cybermaps search action, informational and transactional collections for public post types and taxonomies, an optional link from the website to the primary entity, and an optional administrator Person.

Robots controls can append to WordPress’s virtual robots.txt output or take over that response. Cybermaps emits its per-crawler deny rules in takeover mode; append mode retains the existing response and adds configured manual directives, publisher preferences, and publication links. Content-use signals express preferences whose interpretation depends on the client. WordPress’s site-visibility setting remains authoritative. The generated response is always dynamic, even when the Static File Engine publishes other files. Cybermaps does not publish a physical robots.txt; a server-owned file must be managed separately.