If you are deciding what to do if your business website is hacked, start by limiting potential harm and preserving evidence. Avoid deleting files or reinstalling the site in a rush. Those steps can erase clues about how the compromise happened, making it harder to stop a repeat.
A redirect is not proof by itself that a site was hacked. It may appear only for visitors arriving from search results, on mobile devices, or under certain conditions. Treat the behavior as a signal to investigate, and ask your hosting provider or a qualified technical professional for help.
Start with these response steps
- Record what you observed. Note when the problem appeared, which pages were affected, the URL visitors landed on, and how the redirect was triggered. Save screenshots and, where possible, record the device, browser, and whether the visit came from a search result or direct link.
- Contact your hosting provider. Report the symptoms and ask for help preserving relevant server and access logs. If you have a website maintainer or security professional, bring them in as well. Tell them what you have observed and what actions have already been taken.
- Limit visitor exposure. If visitors are being sent to an unsafe or deceptive destination, work with your host or technical responder to restrict access or display a temporary maintenance page. Choose a response that limits harm without destroying useful evidence. If the behavior is not confirmed, avoid making broad changes before someone checks the site.
- Do not clean up before documenting. Avoid deleting suspicious files, changing server settings, or restoring a backup until the affected state and available logs have been preserved. Keep a record of who made changes and what they changed.
For a structured overview of incident response, see CISA’s incident response playbooks. The details of a business website incident may differ, but a documented, orderly response helps keep actions coordinated.

Check whether the redirect is consistent
Some compromises behave differently depending on how a visitor reaches the site. A redirect might show up for a mobile visitor or someone coming from a search result, while a direct visit from your usual computer looks normal. One normal visit does not rule out a problem.
Record the exact steps that reproduce the issue and share them with your host or technical responder. They can investigate the relevant page, site files, server activity, and third-party components. Avoid repeatedly sending staff or customers to a suspicious destination just to test it.
Unexpected page changes and redirects are among the kinds of issues addressed in Google’s guidance on hacked content. That guidance can help you understand why a compromised site may affect what visitors see or what appears in search.
Preserve the information that can help explain what happened
Useful evidence may include screenshots, affected URLs, timestamps, host and website access logs, alerts from your hosting or security tools, and a record of recent site changes. Save copies in a location that has not been affected by the website problem. Ask your host how to retain logs before they are rotated or overwritten.
Do not assume a suspicious file is the only issue. The entry point could involve a compromised administrator account, an outdated site component, server access, or a third-party script. A responder should review the site and its environment before deciding what to remove.
If your business uses Linux servers, regular event review can support ongoing upkeep. The Linux server monitoring checklist covers events that can be useful to keep an eye on as part of that work.
Restore the site without bringing the same problem back
A backup is useful only if it is known to be clean and the access path has been addressed. Restoring a backup while a compromised account or vulnerable component remains in place may allow the same issue to return.
Before restoring, have your technical responder identify the likely entry point and check the affected site and server accounts. Choose a backup that predates the compromise and can be verified. Where practical, examine the restoration away from the public site before putting it live. If no clean backup is available, ask a qualified professional to determine the safest recovery approach.
After the site is cleaned or restored:
- Update the website platform, themes, plugins, server software, and other components that are part of the site.
- Remove unrecognized administrator accounts and review legitimate accounts for unauthorized changes.
- Change passwords for affected website, hosting, domain registrar, database, and server access accounts. Use a trusted device, and enable multifactor authentication where available.
- Review DNS settings and any outside scripts or services connected to the site.
- Monitor site files, access logs, and visitor behavior for renewed changes or redirects.
Do not treat a site that loads correctly once as fully recovered. Ask your responder to check that the suspicious behavior has stopped across the affected pages and conditions, then continue monitoring for signs of recurrence.
Handle possible exposure of personal information separately
A website compromise does not automatically mean personal information was exposed. But if customer, employee, or other personal information may have been accessed, involve security and legal professionals promptly. They can help determine what information was involved and assess applicable notification duties, including any sector-specific requirements. Florida’s statute on security of confidential personal information is available in the Florida Statutes. This is a situation-specific assessment, not a decision to make from the redirect alone.
Frequently asked questions
Should I take a hacked website offline?
If visitors are being sent to a harmful destination, limiting public access may reduce exposure. Coordinate with your host or technical responder so the action fits the situation and does not destroy useful evidence. A temporary maintenance page may be an option.
What should I save before cleaning up a hacked website?
Save screenshots, affected URLs, the time and steps associated with the behavior, relevant host and access logs, and a record of changes made. Ask your hosting provider how to preserve logs and copies of the affected site.
Why does my website redirect only some visitors?
A redirect may depend on how a visitor arrives, the device or browser, or a third-party component. It can also be a sign of compromise. Record the conditions and have the site checked rather than assuming the cause from one test.
Do I need to notify customers if personal information may have been exposed?
Get prompt advice from legal and security professionals. They can assess what information may have been accessed and whether notification duties apply to your situation.
Recover carefully, then close the gap
The practical sequence is straightforward: document the symptoms, limit visitor exposure where appropriate, preserve evidence, investigate the entry point, and restore only after the site and its accounts have been checked. Keep monitoring after recovery so you can catch a returning problem early.
For ongoing website management and security or Linux managed services in Jacksonville, you can contact Zevonix to discuss your needs.