H2
Use H2 for major section headings below the main page headline.
When to use H2
- Introduce benefit sections, product sections, FAQs, testimonials, or pricing blocks.
- Break a long landing page into readable parts.
- Keep page structure clear after the H1.
Content settings
| Setting | What it controls |
|---|---|
| Text field | The visible section heading. |
| Type | H2 uses the h2 heading tag. |
| Inline formatting | Highlighted words, links, or emphasis when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Alignment | Heading alignment. |
| Typography | Font family, size, weight, line height, letter spacing, and responsive values. |
| Color | Text and highlight colors. |
| Spacing | Margin, padding, width, and responsive spacing. |
Best practices
- Use H2 to start each major page section.
- Avoid skipping from H1 directly to H3 when H2 would better describe the structure.
- Keep headings direct and benefit-focused.
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 H2, 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 H2, 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 H2, 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 H2, keep a short checklist of the fields you changed and test the result in the same browser session.