Tags

What tags are for

Tags are optional, user-managed page metadata for organizing and grouping pages in the destination where StaticPagesApi deploys them.

AI clients, page blueprints, and tutorial builders do not create or assign tags. Add them manually only when they are useful to your own organization.

Use tags for destination groupings such as campaigns, product launches, help-center areas, collections, regions, or audiences.

Webhook and destination behavior

Page tags are sent with every page webhook so a receiving platform can apply the same organization to its imported page.

• StaticPagesApi sends comma-separated tag names in the X-Static-Pages-Api-Tags header.
• The WordPress receiver maps these values to WordPress post tags when WordPress page storage is enabled.
• Sending an empty tag header clears destination tags managed by a receiver that implements synchronization.
• Section and Row tag controls are not part of the application UI.

How tags affect rendering

Tags do not make a page render differently by themselves. They are page-level destination organization metadata.

• Page tags are searchable in StaticPagesApi and travel separately from the rendered HTML.
• Tags do not populate meta keywords or change page SEO metadata.
• Tags and categories use separate webhook headers and remain separate destination taxonomies.
• AI may use existing tags as read-only context, but it must not create or assign them.

Related concepts

Page tags organize deployed pages in the destination. Categories provide a separate page classification for filters and integrations. Page Shells attach inherited rendered structure and settings to pages.