GEO Readiness
Deprecated: replaced by Content Governance. MODULE is now part of Content Governance, which brings it together with the other content checks in one drawer, switched on per site. MODULE receives no further releases. To move, uninstall MODULE, then install Content Governance and enable it on your sites; the upgrade notes say what carries over.
Screenshots
How to install
1. Install the prerequisites - GEO Readiness declares jcontent, robots and llms as module
dependencies. jcontent hosts the interface; robots and llms own the node types the site-files
editors write to. Jahia holds the module in "installed" rather than starting it until all three
are there, so install robots and llms from the Store first if your platform does not have them.
2. Install the module - from the Jahia Store directly, or download geo-readiness-x.y.z.jar from the
GitHub releases and upload it in Administration > Server > Modules and Extensions > Modules.
3. Enable it on your site(s) - in Administration > Server > Modules, select GEO Readiness and enable
it on each site to check (or from the site's own module management panel). Neither entry point
appears on sites where the module is not enabled.
4. Use it - open any page in jContent and use the GEO readiness action for the per-page drawer. For
the whole site, go to Additional > SEO > GEO readiness, then either run a scan from the Site
score panel or set a schedule there.
Requirements: Jahia 8.2 or later, plus the jcontent, robots and llms modules. No configuration is
needed to start. The dashboard requires the publish permission on the site; the page drawer needs
only read access to the page in the editing workspace. No external service is called unless you
explicitly configure an AI provider for the optional written report.
FAQ
The module is installed but never starts.
It waits for its dependencies. jcontent, robots and llms must all be started first - Jahia holds
the module back rather than starting it and failing at the first write. Install robots and llms
from the Store, then GEO Readiness starts on its own.
I installed the module but I don't see the GEO readiness action or the dashboard.
Both entry points only appear on sites where the module is enabled (Administration > Modules >
enable on site). The dashboard additionally requires the publish permission on that site, and the
endpoints behind it check the same permission rather than trusting the screen to hide itself - an
editor without it gets no dashboard and no robots.txt or llms.txt editor.
The report says a page is blocked, but my robots.txt allows it. Is that a bug?
No, that is the finding. Something between the crawler and Jahia is refusing the request, most
often a firewall or CDN rule that nobody remembers adding. The module also deliberately fetches a
page even when robots.txt disallows it, because knowing that a disallowed page is nonetheless
reachable is equally a finding.
It is reporting pages and a robots.txt that are not mine.
Set PUBLIC_BASE_URL. The address a check fetches comes from that setting, or from the site's own
server name when it is blank. A site that declares no server name, or names localhost, falls back
to http://localhost:8080 - on a box serving one site that is usually right, but on a box serving
several it is the default site, so the check reports another site's pages as if they were yours,
quietly, because the fetch succeeds. On a multi-site server, and on most Docker installs where the
server name is not resolvable from inside the container, this setting is required rather than
optional. It lives in digital-factory-data/karaf/etc/org.jahia.se.modules.georeadiness.cfg and
applies immediately, with no redeploy.
Does any data leave my platform?
Only the module's own fetches of your site. There is no telemetry and no external vendor. The one
exception is the optional written report: if an administrator configures a provider, a digest of
the measurements - scores, failing check ids, page paths and titles, counts - is sent to it. Page
bodies are never sent, and the API key never reaches the browser. Leave AI_PROVIDER blank and the
tab does not exist.
Why not just look at the page in the editor?
Because the editor's browser is authenticated, runs JavaScript and is never challenged by the
firewall, and a crawler is none of those. A page whose content only appears after JavaScript runs
looks perfect in the editor and arrives empty at a crawler. Every check here is answered
server-side, on the initial HTML, with no cookies and no session.
Why is "disallowed in robots.txt" not counted as a failure?
Because refusing a crawler is a legitimate decision, and a tool that scores it as a defect is
telling you to reverse a choice you made on purpose. What is counted is a disagreement between the
policy and the server, because then one of the two is wrong and somebody owns the fix.
Will it change my robots.txt or llms.txt?
Only when you ask, and never unseen. Both editors show a highlighted line diff against what is
stored and need a second confirming click, and what gets written is exactly the text on screen, so
hand edits made before applying survive. The robots.txt merge is line-based rather than a full
rewrite: it does not reorder, deduplicate or tidy, so a hand-written file comes back recognisable.
Everything else the module does is read-only - structured data is shown as a snippet for someone to
place, never injected into a page.
How do I check the whole site regularly?
The Site score panel holds the schedule: a cron expression built from dropdowns, an optional scope
and an enable toggle. A running scan appears in the administration job list. A scan is capped at
2000 pages per run and is synchronous when started from the button, so a large site should use the
schedule rather than the button.
My site is multilingual.
A scan covers one language per run, so set one schedule per language. Coverage and score are then
shown per language side by side, and a language nobody has scanned reports as not measured, never
as zero. The link graph and the freshness picture also judge only the language that was scanned.
Do I need an AI provider?
No. Everything except the Report tab is measured, and works with no provider and no key. The report
is the one place a model is asked for judgement instead of measurement, and it is off until an
administrator sets AI_PROVIDER, AI_MODEL and AI_API_KEY.
Does the score certify that my site is AI-ready?
No. It is a count of eighteen observed checks, each showing the fact behind its verdict, so you can
disagree with a specific line. It measures what a crawler receives from your server - not whether
any assistant chooses to cite you.
I am upgrading from 1.2.0 or earlier. Will I lose my settings?
No. The groupId moved to org.jahia.community in 1.3.1, but the Java package, the OSGi configuration
PID and the bundle name are unchanged, so an existing install upgrades in place and keeps its
configuration file.
Why is there no llms-full.txt?
The community llms module declares one property and one route, so the full variant cannot exist on
this stack. The report calls the file absent, which is the closest it can say.
MIT License
Copyright (c) 2026 Jahia Solutions Group SA
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
Dependencies
Depended on by
Nothing depends on this module.