What is Google-Firebase? AI crawler guide

Google-Firebase by Google: Google Firebase AI product token reported for app-related fetches. Check its reported user-agent, robots.txt behavior, source, and verification guidance.

Google Firebase AI product token reported for app-related fetches.

What is Google-Firebase?

Google-Firebase is a user-agent token associated with Google's Firebase platform. It appears in server logs when Firebase-powered applications make server-side requests, often triggered by AI-related features within Firebase products. The token is not a general-purpose web crawler; instead, it reflects programmatic fetches initiated by app configurations or user interactions. Its presence indicates that a Firebase service is reaching out to a web resource, typically as part of an application's backend logic rather than a broad indexing effort.

What it's for

For site owners, a hit from Google-Firebase usually means that a Firebase application is configured to fetch resources from your site. This could be part of an AI feature, a cloud function, or a user-driven action within an app. It is not a traditional search crawler, so its impact is tied to how third-party developers use Firebase services that interact with your content. Understanding this can help you differentiate between organic search traffic and application-level requests.

Google-Firebase access decides whether Google can fetch your pages. Whether those pages get used in generated answers is a separate question, so track your presence in Google's AI results rather than treating crawl volume as visibility.

How to handle Google-Firebase

If you wish to block requests from this token, you can add a robots.txt rule targeting the user-agent 'Google-Firebase'. However, because the token is used by Firebase applications, blocking it may affect the functionality of apps that rely on fetching your content. Consider whether the requests are legitimate and beneficial before disallowing, as the token is not a generic crawler and may be integral to specific user-facing features.

robots.txt rule

User-agent: Google-Firebase Disallow: /

Blocking cost

Blocking Google-Firebase may prevent Firebase applications from accessing your content, potentially disrupting AI features or user experiences that depend on those fetches.

Examples

• A Firebase cloud function triggers a request to your API endpoint, appearing in logs with the user-agent 'Google-Firebase'.
• An AI feature in a mobile app built on Firebase fetches data from your site, showing the 'Google-Firebase' token.
• A user action in a Firebase-hosted web app causes a server-side fetch to your resource, logged as 'Google-Firebase'.

Related bots

• GoogleOther: Another Google general crawler to compare.
• GoogleOther-Image: Another Google general crawler to compare.
• GoogleOther-Video: Another Google general crawler to compare.
• Google-CloudVertexBot: Another Google general crawler to compare.
• bedrockbot: Also tracked as a general crawler.
• Brightbot: Also tracked as a general crawler.
• Amazonbot: Also tracked as a general crawler.
• Scrapy: Also tracked as a general crawler.
• Diffbot: Also tracked as a general crawler.
• Gemini: Google-Firebase gives crawler context for Gemini.
• Gemini 2.0: Google-Firebase gives crawler context for Gemini 2.0.