If your business website appears to have been hacked, record the symptoms, contact the responsible technical support team and contain the immediate risk before attempting a broad rebuild. Preserve useful evidence and agree a recovery plan.
Unexpected redirects, unfamiliar administrator accounts or altered pages deserve investigation. A broken layout alone does not prove a compromise, so describe what you observed rather than guessing the cause.
Record what happened
Note the affected URLs, when the problem was first seen, screenshots and any provider alerts. Record recent legitimate changes too, because they may help distinguish an update problem from an intrusion.
Preserve relevant logs and a controlled copy of the affected environment where appropriate. Do not publish suspicious files, credentials or customer details in a public support thread.
WordPress recommends identifying the symptoms and taking a practical approach to recovery in its guidance for compromised sites: https://wordpress.org/documentation/article/faq-my-site-was-hacked/.
Assign one recovery owner
Choose who coordinates the host, developer, security specialist and business team. Several people making unrecorded changes can destroy evidence or create new problems.
| Workstream | What to establish | Responsible role |
|---|---|---|
| Containment | Which affected services need restricting? | Host or qualified technical owner |
| Evidence | What records need preserving? | Recovery lead |
| Access | Which accounts or credentials may be affected? | Authorised account owners |
| Recovery | Which clean source or backup can be trusted? | Technical recovery team |
| Business communication | What do staff or customers need to know? | Authorised business lead |
Contain the problem without hiding the evidence
The appropriate action depends on the incident. A host may isolate the affected site, restrict access or provide a temporary information page. A store or portal may need to pause transactions while its integrity is assessed.
Do not encourage visitors to bypass browser security warnings to use the site. Give staff a trusted alternative contact route and a clear description of which services are available.
If several sites share an account, ask whether the investigation should cover the wider environment. Cleaning only the most visible page may leave the source of the problem untouched.
Review access through the proper account owners
Investigate unfamiliar users, tokens, integrations and access methods. Confirm legitimate use before removing something the business depends on. Where credentials may be compromised, coordinate their replacement and the invalidation of old sessions.
This may involve more than WordPress. Hosting, domain, email and other connected services can be relevant. Use trusted devices and the providers’ normal recovery processes.
Resetting one password does not establish that the website is clean. Access review should support the broader investigation and recovery work.
Recover from a source you can assess
A backup can help, but its date alone does not prove it is clean. The team should assess the suspected compromise period and any changes that must be preserved before choosing a restore point.
Use trusted software sources and address the identified cause where it can be established. Restoring a vulnerable setup without correcting the underlying issue can leave the website exposed again.
Record what was replaced, updated, removed or retained. If the cause remains uncertain, say so and define the additional investigation or monitoring required.
A hypothetical recovery mistake
Imagine a company removes a visible spam page and sees its homepage return to normal. An unauthorised administrator remains active, and the spam later reappears.
The lesson is to assess the system and access paths, rather than use appearance as the only completion test. This is an illustrative scenario, not a description of a named client’s incident.
My website technical support can begin with an assessment of the problem and the specialist support needed. The scope should reflect the incident, rather than promise a universal one-click cleanup.
Check business functions before resuming normal use
- Review important public pages and redirects.
- Check administrator and integration access.
- Test forms and notification delivery.
- Verify payment and order handling where applicable.
- Check for missing or changed business records.
- Confirm backups and recovery procedures.
Keep a record of the tests and unresolved issues. A clear handover helps the business understand what was checked and what remains uncertain.
Assess communication and privacy implications
If personal information may have been affected, involve the organisation’s responsible privacy and legal advisers promptly. Technical recovery and any notification obligations are separate matters; do not assume that fixing the site resolves both.
Communicate confirmed facts, the services affected and practical next steps. Avoid unsupported claims that no data was accessed or that the website is permanently secure.
Frequently asked questions
Should I delete everything immediately?
Agree containment and evidence preservation first. Destructive changes can make investigation and recovery harder.
Will a security plugin guarantee recovery?
No. Tools can assist, but the incident still needs an appropriate assessment, recovery process and verification.
When should we consider rebuilding?
When the existing environment cannot be trusted or maintained economically, a rebuild may be appropriate. Scope it from evidence and include content, account and integration recovery.
For a broader rebuild, see my website development service.
Discuss your next step
For help applying this to your organisation, share a short description of your situation and the decision you need to make.





