Title: Exclude Google bots
Last modified: February 23, 2023

---

# Exclude Google bots

 *  Resolved [RLDD](https://wordpress.org/support/users/rermis/)
 * (@rermis)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/exclude-google-bots/)
 * Hi, Is it possible to exclude bots on the /checkout/order-received page? I am
   seeing several instances where a bot has revisited a checkout page for old orders
   and the pixel has fired. I then see a corresponding conversion for these in Google
   Ads on the day the bot visited.
 * There are a few other instances where I’ve chosen to exclude bots and the following
   line of code has been fairly reliable.
 *     ```wp-block-code
       if(stripos(gethostbyaddr($ip),'google')==true) return;
       ```
   

Viewing 3 replies - 1 through 3 (of 3 total)

 *  [Kenneth](https://wordpress.org/support/users/kavillarosa/)
 * (@kavillarosa)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/exclude-google-bots/#post-16502134)
 * Hi [@rermis](https://wordpress.org/support/users/rermis/) ,
 * Our plugin already excludes common bots. But, this is only for the server-to-
   server implementation. This intends to reduce the stress on the server.
 * Blocking the browser pixel, especially for Google bots would be a bad idea.
 * Google Ads bots crawl the websites regularly to check if the Google Tags have
   been implemented correctly. If it sees that the implementation is wrong, you’ll
   see warning in Google Ads and possibly even lower ads performance.
 * Also, Google bot can’t trigger conversions. A conversion can only be triggered
   when a person clicks on an ad and reaches the purchase confirmation page with
   the same browser.
 * I hope that helps.
 * Let me know if you have any questions.
 * Regards,
   Kenneth
 *  Thread Starter [RLDD](https://wordpress.org/support/users/rermis/)
 * (@rermis)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/exclude-google-bots/#post-16503386)
 * Hi Kenneth,
 *  Thanks for your reply. It makes sense not to block the Ads bot. But I still 
   have 4 conversions registered on Feb 22nd from orders that are 2+ years old. 
   The only visitors for the orders were bots. Could you consider another approach,
   and don’t render the pixel when the order is over a x days old, or if the order
   is already completed?
 * Thanks for listening!
 *  Plugin Author [alekv](https://wordpress.org/support/users/alekv/)
 * (@alekv)
 * [3 years, 3 months ago](https://wordpress.org/support/topic/exclude-google-bots/#post-16503920)
 * Hi [@rermis](https://wordpress.org/support/users/rermis/)
 * You can set the conversion window on the conversion in the Google Ads settings
   from one day up to 90 days.
 * But again. Google bots won’t trigger conversions.
 * Kind regards
    Aleksandar

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Exclude Google bots’ is closed to new replies.

 * ![](https://ps.w.org/woocommerce-google-adwords-conversion-tracking-tag/assets/
   icon-256x256.png?rev=2704744)
 * [Pixel Manager for WooCommerce – Conversion Tracking, Google Ads, GA4, TikTok, Dynamic Remarketing](https://wordpress.org/plugins/woocommerce-google-adwords-conversion-tracking-tag/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/woocommerce-google-adwords-conversion-tracking-tag/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/woocommerce-google-adwords-conversion-tracking-tag/)
 * [Active Topics](https://wordpress.org/support/plugin/woocommerce-google-adwords-conversion-tracking-tag/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/woocommerce-google-adwords-conversion-tracking-tag/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/woocommerce-google-adwords-conversion-tracking-tag/reviews/)

## Tags

 * [google bot](https://wordpress.org/support/topic-tag/google-bot/)

 * 3 replies
 * 3 participants
 * Last reply from: [alekv](https://wordpress.org/support/users/alekv/)
 * Last activity: [3 years, 3 months ago](https://wordpress.org/support/topic/exclude-google-bots/#post-16503920)
 * Status: resolved