I run a small site called Books in 60 Seconds. It does one thing: short summaries of bestselling books, each readable in about a minute. I am a school teacher in Narowal, Pakistan, and I built it in the evenings, with plain HTML, CSS, and JavaScript, hosted free on Cloudflare Pages.
This week it moved to its own domain: books60seconds.com.
Nothing about the site changed for readers. Same summaries, same pages, same address structure. The old address redirects to the new one. What changed is what the site is: instead of living on a free subdomain, it now has an address of its own.
Why that mattered to me:
A free subdomain looks borrowed. When I shared the old link, people saw a platform's name first and mine second. The new address is just the site's name. Easier to say, easier to remember, easier to trust.
Search engines treat it as a real site. The site had zero pages in Google's index on the free subdomain. A standard domain is the baseline Google expects for a site it takes seriously. This is not a guarantee of anything — it is removing one obvious obstacle.
It made the project feel permanent. Sixty-plus summaries is a lot of evenings. Giving the work its own address felt like deciding it is here to stay, not an experiment I might abandon.
The cost was $11.17 for a year, at Cloudflare's at-cost registrar pricing, with free WHOIS privacy. The move itself was a custom domain on the existing Pages project, redirects from the old address, and updated canonical URLs. No redesign, no new stack, no new tools.
I don't know what comes next. Traffic is near zero, and a domain doesn't fix that on its own. But the site now has a front door with its own name on it, and that is a better place to build from.
If you want to look: https://books60seconds.com/?utm_source=devto&utm_medium=article&utm_campaign=books-launch
Top comments (0)