{"id":25671,"date":"2026-09-06T00:47:44","date_gmt":"2026-09-05T21:47:44","guid":{"rendered":"https:\/\/alienroad.com\/google-bilgi-bankasi\/verify-requests-from-google-crawlers-and-fetchers\/"},"modified":"2026-09-06T00:51:47","modified_gmt":"2026-09-05T21:51:47","slug":"verify-requests-from-google-crawlers-and-fetchers","status":"publish","type":"ar_kb","link":"https:\/\/alienroad.com\/google-bilgi-bankasi\/verify-requests-from-google-crawlers-and-fetchers\/","title":{"rendered":"Verify requests from Google crawlers and fetchers"},"content":{"rendered":"

\n You can verify if a request to your server really is
\n from Google<\/a>. Verification
\n is possible for crawlers such as Googlebot, as well as other requests. This is useful if you’re
\n concerned that spammers or other troublemakers are accessing your site while claiming to be from
\n Google.\n<\/p>\n

Google’s crawlers and fetchers fall into three categories:<\/p>\n\n\n\n\n\n
Type<\/th>\nDescription<\/th>\nReverse DNS mask<\/th>\nIP ranges<\/th>\n<\/tr>\n
Common crawlers<\/a><\/td>\n\n The common crawlers used for Google’s products (such as Googlebot). They always respect
\n robots.txt rules for automatic crawls.\n <\/td>\n		\n crawl-***-***-***-***.googlebot.com<\/code> oder
\n geo-crawl-***-***-***-***.geo.googlebot.com<\/code>\n <\/td>\n		common-crawlers.json<\/a><\/td>\n<\/tr>\n
Special-case crawlers<\/a><\/td>\n\n Crawlers or fetchers that perform specific functions for Google products (such as AdsBot) where there’s an
\n agreement between the crawled site and the product about the access or for
\n abuse-specific crawling or fetching. These crawlers or fetchers may
\n or may not respect robots.txt rules.\n <\/td>\n		rate-limited-proxy-***-***-***-***.google.com<\/code><\/td>\nspecial-crawlers.json<\/a><\/td>\n<\/tr>\n
User-triggered fetchers<\/a><\/td>\n\n Tools and product functions where the end user triggers a fetch. For example,
\n Google Site Verifier<\/a>
\n acts on the request of a user. Because the fetch was requested by a user, these fetchers
\n ignore robots.txt rules.
\n Fetchers controlled by Google originate from IPs in the
\n user-triggered-fetchers-google.json<\/code> object and resolve to a
\n google.com<\/code> hostname. IPs in the user-triggered-fetchers.json<\/code> object
\n resolve to gae.googleusercontent.com<\/code> hostnames. These IPs are used, for example,
\n if a site running on Google Cloud (GCP) has a feature that requires fetching external RSS
\n feeds on the request of the user of that site.\n <\/td>\n		\n ***-***-***-***.gae.googleusercontent.com<\/code> oder
\n google-proxy-***-***-***-***.google.com<\/code>\n <\/td>\n		\n user-triggered-fetchers.json<\/a>,
\n user-triggered-fetchers-google.json<\/a>,
\n and user-triggered-agents.json<\/a>\n <\/td>\n<\/tr>\n<\/table>\n

There are two methods for verifying requests from Google:<\/p>\n