Google Analytics Setup After a Website Redesign

Google analytics setup after a website redesign is one of the most consequential technical tasks of the entire project, and one of the most frequently deferred until after launch.

Launching a redesigned site without properly configured analytics is like opening a new store without a cash register: you generate activity you cannot measure, from sources you cannot identify, through a funnel you cannot optimize.

The first 90 days after a redesign launch establish the performance baseline against which every future optimization decision will be made.

Getting analytics right before launch day is not optional, it is the foundation of every ROI claim you will ever make about the project.

Key Takeaways

• Set up GA4 before launch, not after: Analytics configuration that happens post-launch misses the highest-traffic days of the launch period, that baseline data is critical.
• GA4 requires a new setup mindset: The event-based model, conversion configuration, and reporting are fundamentally different from Universal Analytics.
• Conversion events must be explicitly configured: GA4 does not track form submissions or button clicks by default, every business-critical event requires manual setup.
• Historical data comparison requires pre-launch planning: Comparing pre- and post-redesign performance requires a data preservation strategy established before launch day.
• The first 30 days of data are your new baseline: The post-launch period establishes the performance benchmark for all future optimization, getting it right is the highest priority.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

Pre-Launch Analytics Preparation

Post-launch tasks after redesign are manageable when pre-launch analytics preparation is completed correctly. The foundation you build before the site goes live determines the quality of every measurement you make after it.

Migrating or Updating Your GA4 Property

The first decision is whether to use your existing GA4 property, create a new one, or create a new Data Stream within the existing property.

• Preserve the existing property if the domain remains the same: Creating a new property breaks all historical data continuity and audience lists, keep the same property for domain-preserving redesigns.
• Create a new Data Stream when the site structure changes significantly: A new Data Stream within the existing property allows fresh event configuration while preserving historical property-level data.
• Create a new property only if you are starting entirely fresh: A new property is appropriate when the redesign represents a complete brand and audience repositioning that makes historical comparison irrelevant.
• Document the decision and its rationale before implementation: The property strategy decision affects everything downstream, write it down and get stakeholder alignment before acting.

Installing the GA4 Tag via Google Tag Manager

Google Tag Manager is the correct implementation path for GA4 on redesigned sites. Direct code implementation creates technical debt that makes future tracking changes unnecessarily complex.

• Create a GTM container if one doesn't exist: A single GTM container manages all tags, triggers, and variables, including the GA4 configuration tag, from one interface.
• Publish the GA4 Configuration Tag with the Measurement ID: The GA4 tag sends all event data to the correct property, verify the Measurement ID against the GA4 Admin panel.
• Validate tag firing with Google Tag Assistant: Tag Assistant confirms that the GTM container is loading and the GA4 tag is firing correctly on all page templates.
• Test on both the staging environment and the production site after launch: Tag behavior can differ between staging and production, verify in both environments.

Setting Up Annotation for Launch Day

GA4 no longer supports native annotations the way Universal Analytics did, but documenting the launch date is essential for all future analyzis.

• Add an annotation to your Connected Sheets export: Google Sheets linked to GA4 via Connected Sheets can include annotation columns for significant events including launch dates.
• Record the launch date and time in your analytics documentation file: A simple shared document recording key dates, launch, major content changes, campaign starts, serves as the annotation layer.
• Set up a GA4 custom dimension for site version if iterating rapidly: A site version custom dimension allows data segmentation by pre- and post-redesign periods in GA4 explorations.
• Screenshot key pre-launch metrics in GA4 before the new site goes live: Pre-launch screenshots create a permanent, uneditable baseline record that supplements your exported data.

Configuring Conversion Events and Goals

KPIs to track after redesign should be defined before conversion event configuration begins. Every metric you intend to report on requires an explicitly configured event in GA4.

Identifying and Defining Your Conversion Events

Before opening GTM, document every business-critical action on the redesigned site. Configuration without documentation produces incomplete tracking.

• List every form submission on the site by name and location: Contact form, quote request, newsletter signup, and download forms each require separate tracking configurations.
• Document every button click that represents a conversion intent: "Book a call," "Start free trial," and "Get a quote" buttons are conversion events even if they don't lead to a thank-you page.
• Include phone number clicks for sites where phone conversion is important: Click-to-call events are critical conversion data for service businesses, configure them explicitly.
• Define success conditions for each event before writing triggers: "Form submission" means the form was successfully submitted and the thank-you page loaded, not that the submit button was clicked.

Implementing Form Submission Tracking in GTM

Form submission tracking is the most common gap in post-redesign analytics. The correct implementation method depends on how the form is built.

• Use thank-you page URL triggers for forms that redirect on submission: A Page View trigger firing on the thank-you page URL is the most reliable form submission signal.
• Use GTM's Form Submit trigger for forms that don't redirect: Native GTM Form Submit triggers work for most standard form implementations, test with Tag Assistant to confirm.
• Use custom JavaScript event triggers for AJAX forms that don't redirect: AJAX forms require the development team to push a custom dataLayer event on successful submission, document this requirement early.
• Verify that the trigger fires on successful submission, not just button click: A trigger that fires when the submit button is clicked will record form attempts, not form completions, test both.

Marking Events as Conversions in GA4

Collecting events in GA4 is not the same as measuring conversions. Each event must be explicitly designated as a conversion in the GA4 Admin panel.

• Navigate to Admin → Events and toggle "Mark as conversion" for each primary conversion event: Only explicitly toggled events appear in GA4's conversion reports and attribution models.
• GA4 allows up to 30 conversion events per property: Prioritize the conversions most directly tied to business goals, not every event needs conversion status.
• Mark both primary and secondary conversions with documentation of the distinction: A primary conversion (booked call) and a secondary conversion (newsletter signup) serve different reporting purposes, label them clearly.
• Verify conversion event firing in the GA4 Realtime report after configuration: Realtime confirmation that conversion events are firing correctly should be completed before the site goes live.

Connecting GA4 to Google Search Console

Search Console setup after redesign works best when GA4 integration is configured simultaneously. The combined data provides the most complete picture of post-redesign organic performance.

Linking GA4 to Search Console

The integration is established in GA4 Admin and makes Search Console data available within GA4 reports.

• Navigate to GA4 Admin → Product Links → Search Console Links: This is the correct path in GA4, not in Search Console itself, despite what some older documentation describes.
• Select the verified Search Console property that matches the GA4 domain: Mismatched properties are a common configuration error, verify the domain match before saving the link.
• Allow 24 to 48 hours for linked data to begin appearing in GA4: The integration does not populate historical data, it begins reporting from the link date forward.
• Verify the link by checking the Search Console Insights report in GA4: Successful integration surfaces the Queries and Landing Pages reports under the Traffic Acquisition section.

Using the Search Console Integration Reports

Once linked, the GA4 and Search Console data combination provides redesign-specific insights that neither source offers independently.

• The Queries report shows which search terms drive traffic to which pages: This allows direct measurement of whether redesigned pages are maintaining or improving keyword performance post-launch.
• Impressions and clicks by landing page reveal organic visibility changes: Compare landing page performance pre- and post-redesign to identify which new page structures are winning or losing in organic search.
• Average position changes by page indicate ranking shifts after redesign: Positions that move more than three places in either direction in the first four weeks after launch warrant investigation.
• Build a custom GA4 Exploration combining Search Console and engagement metrics: Combining organic traffic quality metrics with engagement data reveals whether redesigned pages serve organic visitors better than their predecessors did.

Identifying Organic Performance Changes Post-Redesign

The GSC integration enables the most important post-redesign SEO analyzis: distinguishing redesign-driven performance changes from algorithm updates or seasonal variation.

• Create a comparison date range matching the pre-redesign period: Four weeks post-launch compared to four weeks pre-launch in the same calendar period controls for weekly seasonality.
• Use year-over-year comparison where available for seasonal content: For sites with strong seasonal traffic patterns, comparing to the same four-week period in the prior year removes seasonal noise.
• Identify pages that gained or lost significant organic clicks after launch: Pages with more than 20% click change in the first 30 days should be investigated for content, structure, or redirect issues.
• Cross-reference organic performance changes with the Coverage report: A page losing organic clicks while showing a Coverage error confirms a technical indexation issue rather than a ranking change.

Pre-Launch Analytics QA Checklist

Quality assurance before site launch must explicitly include analytics verification. Analytics QA that happens after launch misses the highest-stakes data collection period.

Real-Time Report Verification

GA4's Realtime report is the fastest way to confirm that tag firing is working correctly on the staging site before launch day.

• Open the Realtime report and navigate through every page template: Each page type should show an active session in Realtime, missing page types indicate a tag firing gap.
• Complete a test form submission and confirm it appears as a conversion event: This end-to-end test confirms the full tracking path from event trigger to GA4 conversion registration.
• Click every tracked button and verify the corresponding events fire in Realtime: Button click tracking requires individual verification, don't assume all buttons configured in the same trigger work identically.
• Test on mobile as well as desktop: Mobile browsers and mobile network conditions can cause tag firing differences that desktop-only QA misses entirely.

Cross-Device and Cross-Browser Testing

Analytics implementation inconsistencies across browsers and devices are among the most common post-launch data quality problems.

• Test in Chrome, Safari, Firefox, and Edge at minimum: Safari's Intelligent Tracking Prevention affects cookie behavior and can cause session fragmentation in GA4 data.
• Test on both iOS and Android mobile devices: Mobile app browsers and in-app browsers behave differently from native mobile browsers, common in social media referral traffic.
• Verify that ad blockers don't prevent tracking for critical event types: A significant percentage of users have analytics blockers, confirm your implementation degrades gracefully rather than breaking.
• Document browser-specific discrepancies found in testing: Known data quality limitations documented before launch prevent post-launch confusion about unexplained data gaps.

Excluding Internal Traffic Before Launch

Internal traffic inflation is the most commonly missed pre-launch analytics setup step. It consistently distorts baseline data and makes post-launch comparison unreliable.

• Create a GA4 internal traffic filter using your office IP address: IP-based filtering prevents office browsing sessions from inflating session counts and distorting engagement metrics.
• Add developer and agency team IPs to the internal traffic filter: Development team activity during the first weeks after launch is high, exclude it from the outset.
• Activate the "Define internal traffic" configuration in GA4 Admin: Internal traffic rules must be both defined and activated, configuring only the rule without activating the filter has no effect.
• Test the filter by visiting the site from an office IP and confirming the session doesn't appear in GA4 reports: Filter verification confirms the configuration is working before baseline data collection begins.

Diagnosing Traffic Issues Post-Launch

Traffic drops after website redesign are common and frequently attributable to specific, fixable causes. GA4 provides the diagnostic data needed to distinguish tracking issues from genuine traffic problems.

Using GA4 to Identify Traffic Drop Sources

The Traffic Acquisition report separates traffic by channel, making it possible to identify whether a traffic decline is organic, direct, or tracking-related.

• Compare organic channel traffic in the week after launch to the week before: A sudden organic traffic drop signals either a crawling and indexation issue or a rankings impact from content changes.
• A drop in direct traffic that appears simultaneous with an organic drop often indicates a tracking problem: If all channels show simultaneous decline after launch, the most likely cause is a misconfigured or missing analytics tag.
• Referral traffic spikes immediately after launch often normalize within two weeks: New inbound links and social shares of the launch announcement create temporary referral traffic inflation.
• Paid traffic performance changes after a redesign indicate landing page experience changes, not tracking issues: If paid traffic conversion rates change while volume holds steady, the page experience changed, investigate the landing page.

Landing Page Performance Comparison

Comparing the same landing pages before and after the redesign is the most direct measurement of whether the redesign improved or harmed page performance.

• Build a GA4 Exploration with Landing Page as the primary dimension: This report shows every page that served as a session entry point, with engagement and conversion metrics alongside.
• Compare conversion rates for the same pages in pre- and post-redesign date ranges: Session-level conversion rate comparison by landing page is the most direct measure of redesign impact on page performance.
• Account for traffic volume changes when comparing conversion counts: A page with higher conversion rate but lower traffic may produce fewer total conversions, look at both rate and volume.
• Flag pages where both traffic and conversion rate declined: Simultaneous traffic and conversion rate decline often indicates a redirect issue, the page may not be receiving its former organic traffic correctly.

Diagnosing Redirect Chain Issues with Analytics Data

Redirect chain problems created during the redesign are among the most SEO-damaging and hardest-to-spot launch issues. GA4 data provides early indicators.

• Bounce rate spikes on specific pages after launch suggest redirect chain issues: Users landing on a page that has been redirected multiple times experience slow load times and often bounce before engaging.
• Cross-reference high-bounce pages with the Search Console Coverage report: Pages appearing in Coverage as "Crawled but not indexed" alongside GA4 bounce rate spikes indicate redirect or content quality issues.
• Use GA4's Page Path report to identify pages with unexpected URL patterns: Redirect chains often create GA4 session data at intermediate URL paths that reveal the chain's structure.
• Test all priority page URLs with a redirect checker tool after launch: Screaming Frog or a similar tool identifies redirect chains, loops, and broken redirects that GA4 data can only detect after the damage is already occurring.

Using GA4 to Measure Redesign ROI

Measuring website redesign ROI requires the right data, collected correctly, interpreted against the right baseline. GA4 provides the raw material, the analyzis framework determines whether the data tells a clear story.

Building a Redesign Performance Report in GA4

A structured GA4 Exploration designed specifically for redesign ROI measurement provides a repeatable reporting framework for stakeholder communication.

• Create an Exploration with a 90-day post-launch date range compared to 90 days pre-launch: Equal-length periods allow meaningful comparison, shorter periods introduce too much day-to-day noise.
• Include session count, engagement rate, conversion rate, and conversions by channel: These four metrics together tell the complete story of whether the redesign improved quality of traffic and efficiency of conversion.
• Add landing page as a secondary dimension to identify top-performing new pages: The redesign's best and worst performing pages both provide actionable insights for the next optimization cycle.
• Save the Exploration with a clear name and share it with relevant stakeholders: A saved, shared Exploration allows consistent reporting without recreating the analyzis each time.

Conversion Rate Improvement Attribution

Isolating the redesign's contribution to conversion rate changes requires controlling for traffic mix changes that can make overall conversion rate improvements misleading.

• Compare conversion rates by channel, not just overall: An overall conversion rate increase may reflect a shift toward higher-converting channels rather than a redesign improvement, separate them.
• Look for conversion rate improvements in organic and direct traffic specifically: These channels are most directly influenced by page experience changes from the redesign.
• Compare device-level conversion rates before and after: Mobile conversion rate improvement often represents the redesign's most direct impact for sites that had poor pre-redesign mobile experience.
• Control for campaigns that may have increased high-converting traffic post-launch: Marketing campaigns launched alongside a site redesign inflate post-launch conversion rates, identify and account for them.

Presenting Analytics ROI to Stakeholders

Translating GA4 data into a business case requires structured communication that connects metrics to revenue impact.

• Lead with conversion rate before and after as the headline metric: A conversion rate change from 1.2% to 2.1% is immediately understandable to any stakeholder regardless of analytics familiarity.
• Calculate estimated revenue impact using average deal value and traffic volume: Multiply conversion rate improvement by monthly session volume and average deal value to produce an estimated monthly revenue impact.
• Show traffic quality improvement alongside volume metrics: Engagement rate, session duration, and pages per session improvements demonstrate that the redesign improved the visitor experience, not just the visuals.
• Compare cost of redesign to estimated first-year revenue impact: A redesign that costs $40K and generates $8K in additional monthly revenue produces a five-month payback, that is a compelling ROI story.

Conclusion

Proper Google Analytics setup after a website redesign transforms a launch from a leap of faith into a measurable business investment.

The data collected and configured correctly in the first 90 days after launch will guide every optimization decision for years, and the absence of that data cannot be recovered retrospectively.

Open your GA4 property right now and confirm that at least one conversion event is configured, active, and recording data.

If none are configured, that is your most urgent post-launch task, not the next design iteration, not the next content update, and not the next campaign.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

LOW/CODE Agency Delivers Website Redesigns with Analytics Built In from Day One

LOW/CODE Agency treats GA4 configuration, Google Tag Manager implementation, and conversion tracking setup as standard deliverables in every website redesign, not optional add-ons requested after launch.

Analytics-first methodology means the data collection infrastructure is in place before the first user visits the new site.

We work as a strategic product team, not a dev shop.

That means your redesign includes a measurement framework that tells you definitively whether the project delivered on its goals, and gives you the data to drive continuous improvement after launch.

• GA4 property strategy and configuration: Correct property, data stream, and tag configuration decisions made at project start, not at launch.
• Google Tag Manager implementation: GTM container setup, GA4 tag deployment, and all event trigger configuration as a standard deliverable.
• Conversion event documentation and setup: Every business-critical conversion event identified, documented, and configured before launch day.
• Search Console integration: GSC property verification, sitemap submission, and GA4 integration configured as a coordinated launch-day activity.
• Pre-launch analytics QA: Realtime report verification, cross-browser testing, and internal traffic filter configuration as part of the QA process.
• Post-launch traffic monitoring: 90-day performance monitoring with weekly reporting on organic traffic, conversion rates, and page performance.
• Stakeholder ROI reporting: Structured GA4 Explorations and performance summaries that communicate redesign impact in business terms.

LOW/CODE Agency has delivered 450+ digital products for clients including Coca-Cola, American Express, Sotheby's, Medtronic, Zapier, and Dataiku. We bring the same standard of measurement rigor to every project, regardless of size.

Start with a scoping call and ask about our analytics-ready website redesign delivery process.