Hosted blog
A blog on the domain you already own.
The fastest way to get nothing done is to start with a redesign. So the blog does not touch your site: it answers on its own hostname under your domain, behind one DNS record, and the pipeline writes, publishes and maintains it. Your pages stay your pages.
One DNS recordNothing installed on your siteYour domain, your posts
What is on the domain.
Six things served for you, all of them generated from what is actually published. No maintenance window, no plugin warning and no build to babysit.
- An index of every post
- Newest first, with the latest post given the full-width treatment and the rest listed by date underneath — the page a reader lands on from a search result or from the site's own navigation.
- One page per post
- The article with its cover image, in-article images, internal links into the pages you already publish, and the metadata a search result and a social card need.
- A canonical URL on every page
- So the blog and any copy of it are never two competing pages. The domain you give it is the domain the posts are attributed to.
- Sitemap, robots.txt and llms.txt
- Generated from what is actually published: the crawlable list of posts, permission to read them, and the plain-text index for models that read one.
- HTTPS and a favicon
- Served over TLS with the site's own icon, so the blog looks like a section of the business rather than a third-party page that happens to mention it.
- Nothing to maintain
- No plugin to update, no build pipeline, no hosting to keep an eye on. The blog is served by the same routes that write it, which is why the two cannot fall out of step.
What it is not.
A hosted blog is easy to over-sell, because 'blog' can mean a whole publishing platform. Here is the honest list.
What it is: a section of your domain that publishes the articles the pipeline planned, with the technical furniture — canonical URLs, sitemap, robots.txt, llms.txt, images, structured data — handled for you. What it is not is a second website to run.
If you want the posts somewhere else entirely, that is a supported answer rather than a workaround: read them from the API and publish them wherever your editors already work.
- A website builder — it will not design your home page, your shop or your contact page
- A CMS you write in: the posts are produced by the pipeline, then edited or unpublished from the dashboard
- A redesign or a migration of the site you already run
- A second brand on a subdomain you do not control — the domain and the archive are yours
- A place to paste other people's articles
Three ways to serve the same posts.
The blog is the default destination because it removes the integration work, not because the posts can only live there.
- 01
The hosted blog
One DNS record and the blog answers on your domain. The default, because it removes the integration work entirely and nothing touches the site you already run.
- 02
Your own CMS
Read each post from the API as markdown or as rendered HTML, with its metadata and images, and publish it where your editors already work. Nothing in the API can write back.
- 03
Your own build
Fetch the posts at build time and render them into a static site, a documentation theme or a data warehouse. The same JSON, one request per page of posts.
Setup, in the order it happens.
Five steps, one of which is a DNS record. The rest is reading, deciding and waiting for the first post.
- 01
Scan the domain
Free and without an account: the homepage, its headings and the sitemap, plus the queries the site does not answer yet.
- 02
Connect a site and pick a language
The blog gets its own hostname under the domain you own — usually a subdomain. The language decides which market's searches the plan is built from.
- 03
Point one DNS record
A single CNAME. Nothing is installed on your server, no theme is touched and no developer has to be involved after the record exists.
- 04
Read the first plan
Queries, outlines and dates, visible before anything is written. Discard what is not true for the business.
- 05
Let it publish
A post on each publishing day you picked, per language, with images, internal links and metadata, on the domain your readers already trust.
Posts publish whether or not the blog is connected
A planned post is written and published on its date even before the hostname is pointed anywhere — it simply becomes visible on the domain once the DNS record resolves. That is deliberate: a missing record delays the reading, never the writing, and the plan is not held up while somebody finds the login for the DNS panel.
What hosting does not promise
Serving a blog well is a technical job, and it is the part this handles: crawlable pages, one per post, on a domain you own. It does not promise that anyone finds them. Ranking, traffic and revenue are not guaranteed by this or any other host, and our terms say so.
Nor does hosting make the writing good. A blog that answers real questions is worth hosting; a blog of filler is not — which is why each plan is built from the pages the site already has and the questions its market actually searches for, and why approval can be switched on to hold every post until you have read it.
More on content
- SEO content API
Every post as JSON — the article, its metadata, its status and URL.
- Multilingual SEO content
A language is an editorial line, not a translation of your English pages.
- For multilingual markets
Which market to open next, and what it costs.
- llms.txt
The summary file for language models, and what ours contains.
Questions about the hosted blog.
Including where it lives, who owns the posts, and what happens to the site you already run.
Do I have to change my website?
No. The blog is a separate hostname under the domain you own, so nothing is installed, no template is edited and no plugin is added to the site you already run. If you stop the subscription, the site you run today is exactly where you left it.
Where does the blog live?
On a hostname inside a domain you own — typically a subdomain like blog.yourdomain.com. One DNS record points it at Xt4b, the blog answers there over HTTPS, and every post is attributed to your domain with its own canonical URL.
Who owns the posts?
You do. They are published under your domain and they are your content: you can edit or unpublish them from the dashboard, and you can read every one of them back out of the API as markdown or rendered HTML whenever you want to take them somewhere else.
What if I already have a blog?
Then the useful question is which one keeps publishing. Nothing here imports, rewrites or deletes existing posts — the hosted blog starts from the plan, and the pages you already publish are linked to rather than replaced. An existing blog on the same hostname would need moving first.
Can I design it to match my site?
Within limits: the blog uses the site's brand name, its icon and its accent colour, so it does not read as an unrelated platform, and the shape of the articles — table of contents, sources, FAQ section — is set per site. It is deliberately not a page builder: a themeable blog would be a second site to maintain, which is the work this is meant to remove.
Does the blog work in more than one language?
Yes, and each language is a separate line with its own plan and calendar rather than a translation. A site publishing in two markets gets two sets of posts on the same domain: the index lists them newest first, with the most recent post featured and the rest beneath it.
What does hosting cost?
Nothing extra: 20€ per website, per language, per month covers the plan, the writing, the images and serving the blog on your domain. There are no per-article quotes, no separate hosting bill and no charge for the scan.
Is a hosted blog good for SEO?
It is good for the mechanics: posts on your own domain, canonical URLs, a sitemap, crawlable HTML, structured data and internal links into your converting pages. What it cannot do is guarantee anything — no ranking, traffic or revenue is promised, and the terms of service say so plainly.
One DNS record
Put the blog on your domain, not on a platform.
Connect a site and read the plan before anything is written: the queries your domain is missing, the outlines, and the dates each post goes live on.
Hosting included per line20€ / site / language / month3 days free, no card