Signs Your Website Has Been Hacked: What to Check
Your website suddenly sends visitors somewhere else, a customer reports a security warning, or you find a page you never created. These can be signs your website has been hacked. However, a broken page, failed login or slow website can also have a much simpler explanation.
The sensible approach is to look for evidence, record what you find and get the right help. You don’t need to understand computer code to notice a problem. You do need to know which checks are useful, which symptoms deserve urgent attention and why a normal-looking homepage doesn’t tell the whole story.
Quick Answer
Your website may have been hacked if it contains unauthorised pages, redirects visitors to unfamiliar websites, shows malware warnings or has administrator accounts you don’t recognise. Unexpected changes to payment details, contact information or login settings also need prompt investigation. A slow website or failed contact form alone does not prove a hack. Check your security alerts, Google Search Console and website accounts, then ask your hosting provider to investigate suspicious activity. A clean scan cannot guarantee that everything is safe. If visitors or customer information could be at risk, arrange containment and a proper security review before continuing normal use.
The Main Signs Your Website Has Been Hacked
The strongest warning signs involve changes that nobody authorised or credible alerts about harmful activity. One clue may be enough to justify an investigation, especially if customers are being redirected or payment information has changed. Check with anyone who legitimately manages your website before deciding that an unfamiliar change is malicious.
Visitors are sent to an unfamiliar website
A customer clicks your business website and ends up on a gambling page, a fake prize offer or an unrelated sales page. An unexplained redirect like this deserves urgent attention. For example, if someone trying to book a cleaning service is taken to another website, stop treating it as a routine display problem and contact your provider.
You find pages, adverts or links you didn’t add
Unexpected product pages, strange text or unrelated links can indicate that somebody has changed your content. Sometimes these additions appear in Google results while your main pages still look familiar. A plumber’s website showing pages about unrelated medicines or products would be a clear reason to investigate.
Your browser or security software displays a warning
A warning about malware or a deceptive website should be taken seriously. Malware means harmful software or code, while a deceptive page may try to trick visitors into giving away information. Don’t bypass the warning to continue testing the site, and don’t ask customers to ignore it.
There are unfamiliar administrator accounts
An administrator account gives someone substantial control over your website. If you find one that neither you nor your provider recognises, record its details and ask for an immediate review. Unexpected changes to existing account permissions, recovery email addresses or security settings also need checking.
Your hosting provider reports harmful activity
Your host may contact you about suspicious files, outgoing spam or activity affecting other websites. It may also suspend the site while investigating. Confirm the message through your normal hosting account or a known support number, since a convincing security email can itself be a scam.
Business details have changed without permission
Check your contact email, telephone number, booking links and payment destinations. An unauthorised change could send enquiries or money away from your business. If a checkout or payment link looks wrong, pause the affected process and involve your payment provider as well as your website provider.
Problems That Don’t Automatically Mean a Hack
Many ordinary website faults look worrying at first. An update can break a layout, a hosting outage can take a site offline, and an email problem can stop contact form messages arriving. These issues still matter, but they need a diagnosis rather than an immediate assumption that an attacker is involved.
| What you notice | Another possible explanation | What to check first |
|---|---|---|
| Your website is slow | Large images, heavy traffic or limited hosting resources | Hosting status and recent website changes |
| You cannot log in | A wrong password, account lockout or changed login address | Your provider’s records and account recovery options |
| Your contact form stops sending emails | Email delivery settings or a form fault | Form submissions, mail settings and delivery logs |
| You see a connection privacy warning | An expired or incorrectly configured security certificate | The exact warning and certificate status |
| Your website goes offline | A hosting outage, expired domain or billing problem | Hosting service status and domain renewal |
Contact form spam also does not, by itself, prove that someone has accessed your website. Bots can submit rubbish through a public form without breaking into the site. Likewise, failed login attempts show that someone tried to get in, rather than proving they succeeded.
How to Check Without Making Things Worse
1. Record the exact problem
Write down what happened, the affected page address and the time you noticed it. Save screenshots of warnings or unfamiliar content where you can do so safely. Note any recent updates or authorised changes, since that helps your provider compare a possible security incident with an ordinary fault.
2. Check Google Search Console
If your business has Google Search Console set up, review the Security Issues area and any recent messages. Google’s alerts can help identify problems it has detected. The absence of an alert is not a complete security check, so use this alongside other evidence.
3. Look for unexpected search results
You can search Google using site:yourdomain.co.uk, replacing the example with your own domain. Look for unrelated titles or page addresses without opening suspicious results. This search only shows some indexed content, so it cannot reveal every page or confirm that your whole website is clean.
4. Review accounts and recent changes
If you can safely access the dashboard from a trusted device, check the user list and recently added content. Ask your provider about unfamiliar plugins, settings or account activity. Avoid deleting things at random, because you could remove evidence or break a legitimate part of the website.
5. Ask for a scan and hosting review
A security scan can identify some suspicious content or files, but different scans inspect different parts of a website. Ask your host or security specialist to check the server, website files and stored data as appropriate. Tell them about every symptom, including changes that only a customer has reported.
The official WordPress hacked-site guidance explains why recording symptoms, involving your host and using different checks can help. A public scan has a limited view of your website. Treat its result as evidence to consider, rather than a final guarantee.
Can a Hacked Website Still Look Normal?
Yes, a familiar homepage does not prove that the website is safe. Harmful changes may affect a different page, an account or something that happens behind the scenes. Checking only your homepage can therefore miss a problem that matters to your customers.
Customer reports are useful for this reason. If someone describes behaviour you cannot reproduce, ask which page they used, what device they were on and when it happened. Pass those details to your provider rather than dismissing the report because everything looks fine on your own screen.
What to Do If You Find Suspicious Activity
Contact your hosting provider and the person responsible for your website security promptly. Explain what you have observed and ask whether visitors are currently at risk. If the website appears to be serving harmful content or collecting information through an altered process, arrange to restrict access or pause that process while it is investigated.
Ask your provider to preserve relevant logs and a copy of the affected website before cleanup, where practical. An infected copy should be kept securely for investigation, not used as a recovery backup. This can help establish what changed and avoid losing information needed to understand the incident.
Secure affected accounts from a trusted device, including the email account used for password recovery. Have your provider review active sessions and other access methods as well as passwords. Simply changing one website password may leave another route into the account or hosting service available.
Recovery needs to address both the unwanted changes and the weakness that allowed them. Restoring a backup may help, but the backup must be checked and the cause investigated. Otherwise, an old infection or unresolved security gap could put the restored site at risk again.
Before normal use resumes, ask for checks on the main customer journeys: contact forms, bookings, checkout and account access. Where Google has flagged the site, follow its guidance on fixing security issues and requesting a review. Removing the warning is a separate step from repairing your website.
Warning: Check Whether Customer Information Is Affected
A website security incident may also involve personal information, such as enquiry details, customer accounts or booking records. Ask what information was stored and whether it may have been accessed, altered, lost or disclosed without permission. A changed homepage alone does not answer that question.
Under UK data protection rules, a reportable personal data breach must be notified to the ICO without undue delay and within 72 hours of becoming aware of it. Reporting is required unless the breach is unlikely to result in a risk to people’s rights and freedoms. If it is likely to create a high risk, affected people must also be informed without undue delay. Use the ICO’s personal data breach guidance, record your assessment and seek advice promptly if the position is unclear.
Expert Insight From Daren Ward
Daren Ward – Founder, A to Z Website Solutions
I would recommend keeping a simple record of who looks after each part of your website. That includes hosting, domain registration, updates, backups and your business email. When something goes wrong, knowing who can investigate and who has access helps you make a clear decision about the next step.
From a business point of view, I would also check how customers can reach you if the website needs to be restricted. A working telephone number or separate booking channel can help you keep serving people during recovery. Keep any public explanation accurate, and avoid telling customers the site is safe before that has been checked.
How to Reduce the Chance of Another Incident
Once the website has been checked and recovered, review its ongoing care. Keep supported software updated, remove unused components and give each person only the access they need. Use unique passwords and enable multi-factor authentication where available, which adds another check when someone logs in.
Backups should cover the files and stored website data, with copies kept somewhere an attacker cannot easily change. Keep more than one recovery point and check that restoration works. The WordPress security handbook explains why updates, access controls and a sound backup plan belong together.
Make responsibility clear rather than assuming somebody is handling security. Ask who reviews alerts, who applies updates and what happens when a warning arrives outside normal hours. These questions help you understand the support you have and identify gaps before another incident.
Action Checklist
- Record the suspicious behaviour, page address and discovery time.
- Confirm whether anyone authorised the unexpected change.
- Review Search Console messages and known security alerts.
- Check unfamiliar accounts and changed business details with your provider.
- Ask your host to investigate and preserve relevant evidence.
- Arrange containment if visitors or customer information may be at risk.
- Assess whether personal information is affected and reporting is required.
- Confirm recovery checks and agree who will monitor the website afterwards.
Frequently Asked Questions
Does HTTPS mean my website cannot be hacked?
No. HTTPS protects the connection between a visitor and your website, but it does not prove that the website itself is free from harmful changes. Keep it enabled, while also maintaining accounts, software and backups.
Can a small business website be a target?
Yes. A website does not need to belong to a large company to have accounts, content or resources that someone could misuse. Base your precautions on what your website does and the information it handles.
Is every security alert genuine?
No, and even genuine tools can require further investigation. Check alerts through a service you already use rather than following an unexpected email link. Never give someone your password simply because they claim to have found a problem.
Should I install several security plugins?
More plugins do not automatically provide better protection. Ask your provider which tools are appropriate and who will monitor them. Overlapping tools can complicate maintenance without resolving the cause of an incident.
Does a clean malware scan mean I am safe?
No scan can provide a complete guarantee. Ask what it examined and whether suspicious accounts, stored data and server activity also need checking. An unexplained symptom still deserves investigation after a clean result.
Will restoring yesterday’s backup solve the problem?
Only if that backup is suitable and the underlying security issue is addressed. The intrusion may have happened before yesterday, even if you only noticed it today. Check the recovery point before using it.
Will I need a completely new website?
Not necessarily. The right recovery approach depends on the damage, available clean copies and confidence that the site can be secured. Ask for a clear explanation before agreeing to a rebuild.
Do I need to tell every customer immediately?
The answer depends on what happened and the risks involved. Personal data breach rules have specific notification thresholds, while customers may also need practical information about interrupted bookings or payments. Get the facts checked and communicate accurately.
Summary
Unauthorised changes, unfamiliar accounts, harmful redirects and credible security warnings deserve prompt investigation. Ordinary faults can have other causes, so useful evidence matters more than guessing. Record what happened, involve your provider and check the effect on customers as well as the appearance of the website.
A proper recovery should explain what was affected, how access was secured and what was checked before reopening. It should also leave you with clear responsibilities for updates, backups and alerts. That gives your business a more dependable plan for dealing with future problems.
Need Help With Ongoing Website Care?
If you would like support with routine updates, security and stability, you can explore our WordPress maintenance service. For an active suspected hack, contact your host promptly and confirm what incident investigation and recovery support is available.
Key Takeaways
- A normal-looking homepage does not prove the whole website is safe.
- Unauthorised changes need more attention than a general performance fault.
- Security scans and Google alerts provide clues, not complete guarantees.
- Preserve useful evidence and involve your hosting provider promptly.
- Recovery must address the cause as well as the visible damage.
- Check customer information and any data breach reporting duties.