The sitemap can be read, but contains errors
-
Hello all,
I’ve been using your excellent extension for several years on various sites, but I’m currently experiencing a problem with my medibloux2.com site. The 1st extension I installed was Yoast, which was working fine until the end of last week.Unfortunately, the site has been infected by a hacker, and I’ve had a lot of trouble removing the malware and backdoors. After seeing on this forum that you often work with Sucuri.net, I decided to call on them. They did an excellent job of cleaning up the site after two scans, deactivating infected extensions and quarantining everything. The extensions was successfully reset and reinstalled. On their advice, I also set up their firewall, as this was my first experience of infection, so I agreed.
Following this attack, false addresses had been created and indexed by Google Merchant and Google Search Console. So I recreated the permalinks and regenerated the sitemap. At this stage, everything seemed to be working correctly.
However, after deleting the old sitemap in Search Console (this was my mistake) and trying to re-upload the new one, Google did recognise the sitemap, but treated it as an HTML file. The sitemap_index.xml file (available here: https://medibloux2.com/sitemap_index.xml) seems correct to me.
After deactivating all the extensions, except Yoast, and testing in debug mode, the problem persists. The only notable change (apart from the infection) is the addition of the firewall. Even after bypassing the firewall during many tests with the help of Sucuri, the problem remains the same.
We’ve come to the conclusion that we’d like to see if there’s anything you can do. Could you help me solve this problem?
I’m aware that a sitemap isn’t mandatory for SEO, but it’s still a very useful tool, especially for launching a site. (less than 1 month old)
I would like to thank you in advance for your help and remain at your disposal for any further information.
The page I need help with: [log in to see the link]
- You must be logged in to reply to this topic.