Short answer

If your website is hacked, back up the infected site, change every password (hosting, admin, domain, email) and put the site into maintenance mode. Then clean the files and fix the hole the attacker used. Only then ask Google for a review: Google says spam-hack reviews can take up to several weeks.

How do you know your website has been hacked?

The common signs owners report to us:

  • Google results for your site show Japanese or pharma spam titles you never wrote.

  • Visitors on mobile get redirected to a betting or "you won a prize" page.

  • Chrome shows a red warning before your site opens.

  • Search Console sends a "Security issues" email.

  • Your hosting company suspends the account for sending spam.

  • New admin users appear in WordPress that nobody created.

Google's Security Issues report groups these into hacked content (pages or code added without permission), malware, and social engineering such as fake login pages. Affected pages can carry a warning label in search results or a full-page browser warning (Google Search Console Help).

The outside problem is a broken site and lost enquiries. The inside problem is the panic of not knowing who to call or whether your customers' data is gone. A clear order of steps fixes most of that.

What should you do in the first hour?

Speed matters, but the order matters more.

1. Take a full backup of the hacked site. Files and database, as they are. You will need it to see what changed and to recover content.

2. Change passwords from a clean device. Hosting and cPanel, website admin, database, FTP, domain registrar, and the email account linked to them. Turn on two-factor login where offered.

3. Remove unknown admin users. In WordPress, check Users for any admin you do not recognise.

4. Put the site into maintenance mode or take it offline. This stops visitors and Google from seeing spam while you clean.

5. Tell your hosting provider. Many hosts can show access logs and restore from their own backups.

6. Write down what you saw and when. Screenshots, times, the first warning email. You may need this later.

Do not delete files blindly or reinstall over the top. That often removes the evidence of how the attacker got in, and the same hole gets used again next week.

How do you clean a hacked website?

Step

What it means

Who usually

does it

Find the entry point

Outdated plugin, weak password, old PHP version,

leaked FTP login

Developer

Compare against a clean

copy

Check core files and themes against fresh downloads

Developer

Remove injected code

and pages

Hidden scripts, spam pages, rogue redirects in .htaccess

(a server config file)

Developer

Clean the database

Spam posts, injected links, fake users

Developer

Update everything

CMS, plugins, theme, PHP version

Developer or

owner

Restore from a clean

backup

Only if you have one from before the hack

Host or developer

If you have a backup from before the hack and you know the date it started, restoring it and then patching the hole is often the fastest route. If you do not know when the hack began, an old backup may already be infected.

Many SMB sites in NCR run on WordPress with plugins nobody has updated in years. Old plugins and old PHP versions are a common entry point, so check those first.

How do you get the Google warning removed?

Google lists four things to do before you request a review: verify the site in Search Console, remove the hacker's changes, fix the vulnerability, and bring the cleaned site back online. Check that Googlebot can crawl the cleaned pages, with no noindex tags or robots blocks on them (web.dev: request a review).

Expected review times, per Google:

Type of issue

Review time

Phishing

About a day

Malware

A few days

Hacked with spam

Up to several weeks

After approval

Warnings removed within 72 hours

Google also warns that fixing only some pages does not earn a partial return to search results, and that a request sent before the site is fully clean keeps it flagged longer (Google Search Console Help).

Do you have to report a hack to anyone?

Possibly, and this is where you should get advice rather than guess. CERT-In's 2022 directions require covered entities to report listed cyber incidents, including website defacement or intrusion and data breaches, within six hours of noticing them, and to keep system logs for 180 days (UpGuard summary, Jan 2025). [VERIFY: whether a small business website owner is a covered entity under the CERT-In directions.]

If customer personal data such as names, phone numbers or orders was exposed, the DPDP Rules notified on 13 November 2025 require a breach intimation to the Data Protection Board, with a detailed report within 72 hours, and notice to affected people. Most operational obligations start after an 18-month phase, around May 2027 (Monday summary). This is general information, not legal advice.

When is a rebuild cheaper than a cleanup?

Sometimes a cleanup is the wrong spend. Consider a rebuild when:

  • The site was hacked more than once in a year.

  • It runs on a theme or plugins that are no longer updated.

  • The original developer is gone and nobody understands the code.

  • The site is a simple 5 to 10 page business site with little stored data.

A basic business website at Ureka starts from ₹4,999, and a web app from ₹9,999. For a small brochure site that keeps getting reinfected, a clean rebuild on current software can cost less than repeated cleanups. Keep the same URLs, or set 301 redirects (permanent forwards from old addresses to new ones), so search rankings carry over.

Keep the old site and clean it if it holds years of orders or customer records, or if it is a custom app with business logic you still need. If your site is clean now and you only want to keep it that way, a monthly maintenance plan with updates and backups may be all you need.

What this looks like in practice

For example, a Noida interior-design firm notices that its Google results show Japanese text, and enquiries have dropped. The site is WordPress, last updated three years ago, built by a freelancer who no longer replies.

The order of work: back up the infected site, reset hosting and admin passwords, remove two unknown admin users, and switch on maintenance mode. A developer finds an outdated form plugin as the entry point, removes thousands of injected spam pages and a redirect rule, updates everything, and restores the site. The firm then submits a review in Search Console and waits, since spam reviews can take weeks. Because the theme is abandoned, the owner plans a rebuild on the same URLs next quarter. This is a hypothetical example, not a real client.

How Ureka does it

We start with a 20-minute call and a look at what you can still access. You get a fixed written quote within 24 hours for a cleanup, a rebuild, or both, and the price changes only if the scope changes. Hosting, domain, code and database stay in your name, and you get all logins back. You talk to the developer on WhatsApp, with replies within a few hours. If a cleanup is enough, we will say so. See our website development service and cloud and hosting services.

FAQ

My website is hacked. Should I delete it and start again?

Not as the first step. Back up the infected site and change all passwords first, because you need to find how the attacker got in. If the site is small, old and repeatedly reinfected, a rebuild on current software may then be cheaper than cleaning it again.

How long does it take Google to remove the hacked site warning?

Google says malware reviews take a few days and spam-hack reviews can take up to several weeks. After Google confirms the site is clean, warnings are removed within 72 hours. Requesting a review before the site is fully clean only extends the wait.

Why does my site redirect to spam only on mobile?

Some hacks show spam only to mobile visitors or only to visitors arriving from Google, so the owner does not notice on a desktop. Check your site from a phone using mobile data and through a Google search result. A developer can find the redirect code in your files or database.

Can I prevent my website from being hacked again?

You can lower the risk a lot. Keep the CMS, plugins and PHP version updated, use strong unique passwords with two-factor login, remove unused plugins, and keep automatic off-site backups. Check Search Console for security emails.

Do I need to tell my customers if my website was hacked?

If personal data such as names, phone numbers or orders was exposed, India's DPDP Rules include breach notice duties, with most obligations starting around May 2027. CERT-In reporting rules may also apply to some businesses. Ask a lawyer about your specific case.