Verify public retrieval, body validity, routing, and headers after configuration changes.
How it works
For a new or migrated site:
- Save the desired sitemap providers and inspect Sitemap Status.
- Configure Schema, then enable AI Publishing, add Custom AI Instructions, and inspect AI Discovery Status.
- Confirm public HTTP status, body format, and media type instead of relying only on a local file indicator.
- On OpenLiteSpeed or nginx, test the extension-bearing Core JSON paths and
the canonical
/ai-discoveryand/.well-known/api-catalogroutes; AI Discovery Status reports whether the automatic origin bridge is active or the request is still blocked before WordPress. - If Redis or Memcached is installed, confirm the WordPress
object-cache.phpdrop-in is active; Cybermaps uses only the WordPress Cache API. - If edge caching is present, review the advisory snippets and confirm RFC 9111 policy, Repr-Digest/header parity, and exact Cybermaps purge behavior at the proxy or CDN.
- Before enabling Markdown for Agents, verify
Vary: Acceptat the public edge and install the documented LiteSpeed/OpenLiteSpeed request bypass when used. - If analytics is wanted, choose the IP-storage mode, trusted-proxy policy, and retention before enabling recording.
- Run a first Content Intelligence Report as the future comparison baseline.
- Download and secure a JSON site-configuration backup.
- After large setting or content changes, use Regenerate Publications and review the reported written, unchanged, conflicted, failed, deleted, and retained counts.
- On a Cloudflare-proxied site, use Advanced’s authorized optimization flow if header or cache repair is needed. Confirm per-resource body and header results after consent; an authorization success message alone is not a delivery result. Compare the ordinary URL as well as diagnostic probes because a query string can take a different cache path.
- For a reproducible failure, enable expiring logging in Debugging, reproduce the action, and export the redacted support bundle. Record the failing path and expected versus observed behavior alongside it.