Update Page

Update an existing internal, custom HTML, or external (SDK) page.

This existing write saves supported page content live; there is currently no separate public page publish or status operation. Read the page back with GET /api/v2/pages/:id to confirm the resource, then check its computed url separately when public delivery matters. A successful write requests cache invalidation but does not prove propagation or reachability. The path accepts a numeric id or public id, and the JSON body uses the page root. PATCH is also supported.

For internal pages, markup replaces live content; it does not promote a saved editor draft or promise deletion of an existing draft blob. For custom HTML pages, custom_html replaces the ClickFunnels-hosted HTML body. For external SDK pages, deploy content on your own host; external_url only changes its registration.

Field availability depends on the page type — see PageParametersUpdate for the full breakdown. Sending an internal-only field on an external page (or external_url on an internal page) returns 422 with an explicit list of the rejected field names — never silently ignored.

sort_order (optional, top-level): Reposition the page within its funnel. Zero-based. Ignored when funnel.show_page_step_id is also provided.

funnel.show_page_step_id (optional): Swap the page onto an existing show page step. The previous page on that step becomes an orphan. Shared by both page types.

external_url (external pages only): Update the external URL. The SDK token is preserved.

show_page_step.product_ids / show_page_step.bumps (optional, both page types): Append products to the page's checkout step as main products or as order bumps. Both are additive; bumps also promotes a product already attached to the step into a bump, which is how an existing attachment becomes one. Each bumps entry is {product_id, preheadline}, where preheadline is the optional copy shown above that bump's offer. Requires the page to be part of a funnel (400 otherwise).

markup (internal pages only): Replaces live page content. PML covers only a subset of what the ClickFunnels page editor can build, so if this page could have been created or edited in the editor, stop and get explicit approval from the user first: see the approval guardrail. Never resubmit a lossy PML read merely to publish an editor page.

To move externally-hosted pages to a new domain, see Patch one page at a time in the Migrate an External Page Domain Skill.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required
Query Params
expand[]
array of strings

Expand additional data in the response. Use expand[]=field_name to include optional fields (e.g., expand[]=head_code&expand[]=footer_code&expand[]=custom_css&expand[]=markup). Markup is opt-in on every endpoint (show, list, create, update) because PML serialization runs per page. custom_css is available on internal pages only. See the Expanding guide for available fields and examples. Read a page's existing markup with expand[]=markup before editing it: see Reading Current Markup in the Pages Skill.

expand[]
Allowed:
Body Params

Information about updated fields in Page

page
object

Update parameters for a page. Field availability depends on the page type:

Shared (all page types): name, description, sort_order, funnel.show_page_step_id, show_page_step.product_ids, show_page_step.bumps.

Internal (editor) pages only (returns 422 on external and custom HTML pages): markup, theme_id, seo_title, seo_description, seo_index, block_ai_crawler, block_ai_search, block_ai_assistant, head_code, footer_code, custom_css, live_data_changes.

External-only (returns 422 on other page types): external_url.

Custom HTML pages only (returns 422 on other page types): custom_html. Custom HTML pages also accept current_path (like internal pages) — it moves the funnel step's path when the page is a funnel step, or the page's own path when standalone.

The three block_ai_* flags are accepted on any internal page, but robots.txt can only express the block at paths ClickFunnels can currently resolve — today, the funnel step paths of a page that is a step in a funnel. A page that is not a funnel step (standalone landing page, site page, theme/template page, blog or course page) contributes no rules at all, and even for a funnel page the page's own direct URL is not yet listed. In every one of those cases the preference is stored and read back but not yet enforced; it begins taking effect as path resolution is extended, with no further action from the client. A 200 is therefore not proof that a page is blocked — fetch the domain's /robots.txt to confirm. See Crawler access (AI opt-out) in the Pages Skill.

Responses

Language
Credentials
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json