An alternatives or comparison page puts one product next to a competitor, or next to the group of products a buyer is weighing. These pages work when they are honest: the reader can see what was compared, how, by whom and as of when. Whether a rival's name appears in the title is a smaller decision than whether the page actually helps someone choose.
The advice here is for SaaS marketers, B2B product teams and the agencies that write for them. Because rival brands are involved, one caution: this is not legal advice. Comparative statements, trademark use and unfair competition rules differ by country, and only a qualified lawyer can judge a specific page.
Short answer: Google's helpful content guidance gives an example from product reviews, which is to show how many products were tested, what the results were and how the testing was done. The same standard carries over to comparison pages. Using a competitor's name in a headline has no universal yes or no. The closer the name is to an accurate, non-misleading description of what the reader searched for, the lower the risk, though it never reaches zero.
What the searcher is trying to do
Someone who types a product name plus "alternative" or "vs" is usually close to a decision. They may be unhappy with a current tool, they may be building a shortlist, or they may need a justification to take to a manager. Handing that person a sales pitch dressed as a comparison is the most common failure of the format.
Narrow, switch or justify: the three jobs
Most of these searches fall into one of three jobs. The first is narrowing: the reader has ten options and wants to see quickly which two or three fit. The second is switching: they already use a product and want to know how painful a move would be and what they would give up. The third is justifying: they need a neutral-looking summary to show a decision maker. Tell the reader in the opening which job your page does. A page that tries all three at once usually does none well.
Why the page exists at all
Google's guidance on helpful, reliable, people-first content (Opens in a new tab) frames the "why" of a page as perhaps the most important question. Content should exist because it would help people who arrive directly on the site, and content made mainly to attract search visits is not what Google's systems aim to reward. For a comparison page the practical reading is simple: write it for the reader's decision, not to capture a query pattern.
The same page lists warning signs, including producing many pages on different topics in the hope that some rank, mainly summarizing what others have said, and targeting a specific word count because of a belief that Google prefers it. A site that publishes one near-identical page for every competitor, changing only the name, resembles that pattern. Each page needs information that exists only for that rival.
Why a table that always wins backfires
Readers do not expect your product to win every row. A table in which the author's product is best at everything looks like marketing, and readers know it. They are more likely to trust a page that says plainly where a competitor is stronger, because that admission is what makes the other rows believable. A page that can say "this is the better choice if your situation looks like this" earns more confidence than one that cannot.
Alternatives, head-to-head or category guide
| Page type | Reader's question | What the page promises | Common trap |
|---|---|---|---|
| Alternatives to one product | What can I use instead of X? | A short list judged against stated criteria | Ranking your own product first by default |
| Head to head | Which of these two fits me? | The same criteria applied to both | Choosing criteria that favor you |
| Category guide | How do tools of this type differ? | Selection criteria and groupings explained | A generic list with no original information |
If you sell one of the products, say so near the top. If you are writing an independent category guide, say that instead. Hiding which side you are on makes the whole page suspect.
Laying out the page
A fixed order reduces hesitation while drafting. The sequence below suits a head-to-head page. For category guides, replace the two-product table with explained criteria.
The seven blocks, top to bottom
- Short answer plus ownership: who each product suits, in two sentences, and who wrote the page.
- A brief chooser that matches situations to products.
- The criteria table with its caption underneath.
- Strengths and weaknesses of each product, including your own.
- Switching notes: data export, rebuild time, learning curve.
- Frequently asked questions.
- Conclusion with one call to action.
The chooser: matching situations to products
The chooser comes before the table and helps readers recognize their situation: "If your team is small and wants a quick setup, lean toward this product", "If you need many integrations and detailed permissions, lean toward that one". Include situations in which your own product is not the best fit. This is often the most-read part of the page, because readers look for their own conditions before scanning rows.
A CRM vendor's version
Example scenario: A CRM vendor prepares a page comparing its product with a larger rival. The team lists the five questions prospects ask most: import from spreadsheets, email sync, reporting, permission roles and exports. Each cell is checked against the rival's help center and the vendor's own product. The team states that its reporting is lighter than the rival's and adds a line saying that teams with heavy reporting needs may prefer the rival. Under the table go the testing date, the note that rival cells come from the rival's public documents, and a line saying the page belongs to the CRM vendor. The page reads less like an ad and gives a prospect real grounds for trust at decision time.
Cases where the page should not exist
If you cannot actually try the rival product or do not have enough reliable data to compare, do not write the page. A thin comparison misleads readers and leaves you exposed. Spend the time opening a trial account, reading the documentation and consulting a product specialist. If you have nothing concrete about the rival, an impartial buying guide for the category is a safer alternative.
Table design: criteria, cells and evidence
The table is the backbone of the page, but its value sits in what the cells say and what supports them. The same layout can be honest on one site and misleading on another.
Rows come from buyer questions
Row selection is where bias hides most easily. If every row is a feature where your product leads, the table can be accurate in every cell and still mislead. Build the list from real buying questions: pricing model, setup effort, integrations, support options, data export, contract terms, admin controls. Sales call notes and support tickets are a better source of rows than a brainstorm in the marketing team.
Then add the rows your product deliberately does not cover. A tool built for small teams may be thin on enterprise permissions. Writing that as a row costs a little in the short term and gives the rest of the table its credibility.
Qualifiers instead of bare checkmarks
A bare checkmark hides detail that matters. Whether a feature exists is only part of it; the plan it sits on, any add-on it needs and how mature it is all change the decision. Use short qualifiers: "yes, higher plans only", "needs a paid add-on", "not stated in public documentation". If you cannot confirm a cell, say it could not be confirmed instead of guessing. Guessing about a competitor is an error and also an exposure.
Example scenario: A page compares two e-signature tools on "bulk sending". Your tool supports it natively. The competitor's public help center describes it only through an integration. Writing "no" would be unfair and could be wrong. A better cell reads "through an integration, per the vendor's help center; check the vendor's current plans".
Ranking the evidence behind a cell
Google's guidance points to testing and to evidence of the work involved, such as photographs, as ways reviews earn trust. For software comparisons you can apply the same idea in three levels.
- First-hand use: you opened a trial account, followed the steps, took screenshots and recorded the version you tested.
- The vendor's own documents: pricing page, help center and release notes, cited with the link and the date you read them.
- Third-party opinion: the weakest level. Quoting reviews without saying who wrote them or when carries unverified claims onto your page.
You do not need to label every cell for readers, but keep an internal record of which level supports each one. When a competitor asks where a statement came from, you should be able to answer within minutes.
The caption under the table
Place a short note beneath the table. It should say what was tested and on what date, which items come from the vendor's published documents, and who owns the page. Three sentences do more for trust than a long methodology section, and they leave context for anyone who quotes or copies the table.
Review markup and star ratings
Adding star ratings to a comparison can be tempting. Google's review snippet documentation (Opens in a new tab) asks that marked-up reviews be about a specific item and warns against supplying review information about a category or a list of items. It also says not to aggregate reviews or ratings from other websites, not to use fake or undisclosed incentivized reviews, and to keep marked-up review content visible on the page. A page that covers a list of tools with one combined rating therefore sits awkwardly with that guidance. The documentation has no separate rule for comparison pages, and it does not promise any rich result.
Rival names in titles and copy
This section is a list of questions a marketing team should ask, not a legal analysis. Rules on comparative statements and brand use differ between countries, and a lawyer who knows the relevant jurisdiction should review a high-stakes page.
Does the name describe or mislead?
Using a rival's name to describe accurately what the reader is looking for is one thing. Using it so that readers think they are on the rival's site, or that the products share an origin, is another. The first informs; the second misleads. Titles and meta descriptions are the first things a reader sees, so clarity matters most there.
The separate risks of putting competitor names into advertising are covered in using competitor brand names in ads and trademark risks. That article is about ad copy. This guide is about a comparison page on your own site, where platform rules and expectations can be different.
Warning signs to check
- Check the rival's brand guidelines before using its logo or visual identity.
- Do not scatter the rival's name through the page as hidden keywords. Google's spam policies describe keyword stuffing as loading a page with keywords in an unnatural or out-of-context way.
- Put your own name in the title next to the rival's so ownership is clear.
- State negative claims only to the extent you can prove them, and show the source.
- Be ready for the rival's claims about you to appear on the page too; a fair page does not bury them.
When the page drifts toward spam patterns
Google's spam policies (Opens in a new tab) describe several practices, including misleading functionality, hidden content and doorway abuse. A comparison page does not fall into these by default, but two patterns are red flags. One is a page that draws in people searching for "X alternative" and then offers nothing except a sales form aimed at the rival's customers. The page informs no one; it only redirects. The other is a set of near-identical pages that differ only in the competitor name. The policies describe doorway abuse as pages built to rank for near-identical queries that funnel users to less useful intermediate pages. Not every templated comparison page matches that definition, but pages with their own information per rival stay clear of it.
Giving the rival notice
Google's documentation does not address this, and no general rule can be given. In practice, before publishing a page with sharp claims, check that nothing contradicts the rival's public documents and consider a legal review for anything contentious. List a contact address on the page so that a correction request can be handled quickly and with a paper trail.
Title test for a competitor name
| Question about the title | If yes | If no |
|---|---|---|
| Does the rival's name accurately describe what the reader typed? | The name stays a candidate | Leave the name out |
| Does the title show whose page this is? | No change needed | Put your own brand beside the rival's |
| Can the page back up every claim the title makes? | No change needed | Soften the claim or cut it |
| Is the rival a large brand, or is the claim sharp? | Get legal input before publishing | Normal editorial review is enough |
Keeping the page current
Comparison pages age faster than almost any other content type. Rivals change prices, ship features and rename plans. A stale comparison is not just old; it is wrong, and it gives the competitor a reason to correct you in public.
Two dates, stated plainly
Show the publication date and the date the facts were last checked, in plain words: "Pricing and features were checked on 2026-11-02 against each vendor's own pages." That tells the reader how old the data is and frames any later change. For fast-moving values such as price, consider writing the pricing model (per user, per usage, flat) in the cell and linking to the vendor's pricing page instead of copying numbers that will expire.
Why cosmetic date changes backfire
Google's helpful content page warns against changing page dates to make content look fresh when nothing has substantially changed, and it says that adding or removing large amounts of content just to seem fresh does not help rankings. Update the "last checked" line only when someone has actually rechecked the facts. If the check found nothing new, updating that line is honest; making artificial edits is not.
Ownership and review rhythm
Give every comparison page an owner and a review interval. For quick-moving categories a quarterly check is a reasonable starting point, and for stable ones twice a year. These intervals are a working suggestion; Google's documents give no figure for this kind of page. Write down the events that should trigger an early review as well: a vendor announcement, a changelog entry, a pricing page change, or a customer pointing out a mistake.
| Area to recheck | What to look for | Where to look | Suggested rhythm |
|---|---|---|---|
| Pricing model | Plan names, billing unit | Vendor pricing page | Quarterly or on announcement |
| Feature rows | Added or removed features | Release notes, help center | Quarterly |
| Integrations | Listed connections | Marketplace or integrations page | Twice a year |
| Your own product | Roadmap or plan changes | Internal product team | Every release |
| Outbound links | Broken or redirected addresses | Crawler report | Twice a year |
When the rival shuts down or is renamed
A rival can shut down or be acquired and renamed. If your page still receives visitors, add a clear note about the current situation or redirect to an updated alternatives page. Leaving old facts live sends readers toward a product that may no longer exist.
Letting readers report errors
Give readers who spot a mistake a way to tell you, and act on reports promptly. Fixing a wrong cell and noting the date of the fix protects the page's reputation better than defending an error.
Internal links and the single call to action
Comparison visitors arrive with commercial intent, which makes calls to action a delicate matter. Push too early or too often and a neutral resource turns into a sales page.
One call, at the very end
Let readers study the table and reach their own conclusion before showing a next step. A single clear call at the close of the page is enough. Dropping "try it now" links inside the table turns it into an ad strip. Keep the evaluative part of the page free of selling language.
Links that answer the next question
A person reading a comparison tends to ask what similar companies did, how a rollout went and who can handle the work. Choose internal links to match. For vendors, the guide on sponsored content for SaaS and software companies explains how to present a product through content. For readers wanting proof of customer outcomes, how to write a B2B case study is a natural next step. And if you want a model for putting offers with different scope onto one scale, the article on a sponsored post quote comparison table and scope normalization shows the logic, which transfers to product comparisons.
Avoiding a link network across rival pages
Do not link every competitor page to every other one. That weakens the claim of being a neutral resource and makes the set look like a link network. Link to a few relevant pages the reader really needs. A single hub page titled for comparisons, with a one-sentence description for each page, serves as a useful index.
If an agency writes the pages
If an agency writes these pages for a client, build the client's legal and product review into the workflow. Say in the contract who is responsible for claims about competitors, and confirm before launch that every cell has a recorded source.
Launch review and after-launch care
A final review catches the issues that cost trust. Use the list below with the page owner and, where the client or company requires it, with legal and product reviewers.
Launch gate in three groups
Evidence
- Every cell has a recorded source and a check date.
- The date the facts were verified is visible on the page.
- At least one area where your own product is weaker is stated plainly.
Fairness and framing
- The opening says who owns the page.
- Rows came from buyer questions, not only from your strengths.
- The rival's name in the title describes accurately and does not mislead.
- Any use of a logo or visual identity was checked against the rival's guidelines.
Page hygiene
- One call to action, placed in the conclusion.
- A contact address for corrections is listed.
- Each rival page carries information that exists only for that rival.
What to watch once it is live
Look at how readers use the page: how far they scroll, whether they reach the table and which links they click. Sales conversations that quote the page, or objections raised about it, are also signals. None of this guarantees rankings; the point is to learn whether the page helps. When you set up measurement, review cookie consent and personal data rules separately.
If a rival disputes a statement
If a competitor disputes a statement, first check your own record. If the statement is wrong, fix it and note the date. If it is right, reply calmly with the source. For anything that arrives in legal language, talk to counsel before answering.
Archiving or removing the page
When a comparison can no longer be kept current, remove it or mark it clearly as archived instead of leaving stale claims live. Plan where its address will redirect and clean up internal links that pointed to it.
Frequently Asked Questions
Is a page per competitor a problem?
Not if each page carries information unique to that rival. Near-identical pages that differ only in the name can resemble what Google's spam policies call doorway abuse or scaled content. Give each page its own criteria, evidence and notes.
Can a rival's name appear in the page title?
There is no single yes or no. Using the name to describe accurately and without misleading what the reader searched for lowers the risk but does not remove it. This is not legal advice; rules on comparative statements and brand use differ by country, so ask a qualified lawyer before publishing a sensitive page.
Is an alternatives page the same as a comparison page?
Not exactly. An alternatives page gives someone looking for options to a product a short list judged against stated criteria. A comparison page puts two products, or a category, side by side on the same criteria. Because the reader's question differs, the opening, the criteria and the conclusion should differ too.
Is star rating markup suitable for a comparison table?
Google's review snippet documentation asks that marked-up reviews cover a specific item and advises against review information about a category or a list. It also says not to aggregate ratings from other sites. It has no separate comparison rule and promises no rich result, so one combined rating on a multi-product page can clash with its guidance.
Do I have to admit weaknesses in my own product?
No rule requires it, but it is a strong practice. If a reader checks the rival's page and finds that you left out a weak area, trust in the entire page drops. A short, clear statement of a weakness usually raises credibility.
Do prices belong in the table?
Prices change often, so it is more durable to state the pricing model, such as per user or per usage, and link to the vendor's pricing page. If you do write a number, put the check date next to it.
How often should the page be rechecked?
Google's documents give no interval for this kind of page. A quarterly check for fast-moving categories and a twice-yearly check for stable ones is a reasonable working suggestion. Change the date only when someone has actually rechecked the facts.
Related guides: SaaS SEO: What to Do in the First 90 Days, Agency Client Access: Search Console Roles and Offboarding, SaaS Integration Pages SEO: Is Scaling to Hundreds Safe?.
Conclusion
A good alternatives or comparison page helps a reader decide. Google's helpful content guidance treats the reason a page exists as one of the key questions and uses product reviews to show that explaining what was tested, with what results and by what method builds trust. In practice that means choosing rows from buyer questions, recording the source of each cell, stating your own weak spots, and showing when the facts were last verified. Accuracy and non-deception are the main tests for naming a rival; beyond that, a lawyer has to judge the page. This guide is not legal advice.
If you need a team to produce pages like this with a defined workflow for criteria, sources and dates, you can look at the content writing service on Akua Adforce; scope and terms are listed on that page.
Post a comment
Please log in to leave a comment. Login