🔎 Understanding the Rejection

When Google Ads flags your OTTO PPC ads with a policy rejection related to a third-party site (such as joomleadpacks.com), it means Google has detected a reference to an unauthorised or suspicious external domain within your ad or its associated landing page. This can happen when scripts, redirects, or injected code link your landing page to a domain that violates Google Ads policies.

This type of rejection blocks all affected ads simultaneously and will not resolve on its own. You must identify the source of the third-party reference, clean it, and then submit an appeal. Follow the steps below in order.

🧭 Step 1: Identify Which Ads Are Affected

1. Log in to your Google Ads account.
2. Navigate to Campaigns → Ads & assets.
3. Filter by status: Disapproved.
4. Note the policy reason listed — it should reference a third-party site or destination mismatch.
5. Record the final destination URLs attached to the rejected ads. These are the landing pages you will inspect next.

🔬 Step 2: Inspect Your Landing Page Code

The most common cause is injected code on your landing page that references the flagged domain. You need to check the page source for any trace of the offending domain.

1. Open each affected landing page URL in a browser.
2. Right-click anywhere on the page and select View Page Source.
3. Use Ctrl+F (or Cmd+F on Mac) and search for joomleadpacks.com or any partial variation of the domain.
4. Also search for common injection patterns: <iframe, <script src=, and document.write.
5. If you find any references, note the exact lines — you will need to remove them from your page template, theme files, or CMS plugins.

If you use a CMS such as WordPress, Joomla, or similar, also check installed plugins and recently modified theme files, as third-party injections frequently originate there.

🦠 Step 3: Run a Malware and Injection Scan

Manual inspection may miss obfuscated code. Run an automated scan to be thorough.

• Use a free tool such as Google Safe Browsing (search "Google Safe Browsing site check" and enter your domain).
• Use Sucuri SiteCheck (sitecheck.sucuri.net) to scan for malware, injected scripts, and blacklist status.
• If your hosting provider offers a malware scanner in its control panel, run that as well.
• Address every issue flagged before proceeding to the next step.

🧹 Step 4: Clean the Landing Page and Destination URLs

1. Remove all code referencing the flagged third-party domain from your page source, templates, and plugins.
2. If a plugin or theme file was the source, delete or update it immediately.
3. Change any admin or FTP passwords as a precaution if an injection was found.
4. Verify your final destination URL does not redirect through the flagged domain at any point in the redirect chain. Use a redirect checker tool to trace each hop.
5. Republish or re-save your landing page after making changes.
6. Re-run the Sucuri or Safe Browsing scan to confirm the issue is fully resolved before submitting an appeal.

📋 Step 5: Update Destination URLs in OTTO PPC

Once your landing pages are clean, confirm the destination URLs in your OTTO PPC campaigns are pointing to the correct, unaffected pages.

1. In Search Atlas, go to OTTO SEO in the left sidebar.
2. Open the relevant OTTO PPC campaign and review the destination URLs assigned to each ad.
3. If any URL previously passed through the flagged domain, update it to a clean, direct URL.
4. Save your changes.

📨 Step 6: Appeal the Rejection in Google Ads

With the landing pages cleaned and URLs updated, you can now request a review from Google.

1. In your Google Ads account, go to Campaigns → Ads & assets.
2. Filter for disapproved ads.
3. Select all affected ads using the checkbox at the top of the list.
4. Click the Edit menu and choose Appeal or Request review.
5. Select the policy violation listed and confirm you have resolved the issue.
6. Submit the appeal. Google typically reviews appeals within 1–3 business days.

If the appeal is denied a second time, repeat the landing page inspection steps — Google may have detected a different reference or a cached version of the page. Clear your server cache and CDN cache before re-appealing.

⚠️ Preventing This Issue in the Future

• Audit all third-party scripts and plugins on your landing pages before launching new PPC campaigns.
• Set up Google Search Console security alerts so you are notified immediately if Google detects malware or policy violations on your domain.
• Avoid importing ad assets or landing page templates from unverified third-party sources.
• Periodically re-run a Sucuri or Safe Browsing scan on your active campaign landing pages.

💬 Need More Help?

If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.