Find and group buy-intent keywords into comparison pages
List the searches that contain alternatives, versus, pricing, best software for or a buying constraint, check which page types Google shows for them, group the ones that need the same answer, and improve an existing page before building a new one. Each page should carry the comparison, proof and next step a buyer needs.
Why this matters
Mine alternatives, versus and pricing searches, then answer each group with one page.
Before you start
- A list of the products or categories the site competes in
- Access to a keyword tool or search engine for modifier research
How to apply it
Build the buy-intent query list
Collect searches that combine your product or category with a buying modifier: alternatives, versus, pricing, best software for, or a specific constraint such as a platform or company size.
Check: A spreadsheet holds the modifier next to each candidate query, with at least one query per modifier.
Check which page types Google shows
Open the results for each query and note whether the top results are comparison listicles, vendor pages, forums or product pages. Record the dominant page type per query.
Check: Every query row has a page-type label taken from the live results page.
Group queries that need the same answer
Cluster the queries whose answer would be the same page, for example all "X alternatives" variants for one product, and assign one target page per cluster.
Check: Each cluster maps to exactly one URL and no URL appears under two clusters.
Improve an existing page before creating one
Search the site for an existing URL that already targets the cluster, using a site: query or the Search Console Pages report, and update that page instead of publishing a competitor.
Check: A site: query for the cluster's main term returns the existing URL, and the content was edited rather than a new URL published.
Add comparison, proof and a next step
On the chosen page, add the comparison buyers need (price, migration, automations or the relevant criteria), a proof element, and a clear next step such as a trial, demo or enquiry.
Check: The rendered page contains the comparison section, a proof element and a call-to-action link that returns HTTP 200.
This happens outside your codebase
Work through the steps above on the named site or dashboard, then record the result in your agent session. There is no repository edit for this tip.
Source: @borjafat on 2026-09-28 · original post · report an error