Write clear headings and page copy

Outline before you edit

Start with the page’s established title and template. Use one clear content title unless the template or a developer confirms a different structure. Break the page into meaningful sections, then nest subsections under the section they belong to. A heading with rank 2 can introduce a major section, and rank 3 can introduce a subsection inside it. Do not choose a heading because its font looks right, and do not skip from H2 to H4 simply to make text smaller.

Headings should identify the subject of the section. “Project timeline,” “How to register,” and “Download the quarterly report” are more useful than “Overview,” “More information,” or a row of decorative words.

Use the editor semantically

In WordPress, use a Heading block and choose its level from the block controls. The editor’s document outline can help you review the sequence. In Elementor, the Heading widget’s HTML Tag field controls whether the text is an H1 through H6 or a non-heading element; changing that tag does not have to change its visual styling. Set the semantic level first, then apply the approved visual style.

Write short paragraphs, front-load the important noun or action, expand abbreviations on first use, and explain a specialized project term when the audience may not know it. Use lists for steps or requirements, and use link text that still makes sense when read out of context.

Keep the first sentence useful on its own, especially when the page is summarized in search results or a card. Prefer “Submit a comment by Friday” to “We would like to remind stakeholders that comments may be submitted.” Preserve the project’s approved terminology, but add a plain-language explanation when a technical term cannot be avoided.

Hand off template and component questions

Ask a developer to review the heading structure when a page builder, reusable component, sidebar, accordion, or card grid adds its own headings. The fixed navigation and footer may use a consistent rank across pages, while the main content needs to retain a readable outline. The developer should inspect the rendered HTML, not only the editor view, and check that text remains visible and ordered at zoom and on small screens. If the page has no usable main title or generates multiple competing titles, stop and request a template decision.