Automated blogging, on your own domain
Your blog lives at blog.yourcompany.com, wears your brand and fills itself. You choose topics; the articles, covers, FAQ blocks and translations arrive published — as static pages that load fast and read correctly to search engines.
Enter your URL, see your blog
What actually shows up
Articles, not drafts
Long-form posts written from your topics, each with a cover image, an FAQ block and calls to action that point at your site — not at ours.
Every language at once
One article publishes in every language your plan has enabled, cross-linked with hreflang. Translations are not a second order you have to place.
Your brand, derived
Logo, palette and type come from the website you already run. There is no theme picker and no design step to get through.
Static pages
Plain HTML behind a CDN. No framework runtime on the page, nothing to hydrate, nothing that breaks when our API has a bad day.
How it works
Four steps, and only the first one asks anything of you.
- 1
Point a subdomain at us
Add two DNS records for blog.yourcompany.com. The certificate is issued before the switch, so the domain never serves an error while you wait.
- 2
We read your site
Brand tokens come out of the site you already have. If something cannot be read, the blog falls back to a clean neutral look instead of asking you a question.
- 3
Take our topics or bring your own
An idea batch returns around 50 topics drawn from your market and your existing pages. Queue the ones you want, drop the rest.
- 4
Publish
A finished article rebuilds the whole site and reaches your domain in about a minute. Search engines are pinged at the same moment instead of waiting for the next crawl.
SEO handled at the source
The parts that usually go wrong months later are settled at build time, on your domain.
- Per-language sitemaps with alternates, served from your own host
- hreflang across every translated article, and canonicals that point at your domain — never at ours
- JSON-LD for articles, FAQ blocks and breadcrumbs
- IndexNow ping on publish instead of waiting to be crawled
- Pages arrive as HTML — nothing for a crawler to execute before it sees the text
- One URL shape, no redirect chains, no duplicate paginated canonicals
Where the automation actually is
The point is not a faster text box. It is that ideas, drafts, images, translations and publishing stop being separate jobs someone has to remember.
Ideas
Batch runs return roughly 50 topics at a time, built from your site and your market rather than from a generic list.
Approval or autopilot
You decide per project whether a finished article publishes itself or waits for you to read it first.
Reruns
An FAQ block, a set of CTAs or a cover can be regenerated on an article that is already live, and the translations follow automatically.
One engine, one voice
Every language and every article comes off the same pipeline, so tone and structure do not drift between your locales.
Already have a frontend?
Hosting is additive, not a migration. The same content is available through the API and the npm client, so an existing Next.js, Nuxt or Astro site can keep rendering the blog itself. That path stays first-class — sites already built on it are not asked to move.
See what the platform doesFAQ
Questions before you start
What is automated blogging?
Publishing a blog where the recurring work — finding topics, writing the article, making the cover, translating it, putting it live and telling search engines about it — runs as a pipeline instead of as a weekly to-do list. You still decide what gets published and in what voice; you stop doing the assembly.
Will AI-written articles hurt my search rankings?
Search engines judge the page, not the author. What gets sites in trouble is thin, duplicated, near-identical pages published at scale. Each article here is written for your project and published once, on your own domain, with proper structured data — and you can read everything before it goes out.
Do I need WordPress or any CMS?
No. There is nothing to install and no plugin to keep updated. The blog is served as static files from your subdomain, next to whatever your main site is built with.
Can I use my main domain instead of a subdomain?
Not today. The supported shape is a subdomain you own, such as blog.yourcompany.com. Apex domains like yourcompany.com are not supported in this version.
How fast does a new article appear?
Publishing triggers a full rebuild of your site and a cache purge — usually under a minute, and within five minutes in the worst case we design for.
What happens to my articles if I stop paying?
They stay in your account. Serving stops when the subscription ends — visitors see a plain placeholder rather than a broken site — and resubscribing rebuilds everything within minutes.
Look at your own blog first
We read the site you already have — logo, colours, type — and show you the blog that would sit next to it, with sample articles in it. Nothing is generated and nothing is charged at this step.
The preview costs nothing and needs no account. If it looks right, plans start at $49 a month.
See pricing