URL change tracking + paid 404 rescue for agencies
Client sites change.Paid media keeps running.
Start by tracking client URL changes with only a domain — no script, no billing info, no client dev help.
When changes suggest risk, add 404 traffic tracking and temporarily route paid visitors from 404s to approved live pages while the fix is underway.
No script required to start.Most agencies know within 7-14 days whether 404 traffic tracking is worth adding.
See URL changes before they become wasted spend.
Your client renames pages, removes products, updates feeds, and changes promotions. Campaigns, shopping feeds, emails, affiliates, and old links can keep sending visitors to destinations that no longer work.
URLs change
Tracked URL inventory movement across agency-managed sites
URL inventory changes show potential risk. 404 traffic tracking confirms whether real visitors are hitting missing pages.
404 traffic
Detected on 404 pages
utm_medium
- cpc
- cpc_search
- cpc_shopping
- flow
utm_source
- bing
- klaviyo
- yotpo
utm_source (AI agents)
- chatgpt.com
- perplexity
- openai
- copilot.com
Campaigns, shopping feeds, email flows, AI answer engines, affiliates, and old links can keep sending visitors to destinations that no longer work.
Start outside the site.Go deeper only when the data says it matters.
Each step adds evidence and control without forcing traffic changes on day one.
Track URL changes
Add a client domain and monitor added, removed, redirected, and missing URLs.
No script. No billing info. No client dev access.
Use 7-14 days of URL movement to see whether the site is changing enough to create campaign risk.
Track 404 traffic
When a site looks risky, ask the client’s web team to add Rescued.click tracking to the site’s 404 page.
Rescued.click provides client-friendly installation instructions and an installation tester.
404 tracking shows real missing-page visits, including referrer, source, medium, campaign context, URL parameters, and paid indicators.
Redirect while the fix is underway
When paid traffic hits a 404, temporarily route visitors to an approved live page.
Use it to protect visitors while the campaign URL, shopping feed, email link, missing page, or permanent redirect is fixed.
Temporary redirects only run while the original URL still returns a 404.
Bring proof before asking the client to change code.
Agencies are often responsible for performance, but the client controls the site. Rescued.click lets your team start safely, gather evidence, and involve the client only when there is a reason.
Start with only a domain
Track client URL changes without touching the site.
Send clear install instructions
Give the client web team a plain-English explanation, copy-paste instructions, and an installation tester.
Show why it matters
Show what changed, which missing URLs are receiving traffic, and whether paid visitors are affected.
Buy time while the fix happens
Use a temporary redirect only when valuable traffic needs protection.
What Rescued.click helps you catch
Paid search traffic to removed landing pages
A campaign keeps sending visitors to a page that was renamed, deleted, or replaced.
Shopping traffic to unavailable products
A feed or product URL points to a missing page while paid traffic continues.
Email or SMS traffic to expired promotions
A campaign link keeps circulating after the original offer page is gone.
Affiliate or partner traffic to old URLs
External links keep sending visitors to a destination the client no longer maintains.
CMS changes that quietly break campaign paths
A redesign, CMS edit, or bulk update changes URLs faster than campaign QA can catch.
Fix the source, fix the page, or redirect while the fix is in progress
Not every 404 needs the same response.
Alert the traffic owner
Tell the paid media, shopping, email, affiliate, or campaign owner which link is sending visitors to a missing page.
Alert the site owner
Tell the client web team which page needs to be restored, replaced, or permanently redirected.
Use a temporary redirect
Send visitors to a live page while the permanent fix is underway.
Stop automatically when fixed
Temporary redirects only run on 404 pages. Once the original URL no longer returns a 404, the redirect no longer fires.
Simple pricing
Free to monitor. $1 / site / month when paid traffic needs protection. Buy more time to fix only when the issue takes longer.
Rescued.Click monitors for free. If paid traffic is actually hitting 404s, you can protect that site and keep visitors moving while the campaign URL, feed, page, or permanent redirect gets fixed.
URL change tracking
Add client domains and track URL inventory changes.
No script.No billing info.No client dev help required.
404 traffic tracking
Add tracking to the client’s 404 page to see real missing-page visits, referrers, UTMs, source context, and paid indicators.
No redirects unless enabled separately.Client-friendly install instructions.Installation tester included.
Protected Rescue
Protect paid traffic when evidence shows it is hitting a missing page.
Non-paid rescues are included.Unknown/unverified traffic is included and not billed.Paid rescue packs are charged when approved and roll forward until used.
“If the issue takes longer to fix, buy another 100 paid rescues for $10 to keep traffic protected while your team fixes the source.”
Spend controls
Protected Rescue includes 100 clearly paid traffic rescues per site each month.
When a protected site uses its paid rescue allowance, paid rescue pauses for that site.
The agency or client can buy another 100 paid rescue pack for $10. Unused pack rescues stay with that site until used. That approval means: buy more time to fix.
Non-paid rescues are included. Unknown or unverified traffic is included and does not reduce the paid rescue allowance.
Every redirect is reported near real time.
Your team can review what was rescued, why it was classified as paid or included, and how much of the site’s paid rescue allowance has been used.
What moved
Original 404 URL, redirect destination, and timestamp.
Why it was classified
Source, medium, campaign context, and paid indicators when available.
How it was billed
Whether the redirect was billed or included, plus the rescue rule used.
Where spend stands
Site-level allowance usage, non-expiring pack balance, and approved packs so the traffic owner, site owner, and client team stay aligned.
Questions agencies ask before they turn redirects on
Do I need client site access to start?
No. To start URL change tracking, you only need the client’s domain. No script, no billing info, and no client dev help required.
When do I need the client’s web team?
Only when you want to add tracking to the client’s 404 page. Rescued.click provides installation instructions and a tester so the client team can confirm the setup.
Does adding 404 tracking redirect visitors?
No. 404 tracking only records visits to missing pages. Temporary redirects are enabled separately.
What counts as paid traffic?
A visit is counted as paid only when Rescued.click sees clear paid indicators, such as paid UTM values, click IDs, shopping parameters, feed parameters, or campaign markers your team configures.
What about non-paid traffic?
Non-paid visitors redirected by active rescue rules are included and do not reduce the paid rescue allowance.
Can I control spend?
Yes. Protected Rescue is $1 / site / month and includes 100 clearly paid traffic rescues / month.
When that allowance is used, paid rescue pauses for the site unless it has paid pack balance. Your team can buy another 100 paid rescues for $10 to buy more time to fix the source. Unused paid pack rescues do not expire.
Do I get a redirect report?
Yes. Redirect reports update near real time and show the original 404 URL, destination, timestamp, source and campaign context when available, paid indicator, billing status, rule used, and site-level paid rescue allowance.
Is this safe for ad platforms and analytics?
Rescued.click is designed to work after a visitor reaches your site’s 404 page. It does not replace fixing broken ad destinations, feeds, emails, or server-side redirects.
Temporary redirects preserve available URL parameters so your analytics can keep useful campaign context. If an ad platform is reviewing a broken final URL, fix that source directly.
When should I enable a temporary redirect?
Enable one when real traffic, especially paid traffic, is hitting a missing page and your team needs time to fix the source.
That source might be a campaign URL, shopping feed, email link, missing page, or permanent server-side redirect.
When does a temporary redirect stop?
Temporary redirects only run when the original URL returns a 404.
If the page is restored, permanently redirected, or otherwise fixed so it no longer returns a 404, the temporary redirect no longer fires.
Is this a replacement for permanent redirects?
No. Temporary redirects are for live traffic rescue while the permanent fix is assigned and completed.
The goal is to protect visitors now and fix the source as quickly as possible.
Could we build this ourselves?
You can build pieces of it. The harder part is keeping URL change tracking, 404 traffic context, paid classification, site-level rescue approvals, temporary redirects, reports, client handoff, and fix detection working across every site your agency manages.
Rescued.click packages that workflow so your team can start with a domain and add deeper tracking only when the data says it matters.
What happens if the script is removed or unavailable?
The site falls back to its normal 404 behavior. Rescued.click does not replace your site’s core routing or permanent redirect system.
Start with one client domain.
Add a site in seconds. Watch URL changes for 7–14 days. Decide with data whether 404 traffic tracking is worth adding.
No script required to start. No billing info required.