Title: Octoplug GEO Suite
Author: Octoplug
Published: August 19, 2026
Last modified: August 19, 2026
---
Search plugins
# Octoplug GEO Suite
By [Octoplug](https://profiles.wordpress.org/octoplug/)
[Download](https://downloads.wordpress.org/plugin/octoplug-geo-suite.1.28.0.zip)
* [Details](https://wordpress.org/plugins/octoplug-geo-suite/#description)
* [Reviews](https://wordpress.org/plugins/octoplug-geo-suite/#reviews)
* [Installation](https://wordpress.org/plugins/octoplug-geo-suite/#installation)
* [Development](https://wordpress.org/plugins/octoplug-geo-suite/#developers)
[Support](https://wordpress.org/support/plugin/octoplug-geo-suite/)
## Description
Most plugins in this space write an `llms.txt` and stop there. GEO Suite starts
from the opposite end: it **measures** the site, tells you in plain words what is
holding it back, and only then writes the files — and afterwards it **goes and checks
from the outside** that what it wrote is actually being served.
That measure-then-verify loop is what the plugin is built around:
1. **A GEO Score you can argue with.** Six pillars, every check named, every recommendation
carrying the points it is worth and a link to exactly where you fix it. No black
box and no external service: the score is computed on your own site, from data
WordPress already has.
2. **The files and the structured data.** `llms.txt` and `llms-full.txt` kept up to
date on their own, a Markdown copy of every page at `.md`, JSON-LD (
Organization, WebSite, Article, Breadcrumb, FAQPage, Person) written only where
your SEO plugin has not already written it.
3. **The outside check.** The plugin asks its own addresses the way a crawler would
and reports what really comes back — a redirect, a firewall, a cache serving something
else. A file that exists is not the same as a file that is reachable, and this
is the part that usually explains why nothing was working.
4. **The trend.** Your score is recorded from the day you install, along with the “
before” picture of the site, so you can see whether the work is paying off month
after month. It is recorded **and shown**, in the free plugin.
Everything above is in this plugin, free, with no account, no license key, no time
limit and no quota.
Also included:
* **Content the plugin cannot read is not silently scored as empty** — pages built
with Elementor, Oxygen, Bricks, Breakdance, Beaver, Divi, WPBakery or Avada keep
their text where the builder put it. GEO Suite reads it there, without ever executing
third-party shortcodes while it builds the files.
* **AI crawler management** — decide which AI bots may read the site, written into
robots.txt with labels a human can understand: the ones that answer people’s
questions are separated from the ones that harvest content to train models.
* **You decide what AI can see** — a column and two bulk actions on pages, posts
and products: take anything out of the AI files without hiding it from your site
or from Google.
* **Setup wizard** — four steps, a couple of minutes, no jargon.
* **In-app documentation** — every recommendation the dashboard can give you has
a card explaining exactly what to do about it.
* **Multilingual (WPML and Polylang)** — one set of files and structured data per
active language, each at its own address, with headings resolved in that file’s
language.
* **A diagnostic report you can copy** — for when you need to write to somebody.
Nothing is ever sent anywhere.
GEO Suite works alongside Yoast, Rank Math and SEOPress without conflicts and reuses
their data where it can. No dependency on WooCommerce. No external calls, no tracking,
no phoning home.
There is a separate, optional add-on (**GEO Suite Pro**) that adds per-page analysis,
bulk editing, advanced schema and detailed AI crawler monitoring. It is a different
plugin: none of its code is in here, and nothing in this plugin is switched off
waiting for it.
## Screenshots
[⌊The dashboard. One number, the six pillars that make it up, and the few things
worth doing next — each with the points it is worth and a link to where you fix
it.⌉⌊The dashboard. One number, the six pillars that make it up, and the few things
worth doing next — each with the points it is worth and a link to where you fix
it.⌉[
The dashboard. One number, the six pillars that make it up, and the few things worth
doing next — each with the points it is worth and a link to where you fix it.
[⌊Technical files. Every address with its state, a preview of the content, and the
check that asks them from the outside the way a crawler would: present is not the
same as reachable.⌉⌊Technical files. Every address with its state, a preview of
the content, and the check that asks them from the outside the way a crawler would:
present is not the same as reachable.⌉[
Technical files. Every address with its state, a preview of the content, and the
check that asks them from the outside the way a crawler would: present is not the
same as reachable.
[⌊The trend. Your score from the day you installed the plugin to today, with the
reading that changed it and what caused each change.⌉⌊The trend. Your score from
the day you installed the plugin to today, with the reading that changed it and
what caused each change.⌉[
The trend. Your score from the day you installed the plugin to today, with the reading
that changed it and what caused each change.
[⌊Settings. Who you are in one sentence, your official profiles, and the content
you have hidden from AI.⌉⌊Settings. Who you are in one sentence, your official profiles,
and the content you have hidden from AI.⌉[
Settings. Who you are in one sentence, your official profiles, and the content you
have hidden from AI.
[⌊AI crawlers. For each bot, allow or block. The ones that answer people's questions
are on by default; the ones that harvest content to train models are not.⌉⌊AI crawlers.
For each bot, allow or block. The ones that answer people's questions are on by
default; the ones that harvest content to train models are not.⌉[
AI crawlers. For each bot, allow or block. The ones that answer people’s questions
are on by default; the ones that harvest content to train models are not.
[⌊The guide, inside the plugin. Every recommendation the dashboard can give you,
and exactly what to do about it — with a button that does it for you where it can
be done from here.⌉⌊The guide, inside the plugin. Every recommendation the dashboard
can give you, and exactly what to do about it — with a button that does it for you
where it can be done from here.⌉[
The guide, inside the plugin. Every recommendation the dashboard can give you, and
exactly what to do about it — with a button that does it for you where it can be
done from here.
[⌊Pages, posts and products carry a "Visible to AI" column, a link under each title
and two bulk actions: taking content out of the AI files is done where you already
work.⌉⌊Pages, posts and products carry a "Visible to AI" column, a link under each
title and two bulk actions: taking content out of the AI files is done where you
already work.⌉[
Pages, posts and products carry a “Visible to AI” column, a link under each title
and two bulk actions: taking content out of the AI files is done where you already
work.
## Installation
1. Upload the `octoplug-geo-suite` folder to `/wp-content/plugins/`, or install the
plugin from the WordPress Plugins screen.
2. Activate the plugin from the Plugins menu.
3. Open the **GEO** menu item and follow the setup wizard (about 2 minutes).
4. Recommended: use “pretty” permalinks (Settings Permalinks) to serve the files
through the `/llms.txt` and `/llms-full.txt` URLs.
## FAQ
### Does granting access to AI crawlers hurt my Google ranking?
No. AI crawler access and traditional Google ranking are separate things: letting
AI bots read the site does not affect organic ranking.
### Does GEO Suite conflict with my SEO plugin?
No. GEO Suite detects Yoast, Rank Math or SEOPress and works alongside them, avoiding
duplication of the structured data the SEO plugin already generates.
### Does the plugin store visitors’ personal data?
No, and it makes no external calls at all. The plugin counts how many times known
AI bots passed by, as a daily total: no IP addresses, no visitor data, nothing that
identifies anybody. The score history it keeps is a number and a date, stored in
your own database.
### The llms.txt files don’t show at their URL. What should I do?
Make sure “pretty” permalinks are active (Settings Permalinks). If pretty permalinks
are not available, the `?opgs_file=llms` fallback is provided, and it is also reported
in the settings.
### Does it work with multilingual sites?
Yes, with both WPML and Polylang: files and structured data are generated for every
active language, each at its own address (/llms.txt for the main language, /en/llms.
txt for English, and so on).
### Is anything in this plugin locked, limited or time-based?
No. There is no license key, no trial, no quota and no expiry. Every feature described
above works from the moment you activate it. A separate add-on exists for per-page
analysis, bulk editing, advanced schema and detailed crawler monitoring, but that
is a different plugin with its own code: nothing here is disabled waiting for it.
### Where does my score history end up?
In a table in your own database, on your own site. One reading a day plus one every
time you regenerate or recalculate, each a number, a date and what triggered it.
You can see the whole thing under GEO Suite Trend, change how long it is kept,
or switch the recording off entirely, in Settings.
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Octoplug GEO Suite” is open source software. The following people have contributed
to this plugin.
Contributors
* [ Octoplug ](https://profiles.wordpress.org/octoplug/)
[Translate “Octoplug GEO Suite” into your language.](https://translate.wordpress.org/projects/wp-plugins/octoplug-geo-suite)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/octoplug-geo-suite/),
check out the [SVN repository](https://plugins.svn.wordpress.org/octoplug-geo-suite/),
or subscribe to the [development log](https://plugins.trac.wordpress.org/log/octoplug-geo-suite/)
by [RSS](https://plugins.trac.wordpress.org/log/octoplug-geo-suite/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
#### 1.28.0
* **New: the Trend screen — and your score history is now yours.** The plugin has
always recorded your GEO Score from the day you installed it, and captured the“
before” picture of the site at that moment. Until now there was no screen for
it. There is one: GEO Suite Trend shows where you started, where you are, the
curve over 30 days / 90 days / 12 months / everything, and a table of every reading
with what caused it — a scheduled reading, a recalculation you asked for, or
a plugin update that changed how the score is worked out.
* **Removed: the “Pro” page in the admin.** The comparison table, the prices and
the greyed-out tiles on the dashboard are gone. If you want to know about the
separate add-on there is one link, on the plugin’s row in the Plugins list, and
nothing anywhere else.
* Fixed: structured data is now printed through the WordPress core helper, with
JSON encoded so that a title or an author name can never break out of the script
tag.
* Fixed: post type headings in `llms.txt` no longer borrow WordPress’ own translation
domain; they come from the public core API instead, and still follow the language
of each file.
* Housekeeping for the directory: the runtime brand image moved out of the folder
reserved for the WordPress.org listing graphics, and the stylesheet no longer
carries the rules of the removed page.
#### 1.27.3
* New `opgs_contenuto_sorgente` filter: a theme or plugin can now hand over the
real text of a page the plugin cannot read on its own — an archive, a product
list, a portfolio, anything whose content is a shortcode that fills in at render
time. The plugin still never executes third-party shortcodes while building the
files, which is exactly why the filter exists.
* Fixed: filled buttons were picking up the outline button’s corner radius and
padding, so the primary action looked subtly different from the buttons next
to it.
* Fixed: on multilingual sites (Polylang/WPML) the section headings in the per-
language `llms.txt` now follow the language of the file. The English `/llms.txt`
no longer printed the site-language post-type labels (e.g. “## Articoli” instead
of “## Articles”); each file’s headings are resolved in that file’s locale. No
change on single-language sites.
#### 1.27.2
* Changed: the admin top-level menu now reads “GEO Suite” instead of “GEO”, for
clearer branding — consistent across all bundled languages.
#### 1.27.1
* Fixed: hardened input sanitization on the author “Official profiles (sameAs)”
field so it clears WordPress.org’s static analysis. No functional change — every
address is still validated as an http(s) profile URL before it is saved.
#### 1.27.0
* Fixed: on multilingual sites (Polylang) the per-page Markdown endpoint (`.md`) could serve the same content for every language when translations shared
the same slug. The resolved content is now constrained to the language requested
in the URL. No change on single-language sites or with WPML.
* New: structured data (WebSite, Article/WebPage) now declares `inLanguage` with
the real content language.
* New: the BreadcrumbList now builds a real hierarchy on its own — parent chain
for hierarchical pages, and the primary category (with its ancestors) for posts
and custom post types — instead of just Home › Content. A primary term elected
in Yoast or Rank Math is honoured; names and URLs come out in the content language
on Polylang/WPML sites. Falls back to the previous Home › Content chain when
no hierarchy can be determined.
* New: filter `opgs_breadcrumb_items` lets a site (or add-on) supply its own breadcrumb
chain — useful when navigation follows a taxonomy silo that WordPress’ own hierarchy
doesn’t reflect. Positions are renumbered automatically.
#### 1.26.0
* New: full German, French and Spanish translations for the European launch. The
whole interface, setup wizard and in-app manual are now available in de/fr/es
alongside Italian, with native-quality wording. (Free translations are served
through translate.wordpress.org.)
#### 1.25.0
* New: two filters — `opgs_llms_site_intro` and `opgs_llms_item_description` —
let an add-on supply the site intro line and a per-item description for the llms.
txt file. Used by the Pro’s AI summaries; additive and invisible on a standalone
Free install, where the generated files are unchanged.
* Fixed: raised the contrast of the hero gradient on the dashboard so its text
meets the AA readability standard.
#### Earlier versions
* Only recent releases are listed here. WordPress.org trims changelogs past 5,000
characters, so older entries have been dropped from this file.
## Meta
* Version **1.28.0**
* Last updated **17 hours ago**
* Active installations **Fewer than 10**
* WordPress version ** 6.0 or higher **
* Tested up to **7.0.4**
* PHP version ** 8.0 or higher **
* Tags
* [AI](https://wordpress.org/plugins/tags/ai/)[geo](https://wordpress.org/plugins/tags/geo/)
[llms.txt](https://wordpress.org/plugins/tags/llms-txt/)[schema](https://wordpress.org/plugins/tags/schema/)
[structured data](https://wordpress.org/plugins/tags/structured-data/)
* [Advanced View](https://wordpress.org/plugins/octoplug-geo-suite/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/octoplug-geo-suite/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/octoplug-geo-suite/reviews/)
## Contributors
* [ Octoplug ](https://profiles.wordpress.org/octoplug/)
## Support
Got something to say? Need help?
[View support forum](https://wordpress.org/support/plugin/octoplug-geo-suite/)