Blog hosting serves a project's articles at the customer's own domain (blog.customer.com). The customer adds one DNS record pointing at us, and we render a branded blog: list page, articles, the customer's name, logo, and accent color, with no CMS on their side at all.
It exists as the catch-all for every site builder with no write API. Squarespace, Carrd, and the AI builders (Lovable, Bolt, v0, Replit) all host sites that can't receive posts, and every one of them can link to blog.customer.com.
Note: The hosted blog is one of the platforms under the project's Publishing row. Your blog goes live as soon as your CNAME resolves to us and your domain's certificate has issued, and the setup panel names which of those two you are waiting on.
What to know before you start
Choose it when the client's platform has no integration and RSS import isn't available either, or when you'd rather not touch the client's site to give them a blog.
Set up your hosted blog
To set up a hosted blog:
- Set up the hosted blog for the project: domain, brand name, logo, accent color.
- Have the customer add the single DNS record shown during setup.
- Press Verify. That checks the record, registers the domain with our host, and asks for an HTTPS certificate.
- Wait for the certificate. It usually takes a few minutes, and the blog goes live a little after the check passes.
What the setup card tells you
Verify reports where the domain actually is, not just whether the DNS lookup worked:
- DNS not found. The record isn't visible to us yet. Nothing else has happened.
- Issuing certificate. The record is right and the domain is registered. HTTPS isn't ready, so the blog may not load for a few more minutes.
- Live. The domain is registered, the certificate is issued, and the blog answers there.
Two states mean somebody has to act. DNS not accepted means we hold the domain but our host still can't see the record, so re-check it at the registrar. Waiting on us means your DNS is correct and the last step is on our side. Message us and we'll finish it.
What happens after setup
The blog renders under the customer's domain with their branding, so visitors see their blog, not ours. Articles published through the normal content calendar flow appear automatically.
Limits and usage
- One hosted blog per project, one custom domain each.
- The blog updates within a few minutes of publishing. Content is served cached and refreshed on an interval.
- The client's main site should link to the blog subdomain so SEO benefit flows. A blog nothing links to is an island.
- Removing the blog, or moving it to a different domain, releases the old domain on our host. Point it somewhere else afterwards.
If something isn't working
DNS verification fails. The record was added at the wrong host or with the wrong target. Re-check against the values shown in setup. DNS changes can also take time to propagate.
The check passes but the page won't load over HTTPS. The certificate is still being issued. Give it a few minutes and press Verify again. If it stays on "DNS not accepted", the record is resolving somewhere other than where our host is looking, which usually means a second record on the same name.
The blog shows but articles lag. That's the refresh interval, minutes rather than seconds. If an article is still missing after that, check that it actually published in the calendar.
Related guides
For what shipped recently, see the changelog.