CLEO by RegenAI

By CLEO by RegenAI

0+ active installationsVersion 1.6.0

See which AI systems read your pages. Requires a free or paid Cleo account.

Description

ChatGPT, Claude, Perplexity and Gemini read your website to answer other
people’s questions. None of them run JavaScript, so ordinary analytics never
records those visits. They are invisible in Google Analytics.

Cleo for WordPress records them on the server, where they can be seen, and
reports them to your Cleo dashboard. You find out which AI systems read which of
your pages, and how often.

You need a Cleo account

This plugin is a companion to the Cleo service at https://regencleo.ai/ and
does nothing on its own. It sends nothing anywhere until you paste a site key
from your Cleo dashboard into its settings screen. Pasting that key is what
switches it on. See External services below for exactly what is sent.

What it does

Four jobs, from one site key:

  1. Reports AI crawler visits. Each visit is classified as an answer engine
    fetching a page for someone waiting on a reply, a search crawler building an
    index, or a training crawler collecting text. Those three mean very different
    things, so they are counted separately.

  2. Installs your Cleo visitor tag. No pasting scripts into a theme that a
    theme update will overwrite. If you later move tracking onto your own
    subdomain, the tag follows automatically. You can switch it off under
    Settings → Cleo.

  3. Places CLEO lead forms. The [cleo_form id="..."] shortcode and the
    CLEO form block put a form you built in Cleo on any page.

  4. Serves your llms.txt. When you turn on “Serve llms.txt and llms-full.txt
    from CLEO” under Settings → Cleo, the plugin answers /llms.txt and
    /llms-full.txt with the text you publish in CLEO, the same way WordPress
    answers /robots.txt. No file is written to your site. It is off until you
    turn it on, and it steps aside when your site already has an llms.txt: a
    real file, or one from Yoast SEO, Rank Math, All in One SEO or another
    plugin. The plugin only reads whether those plugins have llms.txt turned on;
    it never changes their settings or files. Turning it off, deactivating or
    uninstalling puts /llms.txt back as it was.

Connecting to CLEO

Settings → Cleo → Connection has a “Connect to CLEO” link. It opens CLEO,
where you approve the connection on WordPress’s own Application Passwords
screen. What that means:

  • CLEO receives a core WordPress Application Password with all the permissions
    of the user who approves it. Sign in as a dedicated administrator account
    first (recommended).
  • The password passes once through your browser’s address bar to CLEO’s server.
    CLEO replaces it at once with a new one and stores the replacement encrypted.
  • To disconnect, use Disconnect in CLEO, or go to Users → Profile →
    Application Passwords
    and click Revoke. The Connection panel links to the
    right profile.
  • Deactivating or deleting this plugin does not revoke the password.
    WordPress keeps it until you revoke it.
  • On a multisite network one Application Password works on every site where the
    user is a member, with that user’s role on that site.

The plugin adds a read-only route, /wp-json/cleo-wp/v1/capabilities, for
signed-in administrators. It reports the plugin and WordPress versions and which
CLEO features this version supports, and it changes nothing. The Connection
panel also explains what to check when WordPress, a security plugin or your host
blocks Application Passwords.

Remote helpers

Five optional helpers let CLEO make small, reversible changes on your site once
you have connected it. Every one is off until an administrator turns it on
under Settings → Cleo → Remote helpers, and only that screen can turn one
on. Updating or connecting never switches one on. All of them use the same
connection as above, so a request is made with the Application Password of a
real user and is refused unless that user has the WordPress capability
for the same thing.

  • Look up which page a URL belongs to (/wp-json/cleo-wp/v1/resolve-url).
    Reads only. Given an address on your site, it answers with the matching
    post or page (its ID, type and permalink) when the connected user may edit
    it, or that nothing matches.
  • Edit category and tag descriptions
    (/wp-json/cleo-wp/v1/terms/{taxonomy}/{term_id}/description). Reads a
    description and replaces it, through WordPress’s own term functions and only
    with a fixed list of safe HTML tags. It refuses to save if the description
    changed since CLEO read it.
  • Read and edit Elementor page content
    (/wp-json/cleo-wp/v1/elementor/documents/{post_id}). With this switch on,
    CLEO receives the page’s stored Elementor layout and text, and can save an
    edited layout through Elementor’s own save, so Elementor rebuilds that
    page’s styles itself. It refuses a save that Elementor would make
    destructive, for example when a block’s add-on is no longer installed, when
    your user could not have saved that HTML in WordPress, for the Posts page
    and the shop page, and for a page someone else is editing.
  • Clear page caches (/wp-json/cleo-wp/v1/cache/purge). Asks the cache
    plugins you already run to clear one page, a few URLs or the whole site, each
    through that plugin’s own documented function. It reads nothing and stores
    nothing in a cache plugin’s settings.
  • Change SEO titles, descriptions and canonical links
    (/wp-json/cleo-wp/v1/seo/posts/{id}, /seo/terms/{taxonomy}/{id} and
    /seo/home). Described in the next section.

Two more routes only report: /wp-json/cleo-wp/v1/capabilities (described
above) and /wp-json/cleo-wp/v1/changes/{id}, which shows one change CLEO made
and works with the helper off.

The CLEO changes screen and undo. Every change is recorded on your own site,
in a table the plugin creates, with the values before and after. They stay on
your site and are not sent anywhere by the plugin. Settings → Cleo → CLEO
changes
lists them, shows who made each one, and has an Undo button on the
ones that can be undone (descriptions, Elementor content, SEO fields and site-wide settings). Undo is refused
if the page has changed since, so it never overwrites someone else’s edit.
A cache purge cannot be undone, because there is nothing to put back. You
can clear the recorded values at any time; CLEO keeps only what it needs to
avoid repeating a change.

If your plan or trial ends. Values CLEO already changed stay as they are.
Nothing is reverted, and you can still open the CLEO changes screen and undo.
Deactivating the plugin leaves what the remote helpers changed exactly as it
was
: the pages, descriptions and styles stay as they were, and the helpers
simply stop answering. Site-wide settings (below) are the exception: they stop
when you deactivate the plugin, and come back when you reactivate it.
Uninstalling removes them.

SEO titles, descriptions and canonical links

With the switch “Let CLEO change SEO titles, descriptions and canonical links”
on, CLEO can change three fields on a post, a page, a category or tag archive
and the home page: the SEO title, the meta description and the
canonical link. Nothing else on the page changes, and the page’s text is
never read or sent. The Posts page and the WooCommerce shop page are left
alone, because they show a list of posts or products rather than the page.

  • The values go into your SEO plugin’s own fields. With Yoast SEO, Rank
    Math, All in One SEO, SEOPress or The SEO Framework active, CLEO writes into
    that plugin’s fields for the page, exactly as if you had typed them there,
    and that plugin prints them. CLEO prints nothing itself. Settings → Cleo →
    SEO fields
    shows the plugin it found and which fields it can change where.
  • Only one SEO plugin at a time. If two are active, CLEO changes nothing
    until only one is. A version of an SEO plugin CLEO has not been tested with
    is left alone, and so is SEOPress while its Titles module is switched off.
  • With no SEO plugin active, CLEO stores the values on your site and prints
    one title, one meta description and one canonical link itself. The title is
    printed only when your theme supports it: block themes always do, and a
    classic theme must declare title-tag support. These values stop being
    printed if you deactivate this plugin, and start again when you reactivate
    it.
  • Canonical links may point at this site. To let CLEO point one at another
    site, add that site’s hostname under Settings → Cleo → SEO fields. The
    list is empty until you add to it, and only that screen can change it.
  • What is sent to CLEO. When CLEO reads or changes a field, your site
    answers with which page it is (its type and ID), its address, the field’s
    old and new value, a fingerprint (hash) of each value and the receipt of the
    change. Page content is not sent.
  • History, undo and export. Each change is listed under CLEO changes
    with its old and new value, and Undo puts the old value back unless someone
    has changed the field since. SEO fields has an Export JSON button that
    downloads the values CLEO stored itself, to keep a copy on your computer.
  • When your CLEO plan ends, the values keep working as they are. Nothing is
    reverted.
  • Better titles and descriptions can help people choose your page in search
    results, but no plugin can promise rankings or traffic, and this one does not.

Caching plugins. The plugin only calls the cache plugins listed here, and
each only through its documented function:

  • WP Rocket, W3 Total Cache and WP Super Cache: the page, the URL or the whole
    site.
  • WP Fastest Cache: a page is cleared by its address. A whole-site clear may
    also clear Varnish and the Cloudflare zone when you have set those up inside
    WP Fastest Cache.
  • Speed Optimizer (SiteGround): off SiteGround it clears only its own file
    cache.
  • LiteSpeed Cache: only has an effect on a LiteSpeed server or through
    QUIC.cloud.
  • Cloudflare and Hostinger Tools: CLEO does not purge these. They clear their
    own cache when a page is saved.

When no supported cache plugin is active the purge helper reports that, and
does nothing.

No new third party. The helpers and site-wide settings add no service, no outgoing request and no
script. They are routes on your own site that CLEO calls, so the hosts in
External services are unchanged. The only thing the helpers add to what
CLEO can see is the content of what you switch on: Elementor layout and text,
category and tag descriptions, and SEO titles, descriptions and canonical links.

Site-wide settings

Four more optional settings let CLEO fix small things that affect your whole
site. Every one is off until an administrator ticks it under Settings →
Cleo → Site-wide settings
, and only that screen can tick it. Updating or
connecting never switches one on, and CLEO’s servers cannot switch one on.

  • Add your sitemap’s address to robots.txt. Uses WordPress’s robots_txt
    filter to add one Sitemap: line to the robots.txt WordPress serves, and only
    when there is no Sitemap: line already. CLEO picks the address from three
    fixed paths on your own site (/wp-sitemap.xml, /sitemap_index.xml,
    /sitemap.xml).
  • Switch WordPress’s built-in XML sitemap back on. Uses the
    wp_sitemaps_enabled filter, only on a site that shows itself to search
    engines.
  • Put back WordPress’s standard canonical link. When your theme has removed
    it and no SEO plugin is active, hooks WordPress’s own rel_canonical
    function back on wp_head.
  • Put back the link to your site icon. When your theme has removed it and
    you have chosen an icon, hooks WordPress’s own wp_site_icon function back
    on wp_head.

What these settings never do: write robots.txt or any other file, add or remove
a crawl rule, change “Discourage search engines from indexing this site”, send
a response header, print a canonical or icon link of their own, or change
another plugin’s settings. They step aside when something else already manages
the same thing: a real robots.txt file, a site in a subfolder, plain permalinks,
an SEO plugin or Jetpack’s sitemaps. Settings → Cleo → Site-wide settings
says which, in plain words.

  • What is sent to CLEO. Nothing new. The routes
    (/wp-json/cleo-wp/v1/site-settings/{setting}) return the stored value and
    its fingerprint (hash) to a connected administrator. The record of changes
    stays on your site.
  • History and undo. Each change is listed under CLEO changes with Undo,
    and each setting CLEO has changed has a Turn off button on the settings
    screen that works even when CLEO is disconnected.
  • When your CLEO plan ends, the values keep working as they are.
  • Deactivating the plugin stops all four at once. They come back if you
    reactivate it. Uninstalling removes the stored values.
  • Fixing these things can help search engines and AI systems find and read your
    pages, but no plugin can promise rankings, traffic or citations, and this one
    does not.

Built not to break your site

  • No network request is made while a visitor is waiting. Each visit writes one
    row to a local table; everything else happens on a scheduled task.
  • The local queue is capped, so a Cleo outage cannot grow your database.
  • After repeated failures it stops trying for a while, then resumes.
  • Every hook is wrapped so that an unexpected error cannot take your site down.

Page caching

If your site serves cached pages, WordPress does not run for those visits and
they cannot be counted. Cleo asks your caching plugin to skip the cache for AI
crawlers specifically, which recovers most of them. Where your host caches above
WordPress, as WP Engine and Kinsta do, that is not possible from inside a
plugin, and your dashboard will say coverage is partial rather than pretend
otherwise.

Excluding crawlers from the cache means your server renders those pages instead
of serving a file. AI crawler traffic is small next to search engines, so this
is normally negligible, but it is your server and you can turn it off.

External services

This plugin connects to Cleo, a web service operated by REGENAI CLEO, part of
Regenerative AI. The connection is what makes the plugin work: without it there
is nowhere to report crawler activity to.

Service: Cleo, operated by REGENAI CLEO, part of Regenerative AI.
Website: https://regencleo.ai/
Terms of Service: https://regencleo.ai/terms
Privacy Policy: https://regencleo.ai/privacy

When data is sent. Nothing is sent until you enter a valid Cleo site key on
the plugin’s settings screen. If the field is empty, the plugin makes no
external requests at all. Removing the key stops it again.

What is sent, and why.

  1. Request records, in batches, on a scheduled task (never during a visitor’s
    page load). For each request to your site:

    • date and time
    • HTTP method and response status code
    • host and page path, with the query string removed
    • the visitor’s IP address
    • the User-Agent and Referer headers
    • how long the page took to generate

    This is sent so Cleo can identify which requests came from AI …

Installation

  1. Install and activate the plugin.
  2. Go to Settings → Cleo.
  3. Paste the site key from your Cleo dashboard, under the AI Crawlers panel.
  4. Save.

The status panel then tells you whether data is reaching Cleo. Nothing is sent
before step 4.

FAQ

Can CLEO change my site without asking?

The remote helper switches control only this plugin’s own routes. Every remote
helper is off after an install, an update and a connection, and only an
administrator on Settings → Cleo → Remote helpers can turn one on or off.
The four site-wide settings work the same way under Settings → Cleo →
Site-wide settings
: each is off until an administrator ticks it, and CLEO’s
servers cannot tick it. Each change made through a helper or a site-wide
setting is listed under CLEO changes, and most can be undone there.

Connecting CLEO also uses an Application Password. Until you revoke it (on the
user’s profile, under Application Passwords), CLEO can make any change that
WordPress’s own REST API allows that user to make, whatever the helper switches
say. Changes CLEO makes that way are not listed under CLEO changes.

What if I deactivate the plugin after CLEO has made changes?

What the remote helpers changed stays, exactly as saved, and visitors see no
difference. The helpers stop answering. Reactivating restores the screen and the
Undo buttons. Two exceptions, both kept and back when you reactivate the plugin:
SEO titles, descriptions and canonical links CLEO printed itself, because no SEO
plugin was active, are not printed while the plugin is deactivated, and the
site-wide settings (the sitemap line in robots.txt, the XML sitemap, the
canonical link and the site icon link) stop applying.

Which SEO plugins does CLEO work with?

Yoast SEO, Rank Math, All in One SEO, SEOPress and The SEO Framework, one at a
time, in the versions CLEO has been tested with. Settings → Cleo → SEO
fields
says which one it found and what it can change. With none of them
active, CLEO prints the values itself.

Does uninstalling the plugin disconnect CLEO?

No. The Application Password belongs to WordPress, which keeps it after the
plugin is deactivated or deleted. Revoke it under Users → Profile →
Application Passwords
.

Do I need a Cleo account?

Yes. The plugin reports to the Cleo service and does nothing without a site key
from your Cleo dashboard.

Will it slow my site down?

It should not. No network request is made while a visitor is waiting. Each visit
writes a single row to a local database table, and all communication with Cleo
happens on a scheduled task afterwards.

What happens if Cleo is unreachable?

Records queue locally, up to a fixed limit. After several consecutive failures
the plugin stops trying for a while and then resumes. Your visitors see no
difference either way.

Why do the numbers look lower than I expected?

Most likely page caching. If a page is served from a cache, WordPress never
runs, so the visit cannot be recorded. The plugin asks common caching plugins to
skip the cache for AI crawlers, and your Cleo dashboard states whether coverage
is full or partial.

Does it record my human visitors too?

It records all requests that reach WordPress and lets Cleo classify them.
Ordinary browser traffic is counted separately from AI crawler traffic and is
never mixed into the AI figures.

Is the visitor’s IP address stored?

Not by Cleo. It is used to verify that a crawler really belongs to the vendor it
claims, and only an irreversible keyed hash is kept. See External services.

Can I switch parts of it off?

Yes. Under Settings → Cleo you can switch the visitor tag, form capture and
Leadpipe on and off separately. A switch turned off there stays off, whatever
your Cleo account says. Leadpipe stays off until you turn it on.

How do I remove it completely?

Deactivating stops all collection and keeps everything. Deleting the plugin
removes its database tables (the queue and the record of CLEO’s changes), its
settings, its helper switches, its scheduled task, the site-wide settings it
stored, and the SEO titles, descriptions and canonical links CLEO stored itself, on every site of a
network, leaving nothing of the plugin behind. Use Export JSON under
Settings → Cleo → SEO fields first if you want a copy of those values.
Values CLEO wrote into an SEO plugin’s own fields belong to that plugin and
stay. Pages and descriptions CLEO changed are left as they are. It does not delete users, posts or Application
Passwords; revoke CLEO’s Application Password under Users → Profile →
Application Passwords
.

Changelog

1.6.0

  • New optional Site-wide settings panel under Settings → Cleo, with four switches that are off until an administrator ticks them: add your sitemap’s address to robots.txt, switch WordPress’s built-in XML sitemap back on, put back WordPress’s standard canonical link, and put back the link to your site icon.
  • The plugin only uses WordPress’s own hooks and functions for these. It never writes robots.txt or any file, never changes crawl rules or “Discourage search engines”, never sends a header, never prints a canonical or icon link of its own and never changes another plugin’s settings.
  • A setting steps aside when something else manages the same thing: a real robots.txt file, a site in a subfolder, plain permalinks, an SEO plugin or Jetpack’s sitemaps.
  • Every change is listed under CLEO changes with Undo, and each setting CLEO has changed has a Turn off button on the settings screen.
  • Site-wide settings stop when you deactivate the plugin and come back when you reactivate it. Uninstalling removes them.
  • CLEO receives nothing new. No new outgoing request, script or third party.

1.5.0

  • New optional switch under Settings → Cleo → Remote helpers: let CLEO change SEO titles, meta descriptions and canonical links on posts, pages (not the Posts page or the shop page), category and tag archives and the home page. It is off until an administrator turns it on, and updating turns nothing on.
  • Values go into the active SEO plugin’s own fields (Yoast SEO, Rank Math, All in One SEO, SEOPress or The SEO Framework), and that plugin prints them. With two SEO plugins active, CLEO changes nothing.
  • With no SEO plugin active, CLEO stores the values and prints one title (when your theme supports it: block themes always, classic themes with title-tag support), one description and one canonical link itself, only while the plugin is active.
  • New SEO fields panel: the SEO plugin found and what CLEO can change through it, the hosts a canonical link may point to (none outside your site until you add them), and an Export JSON button for the values CLEO stored itself.
  • Every SEO change is listed under CLEO changes, with Undo.
  • CLEO receives the page’s type, ID and address and the old and new values with their fingerprints, never the page’s content. No new outgoing request, script or third party.
  • Uninstalling also removes the values CLEO stored itself and the canonical hosts list. Values in an SEO plugin’s own fields stay.

1.4.0

  • New: serve /llms.txt and /llms-full.txt from the text you publish in CLEO, with no file in your site’s root folder. Off until you turn it on under Settings → Cleo.
  • Steps aside when your site already has an llms.txt (a real file, Yoast SEO, Rank Math, All in One SEO, Website LLMs.txt or another plugin) and says so on the settings page.
  • Downloads are checked for size and fingerprint before use; a failed download never changes what your site serves.
  • The capabilities route reports the new llms_txt feature.
  • Uninstalling removes the stored llms.txt text.

1.3.0

  • New optional remote helpers under Settings → Cleo → Remote helpers: look up which page a URL belongs to, edit category and tag descriptions, read and edit Elementor page content, and clear page caches. Every helper is off until an administrator turns it on, and updating turns none on.
  • With the Elementor switch on, CLEO receives the page’s stored layout and text. Elementor’s own save is used, and a save it would make destructive is refused.
  • New CLEO changes screen under Settings → Cleo: every change CLEO made with its values before and after, kept on your site, with Undo for descriptions and Elementor content. A cache purge cannot be undone.
  • Cache clearing asks WP Rocket, W3 Total Cache, WP Super Cache, WP Fastest Cache, Speed Optimizer and LiteSpeed Cache through their documented functions. Cloudflare and Hostinger Tools are not purged by CLEO.
  • Values CLEO changed stay if your plan ends, and deactivating the plugin changes nothing visitors see.
  • No new outgoing request, script or third party.
  • Uninstalling also removes the change record table and the new settings.

1.2.0

  • New Connection panel under Settings → Cleo: connect to CLEO with a WordPress Application Password, see who is connected and when it was last used, and a link to disconnect.
  • Explains what blocks Application Passwords (no HTTPS, a plugin or setting, your account) and how Wordfence, Solid Security and Hostinger Tools can switch them off.
  • New read-only route /wp-json/cleo-wp/v1/capabilities for administrators, reporting versions and feature states. It changes nothing.
  • Uninstalling now clears the plugin’s data on every site of a network.

1.1.1

  • Leadpipe now loads only after you turn it on under Settings → Cleo. It is off by default.
  • New switches under Settings → Cleo for the visitor tag, form capture and Leadpipe, each with its current status. A switch turned off there wins over your Cleo account.
  • /wp-admin, /wp-login.php, /wp-json, /wp-cron.php and /xmlrpc.php are always excluded, whatever Cleo sends.
  • The visitor tag is added only from a Cleo domain or a subdomain of your own site.
  • The query string is removed from the Referer before it is sent.
  • A malformed first address in a forwarding header no longer hides the address a proxy added after it.
  • The readme now says the remote switch pauses crawler reporting only.

1.1.0

  • Adds the [cleo_form id=”…”] shortcode and a CLEO form block, to place a Cleo lead form on any page.

1.0.0

  • First release.
  • AI crawler tracking with cache exclusion and honest coverage reporting.
  • Visitor tag installation with automatic custom-domain support.