Publishing and website controls

Manage a shared publication

Your published footer is the delivery source. Edit links, design and relevant website details in the workspace, then publish when the preview is ready. Check the destinations and legal links on each selected domain.

A saved draft can differ from the live footer. Use the published result when checking whether a website is current.

Choose the pages that receive it

Where page targeting is configured, include and exclude rules determine whether a page should receive the footer. Use real pages when testing a rule; a missing URL is not evidence that an excluded page works.

• Check a page that should include the footer.
• Check a real page that should exclude it.
• Test client-side navigation between those pages, as well as a fresh page load.

Pause without losing your settings

Use the website delivery controls to pause or resume a supported installation. Automatic maintenance respects paused delivery. A repair should not turn a paused footer back on.

Verify the public page after changing delivery. Cached output and static snapshots can need another check or a republish before the new state is visible.

Keep static exports current

HTML/CSS and CMS exports are snapshots. Include a fresh export in your publishing workflow whenever the shared footer changes. Server or compatible edge delivery can fetch the publication without a separate static-site republish.

Review delivery and activity

Use your dashboard to review website checks and footer activity where the activity collector is installed. Treat delivery verification, page views and footer clicks as different signals. A footer click does not establish a signup, sale or search ranking improvement.