# Substack Custom Domain: Cost, Setup and the Catches (2026)
Author: Sai Krishna
Author URL: https://superblog.ai/blog/author/sai-krishna/
Published: 2026-09-14
Meta Title: Substack Custom Domain: Cost, Setup, Catches
Meta Description: A Substack custom domain costs $50 once. Here is the DNS setup, the subdomain requirement, the hijack risk, and what it does not fix for SEO.
Tags: blogging, SEO, blog setup
Tag URLs: blogging (https://superblog.ai/blog/tag/blogging/), SEO (https://superblog.ai/blog/tag/seo/), blog setup (https://superblog.ai/blog/tag/blog-setup/)
URL: https://superblog.ai/blog/substack-custom-domain/

![Substack Custom Domain](https://prod.superblogcdn.com/site_cuid_ckox4in4f002nl8lhcib41g2u/images/cover-1789108952866-compressed.png)

Yes, you can put your Substack on your own domain. A Substack custom domain costs $50, once, per publication. Every domain you connect afterwards is free. Substack's [2020 announcement of the feature](https://on.substack.com/p/new-add-a-custom-domain-to-your-substack) puts it plainly: "To use custom domains, you'll be charged a one-time $50 fee per publication," and "After you've unlocked this feature, you can add and remove custom domains at no additional cost." Setup is one CNAME record in your DNS provider. The parts nobody mentions before you pay are the subdomain requirement, what happens to your old URLs, and how little the domain actually changes about your SEO.

This post covers all of it: the honest setup, the catches, and what to do instead if the thing you are really building is a company blog rather than a newsletter.

## What the $50 buys, and what it does not

IncludedNot includedDomainUse your own hostname for the publicationThe domain registration itself, which you buy separatelyRepeat useAdd and remove domains later at no extra costA second publication, which pays its own $50Hostname shapeA subdomain such as `www.` or `newsletter.`Your bare root domain, which only redirectsPathThe publication at its own hostnameYour posts at `yoursite.com/blog`SEO controlsNothing newRedirects, canonical tags, noindex, a sitemap you shape

The fee is cheap. That is the honest starting point. Compared with any monthly platform, $50 once is nothing, and if you are running a personal newsletter and want it to read `letters.yourname.com` instead of `yourname.substack.com`, stop reading and go do it. The rest of this post matters when a business is involved.

## How to set up a custom domain on Substack

The [Substack help center article on setting up a custom domain](https://support.substack.com/hc/en-us/articles/360051222571) is the authoritative source. Here is the sequence, with the decisions you make at each step.

**1\. Buy the domain first, and pick the subdomain.** Substack requires the publication to sit on a subdomain, something like `www.example.com` or `newsletter.example.com`. Choose that prefix carefully, because moving it later means another migration. Most businesses pick `newsletter.` or `news.` so the domain stays free for a real website. Writers who have no other site usually take `www.`

**2\. Unlock the feature in Settings.** Inside your publication's settings you will find the custom domain section. This is where the one-time $50 charge happens, per publication, on the card you have on file.

**3\. Add the CNAME record.** Substack generates the exact CNAME value for you. Take it to wherever your DNS lives (Cloudflare, Namecheap, GoDaddy, your registrar's panel) and create a CNAME record with your chosen subdomain as the host and Substack's value as the target. One record. That is the whole DNS job.

**4\. Handle the root domain separately.** Someone will type `example.com` without the prefix, and Substack cannot serve that. Substack ships its own fix: in Settings, under Domain, tick "Root domain redirects", then add an A record with host `@` pointing at `3.231.35.217` at your DNS provider and select "Setup root domain redirects". Substack says it can take up to 36 hours to start working, and asks you to remove any earlier forwarding workaround first ( [Substack help](https://support.substack.com/hc/en-us/articles/360051222691), updated July 2026). The fallback is domain forwarding at your registrar, a 301 from the bare root to the subdomain. Be aware that one widely shared Substack post argues forwarding is [a visual band-aid rather than a strategy](https://www.sendthesignals.com/p/custom-domain-setup-on-substack), and the author is right that it does not change which hostname holds your content.

**5\. Wait for propagation, then verify.** DNS changes are not instant, and Substack issues an SSL certificate for the new hostname after the record resolves. Load the subdomain in a private window and check the padlock before you announce anything.

If your marketing site already lives on the root domain, do not point `www.` at Substack. That subdomain usually serves your main site, and repointing it takes your homepage down. Use a dedicated prefix instead.

## What happens to your substack.com URLs

Once the custom domain is live, your publication answers on the new hostname, and links to the old `yourname.substack.com` addresses continue to resolve. That is the good news, and it is why the switch feels painless on day one.

The bad news arrives if you ever reverse it. The developer swyx documented changing his publication's domain and found that "hitting the Disable Custom Domain immediately chucked my substack address back to the old https://swyx.substack.com/ subdomain," while the former custom domain was, in his words, [404ing](https://swyx.io/substack-change-domain). No redirect map, no interface for preserving continuity, just dead URLs on a hostname you still own and pay for.

A reader in the comments on [this custom domain walkthrough](https://unstackit.substack.com/p/my-pusing-a-custom-domain-on-substack) described the same trap from the other side after uninstalling a custom domain: "it breaks all your links," with 170 posts to fix, and "It also messes up your search engine rankings if you switch."

The practical rule: treat the custom domain as a one-way door. Decide the hostname before you have an archive worth linking to, and plan to keep it.

## Three catches worth knowing before you pay

The domain is one of several; the rest are collected in [Substack problems](/blog/substack-problems/).

### An abandoned custom domain can be claimed by someone else

This one deserves more attention than it gets. A security researcher's write-up on [Substack's custom domain handling](https://littlehakr.substack.com/p/substack-security-risks) documents that Substack checks whether a CNAME record points at it, but does not verify that the person adding the domain owns it. [Coverage of the disclosure](https://gbhackers.com/substack-custom-domain-vulnerability/) reports 1,426 affected domains, roughly 8% of Substack-associated custom domains, plus 11 wildcard records with a wider blast radius.

The attack is mundane, which is what makes it work. You abandon a newsletter, you forget the stale DNS record, and somebody else adds your old hostname to their own Substack account, pays the $50, and publishes under your name with a valid certificate. If you ever stop using a Substack custom domain, delete the CNAME record the same day. This is not a reason to avoid Substack. It is a reason to keep a note of every DNS record you create.

### Discovery inside Substack's network is a live argument

You will read that custom domain publications lose visibility in Substack's Discover surface and recommendations. The claim was true enough in the early years to become received wisdom. It is now contested: the sendthesignals piece linked above states that "More custom-domain newsletters are showing up in all of those places" and that there is no official rule against it.

Treat it as an unknown rather than a fact in either direction. If your growth depends entirely on Substack's internal network, the safe sequence is to build traction on the substack.com subdomain first and move later, accepting the one-way door above. If your growth is meant to come from search, the network was never going to be the engine anyway.

### The domain does not change your SEO controls

This is the catch that costs businesses the most, and it is the least obvious, because moving to your own hostname feels like taking ownership.

A custom domain changes the string in the address bar. It does not hand you a redirect manager, a canonical tag field, a noindex toggle, or a sitemap you can shape. Substack generates a sitemap on its own terms, and its SEO panel stops at a handful of per-post fields. So a company with syndicated or republished articles still cannot point search engines at the original, an old post whose slug changes still breaks every inbound link to it, and a thin tag archive still cannot be kept out of the index. We enumerate the whole gap, with what Substack does and does not expose, on our [Substack SEO page](/substack-seo).

The second thing it does not change is where authority accumulates. Posts on `newsletter.example.com` build that hostname. Search engines treat a subdomain as a neighboring property rather than part of `example.com`, which is exactly why the strongest setup for a company blog is a path on the main site instead. Our [Substack vs blog comparison](/blog/substack-vs-blog/) works through that decision in full.

## When the goal is a company blog, not a newsletter with a nicer URL

If you are paying $50 so a business blog looks professional, you are solving the visible half of the problem. The half that decides whether the blog earns traffic sits underneath.

[Superblog](https://superblog.ai) is a blogging platform built for that job. It is not a newsletter tool, and it is worth saying plainly: **Superblog does not send email newsletters.** It has built-in signup forms that collect subscribers for you, and if Substack is working as your email channel, keep it. Plenty of teams run Substack for the inbox and a real blog for search, which is a sensible division of labor rather than a compromise.

What changes on the blog side:

**A custom domain is included, on every plan.** No unlock fee, no per-publication charge, free SSL on any hostname you connect. That includes Pro at $49 a month, and Superblog's [pricing page](/pricing) has the full breakdown.

**Your posts can live at `yoursite.com/blog`.** Superblog serves the blog from a path on your existing marketing site through routing rules on your side, with a reverse proxy in the less common setups, and guides for both. Substack cannot do this at all: a Substack publication only ever answers on a hostname of its own, never on a path inside another site. Every link your posts earn then counts toward the domain your pricing page sits on.

**Redirects are yours.** You set 301s from the dashboard, so changing a slug or retiring a post is a two-minute job instead of a broken link. Canonical URLs are generated automatically, which is the control Substack does not expose at all.

**The SEO plumbing ships turned on.** Structured data is written for you on every post (Article, WebPage, Organization, ImageObject and FAQ types), the XML sitemap rebuilds itself, IndexNow tells search engines about a new post without waiting on a crawl, Open Graph tags are filled in, and an llms.txt index is kept for AI assistants. On Super and above the same machinery handles hreflang for multilingual blogs.

**Nothing to maintain, nothing to patch.** Pages are pre-built static files on a global CDN. There is no database at runtime and no plugin surface, so there is no update cycle and nothing to harden. Images convert to WebP automatically and every page is built to hold a 90+ Lighthouse score.

**The editorial side is built for a team.** Drafts autosave, a post can carry more than one author, and access comes in three roles (Admin, Editor, Writer). From Pro upward you also get scheduled publishing and a review step, with room for five people on Pro, ten on Super and twenty-five on Business. Privacy-friendly Pirsch analytics (Pro and above) run without cookies or a consent banner, and Google Analytics works on every plan.

**It holds real archives.** 23 blogs on Superblog carry 1,000 or more posts, and the platform serves more than 150,000 posts in total.

Trying it costs nothing. The trial lasts seven days and asks for no card, and there is a 30-day money-back guarantee. If you want to see how Superblog sits against beehiiv, Ghost, Kit and the rest before deciding, our [Substack alternatives roundup](/blog/best-substack-alternatives/) compares them side by side.

## Substack custom domain FAQ

### How much does a Substack custom domain cost?

$50 USD, once, per publication. That unlocks the feature permanently, so you can add and remove domains afterwards without paying again. The domain registration is separate, typically $10 to $20 a year from a registrar.

### Can I use my root domain on Substack?

Not directly. Substack requires a subdomain such as `www.example.com` or `newsletter.example.com`. Substack's own "Root domain redirects" setting, backed by one A record, sends the bare root to that subdomain, and registrar forwarding does the same job if you prefer it.

### Does a Substack custom domain improve SEO?

It moves your posts onto a hostname you control, which is worth something for brand and for portability. It does not add any SEO capability: no redirect manager, no canonical field, no noindex control, no sitemap you shape. Those gaps stay exactly where they were.

### What happens if I remove my Substack custom domain?

The publication reverts to its substack.com address and the custom domain URLs stop working. One documented case shows the old addresses returning 404s with no redirect offered. Delete the CNAME record immediately afterwards so nobody can claim the hostname on their own Substack account.

### Can I keep Substack for email and blog somewhere else?

Yes, and it is a common setup. Substack handles the newsletter and its subscriber relationships, while your public archive lives on your own site at `yoursite.com/blog` where it can rank and link into the rest of your funnel. The two do not conflict.

* * *

If your Substack is a newsletter, spend the $50 and enjoy the nicer URL. If it is the content engine for a business, the domain was never the constraint. [Start a 7-day Superblog trial](/pricing), no card required, and see what the blog looks like on a domain that comes with the controls attached.


---
This blog is powered by Superblog. Visit https://superblog.ai to know more.
---