page

• Identify a standalone page or page-equivalent resource.
• Associate a stable page identifier with a live URL.
• Distinguish page identity from site identity and section identity.
• Attach page-level metadata such as name, type, description, intent, interpretive frame, authorship, provenance, and revision context.

Page metadata provides resource-level semantic context without replacing site-level or section-level metadata.

• Provide stable identity through id.
• Provide web addressability through url.
• Remain distinct from site, which identifies the website-level semantic entity.
• Remain distinct from section, which identifies a subordinate content unit unless explicitly treated as page-equivalent.
• Support contextual metadata such as name, type, description, intent, interpretiveFrame, author, provenance, and revision where useful

• id — required; stable identifier for the page within the site or implementation.
• url — required; live URL for the page or page-equivalent resource.

Recommended fields include:

• name — human-readable page name or structured naming block.
• type — optional semantic classifier or list of classifiers describing what kind of page or page-equivalent resource is represented.
• description — short or structured description of the page.
• intent — purpose, audience, and scope metadata for the page.
• interpretiveFrame — optional interpretive guidance for agents evaluating the page.
• canonical — canonical URL declaration for the page. Object form is preferred for MSP-1 v1.0.2 declarations.
• parent — higher-level structural context when applicable.
• section — section context or section declaration when applicable.
• author, provenance, and revision — optional page-level lifecycle and origin context.

• AI agents should treat the page object as a single addressable semantic unit within the site.
• Agents should use id and url as the minimal page identity fields.
• Agents should not treat a page as equivalent to the site as a whole.
• Agents should not treat a section as a page unless the section is explicitly declared as a page-equivalent resource.

Page metadata supports interpretation of an individual resource without requiring agents to infer page identity only from URL structure or surrounding site context.

• site — identifies the website-level semantic entity containing the page.
• id — provides stable page identity.
• url — identifies the live URL for the page.
• canonical — identifies the preferred authoritative URL representation when applicable.
• name — provides the preferred human-readable page label.
• type — classifies what kind of page or page-equivalent resource is being described.
• description — summarizes what the page is about.
• intent — explains why the page exists or how it should be used.
• interpretiveFrame — guides contextual interpretation of the page.
• section — describes a subordinate structural unit within the page unless explicitly declared otherwise.
• parent — identifies a higher-level resource or structural context.
• author, provenance, and revision — provide page-level origin, authorship, and change context where useful.

Do not confuse page with site or section. site identifies the website-level semantic entity; page identifies an individual addressable resource within the site; section identifies a subordinate content unit within a page unless explicitly declared otherwise.

{
  "page": {
    "id": "lighting-guide",
    "url": "https://photographyselect.com/guides/lighting/"
  }
}

Page declaration with descriptive metadata:

{
  "page": {
    "id": "lighting-guide",
    "url": "https://photographyselect.com/guides/lighting/",
    "name": "Lighting Guide",
    "type": "guide",
    "description": "A foundational guide explaining natural and artificial light for portrait photography.",
    "intent": "Teach photographers how to use lighting effectively in various scenarios."
  }
}

Page declaration with canonical object:

{
  "page": {
    "id": "canonical-spec",
    "url": "https://msp-1.org/spec/canonical/",
    "canonical": {
      "url": "https://msp-1.org/spec/canonical/"
    }
  }
}

• It expresses page as an object.
• It provides required id and url fields.
• It uses name, description, intent, and related fields consistently when present.
• It does not confuse page-level metadata with site-level or section-level metadata.