Ad Placements on Layout Templates — Per-Template Overrides
Banner placements now live on layout template definitions. Enable ads on Default, override on duplicate templates, and each page follows the template it resolves to.
Ad placements now live on layout template definitions — the same override model as background effects. Enable ads on Default, override on article or landing templates, and pages follow the template they use.
What we shipped
Ads in the Layout tab grouped placement controls with other chrome. This release moves them into each layout template:
Template-level placements
Layout → Engagement → Ads on the default template sets the baseline for every page
Duplicate templates can add an Ads override — keep sidebar banners on articles but turn them off on landing pages
Removing the override falls back to Default, same as background effects
Placements default on within a template once Ads is enabled — the master switch still defaults off until you opt in
Editor regrouping
The template editor is now Structure (header, body, sidebars, footer), Engagement (Widgets and Ads), and Effects (background). Each enabled placement is a nested row with chrome editors instead of accordions.
Render path
The live site resolves ads from the union of placements enabled on any template, but each AdSlot consults the page's resolved template. Folder pins, per-page template overrides, and live preview drafts all pick what actually serves.
Why it matters
Teams running different layouts on the same site — docs with sidebars, marketing without — can tune ad density per template without maintaining duplicate sites or re-booking inventory.
Try it
Open Layout, edit Default, switch on Ads under Engagement, and prune placements you do not want site-wide.
Duplicate the template for landing pages, add an Ads override, and disable sidebar or footer slots.
Assign the landing template on key pages — booked inventory stops serving where the template disables the slot.
