H1
Use H1 for the main headline or primary message of a page.
When to use H1
- Add the main promise or headline in the hero section.
- Identify the primary topic of the page.
- Give search engines and assistive technologies a clear page heading.
Content settings
| Setting | What it controls |
|---|---|
| Text field | The visible headline. |
| Type | H1 uses the h1 heading tag. |
| Inline formatting | Optional highlights, links, or emphasized words when available. |
Style settings
| Style area | What you can adjust |
|---|---|
| Alignment | Left, center, right, or justified heading alignment. |
| Typography | Font family, size, weight, line height, letter spacing, and responsive heading sizes. |
| Color | Main heading color. |
| Highlight | Alternate highlight colors and highlight background. |
| Spacing | Margin, padding, width, and responsive spacing. |
Best practices
- Use one main H1 per landing page when possible.
- Keep the headline readable on mobile.
- Do not use H1 only for visual size; use it for page structure.
- Use H2 and H3 for lower-level sections.
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 H1, 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 H1, 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 H1, 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 H1, keep a short checklist of the fields you changed and test the result in the same browser session.