Description
Most SEO plugins grade a page at the moment you edit it. A page can still quietly go to noindex three weeks later, after an update, and stay that way until someone notices.
SEO GEO Watch treats SEO like monitoring. It reads your own pages on a schedule, compares each reading with the previous one, and alerts you by e-mail or Slack when an indexable page degrades.
It does not give you a score. It tells you what changed, when, and what else happened on the site around that time.
Page monitoring
- Reads HTTP status, title, meta description, robots directives (meta tag and X-Robots-Tag header), canonical, H1 to H3, hreflang and JSON-LD types.
- Keeps a version only when something changes, with a field-by-field comparison.
- Reports noindex, HTTP errors, redirects, removed tags, canonical moves, lost structured data, sharp drops in text or internal links.
- Notes plugin, theme and WordPress updates close in time to a change, as a lead and never as proof.
- Counts what the latest readings show (HTTP errors, noindex pages, pages without a title, meta description or H1, invalid JSON-LD, robots blocked by robots.txt), next to the figure from 7 days earlier, with a link to the pages concerned. Facts, not a score.
- Compares the last 7 days with the 7 days before: changes detected, changes back to normal, AI robot visits, arrivals from assistants.
AI signals you can measure on your own site
- What your robots.txt allows for each AI robot, computed with the RFC 9309 rules, and when that changes.
- What your server really answers to a robot’s User-Agent. A firewall can refuse what robots.txt allows.
- Robot visits seen by PHP, per day, robot and page.
- A cache test that tells you whether your page cache hides those visits.
- Arrivals from AI assistants, when a referrer or a utm_source tag is present. Off by default: this needs a small script on public pages, which you turn on in the settings.
- Presence and changes of llms.txt, llms-full.txt and declared sitemaps.
- Drift over time: a robot that suddenly stops coming, a robot newly blocked.
What this plugin does not measure
It is important to read this before installing.
- Your position or citations in ChatGPT, Gemini, Claude, Perplexity or any other assistant. This plugin calls no AI service, so it cannot see their answers. No WordPress plugin can measure that without querying those services.
- Whether a page was really used to train a model or to write an answer. A visit proves a page was fetched, nothing more.
- All robot visits. A visit is recognised by the User-Agent it declares, which can be faked. Pages served by a page cache or a CDN never reach PHP and are not counted. The figures are a lower bound.
- All arrivals from assistants. Many assistants send no referrer, especially from mobile apps. Google AI Overviews and AI Mode cannot be told apart from classic Google traffic.
The plugin has a “What is measured” screen that says all of this next to the figures.
False alarms
A monitoring tool that cries wolf gets switched off, so most of the work went there.
- Only extracted fields are compared, never the raw HTML. Nonces, attribute order and changing scripts have no effect.
- A text that differs only by a date or a time counts as unchanged.
- A degradation must be seen on a second reading, about 10 minutes later. A server error must be seen three times.
- A title changed on a page you edited in WordPress is logged as information. A noindex always alerts, even after an edit.
- A field that keeps changing, such as an A/B test, stops alerting and stays in the log.
- If every page of a round fails, you get one alert for the site, not one per page.
- The same change on 200 pages fits in one line of the alert.
Performance
- Readings run in small batches through WP-Cron, with a pause between pages. The batch shrinks when the site answers slowly, and readings pause after a 429 or 503 response.
- For a human visitor, the plugin runs one regular expression and adds no database query. See the FAQ for the measured figures.
Privacy
- No IP address is read or stored. No cookie, no visitor identifier.
- The optional arrivals script (off by default) sends only the assistant name and the page path to your own site’s REST API, and only when the visitor comes from a known AI assistant.
- Visit counts are aggregated per day and per page. Retention is yours to set.
- Page readings are requests from your site to itself. A redirect that leads to another host is recorded (status and target address) but never followed, so no request is sent to that host.
- Alerts are sent by e-mail through your site’s own mail function (wp_mail) to the address set in the settings, and to the Slack webhook you provide, if any. Nothing else leaves your site.
About the author
SEO GEO Watch is developed by José Perez, SEO & GEO consultant: joseperez.fr.
External services
This plugin connects to one external service, only if you configure it:
Slack incoming webhooks. When you paste a webhook address in the settings, alert messages are sent to that address. A message holds the site name, the kind of change, the page addresses concerned and the values before and after. Nothing is sent if no webhook is set. Slack is provided by Slack Technologies: terms of service, privacy policy.
E-mail alerts. Alerts are sent with WordPress’ own wp_mail() function to the address set in the settings (by default the site administrator’s address). They go through the mail setup of your site or of your SMTP plugin; the plugin contacts no mail service itself. A message holds the same information as a Slack alert. You can turn e-mail alerts off in the settings.
Links to robot documentation. The AI signals screen shows links to the pages where OpenAI, Anthropic, Perplexity, Google, Apple, Meta, Amazon and Mistral document their robots. They are plain links, opened only if you click them; the plugin sends no request to these sites.
All other requests go to your own site. Redirects to another host are never followed.
Screenshots





Installation
- Install and activate the plugin.
- Nothing to set up. Right after activation, a notice on the Plugins screen offers a first check: one click reads the home page and the most recent pages, then robots.txt, llms.txt and the sitemaps, and opens the overview. The other pages are read in the background, a few every 5 minutes.
- In Settings, check the alert address and paste a Slack incoming webhook if you use Slack.
- If WP-Cron is disabled on your server, call wp-cron.php from a server task or run
wp sgwatch tick.
FAQ
-
Can this plugin tell me if ChatGPT cites my site?
-
No. That would require querying ChatGPT, and this plugin calls no AI service. It measures what happens on your own site.
-
Why are my robot visit figures so low?
-
The cache test on the AI signals screen answers that. If your page cache serves robots before PHP runs, those visits are not counted. The same screen lists the User-Agents to exclude from your cache if you want them counted, at the price of one full page build per robot visit. In our tests this worked with WP Fastest Cache but not with WP Super Cache, which keeps serving existing files to excluded robots: run the cache test again to check.
-
Why is there no AI visibility score?
-
Because no assistant publishes what makes it cite a page, so such a score would be invented. The only composite figure here is the share of pages without an open change, and its formula is shown next to it.
-
Do I need a Google key?
-
No. The plugin works without any key or account.
-
How much does it slow down my site?
-
Measured on a test site with WordPress 7.1, PHP 8.3 and OPcache, over 300 requests per case: no extra SQL query and about 1.3 ms on a 124 ms page for a human visitor, and one aggregated write, about 12 ms, when a known robot visits. The optional script that counts arrivals, off by default, adds less than 1 KB inline to public pages when you turn it on. Your figures will differ.
-
Will it hammer my own server?
-
By default it reads 5 pages every 5 minutes, half a second apart, one at a time. It reduces the batch when pages take over 2 seconds, and stops for 30 minutes on a 429 or 503 response.
-
Does it work behind Cloudflare or another CDN?
-
Page readings work. Robot visits answered by the CDN never reach your server, so they are not counted.
-
My site is multisite.
-
Each site has its own tables and settings when the plugin is activated. Network activation creates them for the existing sites only.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“SEO GEO Watch” is open source software. The following people have contributed to this plugin.
Contributors“SEO GEO Watch” has been translated into 1 locale. Thank you to the translators for their contributions.
Translate “SEO GEO Watch” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.0.1
- Added the plugin and author links in the plugin header.
1.0.0
- First release.
