Writing ·
Why your blog belongs on your own domain
You rent. You rent until Medium changes the rules. You rent until Substack decides who is allowed. You rent until Twitter becomes X and the follower count you spent six years building is a rounding error in someone else's quarterly deck.
You thought you had a blog. You had a tenancy.
The internet is a landlord problem. Most writing online lives in a building owned by someone who doesn't read it. The landlord adjusts the rent, moves the walls, rebrands the neighbourhood, and you keep writing because there is nowhere else to go.
Except there is. A domain costs less than a paperback. A static site is free. Once you own the turf, nobody can evict you off it.
This piece is about five reasons the writing that matters to you should live at yourname.com or yourname.blog or something you can point at and call yours. Not a pitch for any stack. Not really a pitch for Blogroll either, though once you have a blog it can be submitted to the directory. More on that below.
1. Platforms die
Every Medium article from 2016 is a ghost. So is every LiveJournal from 2004. So is every Tumblr from 2012, at least the Tumblrs that covered the topics Tumblr's new owners decided they didn't want to host anymore.
Platforms close. Platforms get sold. Platforms change leadership, and the cofounder who promised never to show ads is replaced by a board that would love to show ads, and also to use your sentences to train a model, thanks.
A domain doesn't close. A domain is a line of text you rent from a registrar and point wherever you like. If your host goes down, you move. If your CMS dies, you export. The words stay attached to the name.
2. Design is identity
Medium's typography is nice. So is Substack's. So is Ghost's. They all look nice in the same way. They all make your writing feel like it came from the same building and the same committee.
A site you build or commission or configure looks like you. It has your colour on it. It has your font on it. It has the left-margin quirk you insisted on because you like it and nobody else cared. The writing is still the point. But the container is part of the signature.
Readers feel this. They may not articulate it. They feel the difference between walking into someone's living room and walking into a hotel lobby with their name on the wall.
3. Portability is the quiet killer
Try exporting your Medium archive. It is possible. It is also a .zip of HTML files that will not import cleanly anywhere else, with image paths that break and comment threads that do not survive the trip.
Own your domain, write in Markdown or plain HTML or whatever you like, and the words move with you. New host. New theme. New generator. Same text. Same URLs if you want them. Same RSS feed that readers have subscribed to for years.
A decade from now you will have changed stacks three times. The URL on your business card will not have to change once.
4. Nobody censors you for you
This is the uncomfortable one.
Platforms moderate. They have to. They host millions of strangers. They cannot read everything. They deploy rules and filters and human moderators, and sometimes those rules hit your writing and sometimes they do not.
Own the domain, own the policy. If your writing is legal and yours, it stays up. Not because you are trying to get away with something. Because the threshold for "content that gets removed" should be you, not a content policy team in a city you have never visited.
5. You stop writing for the feed
A feed rewards urgency. Be quick, be loud, be often, stay on the timeline. A blog rewards the work.
When your writing lives on your site and your readers arrive through RSS or Atom or the bookmark they made six years ago, you stop performing for an audience that scrolls past you in two seconds. You start writing because the piece deserves writing. You start writing longer things, and better things, and probably slower things. Maybe only once a quarter. That is fine.
The feed will still be there when you want to syndicate. Your site is what survives the feed.
Start small
You don't need a stack opinion. Pick any host that can serve static HTML, point a domain at it, and publish one post. Whatever CMS you like. Whatever generator. The stack doesn't matter. Blogroll lists sites from every corner of every stack, because the stack isn't the point. The ownership is.
When you have one, submit it. It will be read. If it fits the criteria, it goes on the map. Literally.