H1 to H3 heading structure audit with a rewritten outline
Checks the headings on a page for order, gaps, skipped levels, vague wording and missing topics, then returns a cleaner outline in which every heading says what its section answers. Use it on long articles, service pages and guides that rank for the topic but do not hold readers or win snippets.
The output this prompt produced, unedited.
The prompt
Constraints first
One H1 per page, and it matches the page's main promise.
Headings never skip a level, such as an H2 followed directly by an H4.
Each heading is written for the reader in plain words; never a string of keywords.
Keep every section that has useful content; rename or move it rather than delete it.
Use only the headings and notes pasted.
Inputs
Page URL and main keyword: [paste]
Current headings in order, with their level: [paste, e.g. H1 ..., H2 ..., H3 ...]
Rough word count under each heading, if known: [paste]
Questions readers ask that the page should answer: [paste, or none]
Check
Headings that are vague, such as "Overview", "More info" or "Conclusion".
Sections that are in the wrong order for a reader deciding or learning.
Two headings that cover the same ground.
Long sections with no H3 to break them up.
Reader questions with no heading that answers them.
Output format
Current tree with an issue note against each heading.
Rewritten outline: H1, then H2 and H3 headings in order, each with one line on what the section answers.
A list of moves, merges and new sections, each with a reason.
Three headings phrased as questions, chosen where a short direct answer can follow.
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.