Skip to main content

What to Do When a Website Is Hacked: First Steps

November 20, 2026 5 min read
Closed laptop beside a network router and blank notepad on a desk

If you are searching for what to do when a website is hacked, start by treating unexpected redirects or unfamiliar content as a possible compromise. A strange page may have another explanation, but continuing to send visitors to a potentially unsafe site can put customers and your business at risk. Contain the issue, preserve what you can, and investigate before attempting a cleanup.

This checklist is designed for business owners and the people responsible for a company website. The precise steps depend on your hosting setup, website platform, and what the site does, so involve your IT or security support early.

First steps: contain the problem and preserve evidence

  1. Stop directing people to affected pages. Pause campaigns, social posts, or other promotions that link to the site. If you can safely disable only the affected feature or page, that may reduce disruption. If visitors may be exposed to harmful content or the redirect cannot be contained, taking the site offline temporarily may be the safer choice. Coordinate with your hosting provider or security support rather than making a rushed change that could complicate investigation.
  2. Contact your hosting provider and incident lead. Tell them what visitors are seeing, when you first noticed it, which pages seem affected, and what changes occurred shortly beforehand. Ask them to preserve relevant logs and help assess whether the issue could involve the hosting account, other sites, or shared systems. If your organization has an IT or security contact, bring them in promptly.
  3. Record what you observed. Note the time, affected URLs, devices or browsers where the problem appeared, and how you reached the page. Save screenshots or screen recordings when safe, and keep copies of relevant alerts and messages. Avoid editing or deleting suspicious files before your support team has had a chance to preserve useful evidence. Incident response guidance from NIST emphasizes organizing response activities and keeping information useful for investigation.
  4. Consider whether sensitive information could be involved. If the site collects or connects to customer, patient, student, financial, or other sensitive information, notify the appropriate leaders and involve your privacy or legal advisers. Do not assume that suspicious content proves information was exposed, but do not dismiss the possibility without checking.
Abstract connected blocks arranged to suggest a website recovery process

Check whether the suspicious behavior is repeatable

A site that looks normal when you check it once may still behave differently for other visitors. Redirects or injected content can depend on the page, device, browser, or how someone arrived at the site. Ask your support team to test the affected pages and common visitor paths, including mobile devices and links from search results or campaigns. Do not repeatedly expose staff or customers to a page you suspect is unsafe just to reproduce the problem.

Unfamiliar pages, altered links, unexpected pop-ups, browser warnings, and sudden changes to search listings are all reasons to investigate. They are clues, not proof on their own. Your hosting provider, website administrator, or security team can help determine whether the behavior comes from the site, a third-party component, an account issue, or another cause.

Secure access without destroying the investigation

Once your support team is ready, change relevant passwords from a device you believe is secure. This may include website administration, hosting, domain management, content management, and associated email accounts. Review who has access, remove accounts that are no longer needed, and use multifactor authentication where available. Ask your provider to guide the order of changes so an attacker cannot simply regain access through another account.

Do not treat a password change as a complete cleanup. The cause could be an outdated component, a compromised account, exposed credentials, or another weakness. Your technical team should investigate how access was gained, what was changed, and whether related systems or accounts need attention. WordPress users can consult the platform’s guidance for responding to a hacked site; the specific recovery process will depend on your website and hosting environment.

Restore only after addressing the cause

A backup can help recover a website, but restoring one is not the same as proving the site is safe. Work with your technical support to identify a backup from before the suspected compromise, confirm it is suitable, and check whether it includes the affected files, database, or configuration. Before restoring, investigate the entry point and address the weakness that may have allowed the problem. Otherwise, the same issue could return.

For more on preparing for recovery, see this guide to business backup and recovery. A broader business continuity plan can also help teams decide how to maintain essential operations while a website or related service is unavailable.

Verify the site before relaunching

Before sending visitors back, have your support team confirm that the weakness has been fixed, relevant software and components have been reviewed and updated, and access has been secured. Test important pages and functions, not just the homepage. Check for redirects and suspicious content across different devices and visitor paths, including links from search or other referral sources. Monitor the site after it returns so a recurring problem is spotted quickly.

If a search platform flags the site or shows a security warning, review its security information and follow the remediation steps it provides. Google’s Security issues report can help site owners review reported security problems. A cleaned page or successful restore does not automatically mean every warning or affected search result has cleared, so check the relevant platform guidance after the technical work is complete.

Frequently asked questions

Should I take my website offline if it may be compromised?

It depends on the risk to visitors and your ability to contain the affected pages or features. If visitors may be sent to unsafe content and you cannot limit the exposure, temporarily taking the site offline may be appropriate. Coordinate the decision with your hosting provider or IT/security support.

Should I change website passwords after a suspected hack?

Yes, relevant credentials should be changed from a device you believe is secure. Include related accounts such as hosting, domain management, and email when appropriate, and ask your support team to help sequence the changes and review access.

Who should I contact if my business website has been compromised?

Contact your hosting provider and the person or team responsible for IT or website security. If sensitive information may be involved, also alert appropriate organizational leaders and involve your privacy or legal advisers.

Take the next step

Responding well means limiting visitor risk, preserving useful evidence, securing access, and verifying the fix before relaunching. Zevonix provides website management and security for businesses across Flagler County. If you need help assessing a website issue, call (386) 260-0777.

Ready to Strengthen Your IT?

Let Zevonix handle your technology so you can focus on what matters most — your business.

Schedule a Free IT Assessment