SEO and metadata

Updated
View as text
Open in Confluence
Open in ChatGPT Open in Claude

A published site is meant to be found. It builds sitemaps, sets per-page metadata, and ships files that let AI tools read it properly.

Most of it is automatic. The parts you control are per page.

#Per page

Sites panel showing the Pages list for a site, with a side panel for the page Progress bar macro containing Title, Description, Slug and Upload cover image fields.
Each page carries its own title, description, slug and cover image, edited beside the page list without opening the page.
The Pages list with one page selected and a side panel offering SEO title, description, slug and cover image fields.
Title, description, slug and cover image are set page by page from the Pages list, and stay empty until you override them.

Set with

Controls

The Site metadata macro on the page

SEO title, description and slug for that page

The Page metadata side panel

The same values, without adding a macro to the body

The site description

The fallback used where a page sets nothing

#Built automatically

  • Sitemaps, rewritten on promote to the live address or your custom domain.

  • A permissive robots.txt on production; a disallow-all one on staging.

  • A Markdown twin of every page, and per-page JSON.

  • llms.txt, llms-full.txt and mcp.json, so AI tools can read the site.

  • A social sharing image per page, falling back to the site default cover image.

#A few things worth knowing

  • Changing SEO settings is a page change, so it needs an Update and Promote to reach the live site.

  • Staging is never indexed, by design.

  • The site description doubles as the default social preview text.

Findable by people, readable by machines.