Skip to content

Why is my website showing Japanese in Google search? How to fix it

Japanese titles under your domain mean the Japanese keyword hack. How to confirm it, clean the site, get the spam out of Google and remove the hacked warning.

The usual answer to "why is my website showing Japanese in Google search" is the Japanese keyword hack. Someone got into your site and added pages of autogenerated Japanese text, or rewrote your titles, to send traffic to stores selling fake brand goods. The trick is cloaking: Google's crawler sees the spam, while you see your normal site or a 404 page.

It is fixable, in this order: confirm the hack, remove any Search Console owner the attacker added, clean the site, make the spam URLs return 404 or 410, then ask Google for a review so the "This site may be hacked" label comes off.

5 minute check: type site:yourdomain.com into Google and flip through 3 or 4 pages of results. Count the Japanese titles and odd URLs. Each is a page Google can show instead of your service pages.

Why is my website showing Japanese in Google search?

Google's guide to fixing the Japanese keyword hack says it creates pages of autogenerated Japanese text in randomly named folders, such as /ltjmnjp/341.html. Those pages carry affiliate links to stores selling fake brand merchandise and show up in Google under your domain. The attacker often adds themselves as an owner of your site in Google Search Console too.

You usually can't see any of it. Google's spam policies define cloaking as presenting different content to users and to search engines. The hacked code serves spam to Google's crawler and a normal page or a "not found" error to you and your customers. Google's guide warns not to be fooled by that 404.

The hack shows up in 2 ways: new spam pages under your domain, or your real pages showing Japanese titles and snippets. Google's spam policies count both adding pages and quietly changing existing ones as hacked content.

The cost is real. Google shows "This site may be hacked" in search results when it believes a hacker changed pages or added spam pages, and it recommends searchers don't visit until the message disappears. If you run ads, Google's Compromised sites policy lists hacked destinations as a reason for disapproval; see our guide to a Google Ads compromised site disapproval.

When it isn't a hack

Open a page that shows Japanese in Google, choose View page source and search for the Japanese words. If they are there, the text lives on your site in plain view, from a translation app, an old plugin or an SEO field. Remove it and wait for a recrawl. If the words are not in the source, Google sees something you don't, and that is the hack.

How to confirm the Japanese keyword hack in 5 minutes

You need Google Search Console access for your domain. If nobody set it up, verify the site now; the review request lives there too.

  1. Search your domain. Run the site: search above and note every URL you don't recognize. Google's guide suggests trying another search engine if Google shows nothing odd.
  2. Open the Security issues report in Search Console. Look for Hacked: URL injection (new pages) or Hacked: Content injection (spam added to your pages). Expand the issue for sample URLs; Google notes it is a sample, not a full list.
  3. Run URL Inspection. Paste a spam URL, or your homepage if its title is in Japanese, into the URL Inspection tool. Click Test live URL, then View tested page, and read the HTML and screenshot. Japanese text you can't see in your browser is cloaking.
  4. Check Performance. On the Pages tab, look for URLs you never created. On the Queries tab, look for Japanese search terms.

Write down the spam folder names. You will need them for the cleanup and the Removals tool.

Not sure what is costing you leads?

Send your website and we will record a free 2 minute video showing the 3 fixes we would make first.

Get my free video audit

Lock down Search Console before you clean

Google's guide says that if someone you don't know has verified your site, revoke their access as soon as possible.

  1. Go to Settings, then Users and permissions. Only owners can see this page.
  2. Next to any owner you don't know, open the menu and click Ownership verification details to see which tokens they used, then click Remove access. Google's help for an owner you don't recognize covers this.
  3. Delete their verification token. It is often an HTML file at your site's root named google plus random characters. Google's guide warns it can also be an .htaccess rule that generates that file. When a test URL like yourdomain.com/google1234.html returns a 404, the generated token is likely gone.
  4. Click Unused ownership tokens to find tokens from owners removed earlier. As long as a token remains, a deleted owner can verify again.

Google is blunt that on a hacked site this is only temporary, because the attacker can probably put the token back. The cleanup is what closes the door.

Then check sitemaps. Attackers often edit yours or add new ones to get their URLs indexed faster. In the Sitemaps report, open any sitemap you didn't submit and choose Remove sitemap from the more options menu. Google's Sitemaps report help says Google won't forget a removed sitemap or its URLs, so delete the file from your server and strip spam links from your real sitemap.

Japanese keyword hack fix: clean files and database

These steps cover the Japanese keyword hack on WordPress, drawn from the WordPress.org hacked site FAQ and Google's guide. The idea is the same on any platform where you control the files.

  1. Back up first. Copy the files and database before you change anything, infected or not.
  2. Tell your host. On shared hosting, a hack can reach beyond your site.
  3. Reset access. Change passwords for the hosting panel, SFTP or FTP, the database and every WordPress admin. New secret keys in wp-config.php log everyone out. Delete any administrator you didn't create.
  4. Replace every .htaccess file, including ones in subfolders, with a clean default.
  5. Reinstall core, plugins and themes from clean copies of the same versions, over SFTP. WordPress.org advises against the dashboard reinstall, since it often only overwrites existing files and hacks often add new ones.
  6. Hunt for leftover PHP. Check recently changed, unusually large or non-standard files. Attackers often inject code into index.php, wp-load.php, 404.php and view.php, plus your theme's header, footer and functions files. Long scrambled strings next to base64_decode, eval or gzinflate are a red flag.
  7. Check the database for admin users you didn't add and posts or pages you never published.
  8. Scan your own computer. WordPress.org notes many attacks start with malware that captures FTP and admin logins on the owner's machine.
  9. Update everything, then change the passwords again, since the first reset happened on an infected site.

This is where DIY often stops making sense. If you aren't comfortable editing files over SFTP, or the spam returns within days, the way in is still open. On an old site full of abandoned plugins, a rebuild can cost less than repeated cleanups; that call is part of our web design work.

Get the spam pages out of Google

Google's page on HTTP status codes says all 4xx errors except 429 are treated the same, and indexed URLs that start returning a 4xx are removed from the index. So 404 and 410 both work, as long as Google's crawler gets them too.

  • Test what Google gets. Run spam URLs through Test live URL. Google's guide says that if they come back as not found in Google's tools, you are probably in good shape. A 404 in your own browser proves nothing while cloaking is in play.
  • Don't block spam in robots.txt. Google has to crawl those URLs to see they are gone, and its Removals help says not to use robots.txt as a blocking mechanism.
  • Hide the worst with the Removals tool. Open Removals, choose New request, then Temporarily remove URL, and enter a spam folder with Remove all URLs with this prefix. Requests usually take up to a day and last about 6 months, so the 404 or 410 must stay in place. Never enter your homepage as the prefix.
  • Get your real pages recrawled. Use Request indexing in URL Inspection for your homepage and main service pages, then resubmit your clean sitemap. There is a daily limit, so start with the pages that bring calls.

The Page indexing report will list the spam URLs as not indexed, often as Not found (404), for a while. That is expected; our guide to pages not indexed in Search Console explains which statuses to ignore.

Remove "This site may be hacked" and track recovery

Request a security review

Google's guide to requesting a review says to confirm 4 things first: the site is verified in Search Console, the hacker's changes are cleaned up, the vulnerability is fixed and the clean site is back online. Then select Request Review in the Security issues report and say what you did for each issue type, for example: "For URL injection, I deleted the spam folders, reinstalled core and plugins from clean copies and updated an outdated plugin."

Don't send it early. Google's Security issues help warns that a request made before the fix can slow the next review and can get you marked as a repeat offender, and asks you not to resubmit while one is pending.

How long recovery takes

StepGoogle's stated time
Removals tool requestUsually up to a day, then lasts about 6 months
Recrawl of fixed pagesA few days to a few weeks, per Google's recrawl guide
Review of a site hacked with spamUp to several weeks
Warnings removed after a clean verdictWithin 72 hours

Google publishes no timeline for rankings. Track progress instead: spam URLs leaving site: results, your titles back in English and impressions for your real pages in the Performance report.

While you wait, open your Google Business Profile on a phone, tap Website and make sure it lands on your clean homepage. Confirm the website field still shows your own domain.

Keep the hack from coming back

Google's guide cites a study that found 20% of hacked sites are hacked again within 1 day. After a cleanup:

  • Use a long, unique password for every account and turn on 2 step verification.
  • Keep core, plugins and themes updated, and delete the ones you don't use.
  • Keep regular backups of files and database, stored off the server.
  • Run antivirus on every computer that logs in to the site.
  • Check Users and permissions in Search Console monthly, and stay a verified owner so new owner notices reach you.
  • Consider a security service that monitors your site.

If the spam came back after an earlier cleanup, something was left behind. Our guide to why a WordPress site keeps getting hacked ranks the usual suspects.

A tool we built for this: Stillward Security is our free WordPress plugin. It hardens the site, locks out repeated login attempts, and audits the database for hidden admin accounts after a cleanup. It is our own plugin, so judge it as you would any vendor's recommendation.

What to do next

Today, run the site: search, open the Security issues report and remove any Search Console owner you don't know. This week, clean the site, make the spam URLs return 404 or 410 and hide the worst folders with Removals. Once Google's tools see a clean site, request the review.

Not sure what else your site is hiding? Send it to us and we'll record a free 2 minute video audit showing the 3 fixes we'd make first.

Common questions

Why is my website showing Japanese in Google search but not when I visit it?

Because of cloaking. The hacked code shows Google's crawler the spam and shows people a normal page or a "not found" error, so the hack is easy to miss. Google's own guide warns not to be fooled by that 404. See what Google actually receives with Test live URL in Search Console's URL Inspection tool.

How long does it take for Japanese pages to disappear from Google?

A Removals tool request usually takes up to a day and hides URLs for about 6 months. For a permanent fix, the spam URLs must return 404 or 410, and Google drops them as it recrawls, which can take a few days to a few weeks. A security review for a site hacked with spam can take up to several weeks.

Should hacked spam URLs return 404 or 410?

Either works. Google's documentation says all 4xx errors except 429 are treated the same, and indexed URLs that return a 4xx are removed from the index. Use whichever your site returns once the spam files are deleted, and confirm with URL Inspection that Google's crawler gets it too, not just you.

How do I remove "This site may be hacked" from Google?

Clean the site, close the way the attacker got in and confirm Google sees clean pages. Then select Request Review in the Security issues report in Search Console and explain what you fixed. Google says warnings come off within 72 hours of a clean verdict, but reviews of sites hacked with spam can take up to several weeks.

Can the Japanese keyword hack affect my Google Ads?

Yes. Under Google's Compromised sites policy, destinations that are hijacked or hacked lead to disapproval, so ads pointing to a hacked site can be disapproved until it is clean. Fix the site and get the Search Console review first, then appeal the disapproval from the Policy manager in your Google Ads account.

Get your free video audit

The 3 fixes we'd make first on your site, within 1 business day.

Send my website
Free video auditWhatsApp