Skip to main content
Jahia Store
EN

Content Governance

community
Download 1.11.0

Information

Module ID
content-governance
Group ID
org.jahia.community
Status
community
Category
SEO & GEO, Content Features, Pre-built templates and components, Admin Features
Author
Stephane Monier
Developer website
http://www.jahia.com
Requires Jahia
8.2.0.0
Released
2026-11-14
Source
scm:git:git@github.com:Jahia/content-governance.git
Tags
  • content governance
  • accessibility
  • wcag
  • seo
  • geo
  • ai crawlers
  • llms.txt
  • botrank
  • compliance
  • glossary
  • readability
  • eco-design
  • ai assist
  • jcontent
  • page builder

Check a page before you publish it, from one drawer in jContent and Page Builder: page quality (accessibility, SEO, speed, readability, eco-design, links), readiness for AI assistants and the terms your glossaries forbid, with AI suggestions on demand and site dashboards. Each site chooses what it uses. In English and French.

Content Governance gives authors one place to check a page before they publish it. A Content governance button in the header of jContent and Page Builder opens a drawer with three sections, each with a red count of the issues to review and a tooltip saying what it is for.

Page quality

  • Accessibility: automated WCAG A, AA and AAA rules (axe-core), issues by severity highlighted in the page, what to verify by hand.
  • SEO: title, meta description, indexing, canonical address, social sharing card, structured data, link texts.
  • Web Vitals, Readability (English and French formulas), Ecodesign (French RGESN referential), Links (broken internal links, unsafe new windows) and Jahia (unpublished content, missing translations, raw labels).
  • Runs in the author's browser, on the page being edited, unpublished changes included.

GEO readiness

  • Whether AI assistants and their crawlers can read and cite the published page: a score made of eighteen explained checks, the access of each AI crawler, what robots.txt and llms.txt say, and the structured data.
  • AI citations: how often AI answers cite the page and for which questions, from BotRank, once the site is connected.
  • The site dashboard, under Additional > SEO: site score, invisible content, sitemap against reality, internal links, addresses, freshness, languages, structured data, robots.txt and llms.txt editors, scheduled scans and a written report by AI.

Compliance

  • Legal or Brand keep glossaries of non-authorised terms, one per language, with the reason and the wording to use instead.
  • The section lists every use on the page and in the content it shows; the site report under Additional > Compliance covers every page and content item, with Export CSV and Export JSON.

AI on demand, one configuration

  • One model serves every AI feature: the page review, suggested titles, descriptions, headings and call-to-action labels, alt text for images (Anthropic and OpenAI read the pictures), plainer rewrites of long sentences, and the GEO written report.
  • Suggestions are written in the page's language, shown and copied, never written to the repository. Until a server administrator configures a provider, the AI features are greyed out and nothing leaves the server.

Each site chooses

  • Administration > Sites > (site) > Content governance: a switch per section and per tab, everything on by default. The server refuses what a site switched off.
  • Checks read with the author's own rights and change nothing; the only writes are the robots.txt and llms.txt editors (diff, then a confirming click) and the site settings.

Video

Screenshots

Dependencies

Depended on by

Nothing depends on this module.

Versions

1.11.0Download

1.11.0

  • Un panneau plus calme : un compteur n'est rouge que s'il contient un constat critique ou grave, gris sinon, et À corriger en premier est une simple ligne qui ne liste que ces constats.
  • Web Vitals affiche LCP, CLS et TTFB comme des valeurs indicatives de l'aperçu d'édition, sans bande de couleur ni constat, puisqu'elles ne peuvent pas correspondre au site en ligne ; ce qui alourdit la page garde ses constats.
  • Préparation GEO n'affiche plus « Cette page n'est pas publiée » pour une page publiée dans une langue de site avec une région, comme le chinois (Chine) ou le portugais (Brésil) ; les analyses de site, les citations et le glossaire d'exemple lisent aussi ces langues.
Requires Jahia 8.2.0.0Released 2026-11-14
1.10.0Download

New Features

  • Page quality's Readability tab lists the page's headings as an outline: every heading indented by its level, the level a heading skips, a heading without text, and a button that shows it on the page. Pages under 30 words show their headings too.

Bug Fixes

  • yarn lint checks the front-end code against the rules of the SonarQube gate before a push, and the pull request CI runs it. The existing code was brought in line with them, with no change for editors.
Requires Jahia 8.2.0.0Released 2026-11-13

1.9.1

  • The drawer and the dashboards no longer stop with "Invalid language tag" on a site language with a region, such as Chinese (China) or Portuguese (Brazil).

1.9.0

  • The exported GEO readiness report says that a model wrote it, in a field a program can read: Export as JSON adds a digitalSourceType field and Export as Markdown opens with front matter holding the same field, the provider, the model and the date (EU AI Act, Article 50).
Requires Jahia 8.2.0.0Released 2026-11-12

1.8.1

  • The drawer moves with the page under edit when a bar above it, such as Page Insights, opens or closes.
Requires Jahia 8.2.0.0Released 2026-11-03
  • The drawer docks beside the page under edit, under jContent's header, instead of covering the screen: the page stays usable while it is open, and its left edge drags to make it wider. In Page Builder, Page quality starts with its preview hidden and Highlight on the page outlines the element in the page under edit (in the preview when the page under edit does not show it).
Requires Jahia 8.2.0.0Released 2026-11-03

New Features

  • jContent's Preview of a non-authorised term now shows the term, its match, reason and suggested wording.
Requires Jahia 8.2.0.0Released 2026-11-02

New Features

  • The Page quality dashboard shows what each audit found: expand a page to read the findings of its latest audit, the most serious first, each with what to do about it, its severity, its tab and, for accessibility, how many elements fail the rule. They are read when the row is opened, from the audit stored when an editor ran it, so nothing is audited again and the list stays fast on a site with many pages.
Requires Jahia 8.2.0.0Released 2026-11-01

New Features

  • The drawer starts with Fix first: the most serious finding of the page on one line, with how many more there are, and on Show the five most serious whatever their section (accessibility violations, the recommendations of every Page quality tab, GEO readiness tabs with something to review, forbidden terms), each with Open to go to the section and tab that explains it. GEO readiness and Compliance join the list once they have been opened.
  • Content Governance speaks German and Spanish: the drawer, the dashboards, the Publish menu line and Site Settings follow the editor's interface language, as do the content type labels and the example glossary created when a site enables the module. jContent itself has no Spanish interface, so a Spanish editor sees jContent in English and Content Governance in Spanish. The German and Spanish texts were machine-drafted and await a native review.
  • Page quality audits are shared by the editors of a site. A complete audit is stored for its page and language, so anyone opening the drawer on that page sees the newest audit at once, with who ran it and when, instead of measuring the page again; the last 10 are kept and the drawer shows how the number of issues moved ("Issues over the last 10 audits: 12 → 9 → 7"). A new site dashboard, Additional > Page quality, lists the latest audit of every audited page in the current language, most issues first, with its issues by tab and its trend, Export CSV and Export JSON; anyone who may open jContent on the site sees it. Audits with a check that did not finish and AI answers are not shared.
  • jContent's Publish menu now starts with a line from Content Governance when the page in view has something to review: "Review before publishing - audit issues: 12, serious accessibility: 2, forbidden terms: 1", from the page's latest audit and a compliance scan, or "Not audited yet" for a page nobody has audited. It opens the drawer on the section to review and never blocks publishing; nothing is added to a page without issues. Shared audits now also count their critical and serious accessibility violations.
  • Swedish, Danish and Norwegian pages get a readability score: LIX (Björnsson), words per sentence plus the share of words longer than six letters, where a higher score reads harder. Bands follow Björnsson's table, the advice aims for a LIX of 40 or less, and the score card is coloured by band. Finnish stays without a score, LIX being untested there.

Bug Fixes

  • Page quality no longer stays on "Loading" or "Analyzing" when part of a page never answers. A page whose images, fonts or scripts keep loading is audited after 20 seconds as it stands, and a check that takes too long (Accessibility 60 seconds, Links 45, Jahia 30, Web Vitals 15) or fails is stopped: its tab says why with a Re-run button, and the other tabs show their results. jContent also starts faster: it now loads about 105 kB of the module instead of 622 kB, with only the editor's language; the drawer loads in the background once its button shows, and the dashboards and settings the first time they are opened.
  • The GEO readiness dashboard no longer risks having a request refused by Jahia's CSRF guard when it loads: requests sent at once to the same module address now wait for the first one's answer instead of all using the session's master token, which the guard accepts once per address. The Cypress suite now runs every night against Jahia 8.2.3.2 in GitHub Actions.
  • The help tooltip of a section or tab no longer stays open over the content after you click the tab: the selected tab shows none. Switching AI citations or the GEO readiness section off now pauses the site's daily BotRank sync instead of turning it off: it syncs again at its first run after the switch is back on, with nothing to save. A sync turned off that way by an earlier version is restarted by saving the BotRank settings once.
Requires Jahia 8.2.0.0Released 2026-11-01

New Features

  • Page quality scores readability with the formula made for the page language: Amstad for German, Fernández Huerta for Spanish, Franchina-Vacca for Italian, Douma for Dutch and Martins for Portuguese, next to Flesch for English and Kandel-Moles for French. Until now these languages got the English formula, which scored them lower than they read. A page in another language gets no score instead of a misleading one, and the tab says why; sentence length, paragraphs and headings are still checked. Japanese, Chinese, Thai and other languages written without spaces between words get no word count either: the tab counts characters and sentences. Syllables are counted with each language's vowels, so accented letters (ñ, ã, ä...) no longer split words. Audits cached by an earlier version are measured again.

Bug Fixes

  • Page quality runs axe-core 4.14 (4.14.0 was already bundled in 1.3.0; it is now the declared minimum). The Accessibility tab now also checks that the visible text of a link or button is part of its accessible name (label-content-name-mismatch, on by default since 4.14) and reports a few more cases in existing rules, while some false positives are gone (colour contrast, target-size on overlapping links to the same page, captions in tables). A page can therefore show a different count than before without its markup having changed. Audits run faster on large pages. The Cypress suite checks that the audit runs the declared axe-core version and that its findings, the new rule included, reach the Accessibility tab.
  • A Cypress suite (tests/, run against a running Jahia) covers the site settings, the compliance scan and its example glossary, the CSRF guard on the module's servlets and the drawer in jContent.
Requires Jahia 8.2.0.0Released 2026-11-01

Added

  • GEO readiness dashboard: Export CSV (one row per finding of the last site scan) and
    Export JSON (the whole stored scan) in the header, like the Compliance dashboard.
  • Enabling the module on a site that has no glossary creates Content Folders > Compliance
    glossaries, which only offers glossaries, with an example glossary in the site's default
    language and one example term. It is created once per site.

Changed

  • The module's servlets go through Jahia's CSRF guard, and the drawer, the dashboards and the
    settings send its token. They answer browser sessions only: calls with an API token are no
    longer accepted.
  • Light tooltips (white, rounded, dark grey text) on the drawer's sections and tabs.
  • Build and test tooling: webpack-cli 7, babel-loader 10, style-loader 4, clean-webpack-plugin 4,
    rimraf 6, JUnit 6, Mockito 5.24, frontend-maven-plugin 2.0.2.

Fixed

  • French labels of the content types (Compliance glossary, Non-authorised term) showed garbled
    accents in jContent.
  • GEO readiness dashboard: uses the full width of a wide window, stays within a narrow one (no
    sideways scroll, header buttons visible) and keeps its group tabs on one row; the BotRank
    settings tab uses the full width too.
  • Links to pages in jContent work when Jahia runs under a context path.

Full history: CHANGELOG.md.

Requires Jahia 8.2.0.0Released 2026-11-01

Changed

  • GEO readiness: llms.txt is written in the llms module's own Llms.txt screen (Additional >
    SEO), no longer generated here. The llms.txt tab shows the published file, read only, with an
    Edit in Llms.txt button, and says when the llms module is not enabled on the site.
  • The llms.txt check lists the links of the file to the site whose page moved or is no longer
    published. A page the file does not list is the author's choice and is no longer reported; the
    drawer says whether the page is listed.
  • The AI output budget (AI_MAX_TOKENS) defaults to 6000.

Fixed

  • The AI review and assists work with any chat model, OpenAI reasoning models included, and with
    models that wrap or skip the JSON.
  • On a server where several sites share a host name, the llms.txt check read another site's file.

Full history: CHANGELOG.md.

Requires Jahia 8.2.0.0Released 2026-10-30

1.1.0

  • After an upgrade from Content Compliance Scan, New content offers Compliance glossary and Non-authorised termagain, with their labels; existing glossaries are unchanged.
  • The Content governance entry of the site administration menu shows the module's icon.
Requires Jahia 8.2.0.0Released 2026-10-30

1.0.0

First version, replacing GEO Readiness, Page Quality Audit and Content Compliance Scan: one drawer with three sections, per-site switches for every section and tab, one AI configuration for every AI feature, tooltips on every section and tab, and the GEO and Compliance site dashboards. Full history, including the three modules it replaces: CHANGELOG.md.

Requires Jahia 8.2.0.0Released 2026-10-29