Has anyone experienced the issue of Googlebot being blocked by robots.txt in Webflow, even though access has been allowed in the file?

TL;DR
  • Ensure robots.txt in Webflow allows Googlebot, verify site is published, and confirm DNS settings point to Webflow's IPs.
  • Check firewall permissions and use Google Search Console tools to test robots.txt and Googlebot access, adjusting settings as needed.

Issues with Googlebot being blocked by robots.txt in Webflow can be frustrating, especially if the file appears to allow access. Here’s how to address this issue:

1. Check Robots.txt Settings in Webflow

  • Go to Project Settings in your Webflow site.
  • Click on the SEO tab and locate the Robots.txt section.
  • Ensure your robots.txt file includes directives to allow Googlebot access, such as User-agent: Googlebot Allow: /.

2. Review Site's Hosting and DNS

  • Confirm the site is published and live on the Webflow servers.
  • Verify your DNS settings are correct and pointing to Webflow’s IP addresses (a) 75.2.70.75, (b) 99.83.190.102.

3. Check for Permissions or Firewall Issues

  • Review any external firewall settings that might restrict Googlebot.
  • Ensure there are no server-side security settings blocking Googlebot’s IP addresses.

4. Test Robots.txt Retrieval

  • Use the robots.txt Tester tool available in Google Search Console.
  • Enter your site's URL/robots.txt to ensure Googlebot can access and read the file correctly.

5. Verify with Fetch as Google

  • Use the URL Inspection Tool in Google Search Console.
  • Request a live test to see if Googlebot encounters any denied access issues.

6. Check for Recent Changes

  • Review any recent changes made in your Webflow settings or DNS configurations that might have affected access.
  • Roll back any changes abruptly preceding the issue to isolate the cause.

Summary

Ensure that your robots.txt settings in Webflow explicitly allow Googlebot, check DNS settings and firewall permissions, and verify with Google Search Console tools. Adjustments to configuration or recent changes might hold the key to resolving this blocking issue.

Rate this answer

Other Webflow Questions