If your website was hacked, call your web host first, then change every password from a clean device: hosting, website admin, domain registrar and email. Restore a backup made before the hack and fix whatever let the attacker in. Then request a review in Google Search Console so any Google warning comes off.
Most contractors find out from someone else: a customer who calls about a strange page, a red warning in Chrome or an email from Google. The first instinct is to start deleting things. Slow down. The order you do things in decides whether the hack is gone for good or back next week.
How Do You Know If Your Website Was Hacked?
The clearest signs come from Google or your host: a red warning page when someone opens your site, a note under your listing in Google that the site may be hacked, an email from Google Search Console or a host that suddenly suspends your account. Google’s help page on site warnings says “Google Search results might show labels such as ‘This site may harm your computer’ or ‘This site may be hacked’ next to your site.”
Other signs are quieter. Watch for these:
- Pages in Google that you never wrote, often in Japanese or selling fake brand-name goods or drugs.
- Customers saying your site sent them somewhere else, usually on their phone.
- Admin users on your website that nobody on your team created.
- An email from Google Search Console saying someone new has been added as an owner of your site.
- A jump in visits from searches that have nothing to do with your trade.
- Business emails that start bouncing or landing in spam. WordPress.org warns that hacked sites get used to send spam, which can get the server blacklisted. See why quotes go to spam.
Then run three free checks:
- Search Google for “site:yourdomain.com” (with your own address) and flip through a few pages of results. Anything you don’t recognise is worth a look. Google suggests this in its guide to spotting a hacked site.
- Open the Security Issues report in Google Search Console. If you haven’t set up Search Console, do it now. It’s free. It’s where Google tells you what it found and where you’ll ask for the warning to come off later.
- Look your site up on Google’s Safe Browsing site status page. It tells you whether Google currently lists the address as unsafe.
Why Does a Hacked Site Look Fine to the Owner?
Because many hacks hide from the owner on purpose. The spam shows up for Google, or for phone users arriving from a Google search, while someone typing the address on an office computer sees the normal site. Google calls this cloaking.
Google’s guide to the Japanese keyword hack warns that a spam page can even look like a dead link when you open it: “Hackers will try to trick you into thinking the page is gone or fixed when it’s still hacked.” Its post on sneaky mobile redirects adds that “if your website has been hacked, a potential result can be redirects to spammy domains for mobile users only.”
So test the way your customers arrive. Pick up your phone, search Google for your business name and tap your own result. Google recommends exactly this: “We recommend you to check the mobile user experience of your site by visiting your pages from Google search results with a smartphone.” If you end up on someone else’s site, something on yours is redirecting your customers. That could be a hack, though Google notes an ad script added to a site can do it too, so check the Security Issues report first. The URL Inspection tool in Search Console shows what Google sees on any page, which is how you catch spam that hides from you.
What Should You Do First When Your Website Is Hacked?
Call your web host, then lock down every login before you clean anything. If you clean first, the attacker can walk straight back in with a password they already have. Here is the order:
- 1. Call your host. On shared hosting the problem can reach past your own site, and the host may already be on it, as WordPress.org’s guide for hacked sites points out.
- 2. Write down what you saw and when. Note the date you noticed, anything that changed recently (a new plugin, a new theme, a new web person) and take screenshots. WordPress.org calls this the start of an incident report, and whoever cleans the site will ask for it.
- 3. Save a copy of the hacked site. Google’s cleanup guides say to back up the whole site, files and database, before you remove anything, in case you need something back later. Keep that copy apart from your good backups so the two never get mixed up.
- 4. Scan the computer you log in from. WordPress.org’s guide says that in many cases the attack starts on the owner’s own computer, where malware picks up the login details. Change passwords from a device you trust.
- 5. Change every password. Hosting, website admin, FTP and database, the domain registrar and your business email. Google’s recovery steps cover the site logins. The registrar and email are the ones owners forget, and whoever holds them can move your domain or reset every other password.
- 6. Turn on two-step login everywhere it’s offered, and stop reusing passwords. Google’s guide to how sites get hacked recommends both.
- 7. Remove users you don’t know from the website and from Search Console. Google says that with one common spam hack, “the hacker will typically add themselves as a property owner in Search Console”.
If an agency or a freelancer built your site, ask them today who holds the hosting and registrar logins. If the answer is “we do”, you’re relying on them to fix this. Our post on what you should own if your agency quit lists the accounts to get into your own name.
Not sure your site is clean? Book a free 20-minute call. We’ll look at what Google shows for your website with you and tell you what to check first.
Book a Free Call →Should You Take Your Website Offline While You Fix It?
Usually yes. Doing it for a short time is unlikely to hurt your rankings. The same Google recovery guide says: “It’s unlikely that taking your site offline intermittently or temporarily during the recovery process will affect future ranking of your site in search results.”
Taking the site down protects your customers from whatever the hacker added, and it stops the hacker from making changes while you work. Google suggests showing a temporary “down for maintenance” response (a 503 code) from outside the hacked files, and says your host may be able to set that up for you. Blocking search engines in your robots.txt file isn’t enough. It only stops crawlers, so customers would still reach the bad pages.
There is a cost. While the site is down, anyone who taps Website on your Google Business Profile lands on the maintenance page. Calls from the profile don’t depend on your website, so make sure the phone gets answered while the site is offline.
How Do You Clean a Hacked Website So It Stays Clean?
Restore a backup from before the hack, then close the hole the attacker used. Skip the second part and the same hole lets them back in. Google’s cleanup guide starts with the backup itself: “First, check that your backup was created before your site was hacked.”
Not every hack needs a paid cleanup. Google’s steps for a clean, current backup are short: restore it, install every update, then carry on with the password changes and the fix below. On a small site with a good backup, that can be the whole job.
Then find the way in. Google’s list of the top ways sites get hacked comes down to a few causes a contractor can check:
- Old software. An out-of-date WordPress, theme or plugin with a known hole. Update everything, and delete plugins nobody maintains anymore. Google adds: “When removing a plugin, make sure to remove all its files from your server rather than just disabling it.”
- Pirated themes and plugins. A “free” copy of a paid theme is a well-known way in. Google says: “It’s a common tactic for attackers to add malicious code to free versions of paid plugins or themes.”
- Weak or reused passwords. Once attackers have a working password, they try it on as many other accounts as they can.
- Tricked logins. A fake email from your “host” or “Google” asking you to sign in. Google lists this kind of phishing as one of the main ways in.
If your site runs on WordPress, our post on WordPress security fixes shows how to tell whether your version is behind. If it’s on a hosted builder like Wix or Squarespace, you don’t install or update the site software yourself, so the plugin route mostly doesn’t apply. A stolen password still works on those platforms, though, so the login steps above matter just as much.
Scanners help, but no single one sees everything. WordPress.org’s guide lists two kinds: security plugins that scan from inside the site, and remote scanners such as VirusTotal and Sucuri SiteCheck that look from outside. A remote scanner only sees what your site shows to visitors, so it can miss files hidden on the server.
Hire help if you have no clean backup or if the hack came back after a cleanup. The same goes if nobody on your side is comfortable working on the server. Google is blunt about it: “Fixing a malware issue on your site requires the ability to read and understand code, and possibly web server configurations for your site.” Before you pay anyone, ask three questions:
- Will you find out how the attacker got in, or only remove the bad files?
- Will you check the database as well as the files?
- What happens if the hack comes back in the next few months?
One more check before anyone deletes files. If the hack could have reached customer details, such as form entries or logins, Google’s cleanup guide says “you may want to consider any business, regulatory, or legal responsibilities before you begin cleaning your site or deleting any files.” Get that advice first, because a wiped server can’t answer questions later.
How Do You Get Google’s Hacked Warning Removed?
Clean every page, then ask for a review in the Security Issues report in Search Console. Google says “you should rely on the Security Issues report as the source of truth to verify whether any security issues exist for your site, or if they have been fixed.”
Two rules from Google’s Security Issues help page matter here. First, fix everything, not only the pages Google listed. The report shows a sample of affected pages, not a full list, and “Fixing the issue on just some pages will not earn you a partial return to search results.” Second, don’t ask too early: “Submitting a reconsideration request when the issue hasn’t been fixed can cause longer turnaround time for the next request, or even get you marked as a repeat offender.”
As for timing, the help page says: “A review can take from a few days to a few weeks to complete.” Google’s older review guide splits it by type: “Reviews for sites infected with malware require a few days to process.” And: “Reviews for sites hacked with spam can require up to several weeks to process.”
While you wait:
- Make the spam pages return “not found”. Google’s cleanup guide says “If you just delete the pages and then configure your server to return a 404 status code, the pages will naturally fall out of Google’s index with time.” If the hacker added only a handful of pages, the Removals tool in Search Console can hide them sooner.
- Ask Google to recrawl your real pages with the URL Inspection tool in Search Console, so the clean versions replace the hacked ones.
Google tries to keep hacked pages out of its results, so a hack can cost you search visits for as long as it lasts. If calls from Google stay low after the warning is gone, look at your rankings next. That is the work our local SEO service does.
How Do You Stop Your Website Getting Hacked Again?
Most of it is routine upkeep. Set it up once, then check it monthly:
- Updates on. Turn on automatic updates where your platform allows it, and check once a month that they actually ran.
- Fewer plugins. Every plugin is more code to keep patched. Delete what you don’t use and remove its files, not just switch it off.
- Two-step login on every account: hosting, website, registrar, email and Search Console.
- Backups stored off the server, and restored once as a test. A backup you’ve never restored is a guess.
- Logins in your name. You or your office manager should own the hosting, registrar and Search Console accounts, with your web person added as a user.
- HTTPS on every page. Google lists signing in over plain HTTP as a security hole. Our post on Chrome’s HTTPS warning shows how to check yours.
If someone else looks after your website, ask them to show you each of these on a screen share, not just tell you they’re done.
Where This Advice Comes From
The steps in this guide come from Google’s help pages for hacked sites (the Search Console help pages on security issues and site warnings, and Google’s hacked-site guides on web.dev) and from WordPress.org’s guide for hacked WordPress sites, all read on November 16, 2026. Several of the web.dev guides carry a 2015 date. Where one of them and the current Search Console help page give different review times, both are shown. No new study was run for this post.
The search figures are U.S. and Canadian monthly averages from Google’s Keyword Planner, pulled on November 16, 2026 for November 2025 to October 2026: about 5,400 U.S. and 880 Canadian searches a month for “website hacked”, a figure Google shares with close variants like “hacked website”. Search difficulty and AI Overview data weren’t available for this post. Wordfence’s pricing page refused automated requests, and no cleanup company’s price is quoted because the one pricing page that could be read didn’t state a currency. Osprey builds websites and sells local SEO to contractors, so weigh our advice with that in mind.
