Skip to main content
web60

Infrastructure

The Chrome Suspicious Site Warning: Your Website Does Not Need to Be Hacked to Get One

Ian O'Reilly··13 min read
Flat illustration of two shield shapes side by side, one built from overlapping teal circles and one drawn as a teal outline, joined by deep navy dots on a warm off-white background

You have probably heard that Chrome only warns people away from websites that have been hacked. Clean site, no warning. Infected site, big red screen. That was close enough to true for years, and it is the reason most business owners never think about browser warnings until something has already gone badly wrong.

It is no longer the whole picture. On 20 October 2026, Google announced that Chrome's Enhanced Protection mode now splits its site warnings into two tiers [1]. Dangerous sites, which Google describes as a "high confidence verdict, high risk of user harm", keep the familiar full-page red warning. Suspicious sites get something new: a "lower confidence verdict, possible risk of user harm", shown when "a page exhibits deceptive patterns commonly associated with known malicious sites" [1].

Read that second definition again. It says nothing about hacking. It describes how a page looks and behaves. That distinction matters for anyone running a business website, and it breaks several assumptions owners have carried for years. This guide takes them one at a time, then sets out a short routine for verifying what Chrome currently thinks of your site.

Myth 1: Only Hacked or Malicious Websites Get a Chrome Warning

The red interstitial has always been reserved for sites Google is confident are harmful: malware, phishing, compromised pages. Getting one usually meant something had broken in. The suspicious tier works differently. It is a judgement about patterns, and Google has not published the list of patterns it checks [1].

What Google has published, for years, is its policy on social engineering, which it defines as "content that tricks visitors into doing something dangerous" [4]. The examples on that page are worth knowing, because several can appear on a perfectly legitimate business website without the owner putting them there:

  • A "deceptive popup claiming that the user's software is out of date"
  • "Ads masquerading as page action buttons"
  • Embedded content that tries to get visitors to do something they would only do for a trusted organisation [4]

Google is explicit on one point: "Embedded social engineering content is a policy violation for the host page" [4]. That means your page, not the ad network's and not the widget maker's.

So a site does not need to be compromised to look deceptive. An old plugin that now serves ads from a network you never vetted, a booking widget loading pop-ups from someone else's server, a "your browser needs updating" banner slipped into a third-party script: none of these are break-ins in the usual sense. All of them are the kind of pattern a lower-confidence verdict is designed to catch.

I want to be careful here. Google has not said which signals trigger the suspicious tier, and I am not going to invent a list. The point is narrower. "We have not been hacked" is no longer the same statement as "Chrome has no reason to warn about us."

Myth 2: If My Site Were Flagged, I Would See It Myself

This is the myth that does the most damage, because it feels like common sense. You visit your own website most days. Surely you would notice a warning.

Probably not. Three things stand between you and what your customers see.

The protection level. Chrome's own help pages state that "Standard protection is on by default" [2]. The new suspicious warnings apply to users who have turned on Enhanced Protection [1], which Google says passed one billion Chrome users in 2025. If you have never changed the setting, you are on Standard. You will not see the suspicious tier at all, while some of your visitors will.

The browsing context. Google's Search Console documentation notes that Safe Browsing "displays warnings to users based on the browsing context" [3]. A warning one person sees may not reproduce for another, which makes a single check from your own laptop close to meaningless.

You are not a stranger. You arrive logged in, from a familiar device, often straight to the dashboard. Your customer arrives cold, from a search result or a link in a message, on a phone you have never seen.

Who is visitingWhat they see on a flagged pageCan you see it from your own browser?
Visitor on Standard protection (Chrome's default)Only dangerous verdicts, shown as the full-page red warningOnly for a dangerous verdict
Visitor on Enhanced Protection, suspicious verdictA shield icon in the address bar, with options to mark the site as safe or go back [5]No, unless your own profile also runs Enhanced Protection
Any Chrome visitor, dangerous verdictThe full-page red interstitial [1]Usually, and Google's confirmed findings appear in Search Console [3]

Myth 3: Google Would Tell Me If There Were a Problem

For the red warnings, there is a proper channel. The Security Issues report in Search Console shows Google's findings when a site is hacked or behaves in ways that could harm visitors, grouped into hacked content, malware and unwanted software, and social engineering [3]. If your site is verified in Search Console and the notification emails go to someone who reads them, a confirmed finding should reach you. If one does arrive after a break-in, the clean-up is only half the job, because what Google does to a hacked site's search visibility can outlast the hack itself.

The suspicious tier is a different matter. Google's announcement does not say whether lower-confidence verdicts appear in Search Console, and it does not describe any way for a site owner to contest one [1]. That may change as the feature matures. For now, an operator should treat it as a gap: a warning your customers can see, with no confirmed notification route to you.

None of this is a reason to panic. It is a reason to stop treating silence as evidence. In operations terms, no alert is not the same as a healthy system. It might just mean nobody wired up the alert.

Myth 4: A Warning Is a Small Annoyance Customers Click Past

Some do. Most do not, at least with the red warnings. In a large field study of real Chrome and Firefox users published at USENIX Security, researchers found people continued through roughly a quarter of Chrome's malware and phishing warnings [6]. Turn that around and around three in every four visitors went back. The study dates from 2013 and measured the red interstitial, not the new shield, so treat it as an indication of how seriously people take a browser telling them to leave rather than a forecast for the suspicious tier.

The suspicious warning is gentler. It sits in the address bar instead of blocking the page, and the visitor gets a choice [5]. Think about when that choice arrives, though. Your visitor is about to type a card number, upload a document, or send their phone number through a form. At that exact moment, the browser suggests your business might be a scam.

Consider a composite scenario, built from patterns we see rather than from one real case. A boarding kennels in Mayo opens its Christmas bookings in late November. The booking page still runs an old calendar plugin nobody has looked at in years, and the plugin's free tier now displays third-party ads, one of which mimics a "Continue" button. A dog owner on Enhanced Protection reaches the deposit step, spots the shield, taps back to safety and books the next kennels on the list. That evening the owner checks the site from a logged-in laptop. Everything looks perfect. The December calendar fills a little more slowly than last year, and nobody can say why.

There was no hack. Nothing turned red, and Search Console stayed silent. The bookings were simply gone by the time anyone noticed.

Flat illustration of a winding deep navy path of oval stepping stones crossing a teal landscape toward a rounded doorway shape on a pale background
A warning at the deposit step is enough for a visitor to turn back.

Myth 5: My Host's Security Tools Cover This

Server-side security matters, and I would never argue otherwise. Malware scanning catches injected code. Intrusion prevention blocks repeated login attempts. Nightly backups give you a clean rollback point if something does get in. For the full picture of the layers a properly run site needs, our complete WordPress security and backup guide sets them out in order.

Be clear about the boundary, though. A host controls the server. It does not control Google's verdict, and it cannot see a third-party script that loads directly from another company's server into your visitor's browser. If an ad network starts serving a deceptive pop-up on your page this afternoon, that content may never touch your hosting account at all.

What a sensible hosting setup should give you

Nobody can honestly promise that a browser warning will never appear. What you can reasonably expect from a hosting platform is narrower and more useful:

  • A hardened, scanned server, so the confirmed, dangerous kind of flag is unlikely in the first place
  • Clean restore points, so that if a plugin is the cause you can roll back in minutes rather than rebuild
  • A real person to ring, who can help you work out whether the conflict lives on the server or in something you embedded

That is the standard Web60 is built to meet. Sites run on Irish-hosted infrastructure with server-level hardening, fail2ban intrusion prevention and automatic malware scanning, with automatic nightly backups, one-click restore and an Irish-based support team of real people. One thing it cannot do is clear a warning on Google's behalf or speed up Google's review. Only Google lifts its own verdicts, and anyone who claims otherwise is overselling.

A word on scale. If you run a large retail brand with its own security operations team, a brand-protection contract and dozens of domains, dedicated threat-intelligence services that watch every browser blocklist around the clock genuinely suit that workload better than any hosting platform can. For a business with one website and a handful of people, that is overkill. What you need is a routine.

How to Verify What Chrome Thinks of Your Site in Five Steps

  1. Create a stranger's view. Make a separate Chrome profile with no saved logins, switch it to Enhanced protection in Chrome's privacy and security settings, and visit your homepage, booking page and checkout from it, on a computer and on a phone if you can [2].
  2. Verify Search Console. Open the Security Issues report for your site, confirm it shows no detected issues, and make sure the email address that receives Search Console alerts belongs to someone who actually reads it [3].
  3. Audit your embeds. List every ad, pop-up, chat widget, booking calendar and payment link on the site, then remove anything you cannot name the owner of or did not deliberately add.
  4. Rollback the cause. If a plugin update or new widget lines up with the warning, restore that page or the whole site to a version from before the change reached production and check again from the stranger's profile.
  5. Request a review. For a confirmed issue, fix it everywhere, then select Request Review in the Security Issues report and describe what you changed; Google says these reviews take from a few days to a few weeks [3]. If you believe a phishing flag is simply wrong, Google also runs a Safe Browsing error report form for that purpose.
Abstract flat illustration of a teal ring hovering over a diamond grid of cream and white tiles, with the tile beneath it coloured deep navy
Verify your key pages the way a stranger would, not the way you usually do.

What This Changes for Your Website

Browser warnings used to be a hacking problem. With the suspicious tier, they are partly a presentation problem as well: what your pages load, what they ask visitors to do, and whose code is running on them. Most of that sits within your control.

Build the stranger's profile once. Put a monthly reminder in the calendar to visit your key pages through it, and keep Search Console's emails going somewhere real. If you are starting a new site, starting clean helps, with fewer leftover plugins, fewer forgotten widgets and less code loading from servers you have never heard of. An AI-built WordPress site on Web60 starts that way, for €60 a year with hosting, SSL and backups included.

Your customers decide in a second whether a page looks trustworthy, and Chrome is now helping them decide. Ten minutes a month spent looking at your site the way they do is one of the cheapest protections you can put in place.

Frequently Asked Questions

What does the Chrome suspicious site warning look like?

Google says suspicious warnings are set apart from dangerous ones by their format, icons, colour and text. Early coverage of the rollout describes a shield icon in the address bar that opens a dialog with two choices: mark the site as safe, or go back to safety. Dangerous sites still get the full-page red warning. Only visitors who have turned on Enhanced Protection see the suspicious tier.

How do I check if Google has flagged my website?

Verify your site in Google Search Console and open the Security Issues report, which shows Google's confirmed findings for hacked content, malware and social engineering. Google also publishes a Safe Browsing site status page in its Transparency Report. Neither is confirmed to show the new lower-confidence suspicious verdicts, so also visit your site from a separate Chrome profile with Enhanced Protection switched on.

Does a suspicious site warning affect my Google rankings?

Google has not said that a suspicious verdict in Chrome affects search rankings. Confirmed security issues are different: Google's documentation says affected pages can show a warning label in search results as well as a browser warning. Either way, the bigger cost is visitors leaving before they contact you, so fix the cause rather than waiting to see what happens.

Can I stop Chrome showing the warning to my customers?

Not directly. Only Google can lift its own verdicts. Remove whatever is causing the warning, verify the page from a stranger's profile, then request a review in the Search Console Security Issues report, or use Google's Safe Browsing error report form if you believe a phishing flag is simply wrong. Avoid asking customers to click Mark as safe, because it teaches them to ignore warnings that might one day be real.

Should I turn on Enhanced Protection in my own Chrome?

For a separate checking profile, yes, because it is the only way to see the suspicious tier your customers might see. Know the trade-off: Chrome's help pages say Enhanced Protection sends the URL of each site and a small sample of page content to Google Safe Browsing. Standard protection, the default, sends full URLs and bits of page content only when a site does something suspicious.

Sources

IO
Ian O'ReillyOperations Director, Web60

Ian oversees Web60's hosting infrastructure and operations. Responsible for the uptime, security, and performance of every site on the platform, he writes about the operational reality of keeping Irish business websites fast, secure, and online around the clock.

More by Ian O'Reilly →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Chrome Suspicious Site Warning: Is Your Site Flagged? | Web60