I Found a Broken URL in Google Ads That Had Already Cost Me €439

I run WowMade, an AI creative platform where users can generate images, videos, and music in one place.

Last week, I was reviewing our Google Ads campaigns when I found something that made my stomach drop.

In the Landing pages report, one row read:

https://wowmade.ai/{ignore}

158 clicks. €439.29 spent.

And when I clicked the link in the report, it opened a 404.

If you run ads, you know the feeling: Have I been paying Google to send potential customers to a page that doesn't exist?

We had recently moved our ads and tracking to a new domain, so my first thought was that something had gone wrong during the migration.

I started investigating.

Here's how I approached it, and how you can check whether a suspicious URL in Google Ads represents actual lost traffic or something else.

Step 1: Check the ad's Final URL

First, I opened the ad in Google Ads and checked its Ad URL options.

Here's what I found:

• Final URL: https://wowmade.ai/
• Ad-level tracking template: empty
• Final URL suffix: empty

So the ad itself wasn't pointing to /{ignore}.

That's a good sign, but it doesn't tell the whole story.

Google Ads allows tracking templates and URL options at different levels, including the account, campaign, ad group, and keyword levels.

An empty tracking template on an individual ad doesn't necessarily mean there's no tracking configuration elsewhere.

My first lesson: Don't change anything yet.

Before editing a live campaign, make sure you understand the actual problem. Otherwise, you might introduce unnecessary changes while trying to fix something that wasn't broken.

Step 2: Use Google's built-in Test button

Under the URL options, there's a small blue Test link.

It checks the landing page using the configured URL and tracking settings.

I ran it.

The result:

"Landing page found."

The tested URL looked like this:

https://wowmade.ai/?utm_source=google&utm_medium=cpc...

There was no {ignore} in it.

That was reassuring.

At least the current ad configuration could successfully reach our website.

But there was still an unanswered question: Why was Google Ads reporting 158 clicks against that strange URL?

And what happened to those visitors?

Step 3: Understand what {ignore} actually is

Here's where things got interesting.

According to Google's official ValueTrack documentation, {ignore} is a special parameter used to identify tracking information in a Final URL.

It helps Google distinguish tracking elements from the actual landing page URL.

Google's documentation shows an example like this:

https://example.com/product?{ignore}utm_source=google

But my Landing pages report showed:

https://wowmade.ai/{ignore}

Notice the difference?

Google's example puts the marker inside the query string. My report displayed it as part of the URL path.

And that path returned a 404.

At this point, I had two possible explanations:

Possibility 1: A reporting or URL-processing issue

The marker was appearing in the report, but users were reaching the correct landing page.

Possibility 2: A real routing problem

Something in the tracking or redirect chain was sending visitors to a URL that didn't exist.

The ad settings alone couldn't tell me which explanation was correct.

I needed to look at what actually reached our website.

Step 4: Check GA4

The next place to investigate is Google Analytics 4.

Go to:

Reports → Engagement → Landing page

Select the same date range as your Google Ads report and look for the suspicious path.

In my case, the search term was:

ignore

If GA4 shows sessions landing on that path, that's evidence that the unexpected URL was actually being visited.

If there are no sessions, that's reassuring, but it isn't definitive proof that nobody reached it.

Why?

Because GA4 relies on tracking code executing.

If someone lands on a broken page and leaves before the analytics tag fires, you might never see that visit in GA4.

A 404 page might also have no analytics tracking at all.

That's why there's one more place worth checking.

Step 5: Check your server or CDN logs

This is where you can look for actual HTTP requests rather than relying only on analytics events.

I use Cloudflare, but the same principle applies to Vercel, AWS, Nginx, or whichever infrastructure serves your website.

If you have request logs available, search for:

/{ignore}

And its URL-encoded form:

/%7Bignore%7D

Look at:

• How many requests reached these paths?
• When did the requests start?
• What HTTP status codes were returned?
• Were the requests from real visitors, bots, or crawlers?
• Do the requests contain Google Ads click identifiers or other evidence connecting them to paid traffic?

That last point matters.

Finding requests to a broken URL doesn't automatically prove that the clicks reported in Google Ads went there.

You need to connect the evidence.

In my case, the timing was especially interesting because we had recently moved our advertising and tracking to a new domain.

If a genuine routing problem existed, I'd want to check whether it started around that migration.

What I actually learned

The most important discovery was that three different things can look like the same problem but aren't necessarily the same:

1. A URL displayed in an advertising report.
2. The destination produced by the current ad configuration.
3. The URL that a real visitor actually requested.

In my case, the report showed /{ignore}, opening that URL manually returned a 404, and Google's URL test successfully reached the correct homepage.

Those observations establish that the suspicious report URL and the tested destination behaved differently.

They don't, by themselves, establish whether the entire €439.29 was wasted.

To quantify any actual lost traffic, I'd need historical request data covering the same period and evidence connecting those requests to the advertising clicks.

That's a much more useful distinction than immediately assuming every click was lost.

The takeaway

If you run Google Ads, especially after migrating domains or changing tracking configurations, make a habit of reviewing your Landing pages report.

And if you discover a suspicious URL:

1. Check the ad's Final URL and tracking settings.
2. Check for inherited tracking templates at other levels.
3. Run Google's built-in URL test.
4. Search for the suspicious path in GA4.
5. Check your server or CDN logs if available.

Don't immediately pause a campaign, change your bidding strategy, or rewrite your ads because one report row looks alarming.

Investigate first.

A few minutes of checking can help you distinguish a broken destination from a reporting issue — and avoid making changes that introduce new problems.

---

I'm building WowMade, an AI platform for creating images, videos, and music, and sharing some of the less glamorous parts of running an AI product: advertising, payments, analytics, and all the unexpected technical problems that come with them.

Have you ever seen {ignore} appear in your Google Ads Landing pages report? Did you find out what caused it? I'd love to hear about your experience in the comments.