> This page is for Home.

> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://developers.webflow.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://developers.webflow.com/_mcp/server.

# `?translatable` now supported on Get Page Metadata

> The get page metadata endpoint now accepts a translatable parameter, matching the get page content, get component, and get CMS item endpoints.

**[Get page metadata](/data/reference/pages-and-components/pages/get-metadata)** now accepts `translatable`, alongside the endpoints that already supported it:

* **[Get page content](/data/reference/pages-and-components/pages/get-content)**
* **[Get component content](/data/reference/pages-and-components/components/get-content)** and **[get component properties](/data/reference/pages-and-components/components/get-properties)**
* **[List](/data/reference/cms/collection-items/staged-items/list-items)** and **[get](/data/reference/cms/collection-items/staged-items/get-item)** collection items, including their [live](/data/reference/cms/collection-items/live-items/list-items-live) counterparts

Pass the id of the secondary locale you're translating into to omit page-level fields (title, slug, SEO title/description, Open Graph title/description) excluded from translation for that locale — they're left out of the response entirely rather than returned as `null`. Behavior matches the other endpoints: the value must be a secondary locale id (`400` otherwise), and the request returns a `403` if translation exclusions aren't enabled for the site.