Chrome dangerous site warning: what it means and what to do

A customer texts you a screenshot. Your own website, wearing a full red screen in Chrome, with a message telling people to turn back. Your first thought is probably "there is a Chrome dangerous site warning on my website, and I need it gone." The calls that were coming in are now hitting a wall.

The red screen means Google Safe Browsing has flagged your site, or a page on it, as potentially unsafe. It is a fixable problem with a set order of steps, and the first two take about ten minutes. The worry underneath, whether your business itself has been compromised, gets an answer as soon as you see what Google found.

What does the red "Dangerous site" screen mean?

Chrome Help says a full-page red warning means the site is flagged as unsafe by Google Safe Browsing. The wording on the screen can read "Dangerous site" or "Deceptive site ahead." Google lists the reasons: phishing and other social engineering, malware, unwanted software, harmful downloads, and links to harmful downloads.

Google's definition of a deceptive page is broad. It covers pages that impersonate a trusted entity or trick visitors into sharing information, calling a support number or downloading software. Malware, in Google's malware policy pages, is software designed to harm a device or the people using it.

Your intentions are not part of the test. Google says an innocent site can be hacked, and a compromised page, an injected redirect, a malicious ad or an embedded third-party item can all put the flag on you without you adding a thing. The red screen also differs from the gray "Not secure" label Chrome shows when a connection lacks HTTPS; if that is what your visitors see, this walkthrough on the HTTPS warning is the right page, because the fix there is a certificate and not a cleanup.

How do I see what Google flagged on my website?

Two checks give you the answer, and neither costs anything. Start with Google's Safe Browsing Site Status tool. Type in your domain or the affected address, and it tells you whether Google currently lists the site as unsafe.

Then open Google Search Console for your verified property, choose Security & Manual Actions, and select Security issues. That report can show the category, the example URLs and the dates Google detected the problem, along with recommended steps. Google's Search Console Help on the Security issues report says it covers hacked content, phishing, malware and unwanted software.

Write down three things before you touch anything: the category, the example URLs and the detected dates. Your host or technician will ask for them, and you will need them again when you request the review. If you have not verified your site in Search Console, set that up first, since the report belongs to a verified property.

Use URL Inspection to view the listed pages instead of opening them yourself. Chrome Help advises people not to enter personal information on a flagged site, and that applies to you too while the cause is unknown.

Who should I call first if my site may be hacked?

If the report points to hacked content or a harmful file you did not add, bring in your hosting provider or a qualified website security professional now. Hand them the category, the example URLs and the dates you wrote down. That one page of notes saves the first hour of a repair.

Your host can often see server files, logs and account activity that you cannot. A security professional can tell whether the problem sits in your site software, a plugin, a theme, an administrator account or a third-party embed. If you also need the broader first-day steps, such as changing passwords and telling customers, our post on the first 24 hours after a website is hacked covers that; the steps here stay on the red warning and the review request.

Not every flag means a break-in. A deceptive ad, a script from a third-party service or an embedded widget can trigger it. In that case the fix may be to remove or replace that one source, and the Security issues report's example URLs usually point you to where it loads.

What does cleaning the whole site involve?

Google's sequence is plain: confirm the issue using the example URLs, find out whether the site was hacked, clean the affected pages and files, close the vulnerability, and verify that the entire site is clean. Cleaning one page is not the finish line. Search Console may list several URLs, and the same weakness can reach pages it has not listed yet.

Depending on the cause, the work looks different. Google's Search Console Help notes that owners can replace affected directories with a known-good backup or remove unwanted pages and files created by an attacker. A harmful download means removing or correcting the file. A harmful outbound link means removing the link and checking for hidden copies.

Closing the vulnerability is the step that keeps the warning from coming back. That means looking at the site software, plugins, themes, accounts, hosting and configuration for the way in, as Google's guidance on preventing malware lays out. Changing the passwords on every account that touches the site belongs here as well.

How do I request a review, and how long does it take?

When the whole site is clean and the way in is closed, open the Security issues report and request a review. Describe what you fixed in a few clear sentences, so whoever reads it can match your repair to the category Google listed. Google's Search Console Help on requesting a review walks through the form.

Plan for a wait. Google says security reviews can take from several days to several weeks. A malware review may take a few days, while a hacked-spam review may take several weeks. Nobody can promise a date, so tell your customers what is happening in the meantime, by phone, email or your social pages.

Send one request, and send it after the fix. Google warns that repeated requests before the problem is fixed can lengthen the process. If you are not sure the site is clean, wait a day and check again instead of sending a request you may have to redo.

Why is the warning still showing after I cleaned up?

A rejected request is not the end. Read the response in Search Console, keep cleaning, fix the vulnerability that let the problem in, and submit again only when the whole site is clean. The response usually points to what Google still sees, which makes it the best clue you will get.

An approved request can still leave a lag. Google says warning-system updates may take additional time to reach Chrome after approval, so a visitor may see the red screen for a while after the report clears. Check Safe Browsing Site Status again before you assume the cleanup failed.

Turning off Safe Browsing in your own browser clears the screen for you only. Every customer's Chrome still checks the same Google list, so hiding it on your machine fixes nothing for the people you want to reach, and it only hides the problem from you. Put that time into the cleanup.

Do I need a full security package or a smaller fix?

A limited, well-diagnosed issue may be something your host, your CMS provider or a qualified technician can handle in a short job. You do not need the largest package to get a site clean. You need the smallest service that makes it clean and keeps it that way.

A cheap one-page cleanup can fall short in two situations. One is when the attacker's access stays open, so the same problem returns after a few days. The other is when several sites or accounts share the same credentials, so cleaning one leaves the rest exposed. Either case is a reason to ask for a wider look.

Help is worth paying for if you lack safe access to the hosting, the CMS or the backups, if the issue returns, or if the report lists several categories or many URLs. That is the point where our website security audit fits: someone reviews the category, the example URLs, the software, the backups, the hosting access and the chance of reinfection, then scopes the work to what the site needs. If the trouble is your business name being mistaken for a scam site, that is a different problem with a different fix.

Frequently Asked Questions About Chrome's Dangerous Site Warning

What does "Dangerous site" mean in Chrome?

Google Safe Browsing has identified a possible threat on the site, such as phishing, malware, unwanted software or a harmful download.

Is it the same as the "Not secure" label?

No. "Not secure" is about an unprotected connection. The full-page red warning is a Safe Browsing flag.

How do I find the cause?

Enter your domain in Safe Browsing Site Status, then open Security & Manual Actions and Security issues in Search Console for the category and example URLs.

What if I never added the harmful content?

The site may have been hacked, or a third-party ad, script, embed or download may be responsible. The example URLs point to where to start.

How do I remove the warning?

Clean the entire site, close the vulnerability, and request a security review from the Security issues report in Search Console.

How long does the review take?

Google says reviews can take several days to several weeks, and the timing differs by the type of problem.

The Bottom Line

Chrome's red screen is a Safe Browsing flag, and the way out runs in a fixed order: check Safe Browsing Site Status, read the Security issues report, bring in the host or a security professional if the site may be compromised, clean the whole site, close the way in, and request one review. Your intentions are not what Google tests, so a hacked or embedded-content cause is a repair job, not a verdict on your business.

Once the site is clean and the access problem is closed, the warning comes down and customers can reach your pages again. A repair that closes the door, plus regular patching and backups afterward, is what keeps the flag from coming back.

If you want a second set of eyes, Web Leveling can start with a website security audit of what Google flagged and how it got in, and our website maintenance covers the patching, backups and monitoring that keep a clean site clean. If your host or CMS provider can solve it with a small job, we will say so. We work with small and medium businesses across the country and overseas. Send us the Security issues details, and we will tell you the smallest fix that works.

Terms