@sam0090 Certainly! The issue with Cookiebot, GTM, and Typo3 seems to be related to script blocking. Make sure essential scripts for your hover menu are correctly categorized in Cookiebot’s settings to prevent them from being blocked. Also, review GTM’s integration to ensure it adheres to Cookiebot's consent settings.
Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Posts made by sam0090
-
RE: Replicate rogerbot error for server/hosting provider
-
RE: Replicate rogerbot error for server/hosting provider
@Moving-Web-SEO-Auckland It sounds like you're having trouble with rogerbot being blocked by your hosting provider, CrazyDomains. Here are a few steps you can take:
Check Robots.txt Syntax: Ensure your robots.txt file is correctly formatted. It seems mostly correct, but it should be double-checked for any syntax errors.
makefile
Copy code
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.phpUser-agent: rogerbot
Disallow:Sitemap: https://www.something.com/sitemap.xml
Contact Hosting Support: Reach out to CrazyDomains support and explain the issue. They may be blocking rogerbot on the server side. Provide them with specific details about your issue and ask if there are any server-side restrictions for rogerbot.Use Alternative Bots: If the issue persists, you could test with other bots to see if the same restrictions apply. This can help identify if the problem is specific to rogerbot or a broader issue.
Server Logs: Check your server logs to see if there are any entries that show why rogerbot is being blocked. This can provide more insight into what’s happening.
Campaign Setup: To duplicate the error, you might set up a staging environment with the same robots.txt and see if the issue persists there. This can help you troubleshoot without affecting the live site.
If these steps don't resolve the issue, you may need to consider switching to a different hosting provider that allows more flexibility with bot access.