Subdomain vs Custom Domain: What It Means for SEO

If you're hosting on static.app's free tier, your website lives at a subdomain like brave-whale.static.domains (the platform assigns a random name; you can customize it in Settings → Domains). You can also connect a custom domain like yoursite.com . The question this article answers: does it matter for SEO, and is it worth the upgrade?

Short answer: yes, but probably not in the way you'd expect.

The technical SEO difference is small

A static.domains subdomain can rank in Google just like a custom domain can. Google doesn't penalize subdomains. Search results don't show "powered by static.app" or anything like that. The user sees your title and description, clicks, and lands on your website.

If two websites are otherwise identical, one on a subdomain and one on a custom domain, the custom domain has small advantages:

Slightly easier to remember and share verbally
A backlink to yoursite.com is more valuable than a backlink to yoursite.static.domains , because the link signals concentrate on a domain you own
You own the URL forever. If you ever leave static.app, your links don't break.

The bigger difference is perception

When someone searches for your business and your website shows up as yoursite.static.domains , many users read it as "this is a hobby website or a demo." Conversion rates on visits will be lower. Other websites are less likely to link to you, and journalists, partners, or potential clients sometimes won't take you seriously.

Both of those indirectly hurt SEO, even if Google doesn't penalize the subdomain itself. Search engines weigh user behavior signals (click-through rate, time on website, return visits) and the quantity of inbound links. A custom domain wins on both fronts.

If you're treating the website as a real business, you want a custom domain. Domains cost roughly 10 to 20 dollars a year. The math is easy.

When the subdomain is fine

You're testing an idea and not sure you'll keep the website
You're learning HTML and not ready to commit
You're hosting documentation, a project page, or a portfolio piece that doesn't need a brand of its own
You're sharing previews with clients before moving to a final domain

Switching from subdomain to custom domain later

This is the part people worry about most, but it's straightforward. The migration generally takes under an hour of active work, plus some waiting for DNS to propagate.

Step 1. Buy your domain from a registrar (Namecheap, Porkbun, Cloudflare Registrar are all fine). Pick a clean name. Avoid hyphens and numbers if you can.

Step 2. In your static.app dashboard, go to Settings → Domains and add your custom domain in the Custom Domain section. Click Test domain. Static.app will tell you the DNS records to add at your registrar. The typical setup is:

A-record pointing @ (your root domain) to 51.81.81.65
TXT-record at @ with the verification string Static.app gives you, in the format static-site-verification=YOUR_UNIQUE_CODE

Step 3. Add those DNS records at your registrar. There are detailed step-by-step guides for the common ones:

One detail worth flagging: if you use Cloudflare, set the A-record's proxy status to DNS only (the gray cloud, not the orange one). Cloudflare's proxy interferes with Static.app's SSL provisioning. The Cloudflare guide above walks through this.

Step 4. DNS changes typically propagate in 5 minutes to a few hours. Once they're live, go back to Settings → Domains and click Test domain again. When you see "Domain is ready!", you're done. SSL is provisioned automatically and free.

Step 5. Verify your website loads on the new domain. The old .static.domains subdomain should redirect to your custom domain automatically. This redirect is what tells Google to credit any links pointing at the subdomain to the new URL, so don't skip verifying it.

Step 6. Add the custom domain as a new property in Google Search Console (and Bing Webmaster Tools). Resubmit your sitemap with the new URLs. The old subdomain property can stay around to monitor any leftover traffic.

If anything goes wrong with the test, the platform allows reconnecting a custom domain multiple times, but no more than 5 times in a single week to avoid propagation issues.

What happens to your rankings

If you do the migration cleanly (with redirects in place from the start), Google passes link equity from the old URL to the new one. You might see a brief dip in rankings during the transition, usually for a week or two, then a recovery. Often the recovery lands you slightly higher than before, because the custom domain reads as more trustworthy.

If you do the migration messy (no redirects, abandoned subdomain), you can lose months of accumulated SEO progress. The redirect is the critical piece. Don't skip it.

If you ever wonder whether to put your blog at blog.yoursite.com or yoursite.com/blog/ , choose the subdirectory. Google treats subdomains as separate websites, so authority you build on the blog doesn't fully transfer to the main website. With a subdirectory, everything compounds together. On static.app, this means putting your blog posts in a /blog/ folder rather than setting up a separate subdomain.

If you're past the testing phase, get the domain.

The technical SEO penalty for a subdomain is small, but the perception penalty (and the link equity penalty over time) is real. Twenty dollars a year is a rounding error compared to what you'll gain in credibility.