The challenge: templates were defining structure incorrectly
The builder’s site used shared templates for communities, floor plans, inventory, locations and supporting content. Over time, headings had been assigned by visual appearance or component availability instead of by what the content meant, so the structure did not describe the page.
Some pages used an H1 for a logo, a navigation element or a reusable template label. Others had several H1s and no clear primary topic. Heading levels were skipped, and text that worked as a visual label was marked as an H2 or H3 even when it introduced no real section.
None of this made pages unusable, but it made the hierarchy unclear for visitors using assistive technology and for systems trying to interpret each page. Across a large template-driven site, it also made it harder to tell what the primary subject of each URL was.
The approach: define hierarchy by meaning
The review began by mapping heading output across representative templates. Each page type was evaluated by its primary topic, supporting sections, reusable components and role in the buyer journey.
- The H1 went to the main subject of the page: the community name, floor plan name, location or article title.
- H2s were used for meaningful sections that support that subject.
- H3s were reserved for subsections inside an H2, not used simply because a component sat lower on the page.
Decorative text, labels and interface elements were separated from structural headings. The goal was not to remove useful visual content but to describe each element’s role accurately in the markup while preserving the design. Because the problem lived in the templates, the fix was built into reusable components and rules rather than hand-editing pages one by one.
The result: clearer page interpretation across 5,000+ pages
The template-level heading fixes reached more than 5,000 pages. The main topic and supporting sections of each page became easier to identify, visitors could scan pages more predictably, and assistive technology had a meaningful structure to follow.
The change also improved governance. New templates and components could be checked against a written heading standard instead of depending on individual implementation decisions, which made it much less likely the problem would return as new communities, floor plans and modules were published.
What was measured and what was not: the scope of the fix, more than 5,000 pages, is documented. A ranking, traffic or engagement change attributable to the heading work alone was not isolated or published, so this case study does not claim one.
Heading structure should not be judged in isolation anyway. It works with titles, page copy, internal links, structured data and how templates render. A clear hierarchy cannot rescue a page with unclear intent, but it makes a well-targeted page easier to understand.
What builders can learn about templates and structure
Heading tags are structural signals, not styling controls. A page can look correct to a visitor while its markup describes a confusing hierarchy to every machine that reads it.
The leadership lesson is to fund templates, not one-offs. On a builder site, one template change can improve hundreds or thousands of community, floor plan and inventory pages at once, while page-by-page fixes are slow and quietly undone by the next release. Ask your team which templates, once fixed, would lift the most pages.
Leaders should also insist on machine readability as a release standard: a unique title, one H1, clear section headings, internal links and structured data on every page. A short release checklist keeps pages from going live without them, and any template change should be validated across page types, devices, content variations and accessibility requirements before it rolls out.
Template problems like this are a core part of technical SEO audits. Clear structure is also part of what lets AI assistants identify and quote a builder’s pages, which is why it underpins AI search visibility work. For another template-level fix, see the image optimization case study.
