Cloudflare, website indexing in Google

2 days56 USD

Yaroslav Perets

2 days56 USD

Good day.

After connecting Cloudflare, indexing often drops due to:

— Bot Fight Mode / WAF, which block Googlebot
— incorrect SSL mode (Flexible → redirect loop)
— caching 403/301
— errors in robots.txt or x-robots-tag
— 5xx errors from the origin
…
I can conduct a technical audit:

🔹 checking Cloudflare logs
🔹 checking Security Events
🔹 analyzing Google Search Console
🔹 checking server response for Googlebot
🔹 configuring WAF Skip Rule for Verified Bots
🔹 checking canonical / robots

Result: restoration of correct indexing and stable access for Googlebot.

I am ready to start today.

Show original

Translate

30 days111 USD

Arseny Antonenko

30 days111 USD

The problem of 70% of pages dropping after connecting to Cloudflare is usually not related to DNS, but is a result of excessive protection or protocol conflicts that block the Googlebot crawler.

Technical algorithm for diagnosis and correction:

Bot Fight Mode and WAF: This is the main reason. If "Bot Fight Mode" is enabled, Cloudflare may issue JS calls or captchas even to legitimate bots if their IPs have not passed internal verification.

Solution: Check the Security -> Events section. If there are blocks from Google services, a WAF Skip Rule needs to be created for the official list of Googlebot IPs (Verified Bot).

SSL/TLS Mode (Flexible vs Full): If your server already had SSL, and Cloudflare is set to Flexible mode, a redirect loop occurs. Users may not notice it due to caching, but Googlebot immediately stops indexing pages with such errors.
…
Solution: Change the SSL mode to Full (Strict) if there is a certificate on the server, or check the redirect settings in .htaccess.

Browser Integrity Check: This feature checks HTTP headers. If Googlebot uses specific headers that Cloudflare considers outdated or suspicious, it receives a 403 error.

Solution: Temporarily disable this feature in the Security -> Settings for checking the response in Google Search Console.

Rocket Loader: This tool changes the loading order of scripts to speed up the site. However, it often "breaks" page rendering for the Google render bot (Headless Chrome), causing pages to be considered empty or erroneous.

Solution: Disable Rocket Loader in the Speed -> Optimization section and check the page through the "Live URL Inspection" tool in GSC.

What specific error codes (for example, 403 Forbidden, 520, or Redirect Error) does Google Search Console show in the "Indexing -> Pages" section for those 70% that dropped?

Show original

Translate

3 days45 USD

Kyryl Shcherbyna

3 days45 USD

Good day. It seems that the indexing issue after connecting Cloudflare may be related to settings or conflicts during this process. I am ready to investigate this matter, review the DNS configurations, firewall rules, and security settings to find the cause and resolve the issue. For this work, I recommend a budget starting from 2000 as it may require some technical knowledge and time for adjustments. The entire process may take up to 3 days to eliminate all possible issues and check the result.

Show original

Translate