Page Summary
Page Summary opens a read-only summary modal for the page currently loaded in the builder. It is designed for QA and handoff: the popup reads the canvas tree, page settings, integrations, custom code slots, delay configuration, pixels, optimizer flags, and modal behavior, then lets you copy the complete summary to the clipboard.
Use it after you finish editing the page, before publishing, duplicating the page, or asking another person to review the setup.
What Page Summary includes​
The summary is generated from the current builder state, not from a separate crawler. It includes:
- Page identity: page name, whether the page is a quiz page, and the generation timestamp.
- SEO and metadata: title, description, Open Graph title and description, keywords, SEO language, author, product name, canonical link count, custom meta tag count, share image status, and favicon status.
- Page features: hide from search engines, pass URL parameters, back redirect and URL, privacy and terms pages, page language, and DevTools protection.
- Delay: delay time, sync with video, and scroll-to-ID target.
- Custom code slots: whether each code slot is filled and the approximate character count for each slot.
- Integrations: Utmify pixel count, AtomicTracker campaign count, optimizer flags, and Facebook pixel count.
- Facebook pixels: pixel name, the last digits of the pixel ID, event count, and whether server events are enabled.
- Modals and popups: global popup presence, click or tap triggers, custom modal target containers, trigger classes, and auto-open behavior such as exit intent, delay, or scroll percentage.
- Canvas outline: the first 100 components or quiz steps, with type counts and short text previews when available.
For quiz pages, the outline uses the first interactivequiz block's internal steps when they exist, so the summary focuses on quiz flow instead of outer layout sections.
Review workflow​
- Save or finish the edits you want represented in the current builder state.
- Open Page Summary from the builder sidebar or summary entry.
- Check the page name and page type badge first, especially when several tabs or cloned pages are open.
- Review SEO & meta, Page features, Delay, Custom code slots, Integrations, Optimizer, and Facebook pixels before looking at the component outline.
- In Modals & popups, confirm whether triggers open a shared global popup or a custom modal container. Custom triggers show their trigger class and target container suffix.
- Use Copy all when handing the page to support, a media buyer, or another builder editor.
Fields that need extra attention​
| Summary area | What to check |
|---|---|
| Custom code slots | A slot marked "on" only confirms code exists. It does not prove the script loaded successfully on the published URL. |
| Facebook pixels | The summary shows event count and server-event status, but you still need to verify event firing in Pixel Helper, Events Manager, or network logs. |
| Delay | The summary shows the stored time and scroll ID. Test the page to confirm delayed sections reveal and scroll at the expected point. |
| Modals | Trigger classes and container suffixes are useful for debugging, but visitors only see the behavior after the popup content and trigger element are both valid. |
| Outline | Large pages are truncated after the first 100 outline items, so a missing component near the bottom may require canvas inspection. |
Testing notes​
- After changing settings, close Page Summary and reopen it to refresh the generated data.
- Pair Page Summary with desktop, tablet, and mobile preview because the outline does not prove responsive spacing or stacking.
- If a summary value is blank, reopen the relevant Page settings tab and confirm whether the field was saved in Save editions.
- When sending the copied summary to support, include the page URL or page ID separately because the copied text focuses on builder configuration.
Related docs​
FAQ​
Why does my quiz summary show quiz steps instead of normal sections?
For quiz pages, Page Summary looks for the first interactive quiz block and uses its internal contents as the outline. That makes the copied summary more useful for reviewing quiz steps, answers, and conversion flow.
Does Copy all include hidden tracking IDs?
It includes practical debugging details such as pixel names, event counts, short pixel ID suffixes, code slot character counts, modal trigger classes, and integration counts. It is still a summary, not a full export of every script or credential.
Why is the outline missing later components on a long page?
The summary limits the outline to the first 100 items and a maximum nesting depth so the modal stays usable. Use the canvas or copied type counts when reviewing very large pages.
Can Page Summary replace final page testing?
No. It is a configuration review. You still need to preview responsive layouts, test forms and buttons, confirm delayed content, and verify pixels or custom scripts on the published URL.