Launches usually go wrong because the DNS switch gets treated as the finish line. Most launch problems are easy to prevent if they are checked, in order, before and after the switch, so the new site goes live without losing leads, rankings or tracking along the way.
A familiar story: the site looks finished in preview and goes live on a Friday. By Monday the form has been sending to a test inbox, old service URLs return 404 and analytics has recorded nothing.
Treat Launch Day as an SEO Event
A launch changes URLs, templates, metadata and tracking all at once. Search engines and buyers both notice when something breaks.
Common launch problems include:
- Old URLs returning 404
- Staging site indexed alongside the real one
- Forms sending to test inboxes
- Analytics missing on new templates
- www and non-www both resolving
- A 404 page that returns a 200 status
Each one is easy to catch with a checklist. Discovering it a week later is far more expensive.
Choose a Host for Functions, Budget and Upkeep
I set up whichever platform fits: Cloudflare Pages, Netlify, AWS with S3 and CloudFront, GitHub Pages, or Backblaze storage for large static assets. The choice depends on your existing accounts, need for serverless functions, budget and who will maintain it.
For example, a site with a quote form that needs a server function might suit Cloudflare Pages or Netlify. A simple brochure site with no functions could sit almost anywhere. Moving hosts later is straightforward, because a static site is just files.
Redirect Old URLs to Their Closest Match
Every old URL with traffic, rankings or links gets a redirect to its closest new equivalent. The map is tested on the preview URL before launch, then again on the live domain.
On Cloudflare this often uses a _redirects file, and other hosts have their own equivalent. For example, an old "/services/ac-repair.html" page would point to the new "/services/ac-repair/" URL, not to the homepage.
Test Forms and Tracking on the Real Domain
Preview environments sometimes behave differently from production. Every form gets a real test submission on the live domain, checked at its destination.
Analytics and conversion events are confirmed in real-time reports, and Search Console is verified with the sitemap submitted. For example, a quote form that worked on the preview domain can fail on production if its endpoint only allows the preview address.
Check These Before Switching DNS
The pre-launch list is short and boring, which is the point:
- Redirects tested, including trailing slash variants
- Titles, descriptions, canonical tags and schema on key templates
- robots.txt and sitemap correct for production
- Preview URLs set to noindex
- Caching and compression enabled
- DNS time-to-live lowered ahead of the switch
- Rollback plan written down
Switch DNS at a Quiet Time
Launch day itself is the fourth of five steps. Most of the risk is removed in the three before it.
- Review the build, domain, forms, redirects and analytics needs.
- Choose and set up the hosting.
- Prepare launch settings and run the checklist on a preview URL.
- Switch DNS at a quiet time, with rollback ready.
- Verify routing, speed, metadata, forms and indexing on the live site.
Watch the First Few Weeks
Some problems only appear once real traffic and crawlers arrive, such as a missed URL with backlinks. I keep an eye on Search Console, analytics and form deliveries for the first few weeks. Anything missed gets a redirect or fix the same day.
A good launch means old URLs redirect correctly, inquiries do not dip and tracking stays continuous. This suits Astro and static site projects, including sites built by someone else.
Questions about static site deployment
Do you support dynamic features on static sites?
Yes. Static sites can use forms, APIs, serverless functions, Supabase, Convex and third-party services. Deployment includes making sure these work on the chosen host, with credentials stored in environment settings.
Can you help with redirects from an old site?
Yes, and it is one of the most important parts of a migration. Every old URL with traffic or links gets mapped to its closest new page and tested before and after launch.
Which hosting platform is best for a static site?
It depends on the project. Cloudflare Pages and Netlify are simple and include serverless functions, AWS suits teams already using it, and GitHub Pages works for simple sites. I recommend based on your accounts, budget and who maintains the site.
How do you avoid downtime during launch?
The new site is tested on a preview URL first, DNS changes happen at a quiet time with a short time-to-live set in advance, and a rollback plan is ready. Forms and redirects are rechecked straight after the switch.