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 profile

Start by implementing the site-level schema:

• 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.

3. Deploy page-level profiles

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.

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.