From 6202d7c9f1b9b432e686e285e6169cdeb9cbcb7a Mon Sep 17 00:00:00 2001 From: hypercharles Date: Thu, 19 Jun 2025 11:35:24 +0200 Subject: [PATCH] Update how-to-fix-performance-issues-caused-by-bots-and-crawlers.md Adds GoogleOther as a bot/crawler in layered navigation --- ...how-to-fix-performance-issues-caused-by-bots-and-crawlers.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md b/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md index 99bb2860..3fbba469 100644 --- a/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md +++ b/docs/best-practices/performance/how-to-fix-performance-issues-caused-by-bots-and-crawlers.md @@ -55,7 +55,7 @@ GET /clothing/pants.html?color=1181_1188_1500 HTTP/1.1 Mozilla/5.0 (compatible; It is clear that the “size” and “color” parameters are used for layered navigation, because they define subsets of your catalogue. For normal indexing, you only want /clothing.html and /clothing/pants.html indexed. To block bots in this case, you should add this to `/data/web/nginx/server.layered_navigation:` ```nginx -if ($http_user_agent ~* 'http|bot|crawl|spider') { +if ($http_user_agent ~* 'http|bot|crawl|spider|GoogleOther') { set $is_bot 1; } # Here, you should define the layered navigation urls.