Is it a hack, or something else?

Not every broken or odd-looking site has been hacked. Match what you see to the likely cause before you act.

What you seeLikely causeFirst check
Site won't load at all, or shows a host errorUsually an outage, an expired domain or a server problemOur website down checklist
Junk messages arriving through your contact formForm spam, not a hackSee contact form spam protection
Search results show pages you never wrote, often in another language or selling unrelated productsHacked content added to your siteSearch Console's Security issues report
Visitors, especially from Google or on mobile, land on a different siteInjected redirectTest from several devices and networks
Browser or search result says the site may be harmfulGoogle or another service has flagged malware, phishing or hacked contentSearch Console and Google's site status tool
Admin users, plugins or files you didn't addSomeone has access they shouldn'tYour host and whoever built the site

WordPress's own hacked-site FAQ lists similar warning signs, including a host disabling the site, a site flagged for distributing malware and new users you didn't authorise.

The first hour: contain it and keep a record

  1. Write down what you see. Note the page addresses, screenshots, the time you noticed and anything that changed recently, such as a new plugin, theme or person with access. The WordPress FAQ calls this the first step, because whoever cleans the site will need it.
  2. Use a device you trust. The same FAQ warns that some attacks start on the owner's own computer, where stolen logins are captured. Run a malware scan on the computers you use for the site before you type passwords on them again.
  3. Tell your host and your web developer. On shared hosting the problem may reach beyond your site, and your host may be able to tell a hack from an outage.
  4. Take the site offline if it is harming visitors. If it is redirecting people to scams or serving downloads, a maintenance page is better than leaving it up.
  5. Change every password, from the trusted device. That means hosting panel, website admin, FTP or SFTP, database and, separately, your domain registrar and the email account those logins reset to. Turn on two-factor sign-in where offered, and remove users you don't recognise. Our guide to domain ownership and registrar access explains why the registrar matters.
  6. Copy the current site before anyone cleans it. Label it as compromised and keep it apart from normal backups; it helps show how the attacker got in.

Check what Google and your visitors see

"It looks fine to me" isn't proof. Google notes that attackers may hide spam with cloaking, showing it only to certain visitors or search engines, and that its warnings depend on browsing context, so you may not be able to reproduce them yourself.

  • Search Console's Security issues report is the place Google says to rely on. It covers hacked content, malware and unwanted software, and social engineering (deceptive pages), and lists sample affected pages. Google says that sample isn't necessarily complete. If you don't have Search Console yet, our Search Console setup guide walks through it.
  • Google's Safe Browsing site status page lets anyone check whether Google currently considers a site dangerous to visit. Google notes that many of the unsafe sites it finds are legitimate websites that have been compromised.
  • Search site:yourbusiness.com and scroll through the results for pages you don't recognise.

Restore, repair or rebuild?

OptionWhen it fitsWatch out for
Restore a clean backupYou have a backup from before the break-in and know roughly when it startedRestoring the same weakness; losing changes made since
Repair in placeNo clean backup, or the damage is limited and well understoodMissing a hidden backdoor; this needs someone experienced
Rebuild on fresh hostingRepeated hacks, an old unmaintained site, or nobody can say what was changedTakes longer; content, redirects and forms must be moved carefully

Whichever you choose, close the way in. WordPress's hardening guide stresses keeping WordPress up to date, noting that older versions don't receive security updates; apply the same habit to themes and plugins on any platform. Remove plugins and themes you don't use, and replace anything no longer maintained. Scanners help, but the WordPress FAQ is clear that no single tool is enough; use more than one, and treat a clean scan as a signal, not a guarantee.

Ask Google to review, once

Google's instructions are to fix the issue across the whole site, because fixing only some pages won't earn a partial return, then select Request Review in the Security issues report and describe what you fixed. Google says reviews can take from a few days to a few weeks, and asks you not to resubmit before you get a decision. Its malware and unwanted software overview explains the policy behind those warnings.

If customer details may be involved

A hacked site can expose more than pages. Check what your forms collect and where it goes, and change any API keys or connections between the website and your CRM, email or booking tools. Our guides to vendor access and API keys and customer data in automations cover where those keys usually live. The WordPress FAQ also warns that hacked sites are sometimes used to send spam email, which can harm email that shares the same server. If personal information may have been taken, talk to a lawyer about any duty to notify customers; that depends on where you and they are.

After it's fixed

  • Updates for software, themes and plugins are applied on a schedule, by a named person.
  • Every login is unique, uses two-factor sign-in and belongs to a current person.
  • Backups run automatically, are stored away from the site and have been restored at least once as a test. Our hosting, SSL and backups questions help you ask your host.
  • Search Console sends alerts to an inbox someone reads.
  • Someone checks the site regularly. A website care plan or our website maintenance service can cover this.

What this guide can't do

It can't diagnose your specific site or promise that a cleanup is complete. Some hacks leave hidden access that only a careful review of files, users and logs will find. If the site keeps getting hacked after a cleanup, treat that as a sign the original way in is still open.

Questions

Will my hosting company clean a hacked site for me?

It depends on your plan and your host. Some hosts suspend a site that is sending spam or malware, some offer cleanup as a separate service and some leave it entirely to you. Ask what they found, what they changed and whether other sites on the same account are affected.

Can I just restore last month's backup?

Only if you know the backup is from before the break-in, and only if you also close the hole the attacker used. Otherwise a restore puts back the same weakness, and the site can be changed again within days.

How long does a Google warning stay after I fix the site?

Google says a security review can take from a few days to a few weeks after you request it in Search Console. Fix every affected page first; asking before the fix is complete can slow the next review.

Sources and further reading

Official documentation changes. Check the current version before you rely on a rule, limit or setting.

Next step

See a site built around your real details.

Look at sample layouts (fictional previews, not client work), read published website pricing, or ask for a free concept preview.

Already happy with your site? Website Maintenance covers monitoring, a monthly form test, backups and edits.