How to Structure a Website for Answer Engine Optimization (H1s, FAQs, Headings)

When an answer engine like Google's AI Mode, ChatGPT, or Perplexity handles a question, it does three things fast. It retrieves candidate pages, matches sections of those pages against the user's question, and lifts the passage that answers most directly. Your heading structure is the map it uses for that middle step. An H2 that restates the question is a direct hit; a heading that says "Excellence in Every Detail" matches nothing a human has ever asked.

Most owners treat headings as decoration, a place for the designer to set a mood. That made a loose kind of sense when only humans read the page. It is actively harmful now, because a decorative heading takes the one slot the machine reads first and fills it with noise. Structure is one layer of a bigger system (the full stack is in our AEO best practices guide), but it is the cheapest layer to fix and, in our experience, the most neglected.

Here is the part agencies hate. The AEO-friendly version of your site is simpler than what they sold you, not fancier. One literal H1. H2s that are real questions. An answer in the first two sentences under each. That is the whole architecture.

Every page gets exactly one H1, and it states what the page is about and where. "Water Heater Repair in Mesa, AZ" is a good H1. "Welcome to Johnson & Sons" is not, and "Quality You Can Trust" is worse. The H1 is the page's declared topic; when you make an engine infer the topic instead of reading it, you tend to lose to the competitor who just said it.

Check what your template is actually doing, because this is where good intentions die. Plenty of themes wrap the logo or the site tagline in an H1 on every page, which means all forty of your pages declare the same topic. Others let a page builder scatter three or four H1s because someone liked the font size. View source and search for the h1 tag: you want one hit per page, and it should read like a label, not a slogan.

Keep the H1 close to the title tag but written for the page. "Emergency Plumber in Mesa | Johnson & Sons" works as a title tag; the H1 can drop the brand and simply say "24-Hour Emergency Plumber in Mesa, AZ." Literal beats clever every time a machine is the first reader.

H2s are where most of the matching happens, so write them as the questions customers actually ask, phrased the way they ask them. Not a keyword fragment, not a theme, the question itself. This feels unnatural to anyone trained on brochure copy. Do it anyway.

Take a plumber in Mesa (invented for this example, but typical). The typical agency-built service page carries H2s like "Our Services," "Why Choose Us," and "Your Comfort Is Our Priority." Rewritten for answer engines, the same page reads: "How much does drain cleaning cost in Mesa?", "Do you handle emergency calls at night and on weekends?", "Which East Valley neighborhoods do you serve?" Same page, same facts, but now every section is addressable by a machine matching a real question.

Then the first two sentences under each H2 must answer the question, not wind up to it. Suppose most of your drain jobs land between $150 and $400. Say so in sentence one: "Most drain cleaning jobs in Mesa run $150 to $400, and we quote a firm price before we start." Everything after that supports the answer: what moves the price, what is included, why it varies.

The passage an engine lifts is commonly the heading plus the first sentence or two beneath it. If your answer arrives in paragraph three, after the founding story and the mission statement, the engine either quotes your throat-clearing or skips you for someone who got to the point.

Your FAQ section should be transcription, not composition. Pull questions from where customers already ask them: call logs, text threads, the Q&A tab on your Google Business Profile, the "People also ask" box for your service. If nobody has ever asked it in those words, it does not belong in your FAQ. "What is the best affordable plumber near me?" is keyword mush; no customer talks like that, and engines match against how people actually talk.

Keep each answer around 40 to 60 words. That is long enough to be complete and short enough to be lifted whole. Answer in the first sentence, add one supporting fact or an honest caveat, stop. If an answer needs 200 words, it is not an FAQ entry, it is a section of the page and deserves its own H2.

Mark the block up with FAQPage schema in JSON-LD, and make the markup match the visible text exactly. Google has mostly stopped showing FAQ rich results for ordinary businesses, but the markup still hands every engine a clean question-and-answer map of your page, which is the actual point. The full implementation, alongside the other schema types a local business should carry, is in our local business schema guide.

Most of the structural damage we see was paid for. Somebody hired a design shop, the site won compliments, and it parses like static. These are the patterns to hunt down and delete.

Start with the dumb checks, they catch most problems. View source and count H1s: the answer is one. Turn off JavaScript and reload; if the FAQs vanish, engines likely never saw them. Read your H2s aloud as a list: if they sound like questions a customer would ask, you built an interface. If they sound like a mood board, you built decoration.

Then run the page through our free AEO checker, which grades headings, schema, and answerability in one pass. For the whole-business view, including whether AI engines can find and describe your company at all, run the Local AI Visibility Check.

Finally, test like a customer. Ask ChatGPT and Perplexity the exact questions in your H2s and note who gets named, then watch your server logs for AI crawler visits (GPTBot, PerplexityBot) landing on the restructured pages. No structure change can promise you a citation, and anyone who says otherwise is selling something. But clean structure reliably raises your odds, and it is one of the fastest odds-raisers available. If you would rather hand the whole job to people who do this daily and prove the results with evidence, that is what a done-for-you AEO agency is for.