# Identity, schema, and crawler policy

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

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

## How it works

The Identity Hub publishes a configured entity both as homepage JSON-LD and in the Knowledge Graph. 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 generated from up to 50 published direct child pages of a selected parent page. Identity input is bounded to 12 catalogs, 200 offers overall, 20 social profiles, 12 contact points, and four opening-hour ranges per day so editor submissions, backups, and public JSON-LD remain predictable. 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 support append mode or full takeover, bounded manual directives, per-crawler overrides, and machine-readable content-use signals. WordPress’s site-visibility setting remains authoritative. The generated `robots.txt` response is always dynamic, even when the Static File Engine publishes other files.