What to include in the first message
Tell us what visitors see, when it began and who manages the hosting account. A screenshot of an unexpected redirect or browser warning is helpful. Keep credentials out of the form. Identify any recent backups and preserve the host’s incident notices for the person handling recovery.
When unexpected AI-style articles appear
An unfamiliar article can come from an authorized automation, a publishing mistake or compromised access. Writing style alone cannot tell you which. Record the affected URLs and publication times, then compare them with editorial approvals, scheduled jobs and available activity records.
What recovery looks like for the business
Verify the affected pages, contact forms and customer journeys against a known good version. Review publishing accounts and connected tools before re-enabling automated posts. Where unwanted URLs have appeared in search, track their removal separately from restoring the website.
Why are spam pages still appearing in search after cleanup?
A search result can outlast the compromised page. Check the affected URL directly, confirm the restored site serves the intended response and review Search Console for security issues. Keep a dated list of affected URLs so recurring spam can be distinguished from an old search preview.
Hacked WordPress site repair starts with containment
If your WordPress site is redirecting visitors or showing harmful downloads, ask your hosting provider how to contain the affected site safely while preserving evidence. Keep a private record of times, affected URLs, notices and recent changes. If the host suspended the site, ask what it found and whether other sites in the same hosting account are involved.
Work from a trusted device and contact the business owner who can authorize changes. Preserve a snapshot and available logs before overwriting WordPress files. If payments or customer data may be affected, involve the people responsible for deciding how to handle those risks.
Check the WordPress dashboard and hosting account
Review administrator user accounts in the WordPress dashboard and compare them with the current staff and vendors. Check for new user accounts created after the first sign of the incident. If you cannot reach wp-admin, work through your web host’s verified support channel. Confirm who controls the domain, hosting account and backups.
A WordPress developer or incident responder can review server and publishing logs, look for unapproved plugins or connected tools and check whether access extended beyond the WordPress website. Keep passwords and recovery codes out of your cleanup inquiry.
What a WordPress malware scan can and cannot establish
A malware scan can flag suspicious files, unusual content and known malware signatures. Review those findings alongside the site’s expected software versions, core files, plugins, themes and database. A scanner’s report can miss signs outside the WordPress installation or changes to user accounts.
Ask the person handling malware removal to document which files or records were changed and which evidence supports that conclusion. Before deleting infected files or replacing WordPress core files, confirm that you can restore the site and preserve the copies needed for investigation.
Restore clean WordPress files and verify the database
A known-clean backup can shorten the recovery of a hacked WordPress site, but first check when it was made and what changes the business would lose. An online store may need to preserve orders taken after the backup. Restore a copy separately for validation where practical.
Replace damaged software with trusted copies from the official source or authorized vendor. Review settings, scheduled publishing, plugins and themes before bringing the WordPress website back. Test a payment, contact form or customer login without using live customer credentials or creating unintended transactions.
Secure access before reopening a hacked site
Once the affected environment is under control, coordinate credential changes for any impacted hosting, WordPress and connected services. Remove unauthorized users, revoke sessions and review active keys. Update WordPress, update plugins and themes, and remove abandoned software instead of leaving it installed.
Use unique credentials and multi-factor authentication where available. Give each person permissions for their role. Restoring the site without addressing the security issues that let unwanted changes happen can leave the business exposed to future hacks.
Fix a Google security warning after WordPress cleanup
Open Search Console’s Security Issues report, record the examples it lists and check for related affected URLs. After cleanup and verification, follow Google’s instructions to request review when the report offers that option. Explain the security issue and what was corrected. If a restored page is ready to be indexed again, use Search Console’s URL Inspection guidance after resolving the security issue.
Search engines may continue to show old snippets or hacked pages until they refresh their records. Confirm the actual URL returns the intended content or an appropriate removal response. Track the site cleanup and the search review as separate outcomes.
How long does hacked WordPress cleanup take?
Timing depends on access, the age and quality of backups, the number of affected systems and how much legitimate content must be recovered. Pages on a small site and a store with recent transactions can require different review steps. Ask how the provider will confirm when the site is safe enough to reopen and what follow-up checks are included.
Recovery records should identify what was fixed, who owns the next step and what remains under review. A current backup and tested recovery process are more useful than a promise to clean any hacked website in a few hours.
Review infected files as part of malware removal
After an initial scan, an authorized professional can examine WordPress files in the context of the site’s expected versions. Review WordPress core files, themes, plugins and the directories that hold uploads and custom work, including wp-content and wp-includes where relevant. Where dashboard access is unavailable, authorized staff may use the hosting provider’s secure file manager to review WordPress files. The affected files and database may tell different parts of the same story. If the site keeps redirecting, authorized staff can review hosting settings and routing rules, including the .htaccess file where the server uses it.
Security plugins and scanner reports are inputs to the investigation. Keep a record of which suspected files were confirmed, which were replaced from a verified source and which permissions changed. Ask the WordPress developer how they validated custom plugins and themes before the site went back online.
When to use professional services for a hacked WordPress site
Contact the host or a qualified WordPress developer if the WordPress dashboard is unavailable, malware appears to affect multiple sites or a payment or login flow changed. Confirm what each professional service covers. A one-time cleanup might address infected files and the WordPress database. An access review can also address connected services and unauthorized administrator accounts.
Ask who will preserve evidence, which parts of the hosting account they need to review and how they will hand access back. Request a written report with the findings, actions taken and the latest verification. Ask whether an old WordPress install shares the hosting account and can be updated or retired. Define follow-up for issues the first cleanup cannot resolve, including what happens if the same cause leads to another incident.
Prevent future hacks after a one-time cleanup
Set a schedule to update WordPress, plugins and themes. Keep supported software on the latest version appropriate for the site, and test updates against business-critical pages before rollout where practical. Remove unused plugins and accounts. Test restoring a copy of the WordPress site from backups kept separately from administrator logins.
Check that the domain, host and WordPress dashboard each have an owner and a fallback contact. Agree who reviews security issues after a host alert, who can authorize taking the site offline and how you will verify critical pages are working. Review those decisions after a staff or vendor change.
How to tell if your WordPress site is hacked
Check what triggered the concern. A notice from the hosting account, a search engine warning, a redirect reported by a customer and an unexpected new administrator each call for a different check. Record the page, time and observed behavior. Do not ask customers to visit a site you suspect serves malicious code.
Give the WordPress developer the symptom list and any relevant change history. The goal is to establish what was affected before making changes. If a change was authorized and the site is healthy, document what caused the warning. If the site is hacked, preserve the evidence and agree which affected components to isolate.
Can security plugins clean hacked websites on their own?
Security plugins can help identify suspect WordPress files and show unfamiliar changes. Their visibility depends on where they run and what the hosting account lets them inspect. A clean malware scan does not establish that the WordPress site, another site on the host, or all of its connected accounts are clean.
Use the scan alongside host logs, a review of the WordPress dashboard and checks against the site’s expected files. After malware removal, confirm the visible page and check that the symptom stays resolved. Decide who will review renewals and software changes to reduce the risk of future hacks.
Start with ownership
Identify who can authorize access and decisions. Record what has changed and what support is already involved.
Agree on recovery checks
Decide who will verify that essential site functions work and who will monitor after recovery.
Official recovery resources
WordPress recovery guidance · Google Search Console security review
What to bring to the first conversation
Note when the unexpected behavior began, what visitors see and whether any recent changes were planned. Share a description through the contact form and keep passwords out of it. After recovery, WordPress security covers ongoing maintenance responsibilities.