Google Safe Browsing

[serpsystems]

Hi,

2 of my sites got hit by Google Safe Browsing. I used HTTrack on some simple landing pages, they do not contain anything malicious. How do I fix that?

 

[Crazy Monkey]

If your site is flagged by Google Safe Browsing, check for hidden scripts or suspicious code from copied pages. Clean everything, update files, and then request a review in Google Search Console after fixing the issues.

 

[WickednDivine]

Don’t assume it’s a false flag,Safe Browsing usually means something hidden.

Quick step is check Security Issues in Google Search Console.

 

[serpsystems]

Don’t assume it’s a false flag,Safe Browsing usually means something hidden.

Quick step is check Security Issues in Google Search Console.

GSC says there is 1 Deceptive Page, which is: N/A.

 

[sam.hunt0710]

try to check your website using this too https://sitecheck.sucuri.net/

 

[serpsystems]

try to check your website using this too https://sitecheck.sucuri.net/

Minimal risk

 

[sam.hunt0710]

You need to audit your codes , there must be something hidden in there which is triggering the issue.

Which tools you have used so far to check ?

 

[Afeez Animator]

Hi,

2 of my sites got hit by Google Safe Browsing. I used HTTrack on some simple landing pages, they do not contain anything malicious. How do I fix that?

Hi,

Google Safe Browsing can sometimes flag sites mistakenly. Try checking your site for any hidden issues and request a review in Google Search Console after cleaning. Keeping your site clean and secure usually helps resolve this quickly

 

[serpsystems]

You need to audit your codes , there must be something hidden in there which is triggering the issue.

Which tools you have used so far to check ?

It's a single Index page, I don't get how it can trigger this.
I used VirusTotal, Sucuri, Claude, GSC.

 

[sam.hunt0710]

It's a single Index page, I don't get how it can trigger this.
I used VirusTotal, Sucuri, Claude, GSC.

Is it possible for you to send me the link in DM , let me try to check.

 

[serpsystems]

Since you used HTTrack to rip the landing pages, the issue is almost certainly hidden in the cloned code. Google Safe Browsing flags malware and phishing, not thin content. HTTrack copies everything, including malicious JS, broken external iframes, or tracking pixels from the original site.

How to fix it:

1 Open the source code and strip out all external JavaScript, old tracking tags, and base64 encoded strings.

2 Remove any hidden iframes or weird redirects HTTrack might have pulled.

3 Scan the code manually. Once it's completely clean, go to Google Search Console (Security Issues report) and Request a Review.

They do not contain malicious JS or old tracking tags.

 

[katie_brooks]

If you used HTTrack, you might have accidentally cloned some malicious scripts or tracking code from the original source. Check your source code for any hidden JS and then request a review through Search Console once it's clean.

 

[Syosin]

I think, if both sites got hit, they almost definitely share the same bad script or copied asset.

When you used httrack, you likely copied not just the visible page but also scripts, embeds, or links that were already flagged somewhere else. Google Safe Browsing doesn’t care how the code got there only that something on the page behaves like malware, phishing, or a deceptive landing page.

Go to Google Search Console - security Issues. That tells you what Google thinks is wrong (malware, phishing, etc.).

Clean the pages:
remove all external js/scripts you didn’t write
delete iframes, trackers, or weird redirects

scan your URL using virustotal.com to see what’s being flagged.
make sure your hosting isn’t infected (check for unknown files or injected code).
Go back to Search Console and request a review.

Look into that

 

[serpsystems]

I think, if both sites got hit, they almost definitely share the same bad script or copied asset.

When you used httrack, you likely copied not just the visible page but also scripts, embeds, or links that were already flagged somewhere else. Google Safe Browsing doesn’t care how the code got there only that something on the page behaves like malware, phishing, or a deceptive landing page.

Go to Google Search Console - security Issues. That tells you what Google thinks is wrong (malware, phishing, etc.).

Clean the pages:
remove all external js/scripts you didn’t write
delete iframes, trackers, or weird redirects

scan your URL using virustotal.com to see what’s being flagged.
make sure your hosting isn’t infected (check for unknown files or injected code).
Go back to Search Console and request a review.

Look into that

I requested a review without fixing anything: they resolved the issue.
100% false flag

 

[bartosimpsonio]

I've had sites get flagged as malware for no reason. There's lots of false positives.

 

[hutehegoca15]

If Google Safe Browsing flagged your sites after cloning pages with HTTrack, it’s usually because Google detected one of these:

phishing-like page structure
copied branding/login flows
deceptive redirects
suspicious scripts/resources
similarity to previously abused templates
compromised third-party assets

Even if the page itself is “clean,” cloned landing pages often trigger automated phishing classifiers.