AI Search Optimization: 24% Questions, 100% Titles

Introduction

If you want AI search optimization that actually matches what answer engines cite, do not turn every heading into a question. In one manual count of 8 readable pages, 106 headings, one question, one engine, one day, the cited pages used a buyer-question title, mostly statement headings through the body, and question headings mainly in the FAQ.

One afternoon, I asked Perplexity a buyer question any SaaS team could care about: how do I get my SaaS cited by ChatGPT. Then the same tool that recommended question-heavy headings pointed me to pages that mostly were not built that way.

• All 10 cited pages echoed the buyer question in the title
• Only 24% of body headings were questions across 8 readable pages
• Question headings clustered in FAQs, not across the full body
• Vague headings failed the sniff test more than statement headings did

That contradiction is the whole point of this piece.

I am not offering another generic answer engine optimization strategy checklist. I am showing the count, the page list, the counting rule, and the caveats so you can rerun the same check yourself this afternoon.

The advice everyone repeats, including the engines themselves

That contradiction started with a very tidy piece of advice. Ask whether headings should be questions, and the clean answer you keep hearing is yes: make more of them questions so AI can understand the page better.

When I asked Perplexity, “should my headings be questions for SEO,” it said informational pages should aim for 60 to 80 percent question-shaped headings, attributing that guidance to flockleads. That was one engine, on one day, answering one SEO-style question.

The story here is not that the advice exists. It is that the same engine then cited pages that did not follow it closely.

So instead of repeating the guidance, I checked the pages Perplexity actually surfaced for a buyer-style query. That is where the useful break appears.

How I ran the test, so you can repeat it this afternoon

The method was simple on purpose. On 2026-09-04, using public Perplexity with no login, I searched “how do I get my SaaS cited by ChatGPT”, opened the cited results, and counted every H2 and H3 inside the article body.

Based on what we saw when we manually counted H2s and H3s on 8 readable pages cited by Perplexity for that query on 2026-09-04, this piece argues for a different page shape than the usual “make everything a question” advice.

I used one explicit rule for what counted as a question heading:

• Question mark endings counted
• Interrogative openers counted: how, what, why, when, where, which, who
• Auxiliary openers counted: should, do, does, can, is, are, will
• Only article-body H2s and H3s counted

I also used two open exclusions:

• Excluded page chrome: nav, header, footer, sidebar, related posts, CTA blocks
• Excluded results: perciva.ai returned a 403, and the Reddit thread had no article headings

That left 8 readable pages. The next section is the exact citation set.

The ten pages the engine chose

Perplexity did not pull from one cloned template. It cited a cluster of agency-style posts, plus a Reddit thread, all aimed at the same buyer problem.

Here are the ten cited pages, with titles shown verbatim:

• margen.net — “How to Get Your SaaS Product Cited by ChatGPT”
• gracker.ai — “How to Get Your B2B SaaS Cited in ChatGPT Within 30 Days”
• loudface.co — “How to Rank in ChatGPT: B2B SaaS Playbook”
• perciva.ai — “How to Get Your B2B SaaS Cited by ChatGPT”
• saasflywheel.io — “Get Your SaaS Cited by ChatGPT and AI Search Engines”
• solvspot.com — “How to get cited by ChatGPT in 2026: a B2B SaaS playbook”
• devcommx.com — “How to Get Your SaaS Recommended by ChatGPT”
• growtika.com — “How To Get Your SaaS Product Mentioned in ChatGPT”
• reddit.com r/SaaS — “5 Steps to Get Cited in ChatGPT & Rank in AI Overviews”
• quoleady.com — “How to get your SaaS brand quoted by ChatGPT”

That matters because the argument here stays attached to real, inspectable pages. The next pattern was the cleanest one in the whole set.

Ten out of ten put the buyer's question in the title

If you want one rule that survived the count without exceptions, this was it. All 10 cited pages put the buyer’s question, or a very close restatement of it, in the title.

None of them tried to get cute with an abstract headline. None led with a brand slogan. None buried the job of the page under something broad like “AI Visibility Framework.”

What they did instead was obvious in a useful way:

• They mirrored the query in the title
• They named the buyer outcome directly
• They kept the subject concrete: SaaS, ChatGPT, cited, quoted, recommended, rank
• They made retrieval easy for both readers and engines

That is the finding that held up cleanly. The title carried the buyer question every time.

The body, though, is where the popular advice started to wobble.

Only twenty-four percent of the body headings were questions

Here is the count that broke the simple rule. Across 8 readable pages, 106 headings, one question, one engine, one day, only 25 headings were questions.

That is 24 percent. Not 60 percent. Not 80 percent. And not remotely “almost every H2.”

The page-level counts looked like this:

• margen.net — 7 headings / 3 questions
• gracker.ai — 18 / 8
• loudface.co — 12 / 3
• solvspot.com — 15 / 3
• saasflywheel.io — 11 / 3
• devcommx.com — 12 / 1
• growtika.com — 8 / 0
• quoleady.com — 23 / 4
• Total — 106 headings, 25 questions, 24 percent

In other words, in 8 readable pages, 106 headings, one question, one engine, one day, the cited pages were mostly structured with statement headings.

That does not make 24 percent a benchmark, a study, or a universal rule. It just means the advice and the evidence disagreed inside one tool on one afternoon.

The question headings had moved to the bottom of the page

That disagreement made more sense once I looked at where the questions sat. They were not spread evenly through the body.

They clustered near the bottom, mostly in FAQ sections.

A few examples made the pattern visible:

• gracker.ai put 5 of its 8 question headings inside FAQ items
• margen.net ended with “Frequently Asked Questions”
• loudface.co also ended with “Frequently Asked Questions”
• quoleady.com opened with “How do LLMs (like ChatGPT) find and use content?” and then ran 22 statement headings

So yes, question headings still mattered in this Perplexity citation set. They just did a different job than the usual advice suggests.

The recurring shape was simple:

• Question in the title
• Specific statement headings in the body
• Question headings clustered in the FAQ

That structure is much more useful for an answer engine optimization strategy than “turn everything into a question.” The next step is to look at what those statement headings actually said.

What the other seventy-six percent actually said

The non-question headings were not generic labels. They were specific, named, and strong enough to make a claim before the paragraph even started.

Here are five verbatim examples from the cited pages:

• loudface.co — “Step 1: Get indexed in Bing, where ChatGPT searches”
• devcommx.com — “Lever One: Lock In a Category Entity the Model Can Retrieve”
• solvspot.com — “The five signals that move citation share”
• gracker.ai — “The Category Anchoring Problem”
• saasflywheel.io — “Cut the Narrative Filler That Buries the Answer”

Each one does useful work without a question mark.

• It names the section clearly
• It previews a concrete argument
• It gives the engine retrieval cues
• It tells the reader why to keep going

This is why the body did not need to sound like an interview transcript. The headings already carried meaning.

That leads to the actual payoff of the count.

The real enemy is the vague heading, not the statement heading

Here is the plainest version of the lesson: for AI Search, the problem is not statement headings. The problem is vague ones.

Across the 8 readable pages, 106 headings, one question, one engine, one day sample, I did not see body headings like Overview, Benefits, Our Approach, or Conclusion doing the structural work.

That is the breakage to fix.

• A question mark does not rescue vagueness
• “What are the benefits?” is as empty as “Benefits”
• Specific headings travel better into retrieval and summaries
• Named claims beat reusable labels every time

A good test is brutally simple: if your heading could sit unchanged on a competitor’s page, it is probably the wrong heading.

So if you are building a page around how do I get my SaaS cited by ChatGPT, stop asking whether every H2 should be a question. Ask whether every heading says something precise enough to be worth citing.

There is still one more step before turning this into a playbook: naming what this does not prove.

What this does not prove

This count is useful because it is narrow, not because it is sweeping. It covered one engine, one question, one day, and 8 readable pages.

That means the limits are part of the result, not a footnote to hide.

• No ChatGPT probe was included
• No Google AI Mode probe was included
• This is correlation only; shared structure does not prove causation
• The 60 to 80 percent figure was what one engine repeated on one day
• The 24 percent figure is not a benchmark, study, or universal target

If anything makes this worth trusting, it is that the caveats stay attached to the number every time. The honest move now is not to canonize 24 percent.

It is to rerun the same count on your own buyer question and see if the same pattern holds. And that brings us to the one place where this article deliberately switches into question headings.

Frequently asked questions

This is the one place in the article where the headings become questions on purpose. That is not a formatting accident.

It matches the pattern the cited pages actually used: question in the title, statement headings through the body, and question headings in the FAQ.

Should every H2 on my page be a question?

No. In this sample of 8 readable pages, 106 headings, one question, one engine, one day, the cited pages used 24 percent question headings, not all-question structures.

Do question headings hurt SEO?

No sign of that appeared here. The issue was not question versus statement; it was specificity versus vagueness.

Do question headings help featured snippets and People Also Ask, or only AI Overviews?

They can help Q&A-style surfaces. This piece, though, only counted one Perplexity citation set and did not test snippets directly.

Do question headings work on product, category and home pages?

They can. They are just not a rule, because the job of the page should decide the structure first.

I turned my headings into questions and nothing happened — why?

Because a question mark is not enough. If the headings are generic, they still do not say much to the reader or the engine.

That leaves the practical question: what should you do with this today?

Your AI search optimization to-do for this afternoon

Key takeaways:

• Use the buyer question in the title
• Write specific statement headings through the body
• Save question headings for the FAQ
• Rerun the count on your own query

If you want a cleaner answer engine optimization strategy, return to the opening contradiction. One engine recommended question-heavy heading ratios, then cited pages that were mostly built another way.

That does not mean question headings are useless. It means their best job may be narrower than the internet keeps saying.

For this Perplexity citation set, the strongest pattern was clear:

• 10 out of 10 titles echoed the buyer question
• Most body headings were specific statements, not questions
• Questions concentrated in FAQs near the bottom

If your goal is how do I get my SaaS cited by ChatGPT, start there.

Rewrite one page this afternoon using that structure:

• Title: mirror the buyer question
• Body: replace vague labels with named claims
• FAQ: move the natural questions to the bottom

That is a much sharper way to approach AI search optimization than spraying question marks across every heading. The next useful step is simple: pick one buyer query, count the cited pages, and let the pages tell you what shape is actually winning.

References

• Perplexity citation set and manual heading count conducted on 2026-09-04 for the query: “how do I get my SaaS cited by ChatGPT”
• Perplexity response observed on 2026-09-04 for the query: “should my headings be questions for SEO”, including the quoted “60 to 80 percent question-shaped headings” guidance attributed by the engine to flockleads