SEO for SaaS: Build a Growth Engine, Not a Blog

I have looked at a lot of SaaS websites in the last decade, and the pattern repeats. A handful of product pages that never change, a blog with three hundred posts nobody reads, a pricing page, and a signup button. Organic traffic grows for a while, mostly on informational posts, then flattens. Signups from organic stay small. Someone concludes that SEO does not work for their category.

It usually does. What did not work was building a blog and calling it a channel. This guide sets out the alternative: a page system organised around the jobs buyers are trying to get done, a content plan that starts from the bottom of the funnel rather than the top, measurement that counts signups and qualified accounts, and a way to let the product earn the references that make the rest rank. It is the approach behind our SaaS industry work, written out.

Why the blog model fails for most SaaS companies

The blog model made sense once. Publish a lot of helpful articles, rank for informational queries, collect email addresses, nurture them. It still works for a few categories with very long consideration cycles. For most SaaS products it produces traffic that never turns into revenue, for three reasons.

• The people searching ‘how to write a project brief’ are not shopping for project management software. Some of them will be, one day, but you cannot measure that and neither can your board.
• Informational queries are exactly where AI Overviews and answer engines now answer without a click. The traffic that the blog model depended on is shrinking, and the pages that lose it first are generic how-to posts.
• A blog is flat. Three hundred posts with the same template and no relationship between them do not support each other. There is nothing for authority to accumulate in.

The companies that do well from organic look different. Their sites are organised around what buyers are trying to do, most of their organic signups come from a few dozen pages near the bottom of the funnel, and their documentation and product surfaces do much of the ranking. The blog, if it exists, is the smallest part.

The page system

Think of the site as a set of page types, each with one job, linked so that every page strengthens the ones around it. This is the Structure stage of the Lucidens Method applied to software.

Start at the bottom of the funnel

Bottom-of-funnel pages have less search volume and much higher value. A query like ‘Tool A vs Tool B’ or ‘Tool A alternative’ is typed by someone with a shortlist and a budget. A query like ‘what is invoicing’ is typed by everyone, including students. Volume tools will tell you to chase the second. Do not.

Build the comparison and alternative set properly, and do it honestly. The pages that win these queries, in search and in answer engines, are the ones that state where the competitor is stronger. Buyers can tell the difference between a comparison and an advertisement, and so can the systems that now summarise these pages.

• One page per competitor pair that buyers actually compare, plus one ‘alternatives to X’ page for each major competitor. Check the panel of buyer questions before writing any of them.
• A real feature table, with the competitor’s strengths shown as strengths. Update it when either product changes and show the date.
• Pricing in plain numbers, with the date checked. Nothing ages faster or costs more trust when wrong.
• A clear statement of who each product suits. ‘If you are a team of two with simple needs, the cheaper tool is fine’ earns more signups than pretending otherwise.
• Integration pages for the tools your buyers already run. These are often the highest-converting organic pages on a SaaS site and the least competed.

Let the product earn the links

SaaS companies have an advantage most businesses lack: they can build things. A free tool, a public template library, a calculator, an open dataset or a status page attracts references from people who would never link to an article. Those references are what make the rest of the site rank.

• A free version of one narrow piece of the product, usable without signup, with its own URL. The best organic asset many SaaS companies own is a stripped-down calculator or converter.
• Public documentation. Locking docs behind a login removes the pages most likely to be cited by answer engines and linked by developers.
• A public changelog with dated entries. It is crawled often, it signals a living product, and it gives partners something to link to.
• Templates and examples that open directly in the product. Each one is a page with a clear job and a clear next step.
• Original data from the product, published carefully and anonymised. Usage patterns, benchmarks, seasonal trends. Journalists and analysts cite data; they do not cite opinions.

Measure signups, not sessions

The single change that reorients a SaaS organic programme is reporting by page group and by outcome. Sessions flatter blogs. Signups, activated accounts and qualified pipeline reveal which pages are doing the work.

Set the baseline before any page changes, split branded from non-branded, and give the programme four quarters. The method for this is in How to Measure SEO ROI; the only SaaS-specific addition is to follow organic cohorts through activation and retention, because organic-acquired accounts often behave differently from paid ones, and that difference belongs in the case for investment.

Technical notes specific to SaaS

Most SaaS sites share a few technical habits that cap organic growth. They are cheap to fix and easy to miss because everything looks fine to a logged-in employee.

• The marketing site and the app share a domain, and app routes leak into the index, or the app’s robots rules block the marketing pages. Check both.
• Docs live on a subdomain with no links from the main site, so their authority never flows back. Link them properly, or bring them under the main domain.
• Pricing and feature tables are rendered as images or built client-side. Put the words in the HTML.
• Templates and free tools are behind a signup wall. Let the page be seen; ask for the email to save or export.
• The changelog and status pages are noindexed by default on the tool that generates them. Decide deliberately.
• Comparison pages are noindexed out of caution about naming competitors. Naming competitors on your own site is normal and legal in most markets; check the rules where you sell and write factually.

Run the technical audit checklist once against the marketing site and once against the docs. They usually have different faults.

A ninety-day plan

1. 01

   Weeks 1 to 2: baseline and map

   Export thirteen months of Search Console and product analytics. Group pages. Build the buyer question panel and the list of competitors buyers actually compare you with. Decide the measurement.

2. 02

   Weeks 3 to 4: fix the pages that already earn

   Product, pricing and integration pages: one job each, words in the HTML, clear next step, proper internal links. Technical audit on the marketing site.

3. 03

   Weeks 5 to 8: comparisons and alternatives

   Write the set honestly, with dated tables. Add the ‘alternatives to’ pages. Link them from product and pricing pages.

4. 04

   Weeks 9 to 12: one product-led asset

   Ship one free tool, template library or public dataset with its own URL and a plan to tell the people who would link to it. Open the docs if they are closed.

5. 05

   Week 13: first review

   Compare signups by page group against the baseline. Run the prompt panel again. Decide the next quarter from what moved.

The bottom line

• Replace the blog-with-a-signup-button model with a page system built around what buyers are trying to do.
• Build the bottom of the funnel first: comparisons, alternatives, integrations, pricing. Do them honestly and keep them current.
• Use the product to earn references: free tools, public docs, templates, changelogs, original data.
• Report signups, activation and pipeline by page group, with a baseline set before the work and four quarters to judge it.
• Fix the technical habits that are specific to software sites before writing anything new.

Frequently asked questions

Does SEO still work for SaaS now that AI answers many queries?

For informational blog content, less than it did. For the pages buyers use to decide, yes, and increasingly through answer engines as well as search. Comparison, integration, pricing and documentation pages are cited by AI systems because they contain specific, checkable facts. The blog model is what stopped working, not organic.

How many comparison pages should we build?

As many as buyers actually search for, which is usually far fewer than the number of competitors you can name. Start from the panel of buyer questions and from sales call notes. Five well-maintained pages beat forty thin ones, and thin comparison pages damage trust.

Should our docs be public?

Almost always. Public docs rank for long-tail product queries, get linked by developers, and are among the pages answer engines cite most. Keep genuinely sensitive material behind login; open the rest.

How long before organic produces meaningful signups?

Bottom-of-funnel pages can produce signups within a quarter if the site has some authority already. A new domain takes longer. Plan on four quarters before judging the channel, and make sure the baseline and the page groups are set before work starts so that the judgement is fair.

We have a small team. Where do we start?

Fix the product and pricing pages, write the five comparison pages buyers ask about most, and open the docs. That is a quarter of work for one person and it usually moves signups more than a year of blogging.

Is this what Lucidens does for SaaS clients?

Yes. The SaaS industry page describes the engagement shape, and the AOVANCY case study shows the page-system approach applied to a digital-products marketplace. The order of work is the one in this guide.

How this guide was put together

• The guide reflects Lucidens practice across SaaS and technology engagements and the public guidance of the major search engines. It contains no client figures.

Sources

1. Google Search Central: Creating helpful, reliable, people-first content
2. Google Search Central: Spam policies for Google web search
3. Google Search Central: AI features and your website
4. Lucidens: The Architecture of Organic Growth
5. Lucidens: SaaS industry page