Footer
Use Footer for legal links, copyright, disclaimers, and bottom-of-page navigation.
Content settings
| Setting | What it controls |
|---|---|
| Disclaimer | Legal, support, or informational footer text. |
| Product name | Product or brand name shown in the footer. |
| Copyright | Copyright text. |
| Symbol | Copyright or related symbol. |
| Terms URL | Link to terms of use. |
| Privacy URL | Link to privacy policy. |
Style settings
| Style area | What you can adjust |
|---|---|
| Typography | Footer text and link styles. |
| Layout | Alignment, columns, gap, and responsive stacking. |
| Background | Footer background color or image when available. |
| Spacing | Padding, margin, and section width. |
Best practices
- Include privacy and terms links before paid traffic.
- Keep disclaimer text readable on mobile.
- Test all footer links after publishing.
FAQ
When should I use this page?
Use this page when you need a quick reference for this Atomicat feature and want to understand what it changes before editing or publishing. It is especially useful while reviewing a page, funnel, quiz, lead flow, product setup, video configuration, or account setting. For Footer, keep a short checklist of the fields you changed and test the result in the same browser session.
Do I need to configure this before publishing?
Configure it before publishing whenever the feature affects visitor behavior, tracking, SEO, forms, embeds, checkout, or access. If the feature only changes internal organization, review it before launch so your team can manage the campaign consistently. For Footer, keep a short checklist of the fields you changed and test the result in the same browser session.
Can this affect live pages?
Yes, some settings can affect live pages after saving or publishing. Always preview the page, test the main action, and confirm desktop and mobile behavior before sending paid traffic or sharing the URL. For Footer, keep a short checklist of the fields you changed and test the result in the same browser session.
What should I check if something looks wrong?
Check the page status, project access, saved revisions, browser cache, connected domain, and any related integrations. If the feature depends on a plan, permission, or enabled module, confirm that your workspace has access. For Footer, keep a short checklist of the fields you changed and test the result in the same browser session.