A website go-live succeeds or fails in about six workstreams: DNS cutover, redirects, CRM and analytics tracking, sitemap and search-engine submission, forms and lead flow, and system pages. The pattern that repeats across launches is not exotic — it is a site that renders perfectly but quietly loses leads because the tracking code never fired, forms submit to nowhere, or old URLs 404 with no redirect map. Whether the new site runs on HubSpot or another CMS, the checklist below is the order of operations: content and QA first, DNS and redirects at cutover, tracking and CRM verification immediately after, and a rollback plan agreed before anyone changes a nameserver. This guide is written for marketing and ops teams who own the launch and the CRM it feeds.
Content skim and QA. Even after formal QA, do a final site-wide skim on launch week: placeholder text, broken internal links, orphaned images, and wrong phone numbers all survive staging environments with remarkable consistency. Check every template type, not just the homepage.
Redirect map. Every URL that existed on the old site needs a decision: keep, redirect (301), or deliberately retire to a well-built 404. Build the map as a spreadsheet — old URL, new URL, redirect type — and stage it in the CMS before DNS moves. HubSpot's URL redirects tool supports individual and bulk-imported redirects; either way, importing after traffic arrives means real visitors hit dead ends in the gap.
Tracking staged, not just planned. The HubSpot tracking code, Google Analytics, ad-platform pixels, and any consent-management tooling should be installed and verified on the new site before it is public. HubSpot's tracking-code documentation covers installation and verification; the fastest check is viewing the page source and confirming the code renders, then watching a test visit appear in analytics real-time views.
Forms tested into the CRM. Submit every form with test data and trace the full path: submission recorded, contact created or updated, notification emails sent, any workflow or lead-routing triggered, thank-you page or redirect correct. Form-to-CRM mapping failures are the single most expensive launch defect because they are silent — the site looks fine while leads evaporate.
Lower the TTL on your DNS records at least a day ahead so the cutover propagates in minutes, not hours. Confirm with your DNS host exactly which records change — for a HubSpot-hosted site this is typically a CNAME pointed at HubSpot — and screenshot the prior records so rollback is a paste operation, not a reconstruction. After the change, verify the site resolves on the new host, SSL is active (HubSpot provisions SSL for connected domains; verify the padlock on multiple templates, not just the homepage), and both the apex and www variants behave as intended. Only then announce.
Decide the rollback trigger before cutover: what failure (site unreachable, SSL broken, forms down) means you revert DNS, and who is authorized to call it. Keep the old site reachable at its origin for a few days so rollback is a DNS change, not a restore. Assign one person as launch-day owner with the authority to sequence the checklist — launches fail by diffusion of responsibility more often than by technical surprise. HubSpot-focused launch checklists from experienced partners converge on the same short list: content skim, DNS, tracking codes, sitemap, redirects, system pages, contingency — in roughly that order.
Turn this checklist into a runbook with named owners and timestamps, and schedule the launch for a low-traffic window with the team available the following morning — not Friday afternoon. If the new site introduces a new CRM, new forms, or a new domain at the same time, sequence the risk: launch the site first, migrate lead flow second, or run both under a single, rehearsed plan with a tested rollback. The goal is not a perfect launch; it is a launch where every failure is detected in hours, not discovered in next month's lead report.
Vantage Point supports website launches where the CRM is the point — HubSpot tracking, form-to-CRM mapping, lead routing, and post-launch verification — through HubSpot services and HubSpot implementation. For teams replatforming and rebuilding integrations at once, system integration and data migration keeps the data side of the launch honest.
Vantage Point is a HubSpot and Salesforce Solutions Partner and is employee-owned. Senior consultants only — no junior handoffs; the experts you meet are the experts who deliver.
Content and QA first, redirect map and tracking staged before cutover, DNS changes at cutover (with TTL lowered in advance), then immediate verification of tracking, sitemap submission, redirects, forms, and system pages — with a rollback plan agreed before anyone touches DNS.
View the page source on several templates and confirm the tracking code renders, then watch a test visit appear in HubSpot analytics and on a test contact's activity timeline. HubSpot's tracking-code documentation covers installation and verification steps.
Every URL from the old site with a decision: keep, 301-redirect to a specific new URL, or deliberately retire. Build it as a spreadsheet, stage it in the CMS before DNS moves, and spot-check the highest-traffic entries immediately after cutover.
TTL controls how long DNS resolvers cache your records. Lowering it a day ahead means the cutover — and any rollback — propagates in minutes instead of being stuck behind a hours-long cache on visitors' networks.
CRM and form verification. Sites routinely launch looking perfect while form-to-CRM mapping silently fails or tracking never fires — test every form end-to-end on the live domain, including workflow notifications and lead routing.
Yes. QA happens on staging; DNS, SSL, and third-party scripts behave differently in production. A rollback plan is a screenshot of the old DNS records, a defined trigger for reverting, and a named decision-maker — cheap insurance that makes cutover reversible.