What information does the fetcher retrieve?

Its documented purpose is compiling flight pricing and availability. The record does not support treating unrelated requests as part of that workflow.

Does Google-Flights-Search-Spackle respect robots.txt?

Compliance is unknown in this catalog, while Cloudflare's bot directory marks it false. Google's general guidance also says user-triggered fetchers ignore robots.txt, so enforce any hard restriction outside the file.

Does this fetcher put pages into Google Search?

The supplied evidence ties it to Google Flights pricing and availability, not to general web indexing. A visit should not be counted as a Googlebot crawl.

Is Google-Flights-Search-Spackle used for AI training?

No training use is documented. The record also does not connect this fetcher to Gemini or generative Google Search features.

How can I check whether the request is really from Google?

Match the exact user agent, then use Google's published reverse and forward DNS procedure or the relevant Google fetcher IP files. this bot has no HTTP signature URL and does not mark the bot as IP verified.

Google-Flights-Search-Spackle AI Crawler Guide

What is Google-Flights-Search-Spackle?

Google-Flights-Search-Spackle is a user-triggered Google Flights fetcher. It retrieves airline and travel-site content when a person uses flight search, with the stated purpose of compiling pricing and availability. That is a narrower job than discovering pages for Google's general web index.

The product context matters. The Google Flights page linked by Cloudflare lets signed-in users track fares for routes or flights and receive price-change notifications. The supplied bot record connects the fetcher to the underlying search workflow, where current travel information is needed in response to a user's request.

A request should therefore be read as an on-demand product fetch, not evidence of a scheduled site crawl. An airline may see the bare Google-Flights-Search-Spackle string reach a relevant fare or availability resource. Broad traversal of editorial archives or unrelated application paths would not fit the documented purpose and should be investigated separately.

Nothing in the source record assigns this fetcher an AI training role. It is also not documented as a crawler for AI Overviews, Gemini, or the main Google Search index. Allowing it can affect whether Google Flights obtains information needed for a user's flight search, but there is no basis for promising wider AI search exposure.

Robots handling is not confirmed in the bot metadata. Cloudflare's bot directory marks followsRobotsTxt as false, and Google's documentation says user-triggered fetchers generally ignore robots.txt because a person initiated the retrieval. A token-specific rule can express a preference, but it is not a dependable barrier for this traffic.

Cloudflare's bot directory records one exact user agent, Google-Flights-Search-Spackle, and no Web Bot Auth signature URL. This catalog entry is not marked as IP verified. Google publishes reverse DNS checks and IP files for classes of its fetchers, so operators can use those checks as supporting evidence, but the user-agent header by itself is easy to imitate.

Relevant for AI searchAI Overviews

Is Google-Flights-Search-Spackle relevant for AI search?

Yes. Google-Flights-Search-Spackle feeds AI Overviews, so the pages it can reach shape what those AI products say about you.

Google-Flights-Search-Spackle feeds a search index that also powers that engine's AI answer features and overviews. One crawl can serve a classic results page and a generated summary, so blocking it costs you both the rankings you would expect and a growing share of AI answers built on the same index.

How to handle Google-Flights-Search-Spackle

Airlines and travel services that expect Google Flights traffic should keep the necessary pricing or availability resources reachable and watch for failed responses. Other parts of the application do not need to be opened merely because this fetcher is allowed to reach a flight-data route.

The stable token allows this robots.txt declaration:

User-agent: Google-Flights-Search-Spackle
Disallow: /

Do not rely on that file for enforcement. Cloudflare's bot directory records the fetcher as not following robots.txt, and Google says user-triggered fetchers generally ignore it. If the requests are unwanted, apply a route-specific server or edge rule after checking the source with Google's documented DNS or IP verification process.

Examples

An airline sees the exact fetcher string on a fare endpoint shortly after a traveler searches for a route in Google Flights.
A travel platform allows the bot on availability resources but rejects attempts to reach customer account pages.
A security team receives traffic with the right user agent from an unexpected source and verifies the source before creating an allow rule.

Frequently asked questions about Google-Flights-Search-Spackle

Learn about AI visibility monitoring and how Promptwatch helps your brand succeed in AI search.

The supplied record describes it as user triggered. It fetches airline or travel-site information on behalf of an end user's Google Flights search.

Related bots

Google-Agent

Google-Agent navigates the web and performs actions upon user request, used by agents hosted on Google infrastructure such as Project Mariner.

Agent

Google-Extended

Google-Extended is a robots. txt product token, not a separate crawler that identifies itself in HTTP requests.

AI Crawler

Google Image Proxy

Google's image caching proxy service used by Gmail and other Google services to cache and serve images.

Preview

Google NotebookLM

Google NotebookLM fetches a web page when a person adds that URL as a notebook source.

AI Assistant

Google-AdWords-Express

Google-AdWords-Express is associated with a Google Ads product for small businesses.

SEO

Google-Flights-Search-Spackle