Preparing the launch of Deliberately Difficult & Laughing, I have revisited the question of whether to set up a custom domain for it or not.
Now, having a custom domain for your publication makes absolutely sense. Just ask Jill Hart or read her excellent article that dives deep into the pros and cons:
It convinced me to both have a distinct domain that I personally own (already had it actually) and not enable it via Substackās custom domain feature.
Because redirecting (or forwarding as itās also referred to) your domain to your Substack subdomain gets you the best of both worlds.
Sort ofā¦

Redirecting (forwarding) is the Internetās version of an āI have moved houseā message
Yes, it keeps your publication and its promotion independent from the platform you use. Which is a humongous biggie in my world.
Because it means Iām free to move to Beehive, Ghost, Patreon, or whatever rocks your socks off when the fancy takes you (or the economics make sense, orā¦)
When you switch, you only need to update your āIāve moved houseā message. And it keeps doing that for as long as you keep the redirection.
Both Jill Hartās article (which was inspired by and points to one by Kristi Keller šØš¦ tell you how to redirect (forward) your own domain to your Substack.
Jillās is steps are general. Kristiās are specific to GoDaddy.
Both work.
Except for one, naggingly frustrating detail.

Naively redirecting your domain still kills links
Yes, using the method both Jill Hart and Kristi Keller give you, people clicking on links get redirected to where you point your domain.
Butā¦
And this is a major ābutā!
They get sent to the main/home page, not the specific article the clicked the link of.
Thatās not why I have my own domain!
Itās not something that Substack causes, by the way.
Itās inherent to how the internet and domain redirection works when you set it up at the DNS (Domain Name Service1) level.

What domain level (ānaiveā) redirection does
For example, if Iād only have my 42sidenotes.com domain redirected to Substack (itās properly and fully redirected by now), clicking the link to a specific article on LinkedIn or even in a Substack Note like
https://42sidenotes.com/p/nina-changed-my-mind
would take you to
https://42sidenotes.substack.com
Not to the article I linked!
Yikes.
Thatās not what I want.
Thatās not what I want to happen when I share a link to an article on social.
Thatās not the experience I want for my readers when they click a link in an email.
Itās exactly what Substack fixes for you through using their custom domain feature. Like it does for Tim Ebl šØš¦ ās Time to Thrive and did for 42 Sidenotes.
But then you also lose you most of the benefits of having a Substack publication.
(Which I didnāt even know it did until reading Jill Hartās article. Because Substack didnāt tell me. At least not in any obvious way.)
Thatās not nice!
So I hesitated to disable 42 Sidenotesā custom domain. And wasnāt sure about using redirection for Deliberately Difficult & Laughing.
But you can have your cake and eat it too.

What I want, what I really, really wantā¦
This is where my former life in software and web design/development came in. I know whatās possible. So I donāt lie down and take a solution I find less than useful and user-friendly. And letās not even talk about shooting-yourself-in-your-marketing-and-promotion of it.
When I share a link to an article āout in the wildā ā like on social platforms ā I want anyone who clicks it to be taken to that specific article. Regardless of whatever platform I happen to use at any given time.
So, when I share
https://42sidenotes.com/p/nina-changed-my-mind
I want readers to be taken to
https://42sidenotes.substack.com/p/nina-changed-my-mind
at the moment, and to
https://42sidenotes.any_platform].com/nina-changed-my-mind
when I decide to switch platforms.
Let me tell you how to do it. And donāt worry, it involves a little more than setting up a redirect for your domain, but itās still pretty simple.

How to fix naive redirection without losing the benefits of publishing on a Substack subdomain
And WITHOUT killing all links in the wild in the process.
What you need:
A domain name (dāoh)
A hosting plan connected to that domain
You need the hosting plan because full redirection of both the domain and all its individual pages requires a single, specific file on your domain.
Most domain name providers also offer hosting and vice versa.
As you only need one file, you can go with the cheapest hosting you can find. Speed and capacity donāt really matter because nothing else will be load from that host.
When you have a hosting plan connected to your domain, this is what you do:
Step 1: Remove any redirection youāve set up
Any redirection at the domain level will prevent the real solution from working. Thatās because it kicks in before the file youāll create in the next step gets read.
Step 2: Open your hostingās file manager
At your hosting provider, locate the file manager for your site. Open it.
I use Hostinger (aff)2 as my hosting provider at the moment3.
Step 3: Navigate to your siteās home folder on the server
If you were creating a standard bare-bones HTML4 site, your siteās pages would live in a specific folder on one of the hosting providerās servers.
Full redirection of all the pages on your publication, requires a single, specific file. This file needs to be created in the āhomeā folder of your site.
If you have a hosting plan for multiple sites like I do, the file manager often can take you to the folder in which all your sites live or to a specific siteās folder:

At Hostinger (aff), when I click the āAccess files of ā¦ā for a site, the file manager opens in another tab and shows me this:
āDO_NOT_UPLOAD_HEREā speaks for itself, Iād say. The folder you want to open is the āpublic_htmlā one (most hosting providers use that). If you have a hosting plan for a single site, opening the file manager usually takes you straight there.
Step 4: Create the all important file
With your home folder open (double-clicking it usually does the trick), use the menu item that letās you create a new file:
That either opens the file content editor directly (in which case you need to name it when saving the contents) or opens a small dialog to name the file first.
Either way, name the new file .htaccess exactly, character for character!
In the image above itās already showing because I created the file before creating this screenshot. Itās greyed out because itās a system file: a file that governs the operating of your site.
When youāre in the file content editor enter the following lines:
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_HOST} ^42sidenotes.com [NC,OR]
RewriteCond %{HTTP_HOST} ^www\.42sidenotes\.com$ [NC]
RewriteRule ^(.*)$ https://42sidenotes.substack.com/$1 [L,R=301,NC]Obviously replacing 42sidenotes.com with yours!
The first
IfModuleline checks for the presence of a software module that provides what we need. Most hosting providers provide this by default.The second
RewriteEngineline switches on the features in that file.The third and fourth
RewriteCondlines tell it when to apply the fifthRewriteRuleline.
What it accomplishes is this: when someone types in (or clicks a link) either to 42sidenotes.com (line 3) or to www.42sidenotes.com (line 4), it rewrites the requested pageās URL (address) to https://42sidenotes.substack.com/$1
This is what takes care of redirecting both the ābareā domain 42sidenotes.com as well as the usual www Internet subdomain: www.42sidenotes.com5
The /$1 is where the magic happens for links to individual pages. It ensures that when people enter or click https://42sidenotes.com/p/nina-changed-my-mind, they get send to https://42sidenotes.substack.com/p/nina-changed-my-mind.
Be sure to save the file (click save or done after entering the lines and triple checking them for typos) and youāre all done!

How Substack still kills the advantage of a custom domain unless you pay attention
I like what Jill Hart and Kristi Keller wrote about custom domains vs subdomains.
But thereās one thing I noticed about Substack that neither of them mentions. And it happens with both a Substack subdomain and a custom domain.
Substack tries to keep its foot in the door when providing you with a link to share!
You know what Iām talking about: the page Substack shows after you schedule or publish an article. It prominently gives you a link to share for promoting it.
Thatās nice and helpful, isnāt it?
Whatās less than helpful is this link does not link directly to your article. Not when youāre using a Substack subdomain. Not when youāre using a custom domain.
They give you a link that does show your article immediately, but⦠it points to a page thatās within the reading experience of Substackās own domain!
Now, I understand that Substack wants to grow too. And that its growth is, probably, good for my growth as well.
But if you, like me, want the full benefits of having my own domain, DO NOT SHARE the link they give you.
For example, for my initial post on Deliberate Difficult & Laughing itās:
https://open.substack.com/pub/deliberatelydifficult/p/coming-soon?r=2ww51&utm_campaign=post&utm_medium=web&showWelcomeOnShare=true
Donāt share that. NOT EVER. Only use direct links to your domain. Otherwise all effort to remain independent of Substack still goes down the drain when you leave it.
Iād edit the link above to be:https://deliberatelydifficult.com/p/coming-soon
Even better: use the SEO URL. Youāll find it (and customize it) for any post via its settings (bottom right corner when editing it).
Thatās it.
Enjoy!


DNS (Domain Name Service) is the internetās version of a telephone book, providing browsers with a way to connect a domain name to an otherwise meaningless IP (Internet Protocol) address like 194.164.74.80.
That link is my affiliate link for Hostinger web hosting. I earn a small commission if you use it and buy something from them within a given (donāw know what) period.
At NO cost to you.
If you want to make sure there are no hidden costs, feel free to go straight to hostinger.com, but you may miss out on some discounts given to āfriendsā of affiliates.
In other words: Iād do both and pick the one thatās friendliest to my wallet ;)
I make full use of the ridiculously enormous discounts Hostinger and Siteground (both excellent providers, both affiliate links) extend when you FIRST sign up with them and commit to several years with them. After that period, I switch from one to the other.
The beauty: I get excellent hosting at a very low cost. Yes, switching from one to the other is a not quite a breeze, but easy enough. Simply create an account or take out a new hosting plan with the ānewā provider before your contract with your current one ends. That way you have time to move everything across and activate your new setup (getting DNSs - the Internetās telephone books) to point to the new location before your current one expires. And this way you wonāt lose any traffic at all!
HTML: Hyper Text Markup Language. The file format all pages on all sites use to send a pages from an internet server to your browser.
A ābareā domain name, like 42sidenotes.com, is usually not where a site actually can be reached. This is more often the www subdomain, like www.42sidenotes.com. The fact that you can use either to reach a website is thanks to proper setup of the siteās DNS records (the Internetās version of telephone book entries).









this is fantastic information!! I've got some domains that I could totally do this with!! and yeah NEVER use that open link ... not only is it "ugly" but it doesn't help you at all.
I'm glad you wrote this because it sort of broke my brain lol. I would've never been able to pick this apart!