Back to home
Build

Ship a site from zero: a 6-step flow

Domain, code, deploy, analytics, SEO & GEO, monetization — which site to use at each step, what you end up holding, and where people get stuck.

8 sites · 6 steps

The order follows causality, not importance: a domain comes before DNS, a live URL comes before analytics, and being indexable comes before earning anything. Six steps and you have a site that can pay for itself — at zero cost the whole way.

  1. Register a domain, set up DNS

    Get a name that is memorable, affordable to renew, and ready to point at your host.

    • Search your preferred TLD on NameSilo first. A .com runs around $10 for the first year, with the price shown upfront and no coupon hunting.
    • Turn on WHOIS privacy at checkout (free there) — otherwise your real name, phone and email are public.
    • Hand the nameservers to Cloudflare (the free plan is plenty) so DNS records, TLS and CDN are handled in one place.

    You end up withA live domain plus a DNS console you control.

    Heads upNever compare first-year prices alone — plenty of registrars hook you at $1 then renew at $20. NameSilo publishes renewal pricing too, so compare the three-year total.

  2. Create the repo

    Get the code under version control — in a repo that can trigger deploys directly.

    • If your audience is mainly in mainland China, start with Gitee — fast pushes, no proxy needed, and it still works with Vercel.
    • For open source or international projects, GitHub wins on ecosystem: Actions, Pages, and the biggest pool of templates.
    • One repo per site, keep a single main branch. Every push builds automatically, which is effectively a free preview environment.

    You end up withA remote repo you can clone and push to, with a README.

    Heads upNever commit secrets. Not even in a private repo — put every token in the platform env vars.

  3. Deploy

    Push and it is live, then bind your own domain with automatic HTTPS.

    • Connect the repo to Vercel and it auto-detects your framework (Nuxt, Next, Astro all work with zero config) and gives you a preview URL.
    • Static sites can go on Cloudflare Pages instead — global edge nodes, a generous free tier, and it lives next to your DNS.
    • Add the custom domain in the platform, create the CNAME / A records back in Cloudflare, and the certificate issues itself within minutes.

    You end up withA live site at https://your-domain.

    Heads upIf the site 404s or asks for auth right after binding, check Vercel Deployment Protection — preview URLs are gated by default, custom domains are not.

  4. Wire up analytics

    Know who arrives, from where, and where they leave — otherwise there is nothing to optimize.

    • Drop in the Microsoft Clarity snippet — free, unmetered, and its heatmaps and session replays show exactly what people click.
    • Tag traffic sources in Clarity, or add one lightweight counter — do not stack five scripts on day one and wreck your first paint.
    • Load it async, even in head, so it never blocks rendering.

    You end up withA dashboard with live visits and heatmaps.

    Heads upA brand-new site has near-zero traffic. Do not stare at the counter — the value shows up months later when you rewatch the recordings.

  5. Get indexed: SEO & GEO

    Be findable by search engines, and quotable by AI assistants.

    • Verify the site in Search Console (DNS or HTML tag, either works) and submit sitemap.xml.
    • Give every page its own title, description and canonical, plus JSON-LD (Organization, WebSite, BreadcrumbList).
    • The cheap way to do GEO: publish an /llms.txt describing your structure, and explicitly allow GPTBot, ClaudeBot and PerplexityBot in robots.txt.
    • Write conclusion-first, in short quotable paragraphs — both AI summaries and search snippets prefer that shape.

    You end up withSearch Console reports the pages as indexed and the sitemap as successful.

    Heads upIndexing is not instant — days to weeks is normal for a new site. Do not buy links to speed it up; that is the fastest way to kill a site.

  6. Monetize

    Only talk money once traffic is stable — and know your numbers first.

    • Before applying to AdSense, have a dozen real pages, a privacy policy, an about page and working navigation — that is what review looks at.
    • Do not carpet the page. One or two above the fold, one mid-article, one at the bottom on mobile — let auto ads explore the rest.
    • Track your own numbers too — daily PV, bounce rate, time on page — and compare the week before and after ads go live to see if they hurt the experience.

    You end up withAdSense approved, with revenue showing up.

    Heads upAdSense requires content-first, ads-second. Overloading ads gets you rejected or banned — better to run two fewer slots than lose the account.