On this page
Published: September 10, 2026
Text that looks like a heading is not necessarily marked as one. The reverse also happens when a component uses a heading element only to obtain a visual style.
Start with the page purpose
Name the page's main topic and assign the primary heading. Then map section headings by meaning. Do not choose levels because one size looks better; typography belongs in the design system.
Exercise reusable components
Cards, accordions, sidebars, and inserted modules can disrupt an otherwise sensible outline. Test templates with the smallest and largest realistic component combinations. Decide how a component receives its heading level from context.
Compare code and screen
Inspect the heading sequence in the browser and read the page visually. Confirm that each heading introduces the content that follows and that no empty headings appear. Record intentional level changes so later content edits do not "fix" them blindly.
Further reading
Related Articles
Keep this decision with the approved page brief and acceptance record.
Ready to plan your next step?
Contact WebsiteDesignOutsource.com
Turn the guidance into a reviewable handoff
Record the owner, input, acceptance condition, evidence, and escalation point before production begins. That small contract makes the work easier to inspect and approve.
Plan a website production handoff