You can build a working website for $0 by pairing a free hosting plan with an open-source publishing tool — WordPress.org on free hosting, GitHub Pages, or Netlify — and registering a free subdomain instead of a paid one. The catch is structural: on every major no-cost tier you trade either a platform badge, a subdomain URL, or monthly bandwidth, and some “free” hosts quietly lock your files behind a paywall. The steps below take you from blank browser tab to live, indexable site without a credit card, and flag exactly where each ceiling sits.

Step 1: Pick a Free Platform That Matches What You're Publishing

The right choice depends on one question: do you need a database-driven site you can move later, or a fast static site? Free hosting splits cleanly into both camps, and picking wrong means a migration in month two.

Platform Free tier model Subdomain you get Best for Key ceiling
WordPress.com Ads on your site, 1 GB storage yoursite.wordpress.com Bloggers who want zero setup No plugin uploads on the free plan
GitHub Pages Static files only, 1 GB repo limit username.github.io Developers, portfolios, docs No server-side code (no PHP)
Netlify Static hosting, 100 GB bandwidth/month sitename.netlify.app Static site generators, forms Build minutes capped at 300/month
InfinityFree Unlimited storage, no ads injected sitename.infinityfreeapp.com or your own domain WordPress on a budget Inactivity suspensions on dormant accounts

GitHub's own documentation states the 1 GB repository limit and a soft 100 GB-per-month bandwidth limit for Pages — figures worth knowing because they cap video-heavy sites fast. WordPress.com's free tier injects its own ads, which matters if you plan to monetize later.

If you haven't chosen a host yet, start with the tool you'll publish from. Site builders like WordPress.com and static generators like Hugo or Jekyll force different decisions: WordPress gives you a dashboard and themes, while static generators demand a Git workflow but survive traffic spikes without crashing. The table above maps that trade-off.

Pick GitHub Pages if you can edit text files and want a site you fully control. Pick WordPress.com if you want to type into a browser and never touch code. Pick Netlify if you're learning static site generators and want deploy previews. Skip InfinityFree if your site will sit idle for weeks — account inactivity triggers suspensions that take hours to reverse.

Step 2: Claim a Free Subdomain (and Know What the Paid Upgrade Actually Buys)

Every free tier hands you a subdomain, and that URL is the real cost of free. A subdomain looks like yourname.github.io or yoursite.wordpress.com — it works, it's indexable, and it costs nothing. What it doesn't do is build brand equity you own the way a custom domain does.

Custom domains cost roughly $10–20 per year from registrars like Namecheap or Cloudflare, per each registrar's published pricing. That's the only unavoidable expense in this entire guide, and you can defer it indefinitely. Google's search documentation confirms subdomains are indexed and ranked as normal sites, so the SEO penalty people fear is largely myth — the real loss is brand recall, not ranking.

Choose your subdomain the way you'd choose a domain: short, pronounceable, no numbers substituting for words. GitHub usernames become part of the URL, so check the name you want before committing — you can't change a GitHub Pages URL without renaming your account or using a custom domain. WordPress.com subdomains follow your account name too.

A free-plan subdomain has one hard limit worth naming: you can't transfer it. If you build six months of content on yourname.wordpress.com and later want a custom domain, WordPress.com's paid plans allow mapping one, but the platform badges and storage caps follow the plan, not the domain. Plan the rename before you publish anything you'd regret abandoning.

Step 3: Install Your Publishing Tool and Choose a Theme

With hosting picked, you need the thing that turns blank pages into HTML. On WordPress.com there's nothing to install — themes come from the dashboard under Appearance → Themes. On GitHub Pages and Netlify you install a generator locally: Jekyll ships preinstalled on GitHub Pages, so a Jekyll site deploys with no build configuration at all.

The theme is where beginners lose the most hours. Free themes number in the thousands, and most are built for different jobs. Start with a theme's demo content, replace the text, and delete what you don't need — rebuilding a theme's layout from scratch is the slowest possible path. On WordPress.com, Twenty Twenty-Four is the current default block theme and works without plugins.

Watch for theme bloat on free tiers. A theme that loads ten font files and four JavaScript libraries consumes storage on capped hosts and slows your site on shared infrastructure. Weigh a theme's demo speed over its screenshots — a pretty theme that takes six seconds to paint loses readers before your content appears.

If you're on Jekyll, the default Minima theme is intentionally minimal and deploys without configuration; swap it once you understand how layouts, includes, and front matter work. The fastest route to a live page is committing the default theme untouched, confirming the deploy, then customizing. Establish the pipeline before styling anything.

Step 4: Build the Four Pages Every New Site Needs

Aim for four pages before launch, not twelve: Home, About, one content page (a blog post or portfolio piece), and a Contact page. Four pages is enough to be indexed, tested, and useful, and it's small enough to finish in an evening. Most beginners stall because they plan a site too large to ship.

Build Home first, because it's the page search engines and humans see first. Put one clear sentence at the top saying what the site is for, then links to everything else. On WordPress.com that's a page with blocks; on Jekyll it's index.md with front matter. Don't decorate before the words exist — content decides layout, not the reverse.

The About page does more ranking work than people expect. Named entities, a person, a place, a specialty, give search engines signals to associate with your site, and visitors decide in seconds whether to trust you. Write it in first person, name the city or niche, and state what you'll publish. Skip the mission-statement voice.

Contact pages on free tiers are where forms break. Static hosts don't run server code, so a plain HTML form has nowhere to submit; Netlify Forms processes up to 100 submissions per month on its free tier, per Netlify's pricing page, and WordPress.com provides a built-in contact form block. If neither applies, put an email address in plain text — a mailto link beats a form that silently discards messages.

Step 5: Make the Site Findable Before It Goes Live

Publishing is not the same as being found. Three settings do most of the discoverability work, and all three are free: a title tag per page, a meta description per page, and a sitemap submitted to Google Search Console. Skip them and you'll wait weeks for indexing that could take days.

Set every page title deliberately. WordPress.com handles this under Settings → General for the site title and per-page settings for individual titles; Jekyll sites use SEO plugins or hand-written front matter. A title like "Jane Doe — Freelance Illustrator in Leeds" beats "Home" because it names the person, the service, and the place. Google rewrites titles sometimes, but a strong one usually survives.

Submit a sitemap to Google Search Console and Bing Webmaster Tools. Both are free with any Google or Microsoft account, and both accept sitemap URLs. WordPress.com generates sitemaps automatically at yoursite.wordpress.com/sitemap.xml; Jekyll needs the jekyll-sitemap plugin, which GitHub Pages supports because it's on the allowed-plugins list. Google's own documentation confirms submission speeds discovery but doesn't guarantee ranking.

Verify mobile rendering before launch. Google indexes the mobile version of pages first, so a desktop-only layout loses visibility. Test with your phone, not a browser emulator — emulators miss touch targets and font scaling that real thumbs notice. Fix navigation first; a menu that requires pinching kills a site faster than slow load times.

Step 6: Publish, Then Set Up Free Backups and Analytics

The first deploy is anticlimactic by design. On GitHub Pages you commit to the main branch and the site builds in under a minute; on Netlify you connect a repository and every push triggers a deploy; on WordPress.com you press Publish. Confirm the live URL loads in a private window, because cached logins hide broken pages.

Back up before you need to. Free tiers rarely include automatic backups, and a deleted page on a static host is only recoverable from your local files or Git history. Keep the project folder on your machine and in a repository — that's your backup. On WordPress.com free, exports run through Tools → Export, and you should run one after every significant content addition.

Analytics on a zero budget means choosing privacy-friendly tools or none. Google Analytics 4 is free and works on every platform covered here, but requires a script snippet; static sites add it in the theme's head include, WordPress.com adds it via a plugin or the built-in integration on paid plans. Cloudflare Web Analytics is free without a script and doesn't use cookies. Pick one and stop — two analytics scripts on a free host slow the site for duplicate data.

Set a reminder to check the site monthly. Free tiers suspend inactive accounts, expire dormant repositories in some cases, and change terms without email. A five-minute monthly visit — load the homepage, click three links, confirm the contact method works — catches the failure modes that silently break free sites. Automation is worth more than monitoring here.

Static Hosts vs. Managed Builders: Which Free Tier Fits Whose Skills

The choice between a static host like GitHub Pages or Netlify and a managed builder like WordPress.com isn't about quality; it's about how much friction you can absorb and what you'll do with the site in a year. Static hosting rewards people comfortable with files and version control. Managed builders reward people who want to write and publish, full stop.

Dimension GitHub Pages / Netlify WordPress.com free
Setup time to first page 30–60 minutes with Git installed 10–15 minutes, browser only
Technical floor Markdown, Git basics, YAML front matter None
Free storage 1 GB (GitHub) 1 GB
Ads injected None Platform ads on free tier
Plugins/extensions Build-step plugins only No third-party plugins on free
Portability Full — files are yours Content exportable, design not
Failure mode Broken build, blank deploy Account-level limits, ads
Best for Portfolios, docs, developer blogs Writers, small personal sites

Time-to-first-page is the honest differentiator. A Jekyll site on GitHub Pages took me roughly an hour to get live the first time, mostly spent on Git authentication; WordPress.com is a form and a password. Neither number is a criticism — the static site is faster to maintain once the pipeline exists, and the managed site is faster to start but slower to migrate away from.

Portability matters more than most beginners think. If your site becomes valuable, moving from GitHub Pages means copying files to any host you like — no export step, no design loss. Moving from WordPress.com free means exporting content as XML and rebuilding the theme elsewhere, which is a weekend project for a small site and a contractor project for a large one. That asymmetry should influence where you start if you expect the site to grow.

Skip static hosting if you'll never use version control and have no interest in learning it. Skip WordPress.com free if platform ads on your pages are unacceptable, which they are for anyone building a professional portfolio on a budget. For everyone in between, the tiebreaker is content type: prose favors the builder, structure favors the static host.

Five Failure Cases That Kill Free Sites (and the Fix for Each)

Free hosting fails in patterns. Knowing the patterns before they hit saves the specific hours beginners lose to invisible problems — most of which have published fixes.

GitHub Pages builds fail silently after a theme change. The repository shows the commit, but the live site keeps the old HTML for ten-plus minutes. Check the Actions tab for the build log; a missing dependency in _config.yml is the usual culprit. Fix the plugin list, commit again, and wait for the green checkmark before assuming the site is broken.

WordPress.com free storage fills without notice. The 1 GB cap counts media uploads, and a single uncompressed photo from a modern phone can exceed 5 MB. Compress images before upload — 1,600-pixel-wide JPEGs at quality 80 keep most photos under 300 KB. If you hit the cap, media uploads stop and posts save without their images.

Netlify's 300 monthly build minutes run out mid-month on actively edited sites that rebuild on every commit. Vercel's free tier and Netlify both exist for this reason; if you edit daily, either reduce build frequency or expect an upgrade email mid-month. Check the usage dashboard weekly rather than discovering the limit on a deadline.

Free hosts suspend inactive accounts. InfinityFree and comparable free hosts enforce activity rules; GitHub doesn't suspend repositories, but dormant Pages sites remain live. The risk is concentrated in free PHP hosting, where suspension takes hours to reverse. Keep a calendar reminder if you choose that route.

A mailto contact link gets harvested into spam. Publishing a raw email address on a free site attracts crawlers within days. Use a form service with a free tier, or obfuscate the address. There's no passive fix; a public email is public.

What Free Actually Costs You Over Twelve Months

A year of free hosting is genuinely free in money and expensive in two currencies: time and optionality. Add up the real hours and the upgrade prices, and the “free” decision becomes a budget line instead of an assumption.

Time is the largest cost, and it clusters at the start. Expect 5–10 hours to launch on a managed builder and 8–15 hours on a static host for a first-timer, based on the setup work in Steps 1–6. After launch, maintenance runs 15–30 minutes a month for backups, analytics checks, and small edits. That's roughly 8–14 hours in year one, which is the actual price of the free tier.

Upgrades cost real money the moment you outgrow the ceiling. WordPress.com's paid plans and custom domain mapping run in the low tens of dollars per month at the entry tier, per WordPress.com's published pricing, and static hosts charge for bandwidth overages or team features on their paid tiers. None of these are necessary on day one, but a site that grows past 1 GB of images or 100 GB of bandwidth will hit them.

The cheapest durable setup for most readers is a free static host with a paid custom domain: $10–20 per year, all other costs zero, no injected ads, full file portability. The second cheapest is WordPress.com free plus a domain, at the same domain cost with platform ads attached. Price the upgrade path before you commit content you can't move easily.

FAQ

Do I really need to pay for a domain, or is a free subdomain fine forever?

A free subdomain is fine indefinitely for testing and personal projects, and Google indexes subdomains normally. The real cost is brand: readers remember “janedoe.com,” not “janedoe.github.io.” A custom domain costs about $10–20 per year and is the single upgrade worth making first.

Can I put ads on a free site and keep the revenue?

It depends on the host, not the ads. WordPress.com's free tier shows platform ads and does not let you run your own ad network; moving to a paid plan or self-hosted WordPress unlocks that. Static hosts like GitHub Pages allow ad code, but AdSense approval requires a domain you control and a site with substantial original content.

What happens to my site if the free host shuts down or changes its terms?

You lose whatever you didn't export. Static sites are safer because your files live in a repository you can copy to any host in minutes. Managed builders require a content export and a theme rebuild, so run Tools → Export quarterly and keep the file somewhere you control.

Is a free website fast enough to keep readers, or will it feel slow?

Static hosts are typically fast because they serve prebuilt HTML from a CDN, while free WordPress.com tiers share infrastructure and can slow under load. Test your live site with PageSpeed Insights once it's up — a score under 50 usually means heavy images or an overloaded theme, both of which you can fix without paying.

Can I move my free WordPress.com site to my own hosting later?

Yes, but only the content moves cleanly. WordPress.com's export tool produces an XML file you can import into a self-hosted WordPress install; the theme, plugins, and design are rebuilt from scratch. Plan a few hours for a small site and budget paid help for anything over a few dozen posts.

Does a free website work for a business, or will customers distrust it?

A free subdomain signals hobby, not business. For a business site, the $10–20 annual domain plus a free static host is the minimum credible setup, and it removes the ads and badges that make customers hesitate. The content and contact method matter more than the URL once the domain is yours.

This article is general educational information about website hosting and publishing, not legal, financial, or professional advice. Free-tier terms, limits, and pricing change without notice, so confirm current conditions on each provider's official site before relying on them, and consult a qualified professional for business or legal decisions.