How to Remove the Japanese Keyword Hack from a WordPress Website
A Japanese keyword hack can create spam pages, alter search results and sometimes redirect visitors. Treat it as a website compromise: preserve evidence, restrict access, remove the entry point and malicious files, restore clean content, then ask Google to recrawl affected URLs.
Recognise the signs without guessing
Search results may show Japanese-language titles for pages you never created, unexpected shopping snippets, unfamiliar favicons or URLs containing random parameters. These signs justify investigation but do not prove the exact infection mechanism.
Check Search Console’s Pages, Security Issues and URL Inspection reports. Compare a suspicious URL in a normal browser, a private session and the server logs because some attacks show different content to search crawlers.
Contain the incident before editing
Make a secure backup of files, database and relevant logs for investigation. Change compromised passwords and revoke unknown sessions. If possible, limit write access while maintaining a safe way to recover the site.
Do not delete every suspicious file immediately. Evidence can reveal how the attacker entered, and careless deletion can destroy legitimate WordPress code.
Find the source of reinfection
Check WordPress users, plugins, themes, mu-plugins, uploads, scheduled tasks, wp-config.php and web-server configuration. Review recently modified files and unexpected administrator accounts.
A cleanup that removes only visible spam pages may fail if a backdoor remains. Compare core files with trusted originals and reinstall affected plugins and themes from legitimate sources.
Clean files and database safely
Remove confirmed malicious code, injected posts and unauthorised database entries. Reinstall WordPress core and compromised components from clean packages after preserving the necessary configuration and user content.
Avoid broad database queries that delete every URL containing a foreign character. A legitimate multilingual site may have non-English content, and accidental deletion can cause further damage.
Handle indexed spam URLs correctly
Once the infection is removed, invalid spam URLs should normally return a genuine 404 or 410 where appropriate. Remove hacked content from sitemaps and fix compromised redirects.
Robots.txt is not a substitute for removal: blocking Googlebot can prevent it from seeing a 404 or 410. Use temporary removals in Search Console only when urgently needed, then rely on permanent server responses.
Harden and monitor the recovered site
Rotate credentials, enable multi-factor authentication where possible, update software, remove unused plugins and check file permissions. Review logs for recurring requests to known malicious paths.
After cleanup, submit clean sitemaps and inspect representative URLs. Search results can take time to update; do not promise immediate removal of every cached snippet.
What a careful cleanup looks like
A WordPress site begins showing strange Japanese-language search results. The owner checks Search Console and finds hundreds of unfamiliar URLs. The developer first preserves the database, files and logs, then identifies a vulnerable component and suspicious code in an unexpected location.
After replacing compromised files and closing the entry point, the developer checks that fake pages now return the appropriate HTTP response. The site is monitored for reinfection. Google may take time to drop the old results, so the team reports verified technical progress rather than promising an instant clean search page.
A quick decision guide
| Area to review | Useful next step |
|---|---|
| Recognise the signs without guessing | Search results may show Japanese-language titles for pages you never created, unexpected shopping snippets, unfamiliar favicons or URLs containing random parameters. |
| Contain the incident before editing | Make a secure backup of files, database and relevant logs for investigation. |
| Find the source of reinfection | Check WordPress users, plugins, themes, mu-plugins, uploads, scheduled tasks, wp-config. |
| Clean files and database safely | Remove confirmed malicious code, injected posts and unauthorised database entries. |
Details worth checking before you act
Review unexpected WordPress administrator accounts and compare their creation dates with the first signs of spam. Disable or remove unauthorised access only after recording evidence and confirming the account is not legitimate.
Look for suspicious PHP files in uploads directories, modified theme functions and unknown scheduled tasks. Do not run arbitrary cleanup scripts downloaded from forums against a live database.
Inspect HTTP status codes for representative hacked URLs. A page that visually says ‘not found’ but returns HTTP 200 can remain confusing to search engines; a real 404 or 410 is more appropriate for removed content.
Frequently asked questions
Does robots.txt remove Japanese spam from Google?
Search results may show Japanese-language titles for pages you never created, unexpected shopping snippets, unfamiliar favicons or URLs containing random parameters. These signs justify investigation but do not prove the exact infection mechanism. Check the specific requirements and your actual business situation before taking action. Keep a record of what you changed and whether the result improved.
Can I clean the site without deleting everything?
Do not delete every suspicious file immediately. Evidence can reveal how the attacker entered, and careless deletion can destroy legitimate WordPress code. If you are unsure, verify the facts in the official dashboard or with the responsible provider rather than relying on an online shortcut. Avoid making changes that you cannot reverse.
Why do Japanese spam URLs keep returning?
Check WordPress users, plugins, themes, mu-plugins, uploads, scheduled tasks, wp-config.php and web-server configuration. Review recently modified files and unexpected administrator accounts. The safest decision is the one supported by real evidence from your website or account. Test carefully, and do not promise a result that depends on another platform.
Should I use Search Console removals?
Avoid broad database queries that delete every URL containing a foreign character. A legitimate multilingual site may have non-English content, and accidental deletion can cause further damage. Check the specific requirements and your actual business situation before taking action. Keep a record of what you changed and whether the result improved.
Can a clean backup solve the hack?
Once the infection is removed, invalid spam URLs should normally return a genuine 404 or 410 where appropriate. Remove hacked content from sitemaps and fix compromised redirects. If you are unsure, verify the facts in the official dashboard or with the responsible provider rather than relying on an online shortcut. Avoid making changes that you cannot reverse.
How long will Google show hacked snippets?
After cleanup, submit clean sitemaps and inspect representative URLs. Search results can take time to update; do not promise immediate removal of every cached snippet. The safest decision is the one supported by real evidence from your website or account. Test carefully, and do not promise a result that depends on another platform.
What should I do after the site is clean?
Rotate credentials, enable multi-factor authentication where possible, update software, remove unused plugins and check file permissions. Review logs for recurring requests to known malicious paths. After cleanup, submit clean sitemaps and inspect representative URLs. Search results can take time to update; do not promise immediate removal of every cached snippet. Check the specific requirements and your actual business situation before taking action. Keep a record of what you changed and whether the result improved.
Where to go from here
If your business needs help with the issues covered in this guide, review our website maintenance and security services. You can also contact the Afix Smart Web team to understand the next practical step.
