WordPress & WooCommerce support

Security, hack
and bots support

A hacked website, blocked login or flood of unwanted traffic can bring your business to a standstill. Get practical help to understand what is happening, address the cause and strengthen your website.

Investigate the cause. Address the problem.
Put better protection in place.

Hacked website investigationsCloudflare & bot trafficWordfence & firewall supportWordPress & WooCommerce

How I can help

Clear answers. Practical support.

Start with the symptoms and the evidence. Support can cover your WordPress installation, plugins, hosting settings and traffic protection, with changes tailored to how your website actually works.

Hacked websites & malware

Investigate suspicious files, unexpected administrator accounts, injected code and unwanted redirects. Review affected components and plan a clean-up or recovery from a suitable backup.

Bot traffic & repeated attacks

Review repeated login attempts, automated scans and unusual request patterns. Tune traffic rules to reduce unwanted activity while considering customers, search engines and legitimate services.

Cloudflare configuration

Review firewall rules and traffic challenges, check how visitor IP addresses reach your server, and investigate requests that may be reaching the hosting directly.

Blocked logins & admin errors

Trace access-denied messages, login loops and editing failures across WordPress, plugins and hosting logs. Establish whether the cause is malicious activity, a configuration issue or a software conflict.

Wordfence & hosting firewalls

Investigate scan alerts, firewall conflicts and legitimate requests being blocked. Review relevant Plesk and ModSecurity logs to identify where a targeted adjustment may be needed.

Protection after an incident

Review users, credentials, software updates and backup arrangements. Identify outdated or unnecessary components and agree sensible follow-up checks for your website.

Examples from support work

Problems that need a closer look.

These anonymised examples reflect issues investigated during website support. They show why the symptoms alone rarely tell the whole story.

Access after a hack

The correct password still fails

In one investigation, a password checked correctly at PHP level, but WordPress still rejected it. A malicious plugin was found interfering with password verification.

The focus: investigate the authentication process and remaining malicious components, rather than repeatedly resetting the password.

Unwanted traffic

A quiet website with busy server logs

A low-traffic site showed CPU spikes alongside repeated requests for missing files and sensitive paths. Automated scanning was an important part of the investigation.

The focus: inspect request patterns and resource usage before choosing targeted traffic controls.

Blocked administration

Admin access remains denied

After a hack, a malicious access rule targeting a WordPress update file was corrected, but the admin restriction remained. Server logs still showed an active access denial.

The focus: trace the remaining restriction through file-level and hosting rules, rather than assuming a browser cache issue.

Client details are omitted. These are diagnostic examples, not promises of a particular recovery outcome.

A straightforward approach

From the first symptom to the next steps.

01 / Understand

Establish what changed

Review the symptoms, timing, recent updates and available access. Agree the scope before work starts.

02 / Investigate

Follow the evidence

Check relevant logs, files, accounts and settings. Preserve useful evidence and establish the backup position.

03 / Address

Make targeted changes

Carry out the agreed clean-up, recovery or configuration work, then check the affected website functions.

04 / Review

Plan the follow-up

Explain what was found, what changed and any remaining limitations, with recommendations for ongoing care.

Common questions

A little clarity
before we start.

Does unusual traffic mean my website has been hacked?

Not necessarily. Scans and failed login attempts can occur without a successful intrusion. The investigation looks for evidence of unauthorised access or changes as well as the traffic itself.

Can you help if I cannot access WordPress?

Yes, an investigation may be possible through your hosting control panel and server logs. What can be done depends on the access available and the cause of the problem.

Can security settings break a form, checkout or editor?

They can sometimes block a legitimate request. The aim is to identify the request and the rule involved, then make a specific adjustment and check the affected function.

Will installing a security plugin resolve a hack?

A plugin can help identify issues and provide protection, but an existing compromise may also involve altered files, accounts, access rules or other components. The scope of the problem needs to be established.

Can you guarantee that a site will never be hacked again?

No. Security work reduces risk but cannot eliminate it. Updates, suitable access controls, backups and ongoing attention all have a part to play.

How much will the work cost?

The cost depends on the symptoms, the access available and the scope of the investigation or recovery. Get in touch with your website address and a description of the problem so the next steps can be agreed.

Tell me what is happening

Let’s get to the root of it.

Whether your site has been compromised or something simply does not look right, start with a short description of the issue.

Ask about security support ↗

Useful information to include

  • Your website address and the symptoms.
  • When the problem started and any recent changes.
  • Whether WordPress and hosting access still work.
  • Any error messages or relevant screenshots.

Please do not include passwords in your initial enquiry. Access arrangements can be agreed separately.