# CYBERMAPS is now in open beta

Try advanced WordPress sitemaps, useful AI publications, branded client reports, and delivery diagnostics in the free CYBERMAPS open beta.

OPEN BETA

Give search engines and AI agents more to work with. See what your website can do.

The CYBERMAPS open beta is here. Advanced sitemaps, readable AI publications, branded reports, and public delivery checks are ready to try on your WordPress site. They’re all included in the free plugin.

[Download open beta ↗](https://github.com/Alex9001/cybermaps/releases/)

Open beta for bug reports. Plugin Directory is in review (stage 2). Install from GitHub until then.

01 / OVERVIEW

### See the entire discovery system

Start with a live map of search, AI, structured-data, API, and policy publications. Publication state and direct output links stay together in one workspace.

[Read the guide ↗](https://cybermaps.dev/docs/getting-started/)

1 / 14

14 plugin screens and reports · Select a thumbnail, then open the image to inspect it at full size.

## Start with a better map of your website

Search crawlers still need to find your content. CYBERMAPS gives you detailed control over what goes into your sitemaps, with support for publishers, business websites, and sites rich in images and video.

*   **Publish advanced XML sitemaps:** eligible posts, pages, taxonomies, authors, and additional URLs.
*   **Include your media:** image and video discovery, with dedicated News sitemap support for publishers.
*   **Serve human visitors too:** build an HTML sitemap and configure a separate RSS publication.
*   **Decide what belongs:** control eligibility, exclusions, and sitemap ownership from one publishing system.

**Try this:** follow Guided Setup, choose your sitemap owner, and open the generated sitemap to see how your content is represented.

[Explore sitemap configuration →](https://cybermaps.dev/docs/sitemaps/)

## Turn your content into something agents can use

A customer asks an agent about your services, products, or expertise. CYBERMAPS can publish readable sources that help compatible clients retrieve that information from your site.

*   **A map for discovery**Publish llms.txt and discovery indexes that point to eligible resources.
*   **The actual content**Offer Markdown and full-content publications, plus a concise briefing for smaller retrieval budgets.
*   **Business context**Describe your identity, services, and catalogs with structured information.
*   **Tools for compatible clients**Enable optional MCP and browser agent support, with access governed by the selected mode and permissions.

**Try this:** enable AI Publishing, open your public outputs, and compare them with the content on your site. Each external service decides what it discovers and uses; CYBERMAPS makes useful material available when it arrives.

[Configure AI publications →](https://cybermaps.dev/docs/machine-publications/)

## Find improvements and show clients what changed

For SEO marketers and agencies, **Reports may be the first workspace to open**. Turn a content review into an action list, then give clients evidence of the improvements you made.

*   **Find opportunities:** surface content gaps and pages that need attention.
*   **Plan paid work:** use the findings to scope fixes, content projects, or maintenance.
*   **Make the result presentable:** create branded printable reports and export the available findings.
*   **Keep the evidence:** save reports and compare measurements as the site improves.

**Try this:** generate a report for a client site, choose an improvement to make, and save another report afterward. You get a guide to the work and a deliverable that helps explain its value.

[See the reporting workflow →](https://cybermaps.dev/professionals/)

## Know what is reaching your site

Configuration is only the beginning. The beta includes tools to inspect delivery and understand observed crawler activity.

*   **AI Discovery Status** separates what is enabled, advertised, available, and valid.
*   **Public checks** inspect HTTP responses, media types, headers, and publication bodies.
*   **Crawler analytics** show recognized activity that reaches the plugin’s tracking layer. Requests served directly by a cache or static file can bypass PHP tracking.
*   **Debugging and System Status** help explain your server setup and which optimizations are in use.

**Try this:** inspect a publication in AI Discovery Status. If its public response differs from the configuration, use the delivery evidence to investigate.

[Read the diagnostics guide →](https://cybermaps.dev/docs/status-analytics/)

## Clean controls. Efficient delivery.

CYBERMAPS brings these features together in a focused WordPress workspace, with practical controls for the infrastructure underneath.

*   **Optional static publication** lets your server deliver eligible files without regenerating them through WordPress for every request.
*   **APCu and LiteSpeed integrations** reuse supported caching capabilities.
*   **Scoped invalidation** refreshes CYBERMAPS publications when relevant content or settings change.
*   **Cloudflare integration** helps configure discovery headers and cache safety on supported setups.
*   **Bounded scans and output budgets** keep publication work within defined limits as content grows.

[Explore delivery and caching →](https://cybermaps.dev/docs/static-file-engine/)

## Download, explore, and help shape the release

The open beta is free software under **GPL-2.0-or-later**. It requires **WordPress 7.1+ and PHP 8.2+**. Reports, branding, and the publishing features described here are included in CYBERMAPS.

### What happens when the beta ends?

**The open beta ends when CYBERMAPS is released on WordPress.org. The plugin stays free.** The transition is to the normal WordPress.org update channel, so beta users can carry on with CYBERMAPS and receive future releases through their WordPress dashboard. We’ll include any transition steps with the WordPress.org release announcement.

Until then, you get to live on the bleeding edge of WordPress: try the new publishing and agent capabilities early, put them through real workflows, and help shape the release. You’ll have time to learn the tools and see where they help on your own sites and client projects.

### Get started today

1.  **Download the beta** from GitHub Releases and read the release notes.
2.  **Start on a test site.** Follow Guided Setup and choose which plugin owns your sitemap.
3.  **Try it with your content.** Inspect the sitemaps, AI publications, and reports.
4.  **Share useful feedback.** Tell us what you expected, what happened, and how to reproduce it. Include the plugin version and relevant delivery details.

**Your content. Your control.**  
Put the beta to work and help make the next release better.

[Download open beta ↗](https://github.com/Alex9001/cybermaps/releases/)

[Getting started](https://cybermaps.dev/docs/getting-started/) · [Support and feedback](https://cybermaps.dev/support/)

## About the developer

I’m **Aleksandr Oreshkin** of **CYBER BRAND**. I’ve built hundreds of WordPress websites since 2009 and put that experience into CYBERMAPS. My cat **Nuski** helped a lot, too. We hope you enjoy trying it.

[![Aleksandr Oreshkin outdoors in a snow-covered helmet](/images/blog/aleksandr-thumb.webp)View photo ↗](https://cybermaps.dev/images/blog/aleksandr-oreshkin.jpg)

**Aleksandr Oreshkin**Developer · CYBER BRAND

[![Nuski standing on a branch among spring blossoms](/images/blog/nuski-thumb.webp)View photo ↗](https://cybermaps.dev/images/blog/nuski.jpg)

**Nuski**Cat · Much appreciated help

[Read the story behind CYBERMAPS →](https://cybermaps.dev/about/)
