CMS Templates
Add page-level MSP-1 JSON-LD through reusable templates, theme files, or structured content fields.
MSP-1 - AI-friendly semantics for trusted information.
Enterprise & Development Network
Enterprise Solutions
Platform Integrations
MSP-1 can be integrated into existing CMS platforms, publishing systems, ecommerce frameworks, documentation tools, and enterprise content pipelines as a lightweight semantic declaration layer.
Integration without replatforming
MSP-1 is designed to work alongside existing web infrastructure. It can usually be added through templates, metadata fields, build steps, plugins, modules, or deployment workflows without changing the visible user experience.
The objective is to make content easier for AI systems to interpret while preserving the systems organizations already use to create, review, and publish that content.
Common integration points
Build Pipelines
Generate and validate MSP-1 declarations during static builds, CI/CD workflows, or publishing steps.
Well-Known Files
Publish site-level declarations at /.well-known/msp.json to provide deterministic discovery.
Platform categories
MSP-1 integration patterns can vary by platform, but the underlying model remains consistent: declare site identity, page intent, provenance, trust posture, and interpretive context in a structured machine-readable format.
- Enterprise CMS platforms
- Static site generators
- Ecommerce systems
- Documentation platforms
- Knowledge-base systems
- Custom publishing workflows
Governance-aware integration
Enterprise integrations should include review points for fields that affect interpretation, authority, provenance, and trust. MSP-1 generation can be automated, but deployment should remain aligned with organizational review and approval workflows.
The best integrations make MSP-1 part of normal publishing operations rather than a separate, fragile process.
Progressive implementation
Platform integration does not need to begin with full automation. Many organizations can start with a manually reviewed pilot, then gradually introduce reusable templates, validation checks, and generation workflows as patterns become stable.
Next steps
Logistics
Review a practical rollout path for enterprise MSP-1 implementation.
Tooling
Explore validation, generation, and workflow tooling concepts.
Enterprise FAQ
Read answers for organizations evaluating MSP-1 at scale.