🈲
Security

Japanese SEO spam hack: strange pages from your site appear in Google

21.11.2026
← All articles

You type your site's name into Google and the results show Japanese titles and pages selling cheap watches or bags. Clicking them sometimes leads to a foreign shop, sometimes to your normal page or a 404. This is the "Japanese keyword hack", a form of SEO spam. The attacker borrows your domain's authority, gets thousands of spam pages indexed and drives traffic to their own shops, while your site loses rankings and trust and may get Google warnings.

Why the owner does not see the pages

These attacks usually rely on cloaking. The malicious code checks who is asking: Googlebot gets a spam page, while a normal browser gets a 404 or the homepage. The pages are rarely real files. A PHP generator is planted on the site and .htaccess or index.php routes non-existent URLs to it, so it can produce an unlimited number of pages.

Example: a private school in Namangan

A parent searching for a private school in Namangan saw dozens of Japanese-language results and told the school. The developer opened one spam URL in a browser, got the homepage and dismissed it. Later Search Console showed indexed pages jumping from hundreds to tens of thousands in a few weeks, plus an unknown owner in the property settings. A randomly named PHP file and a Google verification file sat in the site root.

Confirming the hack

site:example.uz
site:example.uz 激安
curl -s https://example.uz/spam-url | head -n 20
curl -s -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" https://example.uz/spam-url | head -n 20

The site: operator limits results to your domain, so pages in a foreign language stand out immediately; adding a typical spam word narrows the list further. If the two curl responses differ, cloaking is confirmed. Some malware also checks that the request comes from real Google IP addresses, in which case curl shows no difference; use the URL Inspection tool in Search Console to see the page as Google does.

Removing rogue Search Console owners

Attackers often verify your site in their own Search Console account by uploading an HTML file starting with google to the root, then submit spam sitemaps. Under Settings, Users and permissions, find unknown owners. Remove their verification token first, meaning the file or DNS record, otherwise they will be re-verified. Then remove the owner and delete any sitemaps you did not submit.

find . -maxdepth 2 -name "google*.html" -ls

Cleaning files and the database

grep -rl --include=*.php -i "googlebot" .
find . -name "*.php" -mtime -30 -not -path "./wp-content/cache/*"
wp post list --post_type=any --post_status=any --orderby=date --order=DESC --posts_per_page=30 --fields=ID,post_title,post_date
wp core verify-checksums

Look for unfamiliar files in the site root as well, since generators are often dropped there with random names next to wp-config.php. Some variants store spam pages as ordinary posts in the database, which is why the post list above is worth checking. Legitimate SEO plugins may mention Googlebot too, so read each match. Check .htaccess, update all plugins and themes, and change hosting, FTP, database and admin passwords. If the entry point stays open, the generator returns within days.

Recovering search results

Once clean, spam URLs should return 404 or 410, and Google drops them as it recrawls, which takes time with many pages. The Removals tool in Search Console can hide the most visible URLs temporarily, but the real 404 does the lasting work. Resubmit your own sitemap, request a review if Security issues shows a warning, and keep watching site: results and the indexed page count for a few weeks. On sayt.uz hosting you can inspect files with the ISPmanager file manager; if the generator keeps coming back, open a ticket from the sayt.uz cabinet.

Related articles

🐘 Critical PHP vulnerabilities: why you should not delay updating 📚 Securing an OJS Journal Site: Updates, File Storage and Bot Load 🧪 Exposed phpinfo() and leftover test files: why they matter 🚨 How to Tell Your Hosting Account Has Been Hijacked: Signs and Steps
🌐 Language
🇺🇿 O⁠'zbek 🇺🇿 Özbek (yangi) 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓