I can audit the heading structure, but I need the headings themselves first. I will not fetch or guess them.
- Outlines (required). For each template you want checked (for example one blog post and one product page), paste the headings in page order as "level | text", like: h1 | [your page's main heading] h2 | [next heading on the page] Include the template name and one example URL from fernhill-garden.example. Why: every finding (skipped levels, missing or extra h1s, empty headings) comes from the order and levels, so I need them exactly as they are on the page.
- Template purpose (optional): one line per template on what the page is for. Default if you skip it: I will flag unclear headings but leave their new wording as [ADD: ...] placeholders instead of suggesting text.
One note on "for SEO": my sources give no ranking rule for heading order or count, so I will not promise a ranking change. I can show where the outline breaks the guidance from W3C and MDN, which helps readers and screen reader users move through the page.