Your blog on your own domain

Your hosted blog starts at https://amplifysignal.com/b/acme.com/. Move it to https://acme.com/blog (a folder on your domain) or https://blog.acme.com (a subdomain): enter the address in Settings → Blog address, do the one step below for your choice, then press Check. Links, canonical tags, the sitemap and the RSS feed switch to the new address the moment the check passes, and the old /b/ links redirect to it.

1. Choose where it lives

Anything else that ends up at the address is fine too — /articles, /guides, news.acme.com. The path can only contain letters, digits, -, _ and ., and the blog must have the whole path to itself: if acme.com/blog already serves something, pick another path or move that content first.

2a. Subdomain — one CNAME

1. In Settings → Blog address, enter https://blog.acme.com and save.
2. At your DNS provider, add the record the card shows you:

   Type   Name              Target
   CNAME  blog.acme.com     sites.amplifysignal.com

   If your DNS is on Cloudflare, leave the record DNS only (grey cloud). An apex address like https://acme.com itself needs a provider that supports CNAME flattening or ALIAS records at the root.
3. Press Check. DNS changes usually take a few minutes to reach us, and the certificate is issued automatically once the record resolves — typically within minutes, occasionally up to an hour. Check again if the first try reports it can't reach the address yet.

2b. Folder — proxy /blog to us

Your host keeps serving acme.com; it fetches anything under /blog from https://sites.amplifysignal.com/b/acme.com/ and returns it as if it were its own. The contract is small:

• Proxy /blog and /blog/* to https://sites.amplifysignal.com/b/acme.com/, keeping the rest of the path (/blog/hello-world/ → https://sites.amplifysignal.com/b/acme.com/hello-world/). Feeds, the sitemap and article images all live under that path, so nothing else needs proxying.
• Send the request to the host sites.amplifysignal.com (a Host header of sites.amplifysignal.com). Most platforms do this on their own for an external rewrite; nginx and Caddy need it set.
• Don't strip trailing slashes: article URLs end in /. Next.js in particular redirects them away unless told not to (see below).
• Don't cache HTML at your edge for longer than a few minutes — that's how a scheduled article shows up on time.

Enter https://acme.com/blog in Settings → Blog address, add the rule for your platform, then press Check.

Cloudflare (Worker)

Workers → Create → paste, deploy, then add a route acme.com/blog* on the acme.com zone (Worker settings → Domains & Routes). The DNS record for acme.com must be proxied (orange cloud) for the route to run.

export default {
  async fetch(request) {
    const url = new URL(request.url);
    if (url.pathname === "/blog" || url.pathname.startsWith("/blog/")) {
      const target = new URL(request.url);
      target.hostname = "sites.amplifysignal.com";
      target.pathname = "/b/acme.com" + url.pathname.slice("/blog".length);
      return fetch(new Request(target.toString(), request));
    }
    return fetch(request);
  },
};

Vercel

vercel.json at the project root:

{
  "rewrites": [
    { "source": "/blog", "destination": "https://sites.amplifysignal.com/b/acme.com/" },
    { "source": "/blog/:path*", "destination": "https://sites.amplifysignal.com/b/acme.com/:path*" }
  ]
}

Next.js

next.config.js. skipTrailingSlashRedirect keeps Next from redirecting /blog/hello-world/ to /blog/hello-world:

module.exports = {
  skipTrailingSlashRedirect: true,
  async rewrites() {
    return [
      { source: "/blog", destination: "https://sites.amplifysignal.com/b/acme.com/" },
      { source: "/blog/:path*", destination: "https://sites.amplifysignal.com/b/acme.com/:path*" },
    ];
  },
};

Netlify

A _redirects file in the publish directory (or the same two rules in netlify.toml). Status 200 makes it a proxy, not a redirect:

/blog    https://sites.amplifysignal.com/b/acme.com/        200
/blog/*  https://sites.amplifysignal.com/b/acme.com/:splat  200

nginx

location = /blog { return 301 /blog/; }
location /blog/ {
    proxy_pass https://sites.amplifysignal.com/b/acme.com/;
    proxy_set_header Host sites.amplifysignal.com;
    proxy_ssl_server_name on;
    proxy_redirect off;
}

Caddy

acme.com {
    handle_path /blog/* {
        rewrite * /b/acme.com{uri}
        reverse_proxy https://sites.amplifysignal.com {
            header_up Host sites.amplifysignal.com
        }
    }
    # …the rest of your site
}

3. After the check passes

• Changing your mind later is safe: set a new address and, once it checks out, the old one 301s every path to the new one for as long as it still points at us — keep the CNAME or proxy rule in place.
• Canonical URLs, sitemap and RSS move to the new address at once. The sitemap is at <address>/sitemap.xml; add a Sitemap: line for it to your site's robots.txt, or submit it in Search Console (a Domain property already covers a subdomain; a URL-prefix property needs the blog's own).
• Old links keep working. https://amplifysignal.com/b/acme.com/… answers with a permanent redirect to the same article on your domain, and social posts we already sent stay clickable.
• Feed subscribers see nothing. Item ids in the RSS feed never depended on the address, so readers don't re-surface the archive.
• Changing your mind is the same card: enter a new address and check again, or choose "Use our domain instead" to go back to https://amplifysignal.com/b/acme.com/. Search engines follow the canonicals either way.