H3
Use H3 for subsection headings, card titles, feature titles, and smaller structured headings.
When to use H3
- Title individual cards inside an H2 section.
- Add subheadings inside FAQ, pricing, feature, or testimonial sections.
- Structure supporting content without using oversized H1 or H2 elements.
Content settings
| Setting | What it controls |
|---|---|
| Text field | The visible subsection heading. |
| Type | H3 uses the h3 heading tag. |
| Inline formatting | Highlights or links when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Alignment | Heading alignment. |
| Typography | Font, size, weight, line height, letter spacing, and responsive values. |
| Color | Text, hover, and highlight colors where available. |
| Spacing | Margin, padding, width, and responsive spacing. |
Best practices
- Use H3 under an H2 section.
- Keep H3 labels short when used in cards.
- Avoid using H3 only because of visual size; choose the level that fits the content structure.
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 H3, 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 H3, 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 H3, 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 H3, keep a short checklist of the fields you changed and test the result in the same browser session.