Google can't crawl sitemap after Japanese hack

BlackFawkes

Regular Member
Joined
Jun 24, 2015
Messages
304
Reaction score
90
Hello BHW !

I'm facing an issue I can't resolve, so I hope someone will be able to help me.

One of my client's website has been hacked with Japanese keywords. Basically, the hacker created thousands of pages with Japanese keywords to rank on Google.

The infected pages have been deleted now. But Google index still shows all Japanese pages and not English ones. I can't even submit a new sitemap in the GSC, I get an Http error. Something is definitely blocking Googlebot from crawling the website but I don't know what.

Send help please, this is driving me crazy :suspicious:
 
God damn that sounds crazy, I have 0 experience with SEO, but I will reply here to bump the thread for someone to hopefully see
 
Hello BHW !

I'm facing an issue I can't resolve, so I hope someone will be able to help me.

One of my client's website has been hacked with Japanese keywords. Basically, the hacker created thousands of pages with Japanese keywords to rank on Google.

The infected pages have been deleted now. But Google index still shows all Japanese pages and not English ones. I can't even submit a new sitemap in the GSC, I get an Http error. Something is definitely blocking Googlebot from crawling the website but I don't know what.

Send help please, this is driving me crazy :suspicious:

how about going down this route
https://www.google.com/webmasters/sitemaps/ping?sitemap=http://www.YOUR DOMAIN.com/sitemap.xml
 
  • Like
Reactions: 200
God damn that sounds crazy, I have 0 experience with SEO, but I will reply here to bump the thread for someone to hopefully see
Thank you ! I really appreciate it
 
Is the GoogleBot being blocked in your .htaccess file?
 
What's the specific error GSC is throwing when you submit the sitemap?
Are you on CloudFlare? Sometimes it can block GoogleBot by accident.

Double check your robots.txt, make sure GoogleBot isn't blocked.
Live Test a URL in GSC and see if it has any errors, or if the page is showing different content for the bot - perhaps your website is still hacked and showing different content for googlebot vs users?
 
It will take a long time for google to forget your indexed pages not matter if you submit the sitemap or not.

Just saying
 
i guess its time for someone to deobfuscate the malware and find out how they force Google to index.
 
What's the specific error GSC is throwing when you submit the sitemap?
Are you on CloudFlare? Sometimes it can block GoogleBot by accident.

Double check your robots.txt, make sure GoogleBot isn't blocked.
Live Test a URL in GSC and see if it has any errors, or if the page is showing different content for the bot - perhaps your website is still hacked and showing different content for googlebot vs users?
Error is HTTP 403. That's why I think GoogleBot is blocked somewhere.
Robots.txt + .htaccess are clean.
And the website is not using Cloudflare.
I'll check to test a live URL but I'm almost sure I did that and it was clear
 
It will take a long time for google to forget your indexed pages not matter if you submit the sitemap or not.

Just saying
Yes I know that, but at least I would like to submit one ahah
 
i guess its time for someone to deobfuscate the malware and find out how they force Google to index.
Yes you're most probably right. Headache incoming
 
Hello BHW !

I'm facing an issue I can't resolve, so I hope someone will be able to help me.

One of my client's website has been hacked with Japanese keywords. Basically, the hacker created thousands of pages with Japanese keywords to rank on Google.

The infected pages have been deleted now. But Google index still shows all Japanese pages and not English ones. I can't even submit a new sitemap in the GSC, I get an Http error. Something is definitely blocking Googlebot from crawling the website but I don't know what.

Send help please, this is driving me crazy :suspicious:

Are you sure the hacked pages aren't being cloaked when googlebot crawls them?
 
Are you sure the hacked pages aren't being cloaked when googlebot crawls them?
How can I be sure ? When I check them manually, everything looks fine.
And every Japanese page indexed in Google is now deleted, so basically every Japanese page indexed is a 404
 
So in the root of the FTP, the .htaccess file is this one :

Code:
# php -- BEGIN cPanel-generated handler, do not edit
# Définissez le package « ea-php56 » comme langage de programmation « PHP » par défaut.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php56___lsphp .php .php5 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

There are MANY MANY other .htaccess located everywhere (dozains).


ht1.PNG


ht2.PNG


There are way more, is this normal? Does an normal e-commerce website have that much .htaccess? Because in my experience, it doesn't.

The website is a prestashop btw.


All those other .htaccess are the same (I didn't checked em all) :

Code:
<FilesMatch ".*\.(phtml|php|PhP|php5)$">
Order Allow,Deny
Deny from all
</FilesMatch>

Thanks guys for your help.
 
So in the root of the FTP, the .htaccess file is this one :

Code:
# php -- BEGIN cPanel-generated handler, do not edit
# Définissez le package « ea-php56 » comme langage de programmation « PHP » par défaut.
<IfModule mime_module>
  AddHandler application/x-httpd-ea-php56___lsphp .php .php5 .phtml
</IfModule>
# php -- END cPanel-generated handler, do not edit

There are MANY MANY other .htaccess located everywhere (dozains).


View attachment 158067

View attachment 158068

There are way more, is this normal? Does an normal e-commerce website have that much .htaccess? Because in my experience, it doesn't.

The website is a prestashop btw.


All those other .htaccess are the same (I didn't checked em all) :

Code:
<FilesMatch ".*\.(phtml|php|PhP|php5)$">
Order Allow,Deny
Deny from all
</FilesMatch>

Thanks guys for your help.

You need a clean install. I think the hack is still live.
 
You need a clean install. I think the hack is still live.
Thank you for your reply. I'm also pretty sure something is still here bugging around. I'll check if we can get an older version of the website (probably not haha)
 
Back
Top