Setup guide · paid tier
Only on Framer's top hosting tier. Multi Site rewrites can serve an outside HTTPS site at /blog, but they come with Pro plus the Advanced Hosting add-on ($200 a month when we checked) or Enterprise. On every other plan, use blog.acme.com with one CNAME. Framer asks for Cloudflare's proxy to stay off on standard domains, so a Worker isn't the answer there.
In AmplifySignal, open Settings → Blog address, enter https://blog.acme.com and save. Nothing public moves until the check passes.
Wherever acme.com's DNS records live, add a CNAME named blog pointing at sites.amplifysignal.com. If that is Cloudflare, leave it DNS only (grey cloud). Framer itself needs no change; we issue and renew the certificate once the record resolves, usually within minutes.
Back in Settings, press Check. When it passes, links, canonical tags, the sitemap and the RSS feed switch to https://blog.acme.com, and the old address redirects there.
Then add a Blog link to your Framer navigation pointing at https://blog.acme.com/.
In AmplifySignal, open Settings → Blog address, enter https://acme.com/blog and save.
In Framer: Site Settings → Hosting → Multi Site → Add. Path /blog, type External, URL https://sites.amplifysignal.com/b/acme.com/. Add a second with path /blog/* and the same URL. Then publish. That's two of the add-on's six rewrites.
Framer documents the fields but not how the rest of the path reaches an outside URL, or whether the trailing slash survives. So before trusting it, run curl -sI https://acme.com/blog/<an-article>/: you want 200, not a 301 and not the blog's home page. Then press Check. If articles don't come through, use Option A and tell us what you saw.
Three requests from any terminal show whether the rule works before you press anything:
curl -sI https://blog.acme.com/ | head -1
# HTTP/2 200
curl -s https://blog.acme.com/_verify.json
# {"edge":true,"host":"acme.com","service":"amplifysignal"}
curl -sI https://blog.acme.com/<an-article>/ | head -1
# HTTP/2 200A 301 on the article that points at the same URL, again and again, means something on the way is dropping the trailing slash. "edge":false means the rule points at amplifysignal.com instead of sites.amplifysignal.com.
Then press Check in Settings → Blog address, or run as site blog-check acme.com. Check fetches /_verify.json through your address and passes when it answers for this site through our edge. From then on, links, canonical tags, the sitemap and the RSS feed use your address, and the old /b/ links redirect to it.
For a /blog route, run the same requests against https://acme.com/blog.
amplifysignal.com/b/…. Use sites.amplifysignal.com; our main domain redirects a verified blog's visitors back to your address.Search engines treat blog.acme.com as its own site, so its authority builds separately from acme.com; a folder shares it. A subdomain still ranks, and $200 a month buys a lot of articles.
Framer's docs say rewrites forward cookies to the destination. Our blog doesn't read or set any.
Not at the same path. Move it, or give the new blog another address such as /articles.
sites.amplifysignal.com is our edge: a request there tells us it came through your proxy, so we serve the page as yours. Once your address is verified, amplifysignal.com redirects a blog's visitors to your address instead, so a proxy aimed there would send people in a circle. Check names the problem if a rule points at the wrong one.
The mechanics carry over: swap the destination for any server that hosts your blog under a path. Copy two things along with them. Keep the trailing slash if that server's URLs end in one, and make sure its links and canonical tags name your address, or search engines index the other host instead. Ours switch the moment Check passes.
Yes, on any platform: one CNAME from blog to sites.amplifysignal.com, and we issue the certificate. A folder shares your main domain's authority, which is why these guides lead with it; the subdomain steps are on the overview.
Checked against the platform's documentation on 2026-10-14; where the facts above say tested, we ran the snippet ourselves against the servers that host our own blog and followed every URL to a 200.
AmplifySignal hosts it, drafts the articles from your keywords and Search Console data, publishes them on a schedule and sends the social posts. Every account starts with a free week, or begin with a free 90-day launch plan.