Setup guide
Yes. Two lines in a _redirects file proxy /blog to your blog: status 200 makes Netlify fetch the page and serve it on acme.com instead of redirecting, and the ! makes the rule win over any /blog folder your site already has. Netlify's docs put no plan limit on proxying, and there is nothing to install.
_redirects in the publish directory, or [[redirects]] in netlify.tomlnetlify dev) against our live edge, 2026-10-14. That's Netlify's local emulator, not its CDN, so step 4's curl on production is the real proofacme.com/blog/hello-world/sites.amplifysignal.com/b/acme.com/hello-world/acme.com/blog/, with canonical tags and links to matchIn AmplifySignal, open Settings → Blog address, enter https://acme.com/blog and save. Nothing public moves until the check passes.
/blog https://sites.amplifysignal.com/b/acme.com/ 200!
/blog/* https://sites.amplifysignal.com/b/acme.com/:splat 200!The file has to end up in the folder Netlify publishes, not just in the repo. With Vite, Astro or Eleventy that usually means public/_redirects, which the build copies into the output. If you would rather keep it in netlify.toml, this is the same thing (force = true is the !):
[[redirects]]
from = "/blog"
to = "https://sites.amplifysignal.com/b/acme.com/"
status = 200
force = true
[[redirects]]
from = "/blog/*"
to = "https://sites.amplifysignal.com/b/acme.com/:splat"
status = 200
force = trueDeploy as usual. Netlify reads the rules from each deploy, so there's nothing to restart.
Three requests from any terminal show whether the rule works before you press anything:
curl -sI https://acme.com/blog/ | head -1
# HTTP/2 200
curl -s https://acme.com/blog/_verify.json
# {"edge":true,"host":"acme.com","service":"amplifysignal"}
curl -sI https://acme.com/blog/<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.
/* /index.html 200 must come after them._redirects at the repo root when the publish directory is dist/. It never deploys. Look for it in the deploy's file list.amplifysignal.com/b/…. Use sites.amplifysignal.com; our main domain redirects a verified blog's visitors back to your address.It did in our test: /blog/hello-world/ reached the blog as …/hello-world/ and came back 200. Netlify's docs don't promise it either way for external proxies, which is why step 4 asks for a curl against production.
Netlify caches proxied responses when the origin sends ETag or Last-Modified. Our blog pages send neither, so every request is fetched fresh and a scheduled article shows up on time.
Either. If both exist, Netlify applies _redirects first. Pick one so there's one place to look.
Without it, Netlify won't shadow a file that exists, so an old blog/index.html would keep winning over the proxy.
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.