How to Build a Side Project on an Expired Domain Using a Static Site Generator

Step 1: Why would you want a static site on an expired domain?

Fresh domains rank slower. An expired domain can carry backlinks, aged registration, and maybe some residual traffic. That means your side project gets a credibility boost with search engines from day one. The catch: the domain must not be penalized by Google. Check its history with Ahrefs or Wayback Machine before you buy. A spammy past is worse than a clean new domain.

Step 2: What do you need before you start?

You need three things. First, an expired domain with clean backlinks - buy one at auction or from a dropservice like Dynadot or GoDaddy Auctions. Second, a static site generator (SSG). Pick Hugo, 11ty, Jekyll, or Astro. Third, a free static host: Netlify, Cloudflare Pages, or GitHub Pages. Total upfront cost: roughly $12 for the domain, zero for everything else. That's the whole stack.

Step 3: How do you choose a good expired domain?

Don't buy blindly. Check the domain on Ahrefs or Majestic for referring domains and traffic estimates. Look at the Wayback Machine for what the site used to be. If it was a pharmacy spam site or a link farm, walk away. Good signs: a niche topic you understand, at least 10-20 referring domains from different IPs, and a clean WHOIS history. Bad signs: sudden registration drops, foreign registrars, or a single backlink profile that looks bought.

Step 4: How do you set up your static site generator?

Install your chosen SSG locally. For Hugo, run brew install hugo on a Mac or download the binary. For 11ty, use npm install -g @11ty/eleventy. Create a new project with a single command: hugo new site your-project or npx eleventy --serve. Add a theme or write your own templates. You want a minimal setup - blog posts, about page, and a landing page. The goal is speed, not complexity.

Step 5: How do you connect the domain to the static host?

Point the domain's nameservers to your host. On Netlify, add the custom domain in Site Settings > Domain Management. Set the DNS records: an A record to Netlify's load balancer IPs (75.2.60.5 and 99.83.190.102) or a CNAME to your-site.netlify.app. Cloudflare Pages uses similar steps. Wait up to 48 hours for DNS propagation, though it usually finishes in 15 minutes. You'll get a green SSL certificate automatically.

Step 6: How do you publish your first post?

Write a blog post in Markdown. Add front matter: title, date, tags. Save it in the content/posts/ directory. Build the site with hugo or eleventy - it generates static HTML in a public or _site folder. Deploy by pushing that folder to your host's Git repository or using their CLI. Netlify can auto-build from a GitHub repo. Your first post goes live in under a minute. No database, no server config.

Step 7: How do you keep the site running without a backend?

You don't need a database because SSGs generate all pages at build time. Comments? Use a third-party service like Hyvor or Utterances. Forms? Use Formspree or Netlify Forms. Search? Use Pagefind or a simple JavaScript library. Analytics? Plausible or Umami can be self-hosted or used as SaaS. Every feature is a static embed or a JavaScript snippet. Your site stays fast, secure, and free to host.

Step 8: What can go wrong with a static site on an expired domain?

The domain's history can bite you. Google might have a manual penalty that takes months to lift. The backlinks might be from spammy networks that disappeared. And the domain could get swooped by a domain investor who outbids you at renewal. Mitigate by checking the domain's Google Search Console status before you build. Also, set auto-renew on your domain registration. Losing a domain you've written 50 posts for hurts.

Step 9: How do you monetize a static site with no backend?

Affiliate links work fine - just embed them in Markdown. Display ads from Carbon or BuySellAds need a JavaScript snippet. Digital products like ebooks or templates can be sold via Gumroad or Payhip with a simple link. No backend needed. The revenue is small at first, but the costs are near zero. A single affiliate sale or ebook purchase can cover your domain registration for years.

Step 10: How do you know when to move on?

If after six months of consistent posting you get fewer than 100 monthly visitors, either the domain's backlinks are worthless or your content isn't matching the niche. Cut your losses and bury your dead project on dead.domains. Someone else might want the domain. Or you can browse the graveyard and see what others built - some failures teach you more than a successful project ever could.

Prerequisites: What you need before starting

• An expired domain with clean backlinks (check via Ahrefs or Wayback Machine).
• A static site generator installed (Hugo, 11ty, Jekyll, or Astro).
• A free static host account (Netlify, Cloudflare Pages, or GitHub Pages).
• Basic knowledge of Markdown and Git.
• About $12 for the domain registration.

What can go wrong: The real risks

The biggest risk is buying a penalized domain. Check Google Search Console after you register it - if it shows a manual action, you wasted your $12. Another risk: the domain's backlinks vanish because the linking sites died. And static sites have no dynamic features, so if you later want user accounts or a database, you'll need to rebuild. But for a side project that tests an idea, the static approach is perfect.

If your side project dies, remember you can always bury your dead project and let someone else revive it - or browse the graveyard to see what others learned from their failures.