seo-aeo-aieo-governance-pack is an SSOT Registry pack for search visibility, answer visibility, AI citation readiness, web metadata quality, accessibility, and performance governance.
It gives product, platform, content, and compliance teams a shared set of Architecture Decision Records (ADRs) and Specifications (SPECs) that can be applied across many repositories. Centralizing these requirements turns discoverability work into reusable governance: one reviewed standard can be synchronized into project registries, linked to features and tests, and reused during release review instead of being rewritten from scratch in every product.
What Is An SSOT Registry Pack?
An SSOT Registry pack is an installable package of governed ADRs and SPECs for ssot-registry. The pack supplies reusable decision and requirement documents. ssot-registry applies those documents to a project registry so teams can trace product requirements from decision, to specification, to implementation, to tests and release evidence.
This makes governance portable. A project can adopt the pack, synchronize the documents, list the active requirements, and connect local features or tests to the shared IDs.
Why This Pack Exists
Search, answer, and AI discovery requirements now span many surfaces: HTML metadata, structured data, robots policy, sitemaps, crawler controls, accessibility baselines, social graph previews, and performance signals. Teams need one durable source for these requirements so product changes, content operations, and technical implementation stay aligned.
This pack helps teams:
- apply reviewed SEO, AEO, and AiEO requirements quickly across projects
- keep search metadata, answer extraction, and AI citation requirements consistent
- give engineering and content teams the same IDs for planning, implementation, and review
- connect accessibility and performance quality to discoverability governance
- make release reviews easier by tracing project work back to shared ADRs and SPECs
Domain Focus
The pack focuses on product domains where discoverability, answer quality, and machine-readable metadata directly affect user acquisition, trust, and citation quality:
- SEO and organic search governance
- AEO answer surface governance
- AiEO citation and provenance governance
- robots and crawler control policy
- sitemap and discovery artifact policy
- HTML head metadata and canonical URL policy
- structured data vocabulary and encoding quality
- social preview metadata for Open Graph and X / Twitter Cards
- accessibility baseline governance through WCAG 2.1 AA
- web performance quality using Core Web Vitals and supporting metrics
- AI crawler controls and experimental
llms.txthandling
Included ADRs
adr:0800SEO, AEO, and AiEO documents ship as an installable extension packadr:0801crawl control is distinct from indexing controladr:0802discovery artifacts are separate from metadata artifactsadr:0803canonical HTML metadata remains the source page contractadr:0804structured data uses layered authorityadr:0805Google AI features do not justify AI-specific schema or AI-only filesadr:0806accessibility conformance is a governed discovery-quality prerequisiteadr:0807social graph metadata is separate from search structured dataadr:0808AI crawler controls must distinguish search, training, and user-triggered fetchadr:0809llms.txtis experimental and must not outrank canonical surfacesadr:0810performance metrics use standards-backed authority where availableadr:0811derived tooling metrics remain separate from web-platform normative metrics
Included SPECs
spc:0800SEO governance surfacespc:0801AEO answer surface contractspc:0802AiEO citation and provenance contractspc:0803robots exclusion protocol contractspc:0804sitemap and sitemap-index contractspc:0805HTML head metadata and canonical link contractspc:0806structured data vocabulary and encoding contractspc:0807Google Search eligibility and structured data quality contractspc:0808Google AI features eligibility contractspc:0809helpful, reliable, people-first content contractspc:0810WCAG 2.1 AA accessibility contractspc:0811Core Web Vitals performance contractspc:0812Open Graph contractspc:0813X / Twitter Cards contractspc:0814DCMI interoperable metadata contractspc:0815OpenAI crawler controls contractspc:0816llms.txtexperimental contractspc:0817First Contentful Paint contractspc:0818Largest Contentful Paint contractspc:0819Long Tasks responsiveness contractspc:0820Total Blocking Time operator contract
Install With uv
Install the pack into a project environment:
uv add seo-aeo-aieo-governance-pack
Install it alongside the SSOT Registry CLI:
uv add ssot-registry seo-aeo-aieo-governance-pack
Run without adding dependencies to a project:
uvx --from ssot-registry --with seo-aeo-aieo-governance-pack ssot --help
Install With The SSOT Registry Pack CLI
Pack-enabled SSOT Registry environments can install and synchronize packs through the pack command surface:
uvx --from ssot-registry ssot pack install seo-aeo-aieo-governance-pack
uvx --from ssot-registry ssot pack sync . seo-aeo-aieo-governance-pack
Use With The SSOT Registry CLI
After the pack is installed in the same environment as ssot-registry, synchronize ADRs and SPECs into a target repository:
uv run ssot adr sync .
uv run ssot spec sync .
Review the synchronized governance surface:
uv run ssot adr list .
uv run ssot spec list .
uv run ssot spec get . --id spc:0805
Use the IDs from this pack when linking project features, tests, claims, and release evidence in your local .ssot registry.
Programmatic Usage
from seo_aeo_aieo_governance_pack import load_document_manifest, read_packaged_document_text
adr_manifest = load_document_manifest("adr")
spec_manifest = load_document_manifest("spec")
print(adr_manifest[0]["id"])
print(spec_manifest[0]["id"])
text = read_packaged_document_text("spec", "SPEC-0801-aeo-answer-surface-contract.yaml")
print(text[:120])
Resources
- GitHub repository: groupsum/seo-aeo-aieo-governance-pack
- PyPI package: seo-aeo-aieo-governance-pack
- SSOT Registry: ssot-registry
Metadata
Release files for seo-aeo-aieo-governance-pack 0.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| seo_aeo_aieo_governance_pack-0.1.6.tar.gz | 32.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| seo_aeo_aieo_governance_pack-0.1.6-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 81.6 kB
Release files / seo_aeo_aieo_governance_pack-0.1.6.tar.gz
| Download URL | seo_aeo_aieo_governance_pack-0.1.6.tar.gz |
|---|---|
| Size | 32.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
4e2a2cab71061c5d3c359f2bbabad93ba2f07632425188cf62455248bb6b861b
|
|
BLAKE2b-256 checksum How to use checksums |
baa454adff4f5693c40cb65864c028c56ac8e18df2d22120bd9f81efd1d0020a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency logRelease files / seo_aeo_aieo_governance_pack-0.1.6-py3-none-any.whl
| Download URL | seo_aeo_aieo_governance_pack-0.1.6-py3-none-any.whl |
|---|---|
| Size | 49.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9c198d549ea30acb9fc2617980e2fbb30252517d9e24442c08b92701c6c60d21
|
|
BLAKE2b-256 checksum How to use checksums |
acef0379c03225a307a0845e47ccb2c986a0a984c7a0401609ea76b38f735d12
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 2, 2026.
Transparency log