Add Schema.org Metatag module (drupal/schema_metatag) to GovCMS
schema_metatag extends Metatag (already in GovCMS) with Schema.org structured data in JSON-LD format — the format Google recommends. The National Archives of Australia's post-AGLS Metadata for the web guidance names Schema.org as the successor metadata standard for government discoverability.
Drupal.org project: https://www.drupal.org/project/schema_metatag
Composer: drupal/schema_metatag
What value does this module/package add to GovCMS?
GovCMS SaaS customers currently have no supported path to structured data — they can't add custom modules. NAA's guidance names Schema.org as the AGLS successor (AGLS decommissioned 31 Dec 2023). Google restricts FAQ rich results to authoritative government and health websites, meaning .gov.au sites are eligible by policy but can't leverage it without structured data output.
Is the module Drupal 11 compatible?
Yes. 3.0.4 (Feb 2026), supports ^9 || ^10 || ^11. Requires Metatag 2.x, already in GovCMS.
Please provide a brief outline of what this module does.
Adds <script type="application/ld+json"> blocks to the page <head> using Metatag's plugin architecture. Site builders enable sub-modules for the Schema.org types they need (Article, Event, FAQPage, WebPage, Organization, Service, etc.) and map entity fields to schema properties via Metatag's token system and existing admin UI. Values resolve through Metatag's override hierarchy — global → entity type → bundle → per-entity — so editors manage structured data in the same interface they already use for meta tags.
Who does this module benefit?
How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
SaaS customers can't add custom modules, so there's no alternative path. Hardcoding JSON-LD in Twig templates is fragile, offers no editor UI, and has to be duplicated per site.
If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
No. Output is a non-executable data block in <head> via hook_page_attachments, not themed markup. It needs Metatag's token resolution and override hierarchy, which Twig can't access.
What is the maintenance and support status of the module. Describe the issue queue activity.
Active. 3.0.4 shipped Feb 2026; dev branch updated Apr 2026. ~181 open / 635 total issues, 8–9 RTBC. Covered under Drupal Security Team advisory policy. Maintainer team is seeking co-maintainers but release cadence remains steady (monthly-to-quarterly).
What permissions are needed to utilise the module (and are any new permissions provided by the module)?
None new. Reuses Metatag's existing administer meta tags and edit meta tags.
Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
No schema changes. Configuration stored as standard Drupal config entities. Per-entity overrides use Metatag's existing serialised field. Zero update-hook risk.
Is the module designed to capture anonymous user data?
No. Strictly one-way output. No cookies, no tracking, no outbound calls.
Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
Fully cacheable. Standard render pipeline with correct cache tags inherited from the rendered entity. Compatible with Internal Page Cache, Dynamic Page Cache, and Akamai/Purge.
What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
~60,000 active installs (~18% of all Metatag installs). Maintained by Karen Stevenson (Lullabot, project creator), Damien McKenna (Mediacurrent, primary Metatag maintainer since 2012), and Jim Birch (Kanopi). All maintainers have multi-year, security-advisory-covered track records. Parent Metatag is on 335,443 sites and co-maintained by Dave Reid (Drupal core committer).
Additional information
Depends solely on Metatag, already in GovCMS. Zero new permissions, zero schema changes, zero anonymous data capture, fully cacheable.
GOV.UK publishes GovernmentOrganization, FAQPage, and BreadcrumbList JSON-LD fleet-wide — this brings GovCMS to parity. The Digital Access Standard (mandatory from 1 Jan 2025) requires improved service discoverability, and the DTA's Content Strategy Guide (Digital Profession) already recommends Schema.org using the ATO as its case study. Schema.org includes types purpose-built for government content: GovernmentService, GovernmentOrganization, and GovernmentOffice.
Add Schema.org Metatag module (drupal/schema_metatag) to GovCMS
schema_metatagextends Metatag (already in GovCMS) with Schema.org structured data in JSON-LD format — the format Google recommends. The National Archives of Australia's post-AGLS Metadata for the web guidance names Schema.org as the successor metadata standard for government discoverability.Drupal.org project: https://www.drupal.org/project/schema_metatag
Composer:
drupal/schema_metatagWhat value does this module/package add to GovCMS?
GovCMS SaaS customers currently have no supported path to structured data — they can't add custom modules. NAA's guidance names Schema.org as the AGLS successor (AGLS decommissioned 31 Dec 2023). Google restricts FAQ rich results to authoritative government and health websites, meaning .gov.au sites are eligible by policy but can't leverage it without structured data output.
Is the module Drupal 11 compatible?
Yes. 3.0.4 (Feb 2026), supports ^9 || ^10 || ^11. Requires Metatag 2.x, already in GovCMS.
Please provide a brief outline of what this module does.
Adds
<script type="application/ld+json">blocks to the page<head>using Metatag's plugin architecture. Site builders enable sub-modules for the Schema.org types they need (Article, Event, FAQPage, WebPage, Organization, Service, etc.) and map entity fields to schema properties via Metatag's token system and existing admin UI. Values resolve through Metatag's override hierarchy — global → entity type → bundle → per-entity — so editors manage structured data in the same interface they already use for meta tags.Who does this module benefit?
hook_page_attachmentsimplementations with a security-covered module.How could you provide/replicate the functionality of this module using alternative methods, eg in your theme?
SaaS customers can't add custom modules, so there's no alternative path. Hardcoding JSON-LD in Twig templates is fragile, offers no editor UI, and has to be duplicated per site.
If this module styles or alters HTML or JavaScript output, can the functionality be provided via the theme? What alternatives have you considered.
No. Output is a non-executable data block in
<head>viahook_page_attachments, not themed markup. It needs Metatag's token resolution and override hierarchy, which Twig can't access.What is the maintenance and support status of the module. Describe the issue queue activity.
Active. 3.0.4 shipped Feb 2026; dev branch updated Apr 2026. ~181 open / 635 total issues, 8–9 RTBC. Covered under Drupal Security Team advisory policy. Maintainer team is seeking co-maintainers but release cadence remains steady (monthly-to-quarterly).
What permissions are needed to utilise the module (and are any new permissions provided by the module)?
None new. Reuses Metatag's existing
administer meta tagsandedit meta tags.Does the module modify the database structure and/or store additional metadata on nodes or other entities? If so, why? What are the risks for future updates?
No schema changes. Configuration stored as standard Drupal config entities. Per-entity overrides use Metatag's existing serialised field. Zero update-hook risk.
Is the module designed to capture anonymous user data?
No. Strictly one-way output. No cookies, no tracking, no outbound calls.
Is the output of the module typically fully cacheable? Would the inclusion of this module potentially render pages uncacheable.
Fully cacheable. Standard render pipeline with correct cache tags inherited from the rendered entity. Compatible with Internal Page Cache, Dynamic Page Cache, and Akamai/Purge.
What is your assessment of the quality of this module, the contribution history of the module's maintainers, and the uptake of the module within the Drupal community?
~60,000 active installs (~18% of all Metatag installs). Maintained by Karen Stevenson (Lullabot, project creator), Damien McKenna (Mediacurrent, primary Metatag maintainer since 2012), and Jim Birch (Kanopi). All maintainers have multi-year, security-advisory-covered track records. Parent Metatag is on 335,443 sites and co-maintained by Dave Reid (Drupal core committer).
Additional information
Depends solely on Metatag, already in GovCMS. Zero new permissions, zero schema changes, zero anonymous data capture, fully cacheable.
GOV.UK publishes GovernmentOrganization, FAQPage, and BreadcrumbList JSON-LD fleet-wide — this brings GovCMS to parity. The Digital Access Standard (mandatory from 1 Jan 2025) requires improved service discoverability, and the DTA's Content Strategy Guide (Digital Profession) already recommends Schema.org using the ATO as its case study. Schema.org includes types purpose-built for government content:
GovernmentService,GovernmentOrganization, andGovernmentOffice.