SaaS SEO
Search that fills the trial queue, not the traffic chart
For a software company, organic traffic is a proxy metric and a misleading one. We build search around the stages a buyer moves through — comparison and alternatives searches first, then the category content, then the top of funnel that only pays off if the rest exists.
Where the money is
Three stages, three completely different jobs
Almost every underperforming software content programme is heavy at one end and empty at the other. Naming the stages makes the imbalance obvious.
| Dimension | Bottom of funnel | Middle of funnel | Top of funnel |
|---|---|---|---|
| What the searcher is doing | Choosing between named options, often with a shortlist already agreed. | Working out what category of tool solves this and what good looks like. | Trying to solve the underlying problem, possibly without buying anything. |
| Typical page | You versus a named competitor, alternatives to a competitor, pricing explainer, integration page. | Category explainer, buying guide, evaluation criteria, requirements checklist. | How-to guide, template, calculator, glossary entry. |
| Volume available | Small | Moderate | Large |
| What it should be measured on | Trials and demo requests started from the page. | Assisted conversions and progression into the bottom-of-funnel set. | Email capture, return visits and downstream assists — never direct signups. |
| How it usually fails | Never built, because naming competitors felt uncomfortable. | Written as a keyword essay with no point of view about how to choose. | Published at volume, measured on sessions, and mistaken for the whole programme. |
| If this is all you have | You convert well but run out of demand quickly. | You look credible but never enter the shortlist conversation. | You get a traffic chart your board likes and a pipeline number they do not. |
The searches that matter
What a software buyer types on the way to a decision
Example patterns, not volume claims. The first group is the one most software companies avoid and the one that converts hardest.
Comparison and alternatives
Late-stage, low volume, and the highest intent searches in the category. Someone is answering them about you already.
- competitor name alternatives
- tool a vs tool b for small teams
- is competitor name worth the price
- cheaper alternative to enterprise tool
- competitor name reviews from actual users
Category and evaluation
The searcher has accepted they need to buy something but has not decided what. This is where a point of view about how to evaluate wins.
- best tools for revenue forecasting
- what to look for in a compliance platform
- requirements checklist for choosing a helpdesk
- open source versus commercial options for this
Integration and technical fit
Often the searcher is an engineer or an administrator who can veto the purchase but never appears in a marketing persona document.
- does this integrate with our accounting system
- api rate limits for this platform
- export data from legacy tool into new system
- single sign on support for this product
The problem before the category
Where category creation actually gets traction. These people do not know your category name and would not search for it.
- how to stop spreadsheet version conflicts across a team
- why do our monthly reports take three days
- manual process for tracking renewals template
These are examples of how customers in this market search, drawn from keyword research and from the questions that come up on sales calls. They are illustrative, not a volume claim — the actual demand in your area is something we size before recommending anything.
Two decisions people get wrong
Programmatic pages and the marketing-site boundary
Programmatic content has an unfair reputation, earned by a period when it meant pushing a list of city names through a template. What actually decides whether a set of generated pages is useful is the data underneath it. If you support four hundred integrations and each one has genuine setup steps, field mappings, limitations and a real screenshot, then four hundred integration pages are four hundred useful pages that happen to be assembled by a build process.
If the only variable is a name in a heading, you have built the thing search engines now describe explicitly as scaled content abuse. We assess the dataset before recommending the technique, and we have told clients not to do it more often than we have built it.
The second decision is where things live. Software companies end up with a marketing site, an application, a documentation site, a community, a status page and a blog, spread across whatever domains and subdomains each team could get provisioned fastest. Every split costs internal linking and makes the accumulated authority harder to concentrate.
The practical rule is that anything a prospect might read before buying belongs on the primary domain if the platform allows it. Anything only a logged-in customer sees can live wherever it is easiest to run. The awkward middle — documentation and help centres — is worth arguing about, because it is often the most linked-to content a software company owns.
The work
Four workstreams, weighted from the bottom up
The order is the opposite of how most content programmes are built, and that is the point.
The bottom-of-funnel surface
Comparison pages, alternatives pages, pricing explainers, use case pages and integration pages. Small volume, difficult to write well, and responsible for a disproportionate share of organic trials in almost every software company we have looked at.
Product-led content
Content built around what the product actually does, ending somewhere in the product rather than in a form. A free tool, a template that opens in the app, a calculator that produces a result worth saving. The link between the article and the surface is the whole design.
Programmatic surfaces with a quality gate
Where a real dataset exists, a generated page set with a written rule about what makes an individual page worth publishing — and a mechanism that keeps the ones which fail the rule out of the index rather than publishing the full matrix and hoping.
Library maintenance
Most software companies do not need more articles. They need the two hundred they already have judged: which to update, which to merge, which to redirect, and which to remove because they attract readers who will never buy and outrank the pages that would convert them.
How we work
What we hold to on a software account
What we commit to
- Reporting on trials, demos and qualified pipeline, with sessions as context rather than as the headline
- Writing comparison pages that name the cases where a competitor is the better fit
- Assessing the dataset before recommending any programmatic page set, and saying no when it is thin
- Recommending pages be removed or merged when they are costing more than they earn
- Working from the same positioning document product marketing uses, not a separate keyword list
- Telling you when a search opportunity exists but your product genuinely does not serve it
What we will not do
- Publish generated pages where the only difference between them is a variable in the heading
- Write competitor comparisons that misrepresent what the competitor does
- Chase volume on searches made by people who could never buy your product
- Measure a six-month sales cycle on last-click attribution and present it as truth
- Promise a trial or pipeline number before the demand has been sized
Questions
What growth leads ask before starting
Why is our blog traffic not turning into trials?
Usually because the articles answer questions that come months before a purchase decision, and there is nothing on the page that makes sense as a next step for someone at that stage. A reader who searched a general how-to question is not in the market yet, and asking them to start a trial is asking too much too early.
The fix is rarely to write better versions of those articles. It is to build the pages that sit at the other end of the funnel — comparisons, alternatives, integration and use case pages — and then use the top-of-funnel content to feed them rather than to convert directly.
Should we publish comparison pages against named competitors?
Yes, if you can do it honestly. Those searches are being made and they are being answered by someone — usually a competitor, an affiliate review site, or a forum thread you have no control over. Being absent does not keep you out of the comparison, it just means you do not get a say in it.
The version that works names the cases where the competitor is the better choice. That single act of honesty is what makes the rest of the page believable, and it tends to filter out the trials that were never going to convert anyway.
Is programmatic SEO safe?
It depends entirely on whether there is real data behind it. Pages generated from a genuine dataset that a user would want — every integration you support, every template in your library, every supported jurisdiction with its actual rules — are useful pages that happen to be built from a database.
Pages generated by pushing city names or job titles through a template with no underlying substance are the thing search engines now specifically describe as scaled content abuse. The technique is the same; the data is what decides which one you have built.
Our category does not exist yet. Can SEO work?
Not for the category name, because nobody is searching for a term they have never heard. But almost every new category exists because an old, painful way of doing the job is still in use, and people search for that constantly.
So the search work targets the problem, the workaround and the incumbent tool, while the category creation happens through channels where you can reach people who are not searching at all. Search captures existing demand well and creates it slowly.
Should content live on our marketing site or on the app subdomain?
Marketing content and documentation should be reachable from the primary domain wherever the platform allows it, because that is where the accumulated authority sits and because splitting them makes internal linking much weaker.
The pragmatic exception is when the help centre or community runs on a third-party platform that only supports a subdomain. That is workable. What is not workable is a marketing site on one domain, a blog on a second and a help centre on a third, with no linking between them.
See who currently answers the comparison searches about you
Before the call we look at what ranks for your brand name plus alternatives, versus, and reviews. It is usually a competitor or an affiliate site, and seeing the actual results tends to settle the internal debate about whether to build those pages.
Related
Where to go next
- selling to a committeeMost software purchases above a certain price are committee decisions.
- our work with software companies
- improving trial conversionOrganic visits are wasted if the signup flow leaks.
- expanding into new marketsSoftware companies hit this decision earlier than most.
- building B2B pipeline
Last updated · Reviewed by Zubair Afzal