Should Blog Headings Be Questions? SEO and AI Search

Blog headings should be questions only when the section answers a specific question a reader actually has. Use statements for steps, comparisons and reference material, and expect most strong posts to mix both. A question mark is not a ranking factor: Google says you don't need to write in any special way for its AI features, so the answer under the heading matters far more than its punctuation.

This guide is for e-commerce and Shopify teams who write blog posts, buying guides and FAQ content and keep hearing that "every H2 should be a question for AI search." You'll get what the data actually says about question queries and AI Overviews, a decision table for each type of section, before and after rewrites, a step-by-step editing process and a checklist you can run on your next post.

Should blog headings be questions? The short answer

Use a question heading when three things are true: the reader arrives with that exact uncertainty, the section answers it in the first sentence or two, and the question is specific enough that a reader could predict the answer's shape. "Can I return an opened product?" passes. "Why does this matter?" fails, because it could sit above any paragraph on any page.

Use a statement heading when the section is a step, a list, a comparison or a reference block. "Set up the cart drawer" reads faster than "How do you set up the cart drawer?" and fits a sequence of tasks. A buyer scanning a size guide wants "Size chart for wide feet," not a question.

Mixing formats is normal. A post can open with a question that matches the search query, use statements for the how-to steps and finish with a question-and-answer FAQ. Consistency means a reader can follow the outline, not that every heading uses the same grammar.

Why the question heading idea took off

The advice has a real basis. People increasingly type full questions into Google and chat assistants, and Google shows AI answers far more often for those queries. In an Ahrefs study of 146 million search results published in January 2026, AI Overviews appeared on 21% of keywords overall but on 57.9% of question queries, compared with 15.5% of non-question queries.

An independent academic measurement points the same way. Researchers Haofei Xu, Umar Iqbal and Jacob M. Montgomery tracked 55,393 trending queries over 40 days in spring 2026 and found that AI Overviews activated on 13.7% of them overall, rising to 64.7% for question-form queries. The paper is accepted to the IMC 2026 conference.

Notice what these studies measure: how often Google shows an AI answer for a query phrased as a question. They do not show that pages with question headings get cited more often. That leap is where most "make every H2 a question" advice goes wrong. The useful lesson is narrower: if your shoppers ask questions, your content should answer those questions clearly, wherever on the page and in whatever heading format makes the answer easiest to find.

When question headings work best

Question headings earn their place when they name a decision or a problem the reader brought with them. They work well in four kinds of sections.

Decisions with a clear answer

"Is merino wool itchy?" or "Do I need a water softener for this filter?" sets up a yes, no or it depends answer. Put the answer in the first sentence under the heading, then the conditions. This mirrors the "Bool" queries in the Ahrefs data, which triggered AI Overviews 57.4% of the time.

Troubleshooting

"Why is my order showing as unfulfilled?" tells a customer exactly which problem the section solves. Support tickets, chat logs and returns reasons are the best source of these headings, because they are already in your customers' words.

Definitions and explanations

"What is a carbon plate running shoe?" works when the reader genuinely does not know the term. Ahrefs found definition queries triggered AI Overviews 47.3% of the time. If your audience already knows the term, skip the definition section rather than retitling it.

The section that matches the search query

If the post targets a question, such as "how long do running shoes last," using that question (or a close variant) as an early H2 makes it obvious the page answers it. That is the same reason this post's first H2 repeats its title query.

In every case, the heading is a promise. If the first two sentences under it do not deliver the answer, the question heading makes the section worse, because it raised an expectation and then wandered.

When statement headings are clearer

Statements are usually better for anything procedural, comparative or meant for scanning. Forcing these into questions adds words without adding information.

• Steps in a process. "Measure your foot length" beats "How do you measure your foot length?" in a numbered sequence.
• Comparisons. "Cotton vs linen sheets for hot sleepers" is already specific. Adding "Which is better" rarely helps.
• Reference blocks. Size charts, care instructions, ingredient lists and spec tables should be labeled, not asked about.
• Limits and caveats. "What the warranty does not cover" is direct and honest.
• Summaries. "Key takeaways" or "The bottom line for small stores" tells readers what kind of section it is.

The biggest warning sign is repetition. Five H2s in a row that start with "How can you" or "What is the" make a table of contents hard to scan, and a reader skimming on a phone sees the same two words over and over. Google's own SEO Starter Guide says there is no magical, ideal number of headings, and adds that if you think it's too much, it probably is.

Do question headings help SEO rankings?

There is no evidence that a question mark in a heading is a ranking factor, and Google's documentation gives you no reason to think it is. What headings do affect is clarity, and clarity affects how both people and search systems understand a page.

Here is what Google's documentation actually says about headings:

• Structure helps. Google's guide to its generative AI features recommends content "organized by paragraphs and sections, along with headings that provide a clear structure to navigate content."
• No special writing style is needed. The same guide says you don't need to write in a specific way just for generative AI search, and there is no requirement to break content into tiny pieces.
• Order is for people. The SEO Starter Guide says semantic heading order is fantastic for screen readers, but from Google Search's perspective it doesn't matter if headings are out of order.
• Headings can shape your title link. Google lists heading elements, such as the h1, among the sources it uses when it rewrites the title shown in search results. A vague H1 gives it worse material to work with.

So the ranking case for question headings is indirect. A heading that matches how people phrase their problem can make the section easier to recognize as an answer. A heading that is a forced, keyword-stuffed question makes the page harder to read and does nothing for rankings.

Your H1 is a separate decision. It should match the post's main query and the title tag closely. If the query is a question, the H1 can be a question too, as this post's is. Check the published page rather than the editor, because some Shopify themes style text to look like a heading without using a heading element. Our free H1 checker shows the real heading outline of any URL.

Question headings and AI search citations

AI Overviews, ChatGPT search and Perplexity pull passages that answer the question being asked. A section with a precise heading and a direct first sentence is easier to lift as a self-contained answer. That is a reasonable editorial bet, but it is not a guarantee, and no public study shows question-format headings alone increase citations.

The stronger predictor is whether the page ranks and is trusted at all. Ahrefs' analysis of 1.9 million AI Overview citations found that 76% of cited pages also ranked in Google's top 10 for the query. A perfectly phrased question heading on a page that does not rank and does not answer well will rarely be cited.

What makes a section easy for an AI answer to quote:

1. A heading that names one topic, specifically.
2. A first sentence that answers it in plain words, with no wind-up.
3. The conditions, numbers or steps immediately after, sourced where needed.
4. No dependence on earlier sections to make sense ("as mentioned above" weakens a standalone passage).

Those four traits work under a question heading or a statement heading. Our AEO checker reviews a page for answer readiness, and our guide to visibility in AI search covers the rest of the picture, from crawl access to brand mentions.

How to rewrite your headings, step by step

Use this process on an existing post or a draft. It takes about 20 minutes for a typical 1,500 word article.

1. Read only the headings. Paste the outline into a doc, or run the URL through the H1 checker. Can a stranger predict what the post covers and in what order? If not, fix the labels before worrying about format.
2. Collect real questions. Pull the questions customers ask from support tickets, product reviews, the "People also ask" box for your main query and Search Console queries for the page. Our guide to the most asked questions on Google shows how to find them.
3. Match each section to its job. Mark each section as a decision, troubleshooting, definition, step, comparison, reference or summary, then use the table above to pick a format.
4. Check the first sentence. Under every question heading, the first sentence must answer it. If you need a paragraph of setup first, the heading is wrong or the section is.
5. Cut repeated openers. If three or more H2s start with the same words, rewrite at least two of them as specific statements.
6. Keep H2s short. Aim for under 60 characters so they work in a table of contents and on a phone screen.
7. Record the change. If the post is live, note the date and what you changed. Avoid changing the title, body, internal links and headings all at once if you want to learn what helped.

Headings on Shopify product and collection pages

The same rules apply beyond the blog. Most Shopify product and collection pages have very few real headings: a product title as the H1, then theme blocks that look like headings but are often plain text. That leaves shopper questions about fit, materials, shipping and returns buried in tabs or not answered at all.

A short, visible question and answer block is where question headings shine on a store. Each item is a real question a buyer has before purchasing, and each answer is two or three sentences. We have tested this pattern repeatedly for clients, and it is one of the most consistent winners in our data.

For collection pages, a short intro with a clear statement heading ("Women's trail running shoes") plus three to five questions at the bottom gives both shoppers and search engines more to work with than a bare product grid. Keep the questions specific to the collection, and do not paste the same block on every page.

FAQ sections vs question headings

An FAQ section and question headings solve different problems. Question H2s organize the main body of a post. An FAQ collects the shorter follow-up questions that do not need a full section. If a question deserves 300 words, give it an H2. If it needs two sentences, put it in the FAQ.

Do not add an FAQ to chase a search feature. Google stopped showing FAQ rich results in Search on May 7, 2026, and removed the documentation in June 2026. Before that, they had been limited to well-known government and health sites since September 2023. FAQ structured data will not get you the expandable questions in search results anymore. Our guide to FAQ schema covers what markup still does.

The visible FAQ still earns its place when it answers questions readers actually have. Avoid repeating the body word for word, since a duplicate answer adds length without adding help. A good test: if you deleted the FAQ, would a reader lose anything? If not, cut it.

Your heading checklist before you publish

Run through these checks on every post. If you answer no to any of them, fix that heading before you hit publish.

• Does the H1 match the main query and the title tag closely?
• Can someone predict the post's content from the headings alone?
• Is every question heading answered in the first sentence below it?
• Are steps, comparisons and reference blocks labeled with statements?
• Do no more than two H2s in a row start with the same words?
• Is every H2 under about 60 characters?
• Are headings real heading elements in the published HTML, in a logical order for screen readers?
• Does the FAQ add follow-up answers rather than repeating the body?

Use questions where they help a reader resolve something specific, and statements where they make the page easier to scan. Then spend the rest of your effort where it pays: better answers, real sources and pages that rank. If you want help turning your blog and store pages into content that wins in Google and AI answers, our AI search optimization team can help, or you can get in touch.