Dangerous Site Warning on Your Website: How to Fix It

On this page
- What the "Dangerous site" warning means
- Why a genuine business website gets flagged
- How to fix the Dangerous site warning, step by step
- How long until the warning goes away?
- Will moving to a new host or domain remove the warning?
- When an urgent website migration does make sense
- How to stop it happening again
- Frequently asked questions
- Need help removing the warning?
Short answer: a red “Dangerous site” warning on your own website means Google Safe Browsing has found something harmful on it, most often because the site was hacked. To remove it, open the Security Issues report in Google Search Console to see exactly what Google found, take the site offline or into maintenance mode, remove every infected file and the weakness the attacker used, then click “Request Review”. Google says a review can take from a few days to a few weeks. Moving the site to a new host or domain does not fix it on its own, because the harmful code moves with it.
Key takeaways
- It covers Chrome, Firefox and Safari users. Google Safe Browsing “helps protect over five billion devices every day” (Google Safe Browsing), and Chrome, Firefox and Safari all use it.
- Search Console tells you what’s wrong. The Security Issues report lists the problem type, such as malware, code injection or deceptive pages, with sample URLs.
- Fix first, then ask for a review. Requesting a review before the site is clean can cause delays “or even get you marked as a repeat offender” (Search Console Help). Repeat offender status lasts 30 days (Google).
- Moving doesn’t clean anything. The warning is about the harmful content, not the server, so copying infected files to a new host or domain serves the same code again. That’s our reading of Google’s guidance; Google doesn’t publish a rule on moves.
- Edge is separate. Microsoft Edge uses Microsoft Defender SmartScreen, which has its own review process (Microsoft Learn).
What the “Dangerous site” warning means
When Chrome shows a full red page headed “Dangerous site” before your website loads, Google’s Safe Browsing service has listed your site, or a page on it, as harmful. Chrome uses this warning for “phishing, malware, unwanted software, or social engineering sites” (Chrome Help). Some Google pages still call the phishing version “Deceptive site ahead” (Google Search Central), so you may see either name.
The warning isn’t limited to Chrome. Firefox uses Google’s Safe Browsing service (Mozilla), and Safari’s Fraudulent Website Warning checks addresses with Google Safe Browsing too (Apple). Google can also label your listing in search results: “This site may harm your computer” for malware and “This site may be hacked” for spam hacks (web.dev).
| Where people see it | What they see | What it usually means |
|---|---|---|
| Chrome, Firefox, Safari | A full-page red warning before the site loads | Google Safe Browsing has flagged the site for malware, phishing, unwanted software or deceptive content |
| Google search results | “This site may harm your computer” | Google found malware on the site |
| Google search results | “This site may be hacked” | Hackers have added spam pages or links |
| Microsoft Edge | A red SmartScreen block page | Microsoft’s own SmartScreen service has flagged the site |
For a business, the effect is immediate. Many visitors will leave rather than click past a red warning, and customers start asking whether you’ve been hacked.
Why a genuine business website gets flagged
Most flagged business sites didn’t set out to harm anyone. They were hacked, and the attacker used them to spread malware, redirect visitors to scams, or host fake login pages. Google’s Security Issues report groups these problems into types such as hacked content (code, content or URL injection), deceptive pages, deceptive embedded resources and harmful downloads (Search Console Help).
The most common ways in are well known:
- Outdated software. In Sucuri’s review of 39,594 sites it cleaned, 39.1% of content management system (CMS) installs were out of date when they were infected (Sucuri 2023 Hacked Website Report). For WordPress, 91% of new vulnerabilities found in 2025 were in plugins (Patchstack).
- Malware and malicious redirects. In Sucuri’s 2024 scan data, malware and redirects made up 74.7% of the infections it detected (Sucuri SiteCheck report).
- Hidden backdoors. Almost half (49.21%) of the sites Sucuri cleaned had at least one backdoor, which lets an attacker come back after a quick clean-up (Sucuri).
- Code from somewhere else. If your pages load a script, ad or file from a site that is flagged, your site can be flagged “for malware loaded from that other site” (web.dev).
- Files you offer for download. A download that Google treats as harmful or unwanted software can trigger a “Harmful downloads” issue (Search Console Help).
How to fix the Dangerous site warning, step by step
These steps follow Google’s own recovery guidance, in order. If you aren’t comfortable working on the server, hand steps 3 and 4 to your developer or host.
1. Find out exactly what Google flagged
Sign in to Google Search Console and open Security & Manual Actions > Security issues. The report names the issue type and lists sample affected URLs (Search Console Help). If you haven’t added your site to Search Console yet, add and verify it now; you need it to request a review. Our guide to how Google Search Console works explains the set-up.
Don’t confuse this with Manual actions. A manual action means a Google reviewer decided pages break Google’s spam policies, and those pages rank lower or are left out of results, without any browser warning. A security issue means the site was hacked or could harm visitors (Search Console Help). The red warning comes from security issues.
2. Contain the damage
Google’s advice is to quarantine the site before you clean it: take it offline or put up a maintenance page, contact your host, delete any user accounts the hacker created, and “change the passwords for all site users and accounts” (web.dev). That includes the website admin, hosting control panel, database, FTP or SFTP, domain registrar and email. Turn on multi-factor authentication as you go, and keep copies of the server logs before anything is deleted.
3. Remove every infected file and close the way in
Cleaning means removing everything the attacker changed: injected scripts, spam pages, fake login pages, unknown files, and redirect rules in files such as .htaccess (web.dev). To find them, compare your CMS core files with a fresh copy from the official source, look for files changed around the time the problem started, check for admin users and scheduled tasks you didn’t create, and run a server-side malware scanner. Then fix the weakness they used, usually an outdated plugin, theme or CMS, a weak or reused password, or a vulnerable script.
A clean backup from before the attack can save time, but only if you know when the attack started and you patch the weakness before going live again. Restoring without closing the hole simply resets the clock. Also check every script, ad and embed your pages load from other websites.
4. Check the site the way Google sees it
Hacked sites often show clean pages to the owner and harmful ones to search engines or mobile visitors. Google suggests fetching your pages with tools such as cURL or Wget to see what is really served (web.dev). The URL Inspection tool in Search Console shows the page as Googlebot fetches it. Check the sample URLs from the Security Issues report and your most important pages. Anyone can also look up a site’s current status in Google’s Safe Browsing Transparency Report.
5. Request a review in Search Console
When every affected page is clean, go back to the Security Issues report and click Request Review. Describe what you found and what you fixed. Don’t send another request before Google has decided on the first one (Search Console Help).
Be sure the problem is truly fixed before you ask. Sites that “repeatedly switch between compliant and noncompliant behavior” can be marked as repeat offenders, and that status lasts 30 days before you can request another review (Google).
6. Clear Microsoft Edge separately
Edge doesn’t use Google Safe Browsing, so a Google review won’t clear an Edge block. On the Edge block page, choose the option to report that the site doesn’t contain threats, or submit the site through Microsoft’s file and URL submission portal. Microsoft’s SmartScreen team replies by email (Microsoft Learn).
7. Check whether personal data was exposed
If your site has contact forms, customer accounts or a shop, check whether the attacker could reach personal data. Under the Personal Data Protection Act (PDPA), a data breach that is notifiable must be reported to the Personal Data Protection Commission (PDPC) within 3 calendar days of deciding it is notifiable (PDPC guide). Singapore organisations can report a cyber incident to SingCERT (CSA reporting page) and get triage and advice from the Cyber Incident Helpline on 6890 9555 (CSA).
How long until the warning goes away?
Google’s current Search Console help says a review “can take from a few days to a few weeks to complete” (Search Console Help). Older Google guidance gave a rough guide by type: phishing reviews took about a day, malware a few days, and spam hacks up to several weeks (web.dev). Treat those as a rough guide, not a promise.
Once Google approves the review, the browser warning and the search result labels should be removed. If the review fails, Search Console tells you why, and you fix what’s left before asking again.
Will moving to a new host or domain remove the warning?
People often ask whether they can escape a “Dangerous site” warning by moving the website to a new host or a new domain. Based on Google’s guidance, a move on its own doesn’t solve it, for three reasons:
- The problem moves with the files. The warning is about harmful content, not the server it sits on. If the infected files, database or backdoor are copied across, the new site serves the same harmful code, and Google can find it again. Even pages that only load a script from a flagged site can be flagged (web.dev).
- A new domain loses your search presence. Moving to a new domain properly means redirecting the old one, and Google’s site move guide says to verify both sites in Search Console and keep redirects for “generally at least 1 year” (Google Search Central). A brand-new domain without those redirects starts again from nothing in Google.
- It can look worse to blocklists. Microsoft advises site owners to “avoid frequent changes to hosting or DNS” to keep a good SmartScreen reputation (Microsoft Learn).
Google doesn’t publish a rule on this; the points above are our reading of its guidance. The reliable route is to clean the site where it is, get the review approved, and only then decide whether a move still makes sense.
When an urgent website migration does make sense
Sometimes moving is the right call, and it can’t wait:
- Your host can’t or won’t help, keeps getting compromised, or has suspended the account.
- The site runs on old software that can no longer be updated safely, so it will keep getting hacked.
- The hosting plan is closing or the server is being shut down.
- You have no access to the old platform beyond what’s needed to move the content out.
If you have to move in a hurry, do it in a way that doesn’t carry the infection or lose your Google traffic:
- Move clean content, not a copy of the infected site. Rebuild or reinstall from trusted sources, and bring across only the content, images and data you have checked.
- Keep the same domain if you can. Changing only the host, with the same URLs, usually keeps your search rankings; Google has separate guidance for moves without URL changes.
- Keep every important URL working. List the old URLs and redirect any that change with 301 redirects, as Google’s site move guide recommends.
- Test before you switch. Check the new site on a staging address, scan it, and confirm forms and tracking work before you point the domain at it.
- Keep a way back. Keep the old setup ready until the new one is proven, so a problem on launch day is a quick switch back rather than an outage.
- Request the review from the clean site. Then watch Search Console until the security issue is cleared.
This is how we approached the CCTVSG.net revamp and migration: every one of its 850 old URLs was checked before launch, and the old site stayed ready for an instant rollback. Our website migration service follows the same checklist.
How to stop it happening again
Most sites are flagged because of a weakness that was there long before the warning. Keep the CMS, plugins and themes updated and remove what you don’t use, protect every login with multi-factor authentication, keep tested off-site backups, and put a web application firewall in front of the site. Add uptime and malware monitoring, and make sure Search Console alerts reach someone who will act on them.
Our website security checklist for Singapore SMEs covers each of these in order of priority, and our website security and website maintenance services can do the work for you.
Frequently asked questions
Why does Chrome say my website is a dangerous site?
Google Safe Browsing has found something harmful on the site, such as malware, a phishing page, unwanted software or deceptive content. Usually the site has been hacked. The Security Issues report in Google Search Console shows what was found and on which pages.
How long does it take to remove the dangerous site warning?
After you clean the site and request a review in Search Console, Google says a review can take from a few days to a few weeks. The warning should be removed once Google approves the review.
Will changing my hosting or domain remove the dangerous site warning?
Not on its own. If the infected files are copied to the new host or domain, Google can find the same harmful code again. Clean the site and get the review approved first, then move if you still need to.
Can I remove the warning without Google Search Console?
As the site owner, you request the review through Search Console, so you need to add and verify your site there. Anyone can check a site’s status in Google’s Safe Browsing Transparency Report, but that tool doesn’t remove warnings.
Why does Edge still block my site after Google cleared it?
Microsoft Edge uses Microsoft Defender SmartScreen, not Google Safe Browsing. Report the site as safe from the Edge block page or through Microsoft’s submission portal, and wait for Microsoft’s reply.
Does the dangerous site warning affect my Google ranking?
It can. Google may label your search listing as possibly hacked or harmful, and hacked spam content breaks Google’s spam policies. The browser warning also turns many visitors away before they reach your pages, so clean the site quickly and request a review.
Need help removing the warning?
If your website is showing a “Dangerous site” warning, our emergency service fixes hacked and flagged websites within 3 working days. We find what Google flagged, clean the site, close the weakness the attacker used and request Google’s review for you. Google then takes from a few days to a few weeks to review the site and remove the warning.
WhatsApp us or send us a message with your website address, and we’ll tell you what we find.
About this guide
Written by the VueTech SG team. VueTech SG is a Singapore web design, SEO and website maintenance agency that builds, secures, migrates and looks after websites for small and medium businesses. Every source was checked on 19 November 2026. This guide is general information, not legal advice; for your PDPA obligations, see the PDPC’s guides.
Sources
- Google: Safe Browsing, Safe Browsing Transparency Report, Site moves without URL changes, Chrome Help: warnings about dangerous sites, Security Issues report, Manual actions vs security issues, Social engineering, Safe Browsing repeat offenders, Site moves with URL changes
- web.dev (Google): Quarantine your site, Hacked with malware, Request a review
- Mozilla: Firefox privacy notice
- Apple: Safari and privacy
- Microsoft: Unexpected block warnings in Microsoft Edge
- Sucuri: 2023 Hacked Website Report, SiteCheck Malware Trends Report 2024
- Patchstack: State of WordPress Security in 2026
- Cyber Security Agency of Singapore: Report an incident, Cyber Incident Helpline launch
- PDPC: Guide on managing and notifying data breaches