Answer-first page shape: what is official, what is folklore

Most on-page advice comes with numbers attached. Write 1,500 words. Keep keyword density near 1%. Put the exact phrase in five places. Keep meta descriptions under 155 characters. Use one H1. Add a TL;DR box and an FAQ block so AI tools can quote you. Split everything into small chunks for the language models.

Numbers like these are easy to follow and easy to audit, which is why they spread. What they rarely have is a source. This article checks each common claim against what the platforms themselves publish, grades it, and then gives the page shape I use. That shape is our method, not a platform rule, and I'll show how to test it on your own pages.

Every claim carries one of four labels: official guidance (a platform documenting its own product), research finding (a named study with a stated method), our observation, or hypothesis. Register ids such as AS-06 point to the source notes in our evidence register. The Google pages were re-read on 2026-10-06. Several changed in 2026, so re-check them before relying on this after early 2027.

The short version

• Google says there is no target word count, minimum or maximum (official guidance, M1-05).
• No Google or Bing page I read gives a keyword density or a keyword-placement formula. Google does say that repeating words unnaturally is keyword stuffing (official guidance, M1-27, AS-12).
• Google builds title links and snippets itself. It may replace your title, and it uses your meta description only when that describes the page better than the page text does (official guidance, M1-07, M1-08).
• FAQ rich results are gone from Google Search. They were limited to government and health sites in 2023 and stopped showing on 2026-05-07 (official guidance, AS-01).
• Google says you don't need to "chunk" content or write a special way for its AI features. Bing's team says its assistants do break pages into pieces, and it recommends headings, Q&A pairs, lists and tables (official guidance from each, AS-06, AS-09). The two platforms emphasize different things, and you should know which one you're reading.
• Putting the answer first is good for readers. No platform documents it as a ranking or citation rule.

Grading scale

Grade	Meaning
Documented	A platform's own documentation states it.
Partially documented	Part of the claim is documented; the specific number, rule or effect is not.
No evidence	I found no primary source either way. It may be true; nobody has shown it.
Contradicted	A platform's own documentation says otherwise.

"No evidence" is not "false". It means that if someone tells you this, they should show you the data, and you should test it before building a process around it.

The claims, graded

#	Claim	Grade	What the primary source says
1	Pages need a target word count (1,500 words for blogs, 400–500 for product pages)	Contradicted	Google says length alone doesn't matter and there is no word-count target, minimum or maximum (M1-05). Its people-first guidance lists writing to a word count as a warning sign (M1-09). Its AI guide says there is no ideal page length (M1-13).
2	Hit a keyword density of about 1–2%	No evidence (for any figure)	No density appears in Google's docs. The Starter Guide says varying your wording naturally gives you more chances to show (AS-05). Repeating words until they sound unnatural is a named example of keyword stuffing (M1-27).
3	Put the exact keyword in the title, URL slug, H1, first sentence and meta description	Partially documented	Descriptive titles and headings are documented advice, and both feed title links (M1-08, AS-04). Keywords in the URL path have "hardly any effect" beyond breadcrumbs (M1-06). No document gives a placement formula or a "first 100 words" rule (AS-12).
4	A keyword-rich slug helps you rank	Contradicted (as a ranking lever)	Same Starter Guide line: hardly any effect (M1-06). Short, readable URLs still help people.
5	Every page must have exactly one H1	No evidence (as a rule)	Google says there is no ideal number of headings (AS-05). Its title-link doc does advise one distinctive, prominent main title, for example in the first visible h1, because several equally prominent headings can confuse title-link generation (AS-04). So: one clear main heading, yes; a penalty for two h1 tags, no source.
6	Headings must run in strict order (H1, H2, H3) for SEO	Contradicted	Google says heading order doesn't matter to Search, though it helps screen readers (AS-05). Keep the order for accessibility.
7	The H1 should match the title tag	Partially documented	Bing's team says the H1 should match or closely reflect the title for its AI systems (AS-09). Google uses headings as one title-link source and may swap in other text when the title is inaccurate or unclear (M1-08), but sets no matching rule.
8	Meta descriptions must be 150–160 characters	Contradicted	Google says there is no length limit on the tag; display is truncated to fit the device (M1-07). A 2020 Ahrefs desktop study found length made little difference to how often Google replaced the description (research finding, AS-03).
9	Meta descriptions are a ranking factor	Contradicted	Google said in 2009 that it doesn't use the description tag in ranking (AS-02). Current docs describe it only as a snippet source (M1-07). That statement is old, so cite it with its date.
10	Google ignores your meta description most of the time	Partially documented	Google documents that snippets come mainly from page content and the description is used only sometimes (M1-07). The "about 63%" figure comes from a 2020 Ahrefs study of 20,000 desktop keywords (AS-03). Today's rate is unmeasured.
11	Add FAQ blocks with FAQPage schema to get rich results	Contradicted	FAQ rich results were limited to authoritative government and health sites in 2023 and stopped showing on 2026-05-07; Google removed the docs in June 2026 (AS-01). Leftover markup causes no problems, but it has no visible effect.
12	FAQ sections help you get cited in AI answers	Partially documented (Bing only)	Bing suggests FAQ sections and Q&A pairs make content easier for its AI to reference (AS-09, AS-10). Google names no format that earns AI citations (AS-06). Neither publishes data showing an effect.
13	A TL;DR box at the top gets you into featured snippets or AI answers	No evidence	Google says you can't mark a page as a featured snippet and publishes no format for one (AS-07). It says no special formatting is needed for its AI features (AS-06). I found no study of labeled summary boxes (AS-13).
14	"Chunk" pages into small self-contained blocks for LLMs	Contradicted (Google) / Partially documented (Bing)	Google: no requirement to break content into tiny pieces; its systems can find the relevant part of a page that covers several topics (AS-06). Bing: its assistants parse pages into pieces, so it advises descriptive headings, liftable statements and no walls of text, without giving any chunk size (AS-09).
15	Add llms.txt, Markdown copies or special AI markup	Contradicted (Google)	Google Search doesn't use them; they neither help nor hurt there (AS-06, M1-13). Other services may read them.
16	A buried answer causes pogo-sticking, which demotes the page	No evidence (as a named signal)	No Google document uses the term. Google says it uses aggregated, anonymized interaction data (M1-19). The 2024 court opinion lists how quickly users return to the results among the click data a search engine collects, without saying how it's used (CL-01). See Do clicks rank pages?.
17	Statistics, quotes and cited sources raise your share of AI answers	Partially documented (research)	In the GEO benchmark study, adding citations, quotations and statistics increased a source's visibility in generated answers on the authors' metric, and keyword stuffing did not (research finding, AS-11). That was a 2023–24 test with a simulated engine and Perplexity, not live Google. Google's push for first-hand, "non-commodity" content points the same way without promising anything (M1-13).
18	Comparison tables and lists get lifted into AI answers	Partially documented (Bing only)	Bing recommends lists and tables for comparisons and steps (AS-09). Google says only to organize content clearly for readers (AS-06).

Two patterns stand out. First, almost every number in on-page folklore (word counts, densities, character limits, chunk sizes) has no source, and Google contradicts several of them outright. Second, the formatting advice that does have an official source comes mostly from Bing, about Bing's own assistants. Google's AI guide goes the other way and lists chunking and AI-specific rewriting under things you can ignore.

What Google actually documents about page shape

Here is everything Google says about page structure in the pages I read, condensed.

Titles. Google generates title links automatically from the title element, the main visible title, headings, og:title, other prominent text, anchor text and WebSite structured data. It may substitute a better title if yours is half-empty, obsolete, inaccurate, boilerplate, stuffed or unclear (official guidance, M1-08). Google advises a title that is unique, clear, concise and accurate (AS-05), and a main heading that is clearly the most prominent text on the page (AS-04). There is no length limit. The display is cut to fit the device.

Headings. Use them to break long content into sections people can navigate (AS-05). Order and count don't matter to Search (AS-05). People-first guidance asks whether the main heading or title gives a descriptive, helpful summary without exaggeration (AS-08).

Snippets and descriptions. Snippets come mainly from page content and are chosen to fit the specific search, so the same page can show different snippets for different queries (M1-07). The meta description is a secondary source. A good one is short, unique to the page and covers its main points. Google's examples favor specific facts (author, price, length for a book) over keyword lists, and it says strings of keywords are less likely to be shown (M1-07). That last point is the only place Google ties description content to whether it's used.

Length. No target, minimum or maximum. Google's guide for AI features adds that sometimes shorter, sometimes longer pages work, depending on audience and subject (M1-05, M1-13).

For AI features. No chunking, no rewriting for AI, no new files, markup or Markdown, no special schema. Organize content in paragraphs and sections with clear headings for people. Make main content easy to tell apart from everything else. Write first-hand material that others can't easily reproduce (AS-06, M1-13). Eligibility is the same as for a normal snippet: the page must be indexed and snippet-eligible (M1-13).

Featured snippets. You can't mark a page as one. Google publishes no minimum length. Your only controls are opt-outs (nosnippet, data-nosnippet, max-snippet) (AS-07).

That is the full list. Everything else in on-page checklists is either a reader-experience choice, another platform's advice, or folklore.

Where Bing differs

Bing's team published its own guidance in October 2025 on the Microsoft Advertising blog. It says Copilot and Bing's AI summaries split pages into smaller pieces, rank those pieces, and assemble answers from several sources (official guidance, AS-09). From that it recommends:

• title, description and H1 that agree with each other,
• descriptive H2 and H3 headings instead of vague ones,
• direct question-and-answer pairs,
• lists and tables for steps and comparisons,
• no long walls of text, and no key answers hidden in tabs, expandable menus or PDFs.

Its February 2026 post announcing the AI Performance report repeats the headings, tables and FAQ advice, and adds examples, data, cited sources and regular updates (AS-10).

The two platforms don't contradict each other on what makes a page good. They differ on whether you need to write for the machine. Google says you don't. Bing says structure helps its parser. Neither publishes data showing the size of any effect.

For a SaaS or B2B page, the practical reading is simple: clear headings, plain answers and real tables help human readers anyway, and Bing says they help Copilot. Nothing in Google's guidance says they hurt. What the evidence doesn't support is rewriting good pages into 150-word fragments or bolting a "TL;DR" box onto everything because someone said LLMs need it.

I found no formatting guidance from OpenAI, Anthropic or Perplexity for publishers. Their help pages blocked automated fetches in earlier checks, so I haven't ruled it out.

The one research finding worth knowing

The GEO paper (Aggarwal and colleagues, KDD 2024) is the most cited study behind "write for AI" advice, so it's worth knowing what it measured (research finding, AS-11). The authors took a fixed set of retrieved sources, edited one of them in different ways, and measured how much of the generated answer drew on it. Adding citations to reliable sources, quotations and statistics raised its share by roughly 30–40% on their main metric. Making the text more fluent helped too. Classic keyword stuffing didn't do well.

What it doesn't show: whether a page gets retrieved in the first place, how live Google AI Overviews behave, or anything about TL;DR boxes or chunk sizes. Effects varied by subject area. It's a useful hint that specific, sourced content does better once it is in the candidate set. It isn't a ranking study.

The page shape we use

This is our method (hypothesis, AS-14). It's built to serve the reader first and to stay inside what Google and Bing document. I make no claim that it improves rankings or citations. It is a sensible default you can test.

Part	What goes there	Why (and the evidence level)
Title	What the page delivers, in the words a buyer uses. Distinct from every other page on the site. Brand short, at the end, or left off.	Google's title advice (M1-08, AS-05). No length target; front-loading the key words because display is truncated is our inference.
Main heading	One heading that is clearly the most prominent text. Same promise as the title, not necessarily the same words.	Google's title-link advice (AS-04); Bing's alignment advice (AS-09).
Answer	The first one to three sentences answer the question the page exists for, with the specific fact: the number, the yes/no, the limit. No label needed.	Reader help. People-first questions on complete answers (AS-08). Bing's liftable-statement advice (AS-09). No platform documents placement as a ranking rule.
Who it's for	One or two lines on who this fits and who it doesn't.	Our method. Saves the wrong reader a click.
Specifics and proof	The details a buyer can check, plus first-hand material: setup screens, test notes, your own data, with dates.	Google's "non-commodity", first-hand content (M1-13); sourced statistics did well in the GEO study (AS-11).
Sections by reader question	Headings that name the question ("Does it sync both ways?", not "Learn more"). Each section opens with its own answer sentence, then the detail.	Google: headings for navigation (AS-05, AS-06). Bing: descriptive headings (AS-09).
Tables and lists	Only where the content is a comparison, a set of steps or a list of limits.	Bing recommends them for those cases (AS-09). Tables full of filler help nobody.
Questions	Real follow-up questions from sales calls, support tickets or Search Console queries, answered briefly. Skip it if there are none.	Bing suggests Q&A pairs (AS-09). Don't expect a Google rich result (AS-01).
Next step	One action that fits the page: trial, demo, docs, migration guide.	Our method.
Dates and author	A visible "last checked" date on facts that change, and a named author. Change the date only when the content changes.	Google lists changing dates to look fresh as a warning sign (M1-09).
Meta description	One or two plain sentences with the page's specific facts. Unique per page.	Google's description guidance (M1-07). Expect Google to use page text instead much of the time (AS-03).

What the template leaves out on purpose: a word count, a keyword density, a placement checklist, a "TL;DR" label, and FAQ schema written for rich results. Length is whatever the reader's decision needs. A pricing-limits page might be 300 words, and a migration guide might be 3,000.

For bottom-of-funnel pages, the BOFU pages article covers what each page type needs and where the doorway line sits.

A worked example (invented)

Take a fictional scheduling tool, Quillstead, and a page answering "does Quillstead work with Outlook calendars".

A folklore-shaped page opens with "In today's fast-paced world, calendar integration is more important than ever", repeats "Quillstead Outlook integration" in every heading, and ends with a five-question FAQ written to carry keywords.

Our shape opens with: "Yes. Quillstead syncs with Outlook and Microsoft 365 calendars both ways, on all paid plans; new events appear within about two minutes in our tests (last checked 2026-10-06)." Then one line saying shared mailbox calendars aren't supported yet. Then numbered setup steps with real screenshots, a short table of which event fields sync and which don't, a section on common errors from the support log, and a link to start a trial with the integration preselected.

The second page is shorter, and every sentence on it is checkable. All the product facts in this example are invented.

How to test it on your own site

A before/after change on one page doesn't show cause. Updates, seasons, launches and competitors all move numbers. Test the template as a set.

1. Pick a matched group. Twenty or more pages of the same type, with similar traffic. Split them into a treatment half and a control half you leave alone.
2. Change one element at a time. For example, rewrite only the opening answer, or only the titles. If you change everything at once, you can't tell what worked.
3. Read Google Search Console by page for clicks, impressions, CTR and position over equal windows before and after, for both halves (M1-15). Note that Google may have rewritten your title or snippet. Check what actually shows in results.
4. Read AI surfaces separately. Google's Generative AI report shows AI Overviews and AI Mode impressions by page (M1-17). Bing's AI Performance report shows citations and grounding queries for Copilot and Bing (N1-10). Keep mentions, citations, referral sessions and signups as separate numbers.
5. Read the business outcome. Key events and qualified pipeline from the treated pages, not just traffic.
6. Size it honestly. Small B2B sites often can't detect small changes. If the difference is inside normal week-to-week noise, report it as an observation, not a result.

Checklist

• One distinct, descriptive title per page. No keyword lists, no fixed length.
• One clearly prominent main heading that makes the same promise.
• The answer to the page's question in the first few sentences, with the specific fact.
• Headings that name reader questions. Heading order kept for accessibility, not for rankings.
• Tables and lists only for comparisons, steps and limits.
• First-hand proof and dated facts.
• A short, specific meta description. Accept that Google will often use page text instead.
• No word-count target, density target or placement formula in your brief.
• No FAQ schema added in the hope of a Google rich result.
• No llms.txt or Markdown copies created for Google's sake.
• Changes tested on a matched group against a control.

If you want a second pair of eyes on your priority pages, RankPropel's audit and baseline sprint reviews page shape alongside measurement. The method above works just as well if you run it yourself.

Sources

Google Search Central: optimizing for generative AI features (page dated 2026-07-10), SEO Starter Guide (2025-12-10), title links (2025-12-10), snippets (2026-04-20), featured snippets (2025-12-10), creating helpful, people-first content (2026-10-05), spam policies (keyword stuffing; 2026-08-28), latest documentation updates (FAQ rich result deprecation, May and June 2026), blog posts Changes to HowTo and FAQ rich results (2023-08-08) and Google does not use the keywords meta tag in web ranking (2009-09-21). Google: How Search Works, ranking results. Microsoft: Optimizing your content for inclusion in AI search answers (2025-10-08), AI Performance in Bing Webmaster Tools (2026-02-10). Research: Ahrefs, How often does Google rewrite meta descriptions? (2020); Aggarwal et al., GEO: Generative Engine Optimization (KDD 2024); United States v. Google LLC, Memorandum Opinion (D.D.C., 2024-08-05). All retrieved 2026-10-06.