Google Ads Cloaking Suspension: What an Old Landing Page Taught Us

A Google Ads account can operate for years and still contain an old campaign, tracking template, or landing-page URL that everyone has forgotten about. If Google later reviews that destination and cannot reach it, cannot verify it, or sees a path that no longer matches the live website, the consequences can be far more serious than a single disapproved ad.

We recently worked through exactly that situation for a small local business while providing website maintenance and technical support. We are not identifying the company because the purpose of this article is not to criticize the client or speculate about Google’s internal decision-making. It is to share what actually happened, what we discovered, and why resolving a Google Ads suspension can be much harder than preventing one.

The account was suspended under Google’s Circumventing systems: Cloaking policy. There was no intentional cloaking, no alternate website built for Google, and no attempt to deceive users. What we ultimately found was an obsolete landing-page subdomain connected to an old campaign that we could no longer edit because the account had already been suspended.

That created a frustrating loop: Google appeared to want the destination problem corrected, but the suspended account would not allow us to change or remove the destination stored inside the campaign.

What Does Google Mean by Cloaking?

In everyday web development, cloaking generally means deliberately showing one version of a page to a search engine or advertising reviewer and another version to real visitors.

Google’s current policy defines cloaking as showing different content to different users, including presenting Google with content that differs from what other people see. Google treats circumventing-systems violations as serious because they can interfere with its review and enforcement processes.

That policy makes sense when someone is intentionally hiding prohibited content. The difficulty is that an automated system can also encounter technical signals that look inconsistent or suspicious even when no one intended to deceive it.

A broken subdomain, an expired landing page, a redirect chain, a disabled third-party landing-page service, different behavior by location, or a server that blocks Google AdsBot may create a destination that Google cannot reliably evaluate.

Google does not disclose every signal used to reach a suspension decision. For that reason, we cannot claim that one URL was definitively the sole cause in this case. We can say that the obsolete landing page was the most significant unresolved inconsistency we found after an extensive technical and content review.

The Hidden Problem Was an Old Campaign Destination

The live website itself was working. Visitors could reach it, its pages accurately represented the business, and there was no intentional difference between what users and search engines were supposed to see.

However, an older Google Ads campaign still referenced a landing-page subdomain that had once been used for advertising and call or form tracking. The business had moved away from that landing-page setup, but the old URL remained in the Google Ads campaign history.

The important distinction is this:

• Removing a landing page from a website does not remove its URL from Google Ads.
• Removing a DNS record does not update an ad’s Final URL or Expanded URL.
• Pausing a current campaign does not necessarily eliminate old destination data from the account.
• A URL that no longer works may still be checked by Google during a policy review.

When the landing-page subdomain was disconnected, it could no longer resolve normally. From a human perspective, the page was gone. From an automated advertising review perspective, the stored destination could still exist while returning a DNS failure or another inaccessible response.

Google’s destination policies require ad landing pages to work on common browsers and devices and to be crawlable by Google AdsBot. Its guidance specifically identifies DNS errors, HTTP errors such as 403 and 404 responses, blocked crawlers, and inaccessible destinations as problems.

Why We Could Not Simply Change the URL

The logical fix seemed easy: open the campaign, replace the obsolete Final URL with the current website, and resubmit the ad.

That was not possible in this account.

Because the account was suspended, the Google Ads interface would not allow us to pause, edit, or remove the affected campaign or ad. The outdated landing-page URL remained visible in the account, but the controls needed to correct it were unavailable.

We also tried to obtain the necessary level of account access. That process introduced another layer of difficulty:

• We attempted to add authorized administrative access.
• We worked through account verification.
• Direct access continued to require the account owner’s two-factor authentication.
• Google Ads Editor required an authentication method involving the owner’s device.
• Opening manager-account links in a different browser session did not automatically provide access to the suspended client account.

Two-factor authentication is important and should not be weakened. In this situation, though, it meant the account owner needed to be physically available with the correct device during several attempts. Even with legitimate authorization and the correct password, we could not bypass Google’s security requirements, nor should we have been able to.

The result was a genuine remediation problem: the person responsible for correcting the website could find the obsolete URL, but could not edit the ad containing it.

Everything We Reviewed Before Appealing Again

We did not assume the old landing page was the only possible issue. Before submitting another appeal, we conducted a broader website audit of the company’s web presence and the technical signals Google might inspect.

1. We reviewed the website page by page

We checked the site for inconsistent business information, misleading claims, unexpected redirects, broken pages, outdated URLs, and content that might appear different from the company’s actual services. These checks overlap with the crawlability, indexing, redirect, and site-architecture work included in a technical SEO audit.

2. We verified ownership in Google Search Console

The website was added and verified through DNS. This does not resolve a Google Ads suspension by itself, but it helps confirm control of the domain and provides tools for inspecting how Google accesses individual URLs.

3. We submitted the XML sitemap

We confirmed the sitemap was available and submitted it in Search Console so Google could discover the current public pages more consistently.

4. We checked crawling and indexability

We reviewed the robots file, page availability, redirects, and indexability. We also used Search Console’s URL inspection process to check the pages that mattered most.

5. We removed a lead-log page from public access

An internal lead-log page did not belong in the public-facing portion of the website. We moved it into a protected area so visitors and crawlers would not encounter operational information that was never intended to function as website content.

6. We documented the corrective work

Our appeal explained the changes made in good faith. We did not claim that the business had intentionally violated policy. We described the technical review, the current website, and the steps taken to eliminate possible inconsistencies.

Despite that work, the appeal was rejected and the account continued to be labeled for cloaking.

The Catch-22 of a Suspended Google Ads Account

Google’s published guidance generally tells advertisers to correct an ad or destination and then request another review. That is straightforward when an ad is merely disapproved and its editing controls remain available.

An account-level suspension can be different. Google states that a suspended account cannot run ads and is considered suspended unless an appeal succeeds. In our specific account, the interface was effectively read-only for the changes we needed to make.

That produced the central contradiction of this case:

1. The old destination needed to be corrected.
2. The campaign containing the destination could not be edited.
3. The appeal did not restore editing access.
4. Without editing access, the obsolete URL remained in place for another review.

Google also limits repeated appeals. Its current guidance states that each ad is generally limited to three unsuccessful appeals before support must be contacted. Repeatedly submitting the same explanation without a meaningful technical change is therefore not a good strategy.

Why We Are Now Using a Server-Side Redirect

Because we cannot change the destination inside Google Ads, our next step is to correct what happens when Google or a visitor requests the old URL.

The plan is to restore the old landing-page subdomain at the DNS and hosting level, secure it with a valid SSL certificate, and configure a permanent server-side redirect to an appropriate page on the company’s current website.

In practical terms, the request should follow a clean path:

Redirect pathOld landing-page URL → HTTP 301 permanent redirect → current compliant page returning HTTP 200

This redirect must behave the same way for everyone. It should not identify Google AdsBot and send it somewhere different. It should not vary by user, device, or reviewer. Creating special behavior for Google would risk becoming the very type of cloaking the policy prohibits.

The goal is much simpler: make an obsolete destination consistently resolve to a legitimate, relevant page that accurately represents the same business.

This is a technically reasonable remediation, but it is not a promise of reinstatement. Google may consider other account, billing, tracking, website, or historical signals that are not visible to us. The redirect gives the old campaign URL a valid and consistent response, eliminating the most obvious unresolved destination failure we can still control.

What Businesses Should Learn From This Experience

The best time to clean up an old Google Ads destination is before an account is suspended.

Never disconnect an advertising subdomain without checking Google Ads

Before deleting a DNS record, canceling a landing-page platform, or removing a tracking domain, search the entire Google Ads account for the URL. Check active, paused, and old campaigns, as well as ads, assets, keywords, tracking templates, Final URL suffixes, and redirects.

Keep a record of every advertising destination

Maintain a simple inventory containing:

• The domain and every advertising subdomain
• The campaigns using each destination
• The owner of the landing-page or tracking account
• DNS and hosting details
• SSL status
• Redirect rules
• The date a destination was retired

Test the Expanded URL, not only the visible homepage

Google explains that an ad’s Expanded URL can include tracking templates and parameters in addition to the Final URL. A homepage may work perfectly while the actual path Google checks fails.

Make landing pages available to Google AdsBot

Review robots.txt, firewall rules, security plugins, geographic restrictions, bot protection, and server responses. A page that loads from your office may still return an error to Google’s crawler.

Preserve account access before there is a crisis

Every business should have at least two properly authorized administrators, current recovery methods, and documented ownership of its Google Ads account. Agency or manager access should be tested while the account is in good standing.

Do not create a new account to escape a suspension

Opening another Google Ads account to bypass enforcement may itself be considered an attempt to circumvent Google’s systems. The safer course is to identify the underlying issue, correct every element you control, document the work, and use the formal appeal or support process.

Do not fire off repeated appeals

An appeal should identify what changed, when it changed, and how the change addresses the cited policy. If nothing has materially changed since the previous rejection, submitting the same appeal again is unlikely to help and may consume a limited appeal opportunity.

A Pre-Appeal Checklist for Landing-Page Problems

Before appealing a Google Ads suspension or destination decision, confirm all of the following:

• Every Final URL resolves correctly.
• Every Expanded URL and tracking template resolves correctly.
• All landing pages return the expected successful response.
• No required hostname produces a DNS error.
• SSL certificates are valid for every relevant domain and subdomain.
• Google AdsBot is not blocked by robots.txt, a firewall, or a security plugin.
• The same content and redirect behavior is shown to Google and ordinary visitors.
• Display URLs, Final URLs, and landing-page domains are consistent.
• Business identity, services, contact information, and policies are clear.
• Old campaigns and paused ads have been reviewed for obsolete destinations.
• Public pages do not expose internal lead records or administrative information.
• The website owner and authorized manager can both access the account.
• The appeal explains the actual corrective work without speculation or exaggeration.

Can a Google Ads Cloaking Suspension Be Reversed?

It can be, but reinstatement is not automatic. Google describes circumventing-systems violations as egregious and says accounts are reinstated only in compelling circumstances when there is good reason. A successful appeal needs more than a statement that the advertiser did nothing wrong.

The strongest appeal is supported by a website and account that have been thoroughly reviewed, specific technical problems that have been corrected, and a clear explanation of why the destination is now consistent and compliant.

In our case, the work is still ongoing. We have repaired and verified the current website, reviewed its pages, confirmed domain ownership, submitted the sitemap, protected an internal lead page, traced the historical destination, and exhausted the normal options for editing the suspended campaign. The next measurable step is making the obsolete landing-page URL resolve through one transparent server-side redirect.

Whether Google reinstates the account remains its decision. What this experience has already shown is that a forgotten landing page can outlive the platform that created it, and once an account is suspended, a simple URL change can become a complicated technical and administrative recovery project.

Frequently Asked Questions

Can an old landing page affect a Google Ads account?

Yes. An old URL may remain stored in a campaign, ad, keyword-level URL, tracking template, or other account component. If Google checks it and receives a DNS failure, HTTP error, crawler block, or inconsistent destination, it may create a policy problem even if the company’s main website works.

Does deleting a DNS record remove a landing page from Google Ads?

No. DNS controls whether a hostname resolves on the internet. It does not change the Final URL or tracking information stored in a Google Ads account.

Will a 301 redirect automatically remove a Google Ads suspension?

No. A redirect can make an obsolete URL resolve consistently, but Google may consider many other signals when reviewing an account. The redirect must be transparent, relevant, technically sound, and identical for Google and ordinary users.

Is redirecting Google AdsBot differently from users allowed?

No. Serving Google different content or routing it differently from normal users can fall within Google’s definition of cloaking. A legitimate remediation should provide the same destination behavior to everyone.

Can you edit ads after a Google Ads account is suspended?

Access and available controls can vary. In the account described here, we could view the obsolete campaign but could not pause, edit, or remove the affected ad. If editing is available in your account, Google’s guidance is to correct the ad or destination before requesting review.

Should you create a new Google Ads account after a suspension?

Not as a way to bypass the suspension. Google prohibits attempts to circumvent its enforcement systems. Address the underlying problem and follow the formal appeal and support process.