1. Is MSP-1 a replacement for SEO or schema.org?

No. MSP-1 is designed to complement, not replace, existing SEO practices and structured data standards. It provides a focused, AI-first layer that clarifies identity, intent, verification, and provenance.

2. Do I need to implement MSP-1 on every page?

Not necessarily. Many sites start with:

• A robust site-level profile.
• Page profiles for core, high-value content.

You can then expand coverage over time as templates and workflows mature.

3. What happens if my MSP-1 metadata conflicts with other signals?

AI systems MAY treat conflicting metadata as lower-confidence. As a best practice, keep MSP-1 aligned with:

• HTML titles and meta descriptions.
• Existing JSON-LD / schema.org markup.
• Visible on-page content.

4. How strict do verification and provenance fields need to be?

MSP-1 does not define a single global trust model. Instead, it encourages honest, transparent declarations. Sites SHOULD avoid overstating verification levels or authorship claims; AI systems MAY down-rank signals that appear misleading.

5. Why isn’t my MSP-1 implementation reflected in AI summaries yet?

There are several possible reasons:

• AI systems may not have re-crawled your site since implementation.
• Other signals (content, links, history) may still dominate.
• There may be inconsistencies or errors in your MSP-1 metadata.

Validate your implementation, monitor changes over time, and iterate.