Skip to content

My Website Was Hacked:
What to Do in the First 24 Hours

A hacked website costs you customers for every hour it is down or defaced. The steps to take in order, how to clear Google's warning, and when to rebuild.

7 min read

Navy and amber illustration of a laptop showing a padlock over an error page, with a phone beside it lit by a missed call

Key Points

  • Hacks are not always loud.
  • If Google or a browser is warning visitors about your site, the warning stays until Google reviews it.
  • Say what happened in two or three plain sentences, what you have done about it, and how they can reach you now.
  • A clean site is only safe until the next update is missed.
  • A rebuild sounds slower than a clean-up.
  • Wire Ninjas is an IT and security company that serves homeowners and businesses in New Jersey, New York and Connecticut.

If your website has been hacked, work through the steps below in order. Take the site out of public view, change every password, restore a clean copy or rebuild, and only then ask Google to remove its warning. Most of the damage from a hack comes from the days of downtime and the enquiries nobody sees. Speed matters, and so does order, because cleaning a site that is still open to the attacker only gets it hacked again.

This guide is written for business owners and marketing managers, not security engineers. We have rebuilt a hacked website for a client, and the last section explains what that taught us.

Signs your website has been hacked

Hacks are not always loud. Look for any of these:

  • A warning page in your browser, or a security notice in Google’s search results, when you visit your own site
  • Pages, links or products you never created, often in another language
  • Visitors sent to a different website, sometimes only when they arrive from Google or from a phone
  • Admin accounts you do not recognise
  • An email from your hosting company saying your account has been suspended or flagged
  • A sudden drop in visits or enquiries with no change on your side
  • A message in Google Search Console about security issues

One sign is enough to act on. Do not wait for a second.

The first hour

  1. Keep a copy of the site as it is now. Ask your host for a backup or download the files and database. Whoever investigates will need the evidence. Do not start deleting files at random.
  2. Take the site out of public view. Switch on maintenance mode or ask your host to suspend public access. A hacked site that stays live can harm your visitors and get your domain flagged as unsafe.
  3. Put a holding page where your enquiries can still reach you. A plain page with your phone number, WhatsApp and email keeps customers from thinking you have closed.
  4. Call your hosting company. They can see server logs you cannot, and many will help scan and restore.
  5. Change every password from a clean device. That means hosting, the website admin, the database, SFTP, the email accounts tied to your domain and your domain registrar. Turn on two-factor authentication wherever it is offered.
  6. Remove admin users you do not recognise, and replace any API keys that sit in the site’s code or settings.

The first day

Find out what changed. Compare the site against your last clean backup. Run a malware scan, or ask your host to. Look at recently changed files and recently added users.

Check where your forms send enquiries. Confirm that every contact form still delivers to an address you own. A hack that quietly redirects enquiries is hard to spot, because the site looks fine.

Update everything before you restore anything. If you restore an old backup and leave the weak point in place, you are back where you started. Update the CMS, the theme and every plugin, and delete the ones you no longer use.

Check your other sites. If several sites share one hosting account, one hack can reach all of them.

Clear Google’s warning

If Google or a browser is warning visitors about your site, the warning stays until Google reviews it.

  1. Open the Security issues report in Google Search Console.
  2. Fix every issue it lists, on every page it names, not just some of them.
  3. Select Request review and describe what was wrong, what you fixed and how you know it is clean.

Do not send the request before the fixes are finished. Google says that asking for a review while the problem remains can make the next review slower. Google also says a review can take several days or weeks, so do the work properly the first time. Its guide to requesting a review explains what to write.

Tell your customers

Say what happened in two or three plain sentences, what you have done about it, and how they can reach you now. If customer data may have been exposed, get legal advice about your duty to report it in each country where your customers live. The rules differ, and this is not a place to guess.

Close the way in

A clean site is only safe until the next update is missed. After the clean-up:

  • Keep the CMS, theme and plugins updated, on a schedule someone owns
  • Remove everything you do not use
  • Give each person their own login, with the smallest permissions that let them do their job
  • Store backups away from the server the site runs on, and test that they restore
  • Set an alert for downtime, so you hear before your customers do

Our Webflow maintenance guide lists what a routine looks like, and our website maintenance service covers it for you.

Clean it, restore it or rebuild it

Your situation The usual best route
Caught early, a recent clean backup exists, you know how the attacker got in Restore the backup, update everything, then harden the site
Hacked more than once, or nobody can say how it happened Rebuild on a clean base
The site runs on an old theme or plugins that are no longer updated Rebuild
Customer data may have been exposed Bring in a security specialist before you do anything else

A rebuild sounds slower than a clean-up. It often is not, and it gives you a site you can trust again. It is also a chance to fix the parts that were already losing you customers.

What a rebuild looked like for Wire Ninjas

Wire Ninjas is an IT and security company that serves homeowners and businesses in New Jersey, New York and Connecticut. Their website was hacked, the site went down, and it stopped bringing in enquiries. For a security company, that damages trust twice: customers lose the way to contact them, and a hacked site undercuts what the company sells.

We rebuilt the site in four weeks. The work followed the order above:

  • Structure first. We rewrote the pages around what a customer needs at the moment of decision: what you do, who it is for, and a simple way to request a quote or call.
  • Design that rebuilds trust. A clean visual system with clearer hierarchy and proof, so the site looks credible at a glance.
  • Built and tested for stability. We rebuilt the site from the ground up, with careful testing for reliability and performance across devices.
  • Conversion and search foundations. Clear calls to action and a structure ready for local search, so the site could win back its steady flow of enquiries.

The full story, with the published result, is on the Wire Ninjas case study.

How we help

If your site has been hacked, or you are not sure whether it has, . We will look at the site with you and tell you whether to restore it or rebuild it. After that, your Co-Driver for the web keeps it updated, so the next missed update does not become the next hack.

Frequently Asked Questions

How do I know if my website has been hacked?

Look for a browser or Google warning, pages you did not create, visitors sent to another site, unknown admin users, a message from your host, or a sudden drop in visits and enquiries. Any one of these is a reason to start the steps above.

Should I take my hacked website offline?

Yes, for the clean-up. A live hacked site can harm visitors and get your domain flagged as unsafe. Put up a simple holding page with your phone number, WhatsApp and email so customers can still reach you.

Will Google remove my site from search because it was hacked?

Google may show a warning to visitors until the problem is fixed and reviewed. Fix every issue in the Security issues report, then request a review. Google says reviews can take several days or weeks.

Can I clean a hacked website myself?

You can if you caught it early, have a clean backup, and can update and check everything. The risk is missing a hidden way back in. If the site is hacked again, or you cannot say how it happened, a rebuild is the safer choice.

How long does it take to fix a hacked website?

It depends on the damage. Restoring a clean backup can be quick. A rebuild takes longer: ours for Wire Ninjas took four weeks.

Can Carril fix my hacked website?

Yes. We clean, restore or rebuild, and we can then keep the site updated and monitored. Tell us what happened on a call and we will say what we would do first.

Tell us what you are building.

Scope, cost, and timeline, mapped with you.

Book a Free Call

Trusted by 150+ teams worldwide