PlayStore-Google is a bot in the other bots category, operated by Google.
PlayStore-Google sends a normal Chrome user agent ending in PlayStore-Google from Google's rate-limited proxy hosts. Google does not document it; the name points to the Google Play Store fetching pages linked from app listings, such as developer websites.
Bots that do not fit the other categories. Review their purpose and allow only what you need.
Anyone can copy a user agent string. Transfon Security also checks where each request comes from, so a request that claims to be a known crawler but comes from the wrong network is treated as a fake, not as the real crawler.
We have not confirmed whether PlayStore-Google follows robots.txt. Add a rule, then check your logs to see that it stopped. robots.txt is a plain text file at the root of your domain, such as https://example.com/robots.txt.
User-agent: PlayStore-Google Disallow: /
User-agent: PlayStore-Google Disallow: /private/ Disallow: /search
User-agent: PlayStore-Google Allow: /blog/ Disallow: /
User-agent: PlayStore-Google Allow: / User-agent: * Disallow: /
User-agent: PlayStore-Google group, PlayStore-Google ignores your User-agent: * rules, so repeat any that should still apply.PlayStore-Google from PlayStore-Google's user agent; check Google's own documentation if it publishes a different robots.txt name.Treat robots.txt as a statement of your policy, and enforce it where requests arrive.
Allow PlayStore-Google if it is a service you use, and keep its visits out of page views and ad requests either way.
Transfon Security for publishersPlayStore-Google is not a person. Exclude it from campaign and conversion data so reports reflect real visitors.
Transfon Security for advertisersAllow PlayStore-Google only if it works for your store, and keep it away from cart and checkout.
Transfon Security for e-commerceIf PlayStore-Google is a service you use, allow it on the endpoints it needs and block it elsewhere.
Transfon Security for SaaS and APIsrobots.txt is a request, not an enforcement. Transfon Security shows PlayStore-Google by name in the Top Bots report, so you can see how often it visits and which pages it reads. Block or allow it with a User Agent rule, or slow it down with a rate limit decision rule.
Transfon Security
PlayStore-Google is a bot in the other bots category, operated by Google. PlayStore-Google sends a normal Chrome user agent ending in PlayStore-Google from Google's rate-limited proxy hosts. Google does not document it; the name points to the Google Play Store fetching pages linked from app listings, such as developer websites.
We have not confirmed whether PlayStore-Google follows robots.txt. Add a robots.txt rule, then check your logs to see that it stopped, and block it by user agent if it did not.
Add "User-agent: PlayStore-Google" followed by "Disallow: /" to the robots.txt file at the root of your site. To enforce it, block requests whose user agent contains "PlayStore-Google" at your WAF. In Transfon Security that is one User Agent block rule.
No. robots.txt is voluntary, so PlayStore-Google may not follow it, and anyone can send PlayStore-Google's user agent, so a fake PlayStore-Google ignores your rule. Enforce the rule where requests arrive, at your WAF, and check the source network.
Bots that do not fit the other categories. Review their purpose and allow only what you need.
Transfon Security identifies every bot in this directory in your traffic reports, flags fake search crawlers, and lets you allow, block or rate limit each bot.
Privacy, security, monetization, and performance insights. A few emails a month, no spam.