How to Track 301 Redirects in Google Analytics

Setting up a 301 redirect is a standard part of website management and SEO, but simply flipping the switch isn’t enough. True success comes from knowing your redirects are not only working technically but also effectively funneling users and search engine equity to the right place. This guide will walk you through practical, step-by-step methods for tracking the performance of your 301 redirects directly within Google Analytics 4.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Why Tracking Your 301 Redirects is Non-Negotiable

You might wonder why you need to go through the extra effort of tracking redirects. Once they're set up, isn’t the job done? The data you gain from tracking is invaluable for several reasons:

• Confirming Functionality: It provides concrete evidence that your redirects are firing correctly and that users are following the intended path.
• Measuring SEO Impact: When you consolidate multiple articles into one powerhouse post or migrate to a new URL structure, tracking redirects helps you measure if you’ve successfully transferred the traffic and authority from the old pages.
• Identifying Valuable Backlinks: Redirects can reveal traffic from old backlinks that are still active. Seeing consistent traffic from an old URL indicates a valuable link you might want to ask the site owner to update.
• Diagnosing Traffic Drops: If you see a sudden, unexplained drop in traffic after a site refresh, your redirect tracking data can quickly tell you if an important redirect failed or wasn't set up correctly.
• Understanding User Behavior: Are people still trying to access an old page from saved browser bookmarks? Understanding this helps you see which legacy URLs still carry weight with your audience.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

The Challenge: Google Analytics Tracks Pages, Not Paths

Before we jump into the "how," it's important to understand why you can't see redirect data in Google Analytics out of the box. Google Analytics (both Universal Analytics and GA4) is designed to track user interactions on pages where your tracking code is present. Its data is based on the final destination URL - the one that actually loads in the browser and fires the GA tag.

When a user visits old-url.com, the server immediately tells the browser, "That URL has permanently moved to new-url.com." The browser then makes a new request to new-url.com without the user even noticing. Since the GA4 tracking script only loads on new-url.com, that's the only pageview it records. GA has no native awareness that the user's journey began with a request for the old URL. To get this insight, we need to manually pass that information along to the final destination.

Method 1: Tagging Redirects with UTM Parameters

The simplest and most direct way to track redirects is by adding UTM parameters to the destination URL in your redirect rule. This treats the traffic coming through the redirect as a specific marketing campaign, making it easy to isolate and analyze in your acquisition reports.

How it Works

You’ll configure your redirect to send users not just to the new page, but to the new page with a special set of parameters appended to the URL. For example, instead of redirecting /old-page to /new-page, you’ll redirect it to /new-page?utm_source=redirect&utm_medium=301. Google Analytics will see these UTM tags and cleanly categorize the traffic.

Step-by-Step Instructions

1. Establish a Naming Convention: Consistency is crucial. Decide on a clear, simple convention for your parameters so your reports are easy to understand. A great starting point is:
2. Construct the Destination URL: With your convention in place, build the full URL. For this example, let's say we're redirecting an old contact page:
3. Update Your Redirect Rule: Implement the redirect on your server using the new tagged URL as the destination. If you're using cPanel and editing your .htaccess file, the rule would look something like this:
4. Find Your Data in GA4: Once traffic starts flowing, finding it is simple.

Graphed

Build AI Agents for Marketing

Build virtual employees that run your go to market. Connect your data sources, deploy autonomous agents, and grow your company.

Build Your First Agent

Pros and Cons

• Pros: Very easy to set up without technical tools like Google Tag Manager. The data is clear and appears in standard GA4 reports.
• Cons: The UTM parameters are visible in the user's address bar, making some people prefer a cleaner appearance. It also attributes the session to your redirect 'campaign,' potentially overriding original source data for a session (e.g., if a user came from organic search to the old URL, the session source may be recorded as redirect_internal, not google / organic).

Method 2: Using Google Tag Manager for 'Invisible' Tracking

If you'd prefer not to use UTM parameters or need a more advanced solution that doesn't interfere with session attribution, you can use Google Tag Manager (GTM) to send a custom event to GA4. This method tags the pageview with information about the redirect without cluttering the URL with UTMs or altering session data.

How it Works

With this method, you pass a simple, non-tracking parameter through the redirect. This parameter acts as a signal for GTM. A GTM tag will be configured to look for this parameter on page load. When it sees the signal, it fires a GA4 custom event - like redirect_traffic - and captures the original URL as a parameter of that event. It provides hyper-granular detail without altering your acquisition reports.

Step-by-Step Guide for GTM

1. Modify Your Redirect Rule: Add a unique query parameter to your redirect's destination. It can be anything, but keep it simple, like ?from_redirect=[old_url_path].
2. Create a Variable in GTM: Now, you need to capture the value passed in that parameter.
3. Create a Trigger in GTM: This trigger will activate your event tag only when your special parameter is present.
4. Create a Tag in GTM: This tag sends the event and the redirect data to GA4.
5. Register a Custom Dimension in GA4: For GA4 to properly display your custom parameter, you need to register it.
6. Publish & Test: Use GTM's Preview mode to test the redirect. You should see your event tag fire on the destination page. Once confirmed, publish your GTM container. You'll now see the redirect_view event in your GA4 event reports, and you can add the Redirect Source Page dimension in secondary columns or Exploration reports to see exactly which old pages are funneling traffic.

Pros and Cons

• Pros: Extremely granular and clean data. Doesn't affect session attribution. Very scalable for websites with hundreds of redirects needing careful monitoring.
• Cons: A significantly more complex setup that requires baseline proficiency with Google Tag Manager. Data only appears in custom explorations and event reports, not the standard acquisition reports.

AI Agents for Marketing

Crash Course

Graphed

Free PDF · the crash course

AI Agents for Marketing Crash Course

Learn how to deploy AI marketing agents across your go-to-market — the best tools, prompts, and workflows to turn your data into autonomous execution without writing code.

Download the PDF

A Note on Server-Side Log Analysis

For more technically-minded SEOs or developers, another source of truth exists entirely outside of Google Analytics: your server logs. Every request made to your server is recorded - including the initial request for the old URL and the "301" status code your server returned. Analyzing these log files with a tool like Screaming Frog Log File Analyser can show you exactly how many times a redirect has been requested by both users and search engine bots like Googlebot. This method is the purest way to confirm redirects are firing but won't give you user behavior metrics like you'd find in GA4.

Final Thoughts

While Google Analytics doesn't track 301 redirects by default, methods like adding UTM parameters or configuring a custom event with GTM give you the exact insight you need. Choosing the right approach allows you to confirm your redirects are working, measure the success of your content strategies, and ensure precious SEO value is never lost in the shuffle of changing URLs.

Managing campaigns, building GA4 explorations, and documenting custom event setups for redirects can quickly add up. At Graphed, we remove the busywork by letting you connect your Google Analytics account and build real-time reports with simple, conversational language. Instead of clicking through menus or building complex explorers, you can just ask, "Show me traffic from our internal 301 redirects last month," and we’ll instantly prepare the report for you.