You know that feeling when the phone rings and it isn't a new job. A customer, or maybe someone in the family, says they tried to open your website and got a big red warning. Something about the site being dangerous, or hacked, or not safe to visit. Your stomach drops. The site looked fine when you checked it last week, and the phone in the office is still ringing like normal.
Take a breath. This happens to ordinary small businesses around Perth, and it's usually fixable. Google has spotted something it thinks could hurt a visitor: malware, spam pages nobody on your team wrote, or a fake page in a folder you've never opened. You've probably already searched Google blacklist removal Perth. Here's what we'd actually say if you rang.
First, don't panic
You don't need to pull the website down this afternoon, and you don't need a new one. Slow down before you start deleting things. Poking around while you're logged in as admin can make it harder to see how someone got in.
If you can, open the site on your phone in a private window, the way a customer would, and write down the exact words. A full-page block in Chrome means Safe Browsing has told the browser to stop people before they reach you. A line under your Google listing that says the site may be hacked is quieter, and people can still click it, but a lot of them won't. Jot down which one you're seeing. It makes the clean-up easier to explain later.
If the site won't load at all, you're dealing with a different mess, and we've written about what to do when a site goes dark, including when the host has switched it off. A warning on a site that still opens means you can get in and clean it.
Find out what Google actually flagged
The clearest place to look is Google Search Console, the free dashboard for site owners. If someone has already hooked it up, sign in and open the Security Issues report. You'll see what Google thinks is wrong, plus a few example pages. Those are only a sample. If it shows three odd addresses, there are often more like them, so look for the pattern rather than just those three links.
Screenshot that page before you change anything, and note the label in your own words: malware, spam pages, a phishing page, unwanted software. You'll want that sentence when you ask for a review. If more than one problem is listed, clear all of them. Leaving one behind is why people end up doing this twice.
If you can't get into Search Console, paste your web address into Google's public Safe Browsing check and see if they're calling the site dangerous right now. That won't show the example pages, and it won't let you ask for a review, so get the business added as an owner on an email someone in the office actually reads. A lot of Perth sites are still tied to a designer's old Gmail, and the warning email goes there. You only find out when a customer rings.
Have a look around yourself too. Search your business name, click a couple of pages in a private window, and watch for pages you never made, admin users you don't recognise, and files that changed when nobody was working on the site. We cover how websites get hacked in more detail if you want the longer version. On a small site it's usually an old plugin, an easy password, or a login that should have gone when someone left.
Clean it up before you ask for a review
If you ask for a review while the problem is still there, the warning just stays up. Ask too soon, more than once, and you can be blocked from asking again for about a month. So clean it first.
When you're ready, work through it in this order:
- Copy the files and the database before you change anything, so the hacked copy isn't your only backup.
- Work out how they got in. Old plugins, easy passwords, leftover logins, and a file manager left switched on are the usual doors.
- Remove the junk: spam pages, strange files, and code dropped into pages that used to be yours.
- Update whatever was abused. Delete plugins, themes, and admin users you don't recognise.
- Change the website, hosting, and domain passwords, and turn on the "code to your phone" prompt anywhere it's offered.
- Send yourself a test enquiry from a private window, and make sure a person still gets it.
If you're on WordPress, those updates need to keep happening. We've written a simple routine for website security updates you can hand to whoever looks after the site.
If you open the file list and none of it looks familiar, stop guessing. That's when hacked website repair is worth a call. We'll tell you if you can finish it yourselves.
Ask Google to check it again
Once you're confident the junk is gone and the way in is closed, go back to that Security Issues report and request a review. Tell them what was wrong and what you did, in a few ordinary sentences. "We removed the spam pages and updated the plugin that let them in" is plenty. "Please take the warning off, we're a real business" doesn't tell anyone what changed.
You'll get an email when Google has the request, and another when they've decided. Don't send a second one while the first is still open. It doesn't jump the queue.
How long does it take? Usually a few days, sometimes a few weeks. A simple clean is often quicker than a site full of spam pages, because those can need a person to look. After the all-clear, the warning in Chrome can linger a little while their systems catch up, so check a private window before you turn ads back on. If they say it's not fixed, they often show more example pages. Clean that kind of page across the site, then ask again.
Keep it from happening again
Once the warning is gone, the thing that brings it back is leaving the way in open. Someone needs to own the updates. Plugins you're not using should be deleted, not just switched off. Passwords should be unique, and that second login step should be on for the website and the host. Old staff and old web people shouldn't still have a login.
Keep the domain name and Search Console on an email the business actually reads, not on someone who left years ago. Store a backup somewhere other than the live server. One taken after the hack will only put the hack back. If the site gets dirty again within a few days, something was missed, so don't keep asking for another review until that something is gone.
Questions we get on the day
Can we just tell customers to click past the warning?
People who already know you might. A stranger who sees a big red warning will usually leave, and that's fair enough. The message stays up until Google is happy the site is clean.
Do we have to take the website offline?
Not always. If you can see the odd pages and you can see how they got there, you can often clean it while the site stays up. If you can't tell what's infected, or the site is sending people somewhere else, switch it off until it's sorted.
We don't use Search Console. Can this still be fixed?
Yes. The site still has to be cleaned. Search Console is how you see the example pages and how you ask Google to check again. Get the business added as an owner while you're dealing with this, on an email you actually read.
How long until the warning goes away?
Usually a few days, sometimes a few weeks. We can't promise a particular day, because it depends on what Google found. You'll get an email when the review is finished, and the warning in the browser can hang around a little longer after that.
If you'd like us to look
If you can see the problem and you know which plugin or password let them in, the steps above are enough to get you moving. If the files don't make sense, or the warning came back after you deleted a couple of pages, just ring us. We'll tell you straight whether it's a clean-up we should do, or whether you're fine to finish it yourselves.
Call 08 6146 2410 or email info@strideit.com.au. If the site is simply down, rather than showing a warning, say that when you get in touch. We can help with that too, and you can read more about the repair work on our hacked website repair page.