Diagnosis
We confirm what kind of infection it is, which files and database tables are affected, and whether the server itself or other sites on it are involved.
It usually starts with a phone call from a customer. Your site opened a gambling page on their mobile. Or Google search shows your company name followed by hundreds of Japanese product listings. Or Chrome throws a red warning screen before anyone reaches your home page. By the time the owner hears about it, the infection has often been sitting there for weeks.
We clean the site, find how they got in, close that door, and work with Google and blacklist services to clear the warnings. Then we explain in writing what happened.
Otherwise the same hack comes back in a few weeks.
We confirm what kind of infection it is, which files and database tables are affected, and whether the server itself or other sites on it are involved.
Code that sends mobile visitors or Google traffic to betting, pharma or adult sites removed from files, database and .htaccess.
Thousands of fake spam pages removed, sitemaps cleaned and Search Console used to get the junk out of Google's index. This one takes patience.
Vulnerable plugins updated or replaced, backdoors removed, passwords and keys changed, file permissions fixed and a firewall added.
Review requests submitted to Google Safe Browsing and other blacklists once the site is clean, and followed up until the warnings clear.
A plain-language note on what was found, how attackers got in, what we changed, and what you should do next.
Find the way in, or it happens again.
A written report at the end.
We've cleaned sites that had already been 'fixed' two or three times. Each time, someone deleted the obvious bad files, and each time the infection returned. That's because attackers almost always leave a backdoor, a small file hidden in an uploads folder or a fake admin user in the database. Unless that's found, and the original weak point is closed, you're paying for the same cleanup again.
So our cleanup includes the boring investigation work. Server logs, file change dates, user accounts, plugin versions, cron jobs, anything that looks out of place. It takes longer than a quick delete, and clients sometimes ask why. The answer is simple: done this way, the site stays clean afterwards.
Hacks get worse the longer they sit. We start work as soon as we have access, any day of the week.
Spam pages removed from Google using Search Console, so your brand searches show your real pages again. This part can take a few weeks to fully settle.
Hacked sites often send spam. We check whether your domain or server IP is on mail blacklists and request delisting.
A verified clean backup taken after recovery, so you have a safe point to return to.
Written into the proposal before we start, so nothing is left to memory later.
Get My Site CleanedNo surprises midway. You always know what stage the work is in.
We take a backup of the infected site as it is, for evidence and safety, then scan files, database and logs to see the full extent of the damage.
We decide whether to clean in place or rebuild from a known clean backup, and explain the choice. Sometimes a clean restore plus updates is faster.
Site is put into maintenance mode if needed, so visitors stop getting redirected while we work. Admin passwords are reset immediately.
Malicious code, backdoors and spam pages are removed, the entry point is closed, and the site is hardened and scanned again until it comes back clean.
Blacklist reviews are requested, Search Console is cleaned up, and you get the written report. We keep scanning for the following weeks in case anything returns.
Straight answers to what clients ask us in the first meeting.
All FAQsCommon signs are visitors being redirected to spam sites, often only on mobile or only when coming from Google, a red warning in Chrome, strange Japanese or pharma pages in your Google results, your host suspending the account, or new admin users you didn't create. Sometimes the site looks perfectly normal to you while showing spam to everyone else.
Many hacks hide from the site owner on purpose. They only redirect visitors on mobile, or those arriving from a Google search, or anyone who isn't logged in. So the owner opens the site directly on a laptop and sees nothing wrong. We test from several devices and conditions to see what visitors see.
After cleanup, we request a review through Search Console. Google decides the timing, but reviews usually complete within a few days. Spam pages from a Japanese keyword hack take longer to drop out of search results, sometimes a few weeks, because Google has to recrawl them.
We try hard not to. Our first step is a full backup of the site as it is. Where we can clean in place, your content and recent orders stay. If we have to restore an older clean backup, we bring across newer content and orders from the infected copy carefully.
Usually, honestly, no. Most attacks are automated, run by bots scanning thousands of sites for one known weakness. What we can tell you is how they got in, which plugin, password or file was the weak point, and what has been done so it doesn't happen the same way again.
Keep WordPress and plugins updated, remove anything unused, use strong unique passwords with two-factor login, and keep off-site backups. If nobody on your side has time for that, our managed WordPress hosting or SiteLock security plans cover it.
Send us the link and what you've noticed. We'll take a look straight away.
Prefer email? Write to hello@m9itcs.com