Add a page
Creates a page on the draft. slug becomes its URL path segment and must be unique on the site; it is lowercased and stripped of surrounding slashes.
Adding a page does not link to it - update the header’s navItems and the footer’s links afterwards, or visitors will never find it.
Authorizations
Organization-scoped bearer credential: a customer API key (1club_sk_live_...) or an MCP OAuth access token.
Query Parameters
Body
Lowercase letters, numbers and hyphens, e.g. "personal-training"
Makes this the homepage, clearing the flag on whichever page held it
Initial sections. See GET /section-types for the types and their config.
SEO title. Falls back to the page title.
Falls back to seoSettings.siteDescription.
Absolute URL. Get one from GET /media rather than composing it.
Ask search engines not to index this page, and leave it out of sitemap.xml. For thank-you pages and campaign landing variants. The page stays publicly reachable - this is not a privacy control.
Per-locale metaTitle/metaDescription, keyed by locale: { "bg": { "metaTitle": "…" } }. Replaces the whole map. ogImage is not localizable - one social card serves every locale.
An override only reaches a visitor for a locale the organization actually serves: check supportedLocales on GET /website and add the locale there first, or the translation has no URL to be served at.
Response
The created page
A page on the website draft.
URL path segment. The homepage is served at "/" regardless of its slug.
Present when fetching a single page; omitted from list responses.
True when the page asks search engines not to index it and is left out of sitemap.xml.
Per-locale metaTitle/metaDescription overrides, keyed by locale: { "bg": { "metaTitle": "…" } }. Present when fetching a single page.
What the published page will actually put in its <head>, after every fallback has been applied - the authored fields alone do not answer "is my SEO right?". Present when fetching a single page. Read-only.
The page's public URL once published.