Safe Official docs Google Bots

Google Ads Quality (Mobile)

Operated by Google

Quick Facts

User-Agent:
AdsBot-Google-Mobile
Category:
Google Bots
Operator:
Google
Safety:
Safe
Blocking Impact:
Low - No SEO ranking impact
SEO Impact Score:
2/10
Official docs:
developers.google.com

Confirmed by the operator

Google names AdsBot-Google-Mobile on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Google Ads Quality (Mobile)?

Google Ads Quality (Mobile) is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.

Google Ads Quality (Mobile) is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Google Ads Quality (Mobile) uses the user-agent token AdsBot-Google-Mobile. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Google Ads Quality (Mobile)?

🔶 AI Visibility Trade-off - Blocking Google Ads Quality (Mobile) will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
Generally safe to allow; provides legitimate crawling value.

How to block Google Ads Quality (Mobile) with robots.txt

<code>User-agent: AdsBot-Google-Mobile</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)
User-agent: AdsBot-Google-Mobile Disallow: /
Allow all (robots.txt)
User-agent: AdsBot-Google-Mobile Allow: /
Block private only (robots.txt)
User-agent: AdsBot-Google-Mobile Disallow: /private/ Disallow: /api/ Disallow: /admin/ Allow: /
Nginx server block
# Nginx: Hard-block Google Ads Quality (Mobile) if ($http_user_agent ~* "AdsBot-Google-Mobile") { return 403 "Bot blocked"; }
Apache .htaccess
# Apache: Hard-block Google Ads Quality (Mobile) SetEnvIfNoCase User-Agent "AdsBot-Google-Mobile" bad_bot Order Allow,Deny Allow from all Deny from env=bad_bot
Meta robots tag
<meta name="robots" content="noindex, nofollow">
X-Robots-Tag header
X-Robots-Tag: noindex, nofollow

Is Google Ads Quality (Mobile) safe to allow?

Yes, Google Ads Quality (Mobile) is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Verify by reverse-DNS lookup: legitimate Google Ads Quality (Mobile) requests resolve to Google's domain.

What does Google Ads Quality (Mobile) do?

Understanding Google Ads Quality (Mobile)'s purpose helps you decide whether to allow or block it.

  • Validates pages, ads, or policy compliance
  • Performs automated quality and safety checks
  • Does not collect training data
  • No impact on search rankings
  • Generally safe to allow

Google Ads Quality (Mobile) in context

Google Ads Quality (Mobile) is a utility crawler operated by Google. In plain terms, it checks pages for an SEO, uptime or analytics service. Our database files it under Google crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 20 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Google Ads Quality (Mobile) rests on what you want from Google, not on its behaviour. How we rate safety and impact.

How site owners treat Google Ads Quality (Mobile)

Our robots.txt study of the Tranco top 10,000 did not track AdsBot-Google-Mobile as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Google Ads Quality (Mobile)'s operator does not clearly document how it treats robots.txt. Write the Google Ads Quality (Mobile) rule anyway, then confirm in your logs that its requests stop.

Google crawlers and close alternatives

Google Ads Quality (Mobile) is one of 32 Google crawlers in our database. A User-agent: AdsBot-Google-Mobile group controls Google Ads Quality (Mobile) only; the other Google tokens below need their own lines.

  • AdsBot-Google-Mobile: this crawler (Tier 3)
  • AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
  • APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
  • Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
  • FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
  • Gemini-Deep-Research: Gemini-Deep-Research, fetches a page when a person asks an assistant or app to open it (Tier 3)
  • Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
  • Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)
  • Google-CWS: Chrome Web Store Fetcher, checks pages for an SEO, uptime or analytics service (Tier 4)

To give Google Ads Quality (Mobile) the same answer as its siblings, stack User-agent: AdsBot-Google-Mobile with their lines above one set of rules; to treat Google Ads Quality (Mobile) differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes Google Ads Quality (Mobile) an unusual case: decide about it on its own merits.

We first recorded AdsBot-Google-Mobile on September 22, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule Google Ads Quality (Mobile) actually follows

Google Ads Quality (Mobile) reads exactly one group in robots.txt, the most specific one that names AdsBot-Google-Mobile, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: AdsBot-Google-Mobile
Disallow: /drafts/
  1. Find the group. Google Ads Quality (Mobile) looks for a group naming AdsBot-Google-Mobile. One exists, so it ignores User-agent: * completely.
  2. Apply only that group. It is refused /drafts/ and nothing else.
  3. The surprise. /private/ is open to Google Ads Quality (Mobile), because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.
Test yourself: does a rule under User-agent: * apply to Google Ads Quality (Mobile) if the file also has a User-agent: AdsBot-Google-Mobile group?

No. Once a group names it, Google Ads Quality (Mobile) reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Google Ads Quality (Mobile) remove your pages from AI answers?

Often, yes. Google Ads Quality (Mobile) is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Related: how AI engines choose their sources

Test yourself: is User-agent: adsbot-google-mobile the same as User-agent: AdsBot-Google-Mobile?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Google Ads Quality (Mobile)? Decide by situation

Recommended setting for Google Ads Quality (Mobile) by type of site
If you are...Recommended setting
You publish content and want AI answers to cite itLow stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI trainingBlocking it does not stop training, because Google Ads Quality (Mobile) is a utility crawler. Block the operator's training crawler instead.
You run an online shopAllow it unless it is overloading your servers.
Your server is under load from botsRate-limit before blocking. It is rated safe in our database.

Check Google Ads Quality (Mobile) on your own site

  1. Open /robots.txt on your domain and search for AdsBot-Google-Mobile. If it is not named, it follows User-agent: *.
  2. List the Disallow lines in the group Google Ads Quality (Mobile) follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
  3. Look beyond the file. A firewall or bot manager can refuse Google Ads Quality (Mobile) even when robots.txt allows it, and that never shows in the file.
  4. Run our AI bot access checker to see how Google Ads Quality (Mobile) and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Google Ads Quality (Mobile)

The errors we see most often with Google Ads Quality (Mobile) in the files and firewalls we test:

  1. Treating Google Ads Quality (Mobile) as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
  2. Relying on robots.txt alone when Google Ads Quality (Mobile) is rated caution or aggressive. Back the rule with a server-side block.
  3. Blocking Google Ads Quality (Mobile) by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check Google Ads Quality (Mobile) from outside after every change.

Spotting Google Ads Quality (Mobile) in your logs

robots.txt says what Google Ads Quality (Mobile) may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "AdsBot-Google-Mobile" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "AdsBot-Google-Mobile" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Google Ads Quality (Mobile) user-agent, so confirm the source before acting on a match:

  • AdsBot-Google-Mobile: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Google Ads Quality (Mobile) request with caution.

Frequently Asked Questions

What is the official user-agent string for Google Ads Quality (Mobile)?
The official user-agent string for Google Ads Quality (Mobile) is: AdsBot-Google-Mobile. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Google Ads Quality (Mobile) by performing a reverse-DNS lookup on the source IP.
Is Google Ads Quality (Mobile) safe?
Yes, Google Ads Quality (Mobile) is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.
Will blocking Google Ads Quality (Mobile) hurt my SEO?
🔶 AI Visibility Trade-off - Blocking Google Ads Quality (Mobile) will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.
How do I block Google Ads Quality (Mobile) in robots.txt?
Add the following lines to your /robots.txt file:
User-agent: AdsBot-Google-Mobile
Disallow: /

This instructs Google Ads Quality (Mobile) not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).
Does Google Ads Quality (Mobile) respect robots.txt?
Google Ads Quality (Mobile) is operated by Google and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.
How do I verify if Google Ads Quality (Mobile) is crawling my site?
Search your web server access logs for the string AdsBot-Google-Mobile (case-insensitive: grep -i "AdsBot-Google-Mobile" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Related Bots

WhatsApp us