Add decision detail to product pages for AI recommendations

Why this matters

Name the buyer, show the workflow, price and limits so AI can justify recommending you

Before you start

• Edit access to the product or service page templates
• Approved pricing details and the date they take effect

How to apply it

1. Name the customer and the job on the page

   Open the product or service page and add a short section that states which customer segment it is for and the specific task it finishes, using the segment and task names buyers use.

   Check: The rendered page contains an H2 naming a customer segment and at least one sentence naming the completed job, not just feature adjectives.

2. Show the workflow with screenshots or a demo

   Document the main flow step by step with annotated screenshots or an embedded short demo, and give every image descriptive alt text that names the step.

   Check: The page includes at least three screenshots covering consecutive flow steps, or an embedded demo, and each image tag has non-empty alt text.

3. Publish pricing with plan, usage and date General best practice

   Add a pricing block that lists the plan name, the usage limits or contact count it covers, and the date the price was last checked.

   Check: The pricing block shows plan, usage limit and a visible date such as "Pricing as of September 2026".

4. Compare against alternatives including limitations

   Add a comparison section that names the alternatives buyers actually consider and lists where this product is weaker or out of scope next to the differences in its favour.

   Check: The comparison section names at least one alternative product and contains an explicit limitations entry.

5. Align product facts across site and profiles General best practice

   List the core facts (price, usage limits, supported flows) and check each one against the homepage, pricing page, product page and any directory or social profiles you control; correct every mismatch.

   Check: A grep for the price strings across page templates returns only values that match the published pricing page.

6. Place the trial or demo link beside the proof General best practice

   Put the trial signup or demo booking link inside the section that contains the workflow and pricing proof, not only in the site header.

   Check: A link with href to the trial or demo path appears inside the proof section and returns a 200 response.

<goal>
target section index signal render alt anchor link anchor section section intent heading anchor.
</goal>

<context>
template verify locale page crawler breadcrumb effort intent caching query cluster caching priority pipeline.
</context>

<discover_first>
render crawl breadcrumb redirect schema caching serp page markup target crawl metadata measure schema.
</discover_first>

<constraints>
breadcrumb anchor payload pipeline payload intent target snippet heading locale index schema render anchor.
</constraints>

<plan>
intent snippet audit template report template route snippet locale pipeline crawler layout snippet target.
</plan>

<verify>
route pipeline report content serp layout caching breadcrumb template breadcrumb priority signal locale markup.
</verify>

<report>
index cluster layout route sitemap sitemap crawl locale heading signal link anchor caching canonical.
</report>

Source: @borjafat on 2026-09-28 · original post · report an error