For SaaS
Be the answer before the demo request.
A SaaS buyer reads for weeks before they talk to anyone: the problem, the shortlist, the alternatives, the price. That reading is searchable, and it is where a pipeline starts.
Comparison and alternatives postsOne plan per marketLinks only to pages you publish
Where a SaaS deal actually starts.
Six shapes of query that sit between the problem and the purchase order. Each one is planned as its own post, with the intent it belongs to written down first.
- The research query
- The problem stated as a question, in the words buyers use before they know the category has a name. Informational posts that hand the reader on to the pages that sell.
- The comparison query
- One product against another, written from a single brief — and the generated in-article image lays the two options out side by side.
- The alternatives query
- Alternatives to a tool they already use, planned only when the query is not already answered by a page your site publishes.
- The how-to query
- The task your product performs, written as the steps someone follows before they have decided to buy anything.
- The integration query
- Pairs with the tools your buyers already run, linking to the page on your site that explains your side of the connection.
- The category query
- The name your buyers use for the whole category, if your site does not already define it somewhere.
Content for the path to the demo.
A plan spread across the buying decision, rather than a cluster aimed at whatever has search volume. The stages below are the ones the plan is built around.
- 01
Research
The problem named the way it is searched, so the first page a buyer lands on is useful before it is persuasive.
- 02
Comparison
The shortlist stage: one product against another, and the alternatives question every evaluation starts with.
- 03
Purchase
The queries asked of pricing, security and integrations — the pages that decide whether a trial starts.
- 04
Expansion
How-to and integration posts for accounts already paying, which is where upgrades and referrals usually begin.
Every post ends by pointing somewhere.
A post that informs and then stops is a post that pays for a competitor’s word of mouth. Each article carries a call to action and internal links to the pages that sell — your pricing, your comparison page, the feature page you actually want ranked.
Those links are resolved against pages your site really publishes, read from the sitemap at publish time. Nothing is linked that does not exist, which is the difference between internal linking and wishful linking.
How internal links are chosen1,204
Clicks
48,910
Impressions
12.4
Avg. position
Multi-market without a multi-market team.
Each language you sell in runs its own plan, its own queries and its own cadence, against one blog on one domain.
Opening a market usually means finding a writer who speaks it, briefing them on the product, and paying per article for the privilege. Here, a language is a line item: 116 are selectable today, and each one gets editorial treatment rather than machine translation of the English archive.
The plan for a market is written around the queries people search in that market, and the calendar is its own. One site can carry the German line, the French line and the English one without any of them competing for the same dates.
- ENEnglish2 posts a week12 / 7planned / live
- DEGerman1 post a week5 / 3planned / live
- FRFrench1 post a week4 / 1planned / live
Same blog, same design — each language gets its own plan and its own dates.
What product marketing still owns.
Positioning is not a brief you can hand over, and category claims are not content operations. The plan is where the pipeline asks your team what it is allowed to say — and where a bad week of entries gets thrown away cheaply.
- The category you claim, and the words you refuse to be described with
- Which competitors are fair game to compare against, and which are not
- Every claim about security, compliance and pricing
- The pages a post is allowed to hand the reader at the end
- What the docs site owns, and what the blog is allowed to cover
- The demo, the trial and the sales conversation the traffic lands in
A backlog item, or a running system.
Most SaaS content programmes do not fail on strategy. They fail because each post is a project with five people in the loop, and the loop closes slower than the quarter.
Content as a ticket in the backlog
- A brief handed to a writer, then to an editor, then to product for the facts
- One market at a time, because each new language needs a writer who speaks it
- Comparison posts written without checking what the competitor shipped last quarter
- Every post an invoice, every invoice a project to justify
- Traffic reviewed when somebody remembers to rebuild the slide
Content as a running system
- One brief carries the query, the outline, the metadata and the links to a live URL
- A new market is a new language line, not a new writer
- Comparison and alternatives entries compete for queries your site does not answer yet
- A subscription per site and language instead of a project per post
- Search Console per site, sitting beside the calendar it came from
Two things worth being straight about.
Comparison content is the most valuable thing here and the easiest thing to do badly, so it is worth saying where the line is.
Competitors and claims
A comparison post is written from the brief and the article, and it is checked before publishing: anything unsupported or thin is discarded rather than shipped. That protects your credibility more than it protects anyone else’s, because a review your buyers can disprove is worse than no page at all.
And ranking, traffic and revenue are not guaranteed. The plan aims at queries your site does not answer yet, publishes on dates and reports what those pages earn in your own Search Console — the mechanism is ours, the result is not.
More on content
- What a plan contains
Every decision a planned post carries before it is written.
- What content costs
The three pricing models, and what actually moves the number.
- Xt4b vs the alternatives
Clearscope, Surfer, MarketMuse, Frase, GrowthBar, BabyLoveGrowth — honest comparisons, side by side.
- For agencies
Several client sites, one account, one calendar each.
- For startups
A content function without a content hire.
- For marketing teams
A pipeline behind the calendar, per site and language.
- For consultants
The enquiries that begin with a search.
- For local businesses
Answer the question before they call.
Questions SaaS teams ask.
Including the two about comparisons and cannibalisation.
Do you write comparison and alternatives posts?
Yes — they are ordinary plan entries. The query is chosen, the intent is set, the outline names both sides, and the post is written to that outline. When the title reads as a comparison, the generated in-article image lays the two options out side by side. What the pipeline will not do is invent claims about a competitor: a post that cannot be supported from what the brief and the article contain is discarded rather than shipped.
Will the posts link to our pricing page, or into the docs?
Internal links are resolved against pages that actually exist: the blog's own posts plus the URLs found in your site's sitemap. So a post can point at pricing, a comparison page or a docs article instead of inventing a URL that 404s — links to your own site go out as absolute URLs, and nothing is linked that does not resolve.
Our buyers ask about security and compliance. Who answers that?
Not the pipeline. The plan can target the query, but the specifics belong on pages your team owns and can stand behind — a trust page, a sub-processor list, a status page. Posts can link to those; use the plan review to discard any entry that would require a claim you are not ready to make publicly.
How do you avoid cannibalising pages we already rank with?
Every URL in your sitemap is recorded before planning, so entries target queries you do not already cover. That is the reason the plan reads your site first: a second page chasing a query you answer today splits your own signals and usually helps nobody but the competitor ranking third.
Can we publish in the languages we sell in?
116 languages are selectable. Each one is its own editorial line with its own queries, plan and dates rather than a translation of the English posts, and each is a separate line on the invoice — so a market that stops paying its way can be switched off without touching the others.
Does it integrate with the SEO tool our team already uses?
Not directly, and it does not need to. Xt4b produces the plan and ships the post; if your writers grade drafts in Clearscope, Surfer or MarketMuse, the brief and the published URL are both there to feed in. Our comparison pages say plainly where each of those tools is the better pick for a given team.
What can you guarantee about pipeline?
Nothing. There is no guarantee of rankings, traffic or revenue, and no invented attribution: posts report clicks, impressions and average position from your own Search Console, and your team decides what that is worth in pipeline terms.
Start with one market
Plan the queries, not the backlog.
Create an account, connect the domain and pick a language: the first week of entries lands ready to review, and the posts publish on their own dates.
Free scan, no signupOne plan per languageAPI for your own tooling