Publish

Make pages Agent Pages now, including pages your sitemap doesn't list. Each path is fetched from your live site, optimized and served once that finishes, usually within minutes. On a page-by-page setup each page is selected for Agent Pages and counts against your Agent Pages budget. On a page-by-page setup, the site serves only its Agent Pages set. With Site Optimization, a site with an empty set serves no Agent Pages; without it, a site serves every page until its first page is marked or published, so the first publish stops serving every page outside the set.

Returns one outcome per requested path. queued means the fetch was sent, not that the page is live: if your site doesn't serve the page (for example it answers 404), it stays selected but isn't served until a scheduled check finds it live (about every 30 days) or you send it again. If the send fails, the hourly scheduled check picks the page up, usually within an hour. warnings says when a queued page waits on your site: it was retired earlier, or recent checks saw it redirect.

A path the Agent Pages Unpublish API put on the Ignore List is published again; a dashboard Ignore List entry or path rule is never overridden (excluded). On a whole-site (legacy) setup the page is optimized without being added to any list. A path your CDN doesn't route to the Scrunch edge worker is stored but never served.

Limits: 100 paths per request; each path once every 5 minutes; per brand, 500 published paths per rolling hour and 5,000 per rolling 24 hours. These quotas are separate from Force Refresh's and Unpublish's.

Publish acts on the Agent Page only. Curated (Adaptive) content at the same path keeps being served, and the response doesn't report it.