Hosted blog
A hosted blog on your own subdomain
For Squarespace, Lovable, Framer and any builder without a publishing API: add one CNAME record and Autoranko serves your articles at blog.yourdomain.com over HTTPS, with its own sitemap, RSS feed, robots.txt and llms.txt.
- About 15 minutes to connect (estimate)
- Last verified November 8, 2026
How it connects
You choose a subdomain of your site — blog.yourdomain.com by default — and add a CNAME record pointing to autoranko.com wherever your domain’s DNS is managed. Verify DNS then checks that the name really reaches Autoranko, following CNAME chains or comparing A and AAAA records with ours. The certificate is issued automatically on the first visit, and only for verified names: our web server asks the app before requesting one, so a name nobody verified never gets a certificate.
From then on the blog is a publishing target like any CMS. A published article gets its own address, blog.yourdomain.com/<slug>; Update live replaces the page; unpublishing takes it offline at once, and publishing again brings back the same URL. Drafts are stored but never shown, and edits saved in the editor appear only after Update live.
Pages are plain server-rendered HTML with no JavaScript: a title and meta description, a canonical URL, Open Graph tags, and BlogPosting, BreadcrumbList and FAQ structured data. The blog also serves /sitemap.xml with real modification dates, /rss.xml with full articles, /robots.txt and /llms.txt. You set the title, description, logo, accent color, up to six links back to your main site and the language of the blog’s own texts.
Set up the hosted blog
- 1
Verify your domain
A hosted blog only runs on a domain you’ve verified in Autoranko (Dashboard → Sites → Verify ownership). That’s what stops anyone from claiming a subdomain of a site they don’t control.
- 2
Choose the address
In Dashboard → Hosted blog, keep the suggested blog.yourdomain.com or enter another subdomain of your domain. Pick it once: changing it later moves every post to the new address.
- 3
Add the CNAME record
Wherever your domain’s DNS is managed (your registrar, Cloudflare, Squarespace Domains, Wix…), add a CNAME record with the name blog and the value autoranko.com. On Cloudflare, set the record to DNS only.
- 4
Verify DNS and check HTTPS
Click Verify DNS; new records usually show up within minutes. Then click Check HTTPS: the first visit triggers the certificate, which normally takes a few seconds.
- 5
Publish there
Click Use the hosted blog to make it the site’s publishing target, and link the blog from your main site’s menu. Approved and auto-published articles now appear on it.
What gets published
Exactly what Autoranko sends and controls on this platform, as of the last verification date.
| Capability | Hosted blog |
|---|---|
| Title | Supported |
| Article body (HTML) | Supported |
| Meta description | Supported |
| Featured image | Supported1 |
| Images in the article | Supported1 |
| Publish as a draft | Supported2 |
| Update a published article | Supported3 |
| Unpublish | Supported4 |
| Tags or categories | Not supported |
| JSON-LD structured data | Supported5 |
- 1.Served from the blog’s own address (/media on your subdomain).
- 2.Drafts are stored but never shown on the blog.
- 3.Update live replaces the page; its modification date changes only with real edits.
- 4.The page goes offline at once; publishing again restores the same URL.
- 5.BlogPosting, BreadcrumbList and FAQ structured data on every post.
Limits and honest caveats
The blog lives on a subdomain, not in a /blog folder of your main site: a folder would need your main host to forward requests, which builders like Squarespace and Framer don’t allow. Link it from your main navigation and footer so visitors and search engines find it.
The design is deliberately simple: one clean, fast layout with your logo, accent color and navigation links. There are no custom templates, comments, newsletter forms or tracking scripts, and categories and tags aren’t shown.
Autoranko serves the content, so the blog stays online only while it’s set up in your account. Export everything at any time — one JSON file with the theme and every post’s HTML, or each post as an HTML page — to move it elsewhere. If you change the address, the old one stops serving the blog, so choose it before you publish.
Troubleshooting
The messages below are exactly what Autoranko shows in the dashboard or returns from the API, with what they mean and how to fix them.
Verify that you own example.com first (Dashboard → Sites → Verify ownership): a hosted blog can only be set up on a verified domain.- The site’s domain isn’t verified yet, and without that check anyone could claim a subdomain of a site they don’t control. Verify ownership on the Sites page (DNS record, file or connector), then come back.
The hostname must be a subdomain of example.com, for example blog.example.com.- The address must sit under your site’s own domain: not the domain itself, not its www form, and not another domain. Enter a subdomain such as blog.yourdomain.com.
No DNS record for blog.example.com yet. Add a CNAME record pointing to autoranko.com; new records usually appear within minutes, sometimes up to 48 hours.- Autoranko found no record for the name yet, through your DNS or public resolvers. Check the record’s name (some providers want blog, others the full blog.yourdomain.com) and give it a few minutes before you check again.
blog.example.com points to … instead of autoranko.com. Use a CNAME record with the value autoranko.com. If your DNS provider proxies the record (Cloudflare's orange cloud), set it to DNS only.- The name resolves to addresses that aren’t ours: an old A record, a parking page or a proxy in front of it. Remove the other records for the name, keep a single CNAME to autoranko.com and, on Cloudflare, switch the record to DNS only.
Publishing failed: The hosted blog at blog.example.com isn't verified yet — finish the DNS step in Dashboard → Hosted blog.- The site publishes to the hosted blog, but its DNS step isn’t finished, so nothing can go live yet. Auto-published articles wait in review instead of failing; finish Verify DNS, then publish them again.
- Check HTTPS says the certificate isn’t valid yet
- The certificate is requested on the first visit after DNS is verified, which usually takes a few seconds. If it still fails after a few minutes, check whether your domain has CAA records: they must allow letsencrypt.org, the certificate authority our server uses.
Questions
Which builders is the hosted blog for?+
Will search engines index the blog?+
Can I leave with my articles?+
Does it cost extra?+
Go deeper
Related integrations
Connect your site in minutes
Start on the free plan — no card — and publish your first article to your own platform.