01Why funnel stage, not content type
A blog post and a landing page can do the same job or completely different jobs depending on what the reader already knows and wants. Organising a content strategy by funnel stage forces you to ask what a piece of content needs to accomplish, before deciding what format it takes.
The SaaS SEO pillar page introduces this as a four-stage table; this page expands each stage with concrete page types and the reasoning behind sequencing them the way I do.
02Problem-aware: category and workflow education
At this stage the reader hasn’t identified software as the solution — they may not even know a category of tool exists for their problem. Content here should never mention your product by name in any meaningful way. Page types that work: “what is [workflow],” “how teams currently handle [problem] without a dedicated tool,” glossary entries defining category terms, and explainer content around the underlying process.
This is also the content most likely to be skipped by teams under pressure to show pipeline quickly — and the content most responsible for topical authority, since it’s the layer that would be useful to someone who never buys anything.
03Solution-aware: comparison and decision-criteria content
The reader now knows tools exist and is trying to work out how to choose between approaches — not yet between specific vendors. Page types: “how to choose a [category] tool,” framework-driven comparison content that names criteria rather than products, and use-case pages segmented by role or industry that help a reader recognise their own situation.
04Product-aware: the commercial core
The reader is now evaluating specific vendors, including yours. This is where feature pages, integration pages, pricing pages and named-competitor comparisons live — the Core layer of the topical map. Page types: feature-specific landing pages, integration directory pages, pricing and plan-comparison pages, and “[Product] vs [Competitor]” pages.
This content converts well precisely because the Outer-layer content from the two stages above already did the work of building trust and category understanding. Product-aware content alone, without that groundwork, tends to convert only readers who arrived already convinced — see Topical Authority for SaaS for why feature pages alone don’t build the authority that gets readers to this stage in the first place.
05Post-purchase: the overlooked organic asset
Documentation, advanced use-case guides, and integration walkthroughs written for existing customers double as organic content for prospective ones — searchers evaluating a tool frequently look at its public documentation to judge depth and maturity before buying. Treating documentation purely as a support cost, rather than partly as content strategy, is a common missed opportunity in SaaS specifically, since documentation for a physical product rarely gets read by prospects the way SaaS docs do.
For how this all sequences into a build plan, see SaaS SEO Strategy.