Google-Firebase
Few readable files block Google-Firebase in October 2026, at 38 sites or 0.6%. The community reference lists its operator as Google.
Who runs Google-Firebase?
| Fact | Google-Firebase reference entry |
|---|---|
| Operator | “Google” |
| Purpose | “Used as part of AI apps developed by users of Google's Firebase AI products.” |
| Does Google-Firebase obey robots.txt? | “Unclear at this time.” |
| Frequency | “Unclear at this time.” |
| Cloudflare managed list for Google-Firebase | No |
These facts quote the stored community ai.robots.txt reference.
“Supports Google's Firebase AI products.”
Here, the listed use is supporting AI apps developed with Firebase. Reading a page to answer a user has a different purpose from building a model with it. Owners may allow the requested visit.
How many sites block it?
The name occurs in 43 out of 6,171 readable files, a 0.7% share. Across the full sample, the whole-site Disallow: / block count is 38, or 0.6%. Files without that ban number 6,133.
For the top 1,000 ranks, its name appears in 17 files out of 552, or 3.1%. Whole-site blocks total 15. Blocking is more common among the leading sites, at 2.7%. Lower in the ranking, blocking reaches 23 files out of 5,619, a 0.4% share.
| Readable files | Named by | Named share | Blocked by | Blocked share |
|---|---|---|---|---|
| Google-Firebase, all ranks | 43 | 0.7% | 38 | 0.6% |
| Google-Firebase, top 1,000 | 17 | 3.1% | 15 | 2.7% |
| Google-Firebase, remaining ranks | 26 | 0.5% | 23 | 0.4% |
This total covers whole-site bans recorded for this name. A blanket User-agent: * rule alone is outside this measure. The overlap between naming and blocking is 38 files. Naming without a whole-site ban accounts for 5, and 6,128 files never name it. We ignore capitalization and repeated names.
How to block or allow it
Put these in robots.txt at the site root. Per the robots.txt standard, a group naming Google-Firebase takes precedence over User-agent: *.
Block the whole site
User-agent: Google-Firebase
Disallow: /Allow access
User-agent: Google-Firebase
Allow: /It's the 125th most-named crawler of the 171 we counted in the crawler index.
Which other crawlers does this operator run?
- Google-CloudVertexBot
- Google-Extended
- GoogleAgent-Mariner
- GoogleOther
- GoogleOther-Image
- GoogleOther-Video
How we counted
For Google-Firebase, our 19 October 2026 collection used Tranco’s top 10,000 sites. Requests could run for 8 seconds, with a 262,144-byte file limit. Only available files we could read enter the percentages. Repeat readings are included, using scripts/robots_2026_08_06.py (robots.py at app commit 07104ff). See the full survey method.
Common questions
Can a file name it and still allow it?
The 43 files that mention its name do not all record a whole-site ban. Those without one total 5.
How do the shares compare by rank?
At the top of the ranking, 3.1% of readable files name it and 2.7% block it. Across all ranks, those shares are 0.7% and 0.6%.
What other entry is close in the index?
MistralAI-Index is named by 43 files and blocked by 54, or 0.9%. For this crawler, 43 files name it and 38 block it, a 0.6% share.