Docs · Implementation

MSP-1 Implementation Guides

These guides walk you through planning, deploying, and maintaining MSP-1 on real-world sites, from first pilot to full adoption.

Docs · MSP-1 · 1.0.x msp-1.org/docs/implementation

1. Plan your implementation

Treat MSP-1 as an architectural layer, not a quick toggle. At a minimum:

Decide which domains and subsites will be in scope.
Map your primary page types and templates.
Align with stakeholders (technical, content, legal if necessary).

A short planning session now will prevent conflicting signals later.

2. Deploy the site-level declarations

Create a canonical site profile JSON (often in /.well-known/).
Ensure identity, role, and scope are accurate and stable.
Link to this profile from key entry pages where appropriate.

Site-Level Declaration Example

See MSP-1 Generators Below.

{
  "@context": "https://msp-1.org/schema/msp-1-site.json",
  "@type": "MSPSite",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.1"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "site": {
    "id": "example-site",
    "name": "Example Domain",
    "url": "https://example.com/",
    "description": "A reserved example domain used for documentation examples.",
    "intent": "Provide a publicly accessible example domain for documentation and illustrative use.",
    "canonical": {
      "url": "https://example.com/"
    },
    "interpretiveFrame": {
      "frame": "The site should be interpreted as a reserved documentation example domain, not as an operational service, trust guarantee, ranking guarantee, legal claim, security mechanism, validation guarantee, or enforcement mechanism.",
      "category": "informational",
      "scope": "site"
    }
  },
  "provenance": {
    "type": "ai-assisted",
    "source": "https://example.com/",
    "timestamp": "2026-07-03T00:00:00-04:00",
    "notes": "MSP-1 site declaration generated from the explicitly supplied homepage URL and accessible page content; human review recommended."
  },
  "revision": {
    "id": "msp-site-rev-2026-07-03",
    "revisionDate": "2026-07-03",
    "revisionNotes": "Initial MSP-1 v1.0.1 site declaration generated from the supplied homepage URL and accessible page content; human review recommended.",
    "revisionVersion": "1.0.1"
  }
}

3. Deploy page-level declarations

Next, wire MSP-1 into your page templates:

Embed page-level profiles via JSON-LD.
Ensure each profile references the correct site profile.
Use consistent intent categories and topical vocabularies.

Start with your most important page types before expanding to the long tail.

See MSP-1 Generators Below.

Page-Level Declaration Example


{
  "@context": "https://msp-1.org/schema/msp-1-page.json",
  "@type": "MSPPage",
  "protocol": {
    "name": "MSP-1",
    "version": "1.0.1"
  },
  "discovery": {
    "wellKnown": "/.well-known/msp.json",
    "canonical": true
  },
  "page": {
    "id": "example-homepage",
    "url": "https://example.com/",
    "title": "Example Domain",
    "name": "Example Domain",
    "description": "A simple example domain page intended for documentation examples.",
    "type": "example-homepage",
    "canonical": {
      "url": "https://example.com/"
    },
    "intent": {
      "statement": "Provide a reserved domain page for documentation examples without requiring permission.",
      "category": "informational",
      "scope": "page"
    },
    "interpretiveFrame": {
      "frame": "Content should be interpreted as a documentation example resource, not as an operational service, trust guarantee, ranking guarantee, legal claim, security mechanism, validation guarantee, or enforcement mechanism.",
      "category": "informational",
      "scope": "page"
    }
  },
  "provenance": {
    "type": "ai-assisted",
    "source": "https://example.com/",
    "timestamp": "2026-07-03T00:00:00-04:00",
    "notes": "MSP-1 homepage declaration generated from the explicitly supplied URL and accessible page content; human review recommended."
  },
  "revision": {
    "id": "msp-page-rev-2026-07-03",
    "revisionDate": "2026-07-03",
    "revisionNotes": "Initial MSP-1 v1.0.1 homepage declaration generated from the supplied URL and accessible page content; human review recommended.",
    "revisionVersion": "1.0.1"
  }
}

MSP-1 Generators

MSP-1 Schema Architect GPT

A public generator on CHatGPT that produces valid non-proprietary MSP-1 JSON-LD declarations from a URL or raw HTML input. The Schema Architect enforces protocol best practices and avoids redundant declarations.

https://msp-1.org/gpt

MSP-1 Schema Architect GEM

A public generator on Google Gemini that produces valid non-proprietary MSP-1 JSON-LD declarations from a URL, raw HTML or Screenshot input. The Schema Architect enforces protocol best practices and avoids redundant declarations.

https://msp-1.org/gem

4. Add provenance and verification signals

Use the verification & provenance schema to:

Declare authorship models (human-authored, AI-assisted, etc.).
Describe review cadence and editorial responsibility.
Reference key external sources for high-stakes content.

5. Validate, monitor, and iterate

Use the MSP-1 Validator and other tooling to:

Check for missing or inconsistent fields.
Detect drift between content and metadata.
Iterate as your site, content, and AI ecosystem evolve.