Short answer. Six steps, in this order. Isolate: a maintenance page, without deleting anything. Copy the infected state, for the diagnosis. Date the entry: it, and not the day you noticed, tells you which backup is clean. Rebuild: a clean installation, software taken from the source, content checked, or the restore of a copy from before the entry. Close: all passwords, unknown accounts, updates. Get the site reviewed by the search engine, then monitor. What not to do: delete the visible page and believe it is over. Allow an hour to isolate, and about five days to reopen cleanly.
This guide is for the manager whose company site shows something other than it should, redirects its visitors, or carries a warning in a search engine or a browser, and for the founder based in France who discovers the problem from a distance. The notions quoted come from public sources: website defacement, the backdoor, the web shell, Google's Safe Browsing service and the help pages of its search console. The site, dates and plugin in the example are constructed. This guide covers neither reporting obligations nor legal action: if customer data may have been read, see your legal adviser.
Six signs of a hacked site, and the first action
The figure gives, for six signs, what they mean and what is done first.
What you see. A defacement is an attack that changes the visual appearance of a website or a page: it is the most visible case. Other attacks leave the site looking intact to you, and make it behave differently for a visitor coming from a search engine or on a phone. So always check from another device and from a search. The warnings. Google Safe Browsing is a service that warns users when they try to visit a dangerous website; Chrome, Safari and Firefox, among others, use it. In search results, the label “This site may be hacked” appears under your name; according to Google's help pages, it only goes away after the site owner acts.
Spam. Pages that are not yours, in a foreign language or pushing unrelated products, published under your domain name: it is a deliberate manipulation of search engine indexes, done at your expense. The host. If it suspends the account, ask for its report: the file detected and the date. The first action, always the same. Put the site in maintenance without deleting anything, and note what you see, with screenshots. If the site does not display at all, the cause may lie elsewhere, an expired domain name for example: see the guide to the domain name.
Putting a site back in order, in six steps
The first step is accented: isolate, without deleting anything.
Isolate. A maintenance page replaces the site; the files stay in place. Passwords are changed at once, from a computer you are sure of: hosting, database, administration accounts, file access. Copy. The infected state is copied as it is: it is the only piece of evidence that will show where the intruder came in. Date. Modified files, accounts created and the server logs give the day of the entry.
Rebuild. On a clean installation: the software core, the theme and the plugins are taken from their official source; the content, texts and images, is checked then put back; files nobody recognises do not return. Close. The way in is identified and closed: update, plugin removed, account deleted, password changed a second time after going back online. Get it reviewed. The review request is made in the search console, when the whole site is clean; according to Google's help pages, a request made too early only prolongs the flag.
The hack is six weeks older than its signs
The figure goes back in time, from the day people notice to the day of the entry, then looks at the backups.
The entry is quiet. In the example, a plugin that had not been updated lets an intruder in on 3 March. The next day they plant a backdoor, a hidden way of bypassing normal authentication. Then nothing visible happens: spam pages are created off the menu, search engines index them, and it is only on 14 April, forty-two days later, that a redirect alerts someone.
The backups. The host keeps fourteen daily copies: all were taken after 3 March, all contain the backdoor. Restoring “yesterday's backup” puts the site back in yesterday's state, hacked. With weekly copies kept twelve weeks, there is one from 26 February, before the entry: that is the one to use, completed with the content published since, once checked. The general rule is in the guide to backups; for a website, it comes down to keeping copies for a long time, and somewhere other than the server.
«Restoring yesterday's backup puts the site back in yesterday's state, hacked.»
What a quick clean leaves behind
The figure shows six places in a hacked site, and what remains when only the visible page has been deleted.
Five doors out of six. A file slipped in among the images: a web shell, which gives access to the server from a browser. An administrator account nobody created. A few lines added to a legitimate theme file. Links injected into the database. A scheduled task that reinstalls everything every night. Deleting the modified home page touches none of that.
Why rebuild. You cannot prove that a site cleaned by hand is clean; you can prove that a rebuilt site is, because every file comes from a known source. It takes a day or two longer, and it is the only way not to start again the following month. Content management systems. The most widespread, WordPress, ran in December 2024 on nearly 62 % of the sites whose content management system is known: so it is also heavily targeted, and its plugins need following. A site that only needs a few pages can be redone more simply, with fewer parts to keep updated.
«You cannot prove that a site cleaned by hand is clean; you can prove that a rebuilt site is.»
A site that stays clean, in five layers
The accented layer is the first: updates.
Updates: every month, by someone whose task it is; unused plugins are removed, and nothing is installed from outside the official sources. Accounts: few administrators, one account per person, two-step verification; the account of the agency from four years ago is closed. The rules are those in the guide to hacked accounts.
Hosting, backups, monitoring. An alert when a file changes or an account appears brings the discovery time down from six weeks to one day. All of this belongs to the routine upkeep described in the guide to managed IT, and is checked once a year by an outside eye, as in the guide to the security audit. If the attack also reached your PCs and files, what to do is in the guide to ransomware.
Five days to reopen cleanly, in 2027
Five days in the example, two of them to rebuild.
- What the manager receives: the date and path of the entry, what was touched, what was rebuilt, the passwords changed, and the date of the review request.
- What the company no longer does: delete the visible page and wait, restore the previous day's backup, leave a site without updates for four years, keep a former provider's account.
- What is measured: days since the last update, number of administrators, age of the oldest backup, time between a file change and the alert.
- What Symloop does: isolation within the hour, the diagnosis, the clean rebuild, closing the way in, the review request, then upkeep and monitoring; and, when the site justifies it, a redesign with fewer parts to maintain.
Day 1, isolate and copy. Day 2, date and diagnose: you know through where and when, and which copy is clean. Days 3 and 4, rebuild: clean installation, checked content, plugins cut to what is needed.
Day 5, reopen and get it reviewed. The site goes back online and the review request is sent. According to Google's help pages, the review takes a few days for malware, and can take up to several weeks for spam: so the warning does not disappear the same day. For a month, the files are watched closely.
- My website has been hacked, what do I do first?
- Put it in maintenance without deleting anything, change all the passwords from a safe computer, and copy the current state. Only then do you look for where the intruder came in. Do not reply to any message left on the site.
- How do I know if my site is hacked?
- Six signs: page replaced, redirect to another site, browser warning, the label “This site may be hacked” in search results, unknown pages published under your name, account suspended by the host. Check from a phone and from a search, not only from your own computer.
- Is it enough to delete the page the hacker added?
- No. Something else generally remains: a hidden file, an account, added code, a scheduled task. As long as those accesses are there, the site is taken again. You have to rebuild on a clean installation, or restore a copy from before the entry.
- Can I restore yesterday's backup?
- Only if you are sure the entry dates from yesterday. A site is often hacked several weeks before anyone sees it; the previous day's backup then already contains the intruder's access. You need a copy from before the entry, hence the value of keeping copies over several weeks.
- How do I remove the Google warning?
- By first cleaning the whole site, then asking for a review in the search console. According to Google's help pages, the review takes a few days for malware and up to several weeks for spam; a request made before the site is clean prolongs the flag.
- How does a company website get hacked?
- The usual ways in: a component that was not updated, a weak or reused administration password, a plugin downloaded from outside the official sources, a compromised hosting account. These attacks are generally run by automated tools scanning the internet, not by someone targeting you.
- Do we have to redo the whole site?
- Not the content: texts and images are recovered after checking. The software is reinstalled cleanly. It is also the moment to ask whether a site of a few pages needs a content management system and twenty plugins.
- How long does it take to get the site back online?
- One hour to isolate it. About five days in our example to date the entry, rebuild and reopen. The search engines' warning may stay a few days to a few weeks longer, for the time of the review.
- Was my customers' data stolen?
- It depends on what the site held and what the intruder could read: forms, customer accounts, orders. The diagnosis tells you from the logs. If personal data may have been read, see your legal adviser about what follows.
- How do we stop it happening again?
- Updates every month, few administrators with two-step verification, backups kept several weeks off the server, and an alert when a file changes. And someone whose task this explicitly is.