Launch your first website

This quickstart walks you from an empty workspace to a production site. Build Me Web handles hosting, certificates, and CDN delivery; you focus on brand, content, and conversion. Budget about ten minutes for the happy path if DNS is already under your control. Domain propagation and stakeholder review can add time outside this guide.

Before you begin, confirm you can sign in to the workspace, that you have permission to create sites, and that you know which hostname visitors should use (apex, www, or a campaign subdomain). Have your logo (SVG or transparent PNG), brand colors, and a short list of pages ready.

1. Choose a template

From your project workspace, open Websites New site. Templates are starting points, not locked designs: brochure, lead generation, blog, and service portfolios ship with responsive layouts, semantic heading structure, accessible navigation, and placeholder content you replace with your own.

Match the template to the job of the site. A brochure template suits brand and about-us storytelling. Lead-gen templates emphasize a single primary CTA and form. Blog templates include listing pages, article chrome, and RSS-friendly markup. If you are unsure, start with brochure and add a blog section later — merging later is easier than ripping out unused complexity.

1. Select a template and give the site an internal name your team will recognize (for example, “Acme marketing 2026”).
2. Choose the primary locale and default language. Secondary locales can be added after the first publish.
3. Set brand colors and upload a logo. Prefer tokens over one-off hex values so later sections stay consistent.
4. Confirm starter pages (typically Home, About, Contact). Remove pages you will not ship; empty stubs hurt SEO and navigation clarity.

New site wizard
├── Template (brochure | lead-gen | blog | services)
├── Locale & brand tokens
├── Starter pages
└── Workspace ownership / billing project

On Growth and Managed engagements, your specialist can seed the site from an approved design system so the first draft already matches production brand guidelines. Starter and self-serve workspaces use the public template gallery.

2. Configure pages

Open the site builder and replace headline, supporting copy, and imagery on each starter page. Keep one clear CTA above the fold on Home. Supporting sentences should explain who you help and what happens after the click — not a laundry list of features.

Use the media library for WebP (or AVIF where supported) assets with explicit width and height. That protects Largest Contentful Paint and Cumulative Layout Shift. Avoid embedding unoptimized PNGs from design tools as hero images; export at 1x and 2x widths you actually need.

Configure global chrome before polishing every section:

Site settings
├── Brand (logo, colors, fonts)
├── Navigation (primary + footer)
├── Shared modules (CTA bar, cookie notice)
└── SEO defaults (title pattern, meta description, social image)

Write unique titles and meta descriptions for Home, About, and Contact even if body copy is still draft. Search engines and social unfurls use these fields immediately after publish. Keep titles under roughly sixty characters and descriptions under roughly one hundred fifty-five.

Forms: wire the contact form to an inbox or CRM destination under Integrations. Send a test submission from preview and confirm the confirmation message, notification email, and spam protections (honeypot / rate limit) behave as expected.

• Home hero states audience + outcome in one sentence
• Primary CTA appears once above the fold and again near the footer
• Images have alt text that describes content, not “image1”
• Contact form delivers to a monitored inbox
• 404 page exists with a path back to Home

When pages feel complete in the canvas, open a shareable preview link. Review on a phone-sized viewport: navigation collapse, tap targets, and form fields are the usual failure points.

3. Connect a domain

Open Domains and add your apex domain, www host, or both. Build Me Web shows the exact DNS records to create at your registrar. After DNS resolves to our edge, SSL certificates provision automatically.

Pick one canonical host and redirect the other. Search engines treat example.com and www.example.com as different URLs if both serve 200s. Prefer a single redirect policy and stick to it across environments.

• Use A / ALIAS records for apex domains as instructed in the Domains panel.
• Use a CNAME for www and campaign subdomains.
• Add any TXT verification records before you expect certificates to issue.
• Wait for DNS propagation before forcing HTTPS-only — premature HSTS can lock browsers onto a host that is not ready.

Propagation is often minutes, occasionally hours, and rarely up to forty-eight hours depending on prior TTLs. The Domains panel shows verification status; refresh after your registrar confirms the change. If you use a DNS proxy (orange-cloud style), follow the proxied vs DNS-only guidance in Custom domains & SSL so certificates can complete HTTP challenges.

4. Publish

Run a final preview against the production-like URL, then publish to production. Publishing builds static assets, invalidates relevant CDN paths, and updates the live hostname once health checks pass.

Immediately after go-live:

1. Load the canonical URL in a private window and confirm HTTPS, redirects, and the homepage CTA.
2. Submit a test contact form and verify delivery.
3. Verify ownership in Google Search Console (and Bing if relevant) and submit the sitemap from Analytics SEO.
4. Spot-check Core Web Vitals on a mobile Lighthouse run against the live URL.

Document the launch in your workspace notes: who approved content, which domain is canonical, and where DNS is managed. Future teammates should not have to reverse-engineer the cutover.

Troubleshooting

Preview looks fine, production does not: confirm you published the correct environment and that a CDN cache purge completed. Hard-refresh or try a second network.

SSL pending: recheck DNS, remove conflicting AAAA records if unused, and ensure the hostname is not pointing at an old host.

Form silent failures: check spam folders, integration credentials, and whether preview vs production destinations differ.

Best practices

Ship a thin vertical slice first — Home, About, Contact — then iterate. Keep staging content non-indexable. Treat every publish as reversible: leave a path to roll back to the previous release from release history. Revisit SEO titles after real Search Console data arrives rather than endlessly polishing before launch.

Prerequisites & preparation

Before changing production settings for website launches, align the people who own content, DNS, analytics, and approvals. A fifteen-minute kickoff that names owners prevents multi-day Slack archaeology later. Capture decisions in the workspace notes so the next teammate inherits context instead of guesswork.

Gather credentials and access: workspace admin or editor role, DNS control when hostnames are involved, payment or API sandbox accounts when money paths are involved, and a shared checklist link. Confirm which environment you will rehearse in — preview first, production only after a green run.

Align brand assets, draft Home/About/Contact copy, pick a canonical hostname, and confirm who approves the final preview. Draft legal pages in parallel if they are required before public traffic.

Detailed walkthrough

Work the happy path slowly the first time. Narrate what you expect to see after each click: a status badge, a DNS record, a webhook delivery, a Lighthouse metric. When reality diverges, stop and resolve the mismatch instead of clicking ahead — most outages begin as ignored yellow states.

1. Create the site from the closest template and delete unused starter pages.
2. Replace hero copy with one audience and outcome; keep a single primary CTA above the fold.
3. Optimize hero media with dimensions set; verify the LCP element on a mobile preview.
4. Wire the contact form; test from desktop and phone against the real destination.
5. Add DNS, wait for SSL, publish production, and submit the sitemap in Search Console.

Worked example:

Launch gates
content approved → DNS verified → SSL green → publish → sitemap → smoke form

Edge cases & failure modes

Plan for partial failure. Networks drop, registrars delay, providers rate-limit, and humans approve the wrong revision. Your runbook should say what “abort” looks like: leave preview up, roll back the release, or freeze campaigns until metrics recover.

• Stale DNS TTLs sending a fraction of users to the old host.
• AAAA records pointing at unused IPv6 targets breaking intermittent clients.
• Proxy modes interfering with certificate HTTP challenges.
• Stakeholders reviewing an expired preview URL after a rebuild.
• Consent UI shifting the hero and harming CLS on first visit.

QA checklist before you announce

• Canonical redirects verified
• Form deliverability confirmed
• Mobile navigation usable
• Analytics page view fires once
• 404 page offers a path home

Operating the change

After launch, watch the metrics that prove the change worked — not vanity charts. Pair quantitative signals with one qualitative check (support ticket themes, sales feedback). Schedule a follow-up within a week to remove temporary flags, raise DNS TTLs, or archive the experiment.

Watch form volume, Search Console coverage, and field Core Web Vitals during week one before scaling paid traffic.

Ship a thin vertical slice first. Holding launch for every future blog idea or calculator delays learning. Publish Home, About, and Contact with honest offers, then iterate with measured publishes.

Make talk tracks and hero copy match. When sales wins with a phrase on calls, that phrase belongs on the site. Mismatch increases bounce and sales frustration.

Locales: freeze information architecture in the primary language before cloning for translation. Moving sections under translators creates expensive rework.

Agency publishes still need a recorded approval on the live preview URL — not screenshots — so fonts, consent, and forms are real.

Record where DNS is managed, who can publish, and which analytics property is source of truth. Certificate emails six months later should not be a scavenger hunt.

After launch, resist dumping every marketing tag onto the homepage on day one. Add tags with owners and performance budgets so LCP does not collapse under celebration pixels.