The guideChapter 4

Pages that answer for your brand

Published Last reviewed

In short

  • Give buyers a public source for current prices and product limits, with the conditions needed to interpret each answer.
  • We recommend visible brand facts pages for accuracy, without selling them as a guaranteed route to recommendations.
  • Correct the underlying information before changing an update date, in line with Google's warning about artificial freshness. 1

Start with the question that names your brand

Imagine a buyer asking whether your product includes a particular integration. Your homepage says it connects with leading platforms. The help centre describes a connector that requires a paid add-on. Which answer should the buyer rely on?

Resolve that ambiguity on your own site first.

Our recommendation is to prioritize the questions that already name your brand. Define the correct answer, give it a public home and verify that related pages agree. Treat this as work on factual accuracy and the buying decision.

Keep discovery questions in a separate review. "Does this product support my workflow?" asks something different from "Which provider should I choose?" A correct product description doesn't establish a recommendation.

Google advises publishers to satisfy their intended audience and provide information that helps people achieve their goal. That supports the editorial principle, without proving an AI citation lift. 1

Make the pricing page sufficient for a buying conversation

Write the pricing explanation so a buyer can repeat it accurately to a colleague. Put the billing basis beside the amount. Show the currency and any minimum commitment wherever you publish a price.

For subscriptions, explain what the buyer receives under each plan. Identify usage limits and what happens when they are exceeded. State whether optional services require an additional payment.

For a service priced by quotation, say that plainly. Explain the factors used to prepare the quote and what information a prospective customer needs to provide. Publish a starting price only when it describes an offer someone can actually buy.

Consider a hypothetical plan advertised as a monthly amount but sold only under an annual contract. Write the annual billing condition beside that amount. Don't leave the reader to discover it at checkout.

Use a comparison table if the plans share meaningful attributes. A cell should contain an interpretable answer, such as an included feature or a clearly stated limit. Explain the meaning of "custom" wherever it affects the purchase.

Keep the material information in readable text. Google recommends textual access to important content and consistency between visible information and structured data. 2

Our editorial check is simple. Ask a colleague to describe the offer using only the public page. If they need private notes to explain the conditions, add the missing explanation.

Describe the product as it works today

Open a product page with its purpose and intended user. Follow with enough detail to decide whether it fits the task. Give limitations the same attention as capabilities.

For integrations, distinguish a native connection from an API that requires development. Explain which plan supports the connection and where setup instructions live. Avoid using a partner logo as the entire explanation.

For a feature under development, label its status. Keep roadmap ambitions separate from capabilities a customer can use now. If availability depends on a region or product edition, state that next to the feature.

A hypothetical export feature makes the distinction concrete. "Export your data" leaves unanswered whether attachments are included. An explanation of supported export formats and exclusions gives a buyer something they can check.

Link the claim to relevant public documentation. We recommend keeping general setup instructions available without an account, while restricting customer information appropriately.

Give each subject a clear home. Explain the feature on its product page, then link to the procedure in the help centre. When those explanations differ, resolve the disagreement before adding more content.

Google warns against creating pages for every query variation primarily to manipulate search rankings or generative AI responses. Consolidate closely related questions into useful pages. 5

Publish brand facts people can inspect

A facts page should help someone identify your business and check its public claims. Link it from a sensible location, such as your About page. Write for a prospective customer or journalist who needs an unambiguous answer.

Start with the trading name and explain any relationship to a different legal entity. Describe the product or service in ordinary language. Include relevant markets and the official channels someone should use to reach the business.

Publish figures only when you can explain what they measure. If you state a customer count, define whether it includes trials or inactive accounts. Add the period or reference date. Leave out a number you cannot substantiate.

For a published study, link to its method. Explain the population and the collection period before inviting anyone to interpret its result. A number without that context gives the reader too little to assess.

Treat a certification similarly. Identify what is certified and where its scope can be checked. Don't imply that a company-wide label covers every product when the certificate describes a narrower scope.

These are our recommended editorial checks. We don't claim that a dedicated facts page makes an engine choose your brand.

Google documents Organization structured data as a way to clarify organizational identity and administrative details. That is a defined use for markup. It isn't evidence of an increase in AI recommendations. 3

Keep every version of a fact consistent

Choose a responsible person for each fact that changes. The pricing owner should approve price changes. The product owner should confirm availability before a writer updates a feature claim.

Maintain a working record of the approved statement and its public URL. Include where else that statement appears. Use the record to find copies when something changes.

Imagine that an integration moves from a paid add-on into a standard plan. Update the plan comparison and the integration page together. Check the setup documentation for references to the old requirement.

Review the structured data during the same edit. Google's guidelines require current information and prohibit marking up content that readers cannot see. Valid syntax alone doesn't satisfy those requirements. 4

Our policy is to use schema for accurate description and applicable search eligibility. We don't sell schema, FAQ formatting or added statistics as independent citation levers.

The same restraint applies to llms.txt and artificial content chunks. Google says its Search system ignores llms.txt and does not require tiny content fragments. Those statements describe Google Search, without establishing how every other service behaves. 5

Use headings and tables when they help the reader compare information. Keep the facts visible on the page that explains the offer.

Review the answer one claim at a time

Our suggested review starts with real questions from sales or support. Record the expected answer using the approved public page. Then inspect what each engine actually says.

Keep the question exactly as tested. Save the answer with its date and the engine used. Note the market or language where relevant. Retain cited URLs so another reviewer can follow the same sources.

Assess individual claims. An answer can name the correct product while misstating its billing terms. Mark each claim as correct, incorrect or unresolved against the current source. Treat an omitted detail separately from a false statement.

Suppose an answer says a connector is included in every plan. Your published documentation says it requires an add-on. Record the exact mismatch and inspect the page cited for that sentence.

If your own page is ambiguous, correct it. If another publisher carries the outdated claim, retain that URL for a separate correction request. Don't rewrite a correct product page merely to match an incorrect answer.

After the source changes, repeat the same questions and preserve the new responses. Report whether the specific error persists. Keep answers that omit your brand in the record too.

This is a practical review method, not a controlled experiment. A corrected answer after publication doesn't isolate the cause of the change. We don't promise how quickly an engine will reflect an edit.

For the related distinction, read our explanation of a cited website without a brand recommendation. Keep factual accuracy separate from how often a brand is recommended.

Update the information before updating the date

Google identifies changing page dates without substantial content changes as a warning sign of content made for search engines. It doesn't recommend date changes as an optimization tactic. 1

Our rule is to record a meaningful edit before advancing the modification date. A revised price qualifies. So does a corrected feature limit or a new explanation of an existing buying condition.

Keep the original publication date. When you display an update date, make it agree with the relevant structured data. Google's date guidance calls for consistency between visible dates and their structured equivalents. 6

Record the actual change in a short editorial log. "Updated integration availability after its release" tells a future reviewer what happened. "Refreshed for AI" doesn't identify a change they can verify.

Have the person responsible for the fact review the edited page. Recheck related pages before closing the task. If the content remains accurate after a review, record that review without inventing a substantive update.

Start with the most consequential unresolved error. Correct its public source, then check the answer again.

Sources

  1. Google Search Central, Creating helpful, reliable, people-first contentAccessed Back to the text, first mention of source 1
  2. Google Search Central, AI features and your websiteAccessed Back to the text, first mention of source 2
  3. Google Search Central, Organization structured dataAccessed Back to the text, first mention of source 3
  4. Google Search Central, General structured data guidelinesAccessed Back to the text, first mention of source 4
  5. Google Search Central, Optimizing your website for generative AI features on Google SearchAccessed Back to the text, first mention of source 5
  6. Google Search Central, Influence your byline dates in Google SearchAccessed Back to the text, first mention of source 6