For in-house marketing teams
Put a pipeline behind the content calendar.
The team is rarely short of judgement. It is short of hours — and most of those hours go on the work around the writing: the metadata, the images, the dates, the sitemap, the update nobody asked for.
Per site, per languageNo per-seat pricingAPI for your reporting
What lands in the calendar.
Everything below arrives per site and per language, so the calendar is a plan you can read rather than a list of topics somebody has to interpret.
- An entry with a spec
- Query, search intent, format, outline, meta title and description, word-count target and the pages the post should link to — decided before writing starts.
- A draft that matches it
- Written to the outline that was approved and checked before it can publish. Anything unsupported, off-plan or thin is discarded rather than shipped.
- Publishing nobody schedules by hand
- Dates on a calendar, canonical URLs, structured data, cover and in-article images and internal links resolved in the same run.
- Markets in parallel
- One editorial line per language, each with its own queries, plan and cadence — rather than a translation queue behind the English blog.
- One dashboard for every site
- Sites sit side by side, each with its own languages, calendar and status, so a stand-up question has one place to look.
- Numbers without the spreadsheet
- Clicks, impressions and average position per site from Search Console, plus an API if the rows need to live in your own reporting.
Who does what.
The split that makes the pipeline worth having: three roles, and only the first one is a full-time marketing job.
- 01
Strategist
Decides which queries matter and reads the plan. Discarding entries that do not serve the campaign is a senior decision, and it is minutes of work rather than weeks of writing.
- 02
Writer
Keeps the pieces that need a human point of view — the launch post, the report, the customer interview. The recurring coverage no longer competes with them for the same hours.
- 03
Ops
Stops assembling metadata, sourcing images, formatting, chasing dates and updating sitemaps. That whole layer is what the pipeline replaces, not the editorial judgement above it.
Stand-ups that do not need a status update.
When anything can be paused mid-flight, the status of the content programme becomes a question rather than a fact. Here it is visible in one place: what is written, what is scheduled, what is live and what was pulled — per site and per language.
Posts that fail the review are flagged rather than quietly dropped, so “why has nothing published this week” has an answer in the dashboard instead of in somebody’s memory.
What each entry carries1,204
Clicks
48,910
Impressions
12.4
Avg. position
Several markets, one team.
Each language runs its own plan and its own dates against the same domain, which is how a small team covers more than one market without hiring into each of them.
116 languages are selectable, and a language is an editorial line rather than a translation setting: its own queries, its own plan, its own cadence, its own line on the invoice.
That keeps the multi-market problem in one dashboard instead of one spreadsheet per market, with the local nuance added by whoever on the team reads that language.
- 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.
It fits the stack you already standardised on.
The question a team always asks first is what this replaces. The honest answer is the publishing layer — not your tools, your CMS or your writers.
- The SEO suite you standardised on
- Briefs and published URLs are there to feed into Clearscope, Surfer or MarketMuse grading if that is your bar. Our comparison pages say where each of those tools is the better pick.
- Your CMS, if it stays
- The API returns markdown and the rendered HTML for every published post, with status, language, dates and the live URL, so an existing CMS can be the destination.
- Your analytics and reporting
- Search Console sits beside the calendar per site, and the API gives you the rows if the monthly slide is built somewhere else.
- Your writers
- Drafts arrive with the spec attached, so any entry can be handed to a writer, a contractor or a freelancer without a briefing call.
- Your brand
- Your uploaded icon is served as the favicon, the brand name appears on generated images, and the accent colour is yours — a blog that looks like the company, not like a template.
- The pages you already publish
- Every URL in the sitemap is recorded before planning, so the new archive adds coverage instead of competing with the pages your team spent two years building.
A topic spreadsheet, or a calendar that holds.
The same quarter, two ways of keeping the promise the calendar made.
How the calendar usually fills
- A topic spreadsheet that is out of date the week it gets approved
- One person owning the metadata, the images and the publish button
- A new market waiting for a writer who speaks the language
- Traffic reviewed in a slide somebody rebuilds from scratch every month
- The calendar stalling quietly in a busy quarter
How it fills here
- A dated plan per site and language, with the spec attached to each entry
- Images, metadata and internal links produced with the draft
- A market opened by adding a language line, not a headcount
- Clicks, impressions and position per site, sitting next to the calendar
- The cadence holds in a busy quarter because nobody has to find the hours
The limits, stated up front
Xt4b does not do link acquisition, digital PR or campaign strategy, and it does not promise rankings, traffic or revenue. What it owns is the pipeline: a plan aimed at queries your sites do not answer, posts reviewed before they publish, and reporting per site and language.
If the constraint in your team is deciding what to say, that decision still sits with you — and it is the one the plan is designed to make cheap to exercise.
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 SaaS
Be the answer before the demo request.
- For consultants
The enquiries that begin with a search.
- For local businesses
Answer the question before they call.
Questions marketing teams ask.
Including what happens to the writers, and what happens to the CMS.
Does this replace our writers?
It replaces the work they least want to do: the recurring how-to and comparison coverage, plus the metadata, image and publishing chores around it. Your writers keep the pieces where judgement shows — the launch post, the report, the interview, the opinion — and because every entry ships with a brief, they can also take over any entry in the plan.
Can we keep our CMS?
Yes. The API returns every post a site has published with its status, language, dates, live URL, markdown and the rendered HTML, so a client CMS, a docs site or a newsletter can be the destination instead of the hosted blog.
Who approves what?
You approve the plan: entries are dated and carry the spec, and anything that does not serve the campaign is discarded before a word is written. After that, each post is checked before it publishes, and anything unsupported or thin is held back rather than shipped quietly.
How do you avoid keyword cannibalisation?
Your sitemap is read before planning, and every URL it contains is treated as already covered — the plan targets queries your site does not answer. It is the same principle behind the covered-query flags on the free scan: a second page chasing a query you already rank for mostly splits your own signals.
We run several sites. Is that several accounts?
No. Sites live in one account, each with its own blog domain, languages and calendar, and the dashboard reports on them side by side. A brand with a product site and a separate docs or regional site is one login, not two vendors.
How does billing work for a team?
€10 per website, per language, per month, and no per-seat pricing — the number does not change when someone joins, leaves or brings in a contractor. A site publishing in three languages is three lines, each carrying its own plan and cadence.
What is not included?
Strategy beyond the plan, the pieces that need your own data or voice, and link acquisition or digital PR. Also worth stating plainly: no ranking, traffic or revenue outcome is guaranteed — what is guaranteed is the pipeline and the reporting.
Start with one site
One pipeline behind the whole calendar.
Connect a site and a language: the plan lands ready to review, and the recurring coverage starts publishing on the dates your team kept.
Free scan, no signupPer site, per languageNo per-seat pricing