Its own sitemap.xml
Regenerated as posts ship, with lastmod dates search engines can trust.
Organic acquisition, published for you
Xt4b finds the searches your site is missing, writes the posts that answer them, and publishes them to a blog on your own domain β on a rhythm you approve.
The product
Every post carries a target search, an intent and a publish date, so the calendar is a growth plan rather than a blog roll.
Planned
12
Live
07
Languages
3
Publishing calendar
September
The output
Publishing is not a folder of drafts. Xt4b ships the post to your own blog at a real URL, with the metadata, canonical and internal links a search engine needs to rank it.
How much does SEO content cost per article?
Agencies quote per word, per article or per month, and the rate moves with research depth, review rounds and how much of the publishing you hand over. This breaks down what a fair per-article rate looks like, and what should move it.
Every market
A language is not a setting in Xt4b β it is a separate editorial line, with its own plan, its own target searches and its own calendar. When Search Console is connected, the clicks and impressions each site earns are reported right beside the calendar, so you can see the channel working.
Same blog, same design β each language gets its own plan and its own dates.
1,204
Clicks
48,910
Impressions
12.4
Avg. position
How it works
Three things are yours, and six run on their own: research, writing, metadata, images, links and publishing.
Your three jobs
Paste the domain and pick a language. Your existing pages and sitemap are read first, so the plan builds around what you already publish.
A post lands on each publishing day you picked, aimed at a different search and a different stage of the buying decision β planned ahead, so the calendar is never empty.
Each post moves from planned to live, with the clicks and impressions it earns reported beside the calendar.
What runs on its own
Reads your homepage, headings and sitemap, and records every URL you already publish so nothing gets duplicated.
Builds the queue across the buyer journey: a post for each upcoming publishing day, every one a distinct intent, none targeting a page you already have.
Writes to the outline, with meta title, description, secondary keywords and links to real pages on your site.
Checks every post before it can publish. Anything unsupported, off-plan or thin is discarded, not shipped.
Assigns the slug, generates cover and in-article images, and ships the post to your blog on its date.
Updates the sitemap, structured data and llms.txt, so crawlers and AI assistants can both find the archive.
Hosting
Good writing is only half of it. The blog it lands on has to be one search engines can crawl, index and quote β the plumbing most teams never get to, and the reason good writing sometimes goes nowhere.
Regenerated as posts ship, with lastmod dates search engines can trust.
Every post declares its canonical URL and renders a proper social card.
Publisher, language and dates in the JSON-LD that rich results read.
Index and follow, with full image previews and uncapped snippets allowed.
A machine-readable index of the blog, so AI assistants can cite it.
The icon you upload is served at every favicon size, not the app's.
The API
Every account gets an API key. Pull the posts Xt4b has generated β status, language, metadata, images and the post itself, as markdown or as ready-rendered HTML β into your own dashboard, CRM or reporting, instead of copying out of a UI.
Read the API reference β every parameter, field and error code.
See the SEO API page β what it returns, and who ends up reading it.
/api/v2/posts?status=published&limit=1Authorization: Bearer xt4b_β’β’β’β’β’β’β’β’β’β’β’β’{
"data": [
{
"id": "57",
"status": "published",
"slug": "seo-content-cost-per-article",
"title": "How much does SEO content cost per article?",
"meta": {
"title": "How much does SEO content cost per article?",
"description": "Three pricing models and what each one hides."
},
"searchIntent": "commercial",
"keywords": {
"primary": "seo content cost",
"secondary": ["seo content pricing"]
},
"images": { "cover": "https://cdn.xt4b.com/β¦/cover.svg" },
"language": "en",
"website": "xt4b.com",
"publishedAt": "2026-09-11T09:00:04.118Z"
}
],
"pagination": { "limit": 1, "offset": 0, "total": 7 }
}The alternative
Content is the channel you own. It compounds while paid traffic stops the moment the budget does β but only if someone keeps publishing.
Doing it manually
With Xt4b
Who it is for
Built for agencies running client sites, lean marketing teams, consultants and founders β the people who have to publish every week without hiring for it.
Pricing
20β¬ per website, per language, per month. Not per article, not per word and not per seat β the plan, the writing, the images and the publishing are all in it.
Per website Β· per language Β· per month
20β¬/ month
A site publishing in two languages is two lines on the invoice, and each line runs its own plan and its own calendar. Remove a language and one line goes with it.
Automate my blogWhat is in it
The price buys the work and the reporting. It does not buy a ranking, a traffic number or a return β and nothing publishes without a plan entry behind it.
FAQ
Including the honest ones about rankings, timelines and what happens to the pages you already have.
Still unsure? Ask us directly.
Each post is aimed at one search and the intent behind it, gets an on-page SEO pass, links internally to pages you already have, and publishes on a consistent cadence β the things that make a page rankable. We do not guarantee rankings or traffic: no one can, and our Terms say so. What we control is that every post is planned, written and published to be eligible to rank.
The plan spreads across the buying decision rather than chasing volume: research posts for people discovering the problem, comparison and alternative posts for people choosing, and commercial pages where they buy. Each post carries a call to action, and internal links point back to the pages on your site that sell.
Posts start publishing on the cadence you approve, usually within the first week. Search engines then need time to crawl, index and rank new pages β that takes weeks, and sometimes months, and the market and the competition set it, not us.
A generic writer starts from a prompt and stops at a draft. Xt4b starts from your site and does not stop until the post is live: the plan, the writing, the metadata, the images, the internal links, the publishing and the indexing plumbing are one pipeline.
They are treated as forbidden topics. Every URL in your sitemap is recorded first, so new posts target searches you do not cover instead of competing with pages you already rank for β the usual way content plans cannibalise themselves.
A planner reads the pages your site already serves, plus its sitemap, then fills the upcoming publishing days: a post each, aimed at a different search intent, none duplicating a URL you already have. You see the whole plan before anything publishes.
The ones you pick, per site, when you connect it β any combination of days. A post lands on each publishing day, the calendar is kept filled ahead of today, and you can change the days later.
Yes. Turn on approval and new posts wait for you instead of publishing themselves on their date. Switching it on also holds what is already queued, so the setting does what it says from the moment you use it β release a post in the calendar and it goes live exactly as it would have.
No. Xt4b hosts the blog for you on a subdomain (or the apex) of your own domain β with its own sitemap, canonical URLs and structured data per post. You add one DNS record and it runs in front of your existing site.
116 languages are selectable today β English, German, French, Spanish, Portuguese, Dutch, Polish, Russian, Ukrainian, Swedish, Czech, Greek, Turkish, Arabic, Hindi, Japanese, Korean, Chinese and many more. Each one runs its own plan and its own cadence.
Posts are generated end to end rather than hand-edited, so there is no WYSIWYG editor. What you control is the outcome: publish it on its date, discard it, or unpublish it after it ships β and discarding deletes the post outright, along with its queued publish.
Nothing at all. There is no script, plugin or build step on your side. The blog is hosted and routed through one DNS record, and your existing site keeps serving exactly what it serves today.
The scan reads HTML: your server-rendered pages, headings and sitemap.xml. Sites that render entirely client-side give the free scan less to work with, and give the plan less context to be specific about.
Nothing goes live until it has a date on your calendar and the publish job runs. Unpublish it and it leaves the queue β it will not be re-queued behind your back.
20β¬ per website, per language, per month. A site publishing in two languages is two lines on the invoice, and each line carries its own plan, its own target searches and its own calendar. There are no per-article quotes and no charge for the scan, which needs no account at all.
Ready when you are
Connect a domain and see the searches you are missing in the first minute. Nothing publishes until the date it was planned for.
20β¬ / site / language / month3 days free, no card