For the complete documentation index, see llms.txt. Every page on this site is also served as Markdown: append `.md` to any URL, or send `Accept: text/markdown`.
Skip to content
Attensira LogoAttensira
Book a demo

Bots

Advertising bots

Advertising bots check pages for ad systems. AdsBot-Google and AdsBot-Google-Mobile review Google Ads landing pages, Mediapartners-Google reads pages that show AdSense ads, and OAI-AdsBot visits pages submitted as ads on ChatGPT. Google's three ignore the wildcard robots.txt group, so a blanket block leaves them running. None of them builds a search index.

Start freeBook a demo

7 days free · card required

Advertising bots4 agents
agents documented
4
publish IP ranges or reverse DNS
4 of 4
requests to attensira.com, 30 days
0
of n=143,601 AI crawler requests

One of the category's rules, from the AdsBot-Google entry, per the operator's documentation; the other 3 are on their own entries.

User-agent: AdsBot-GoogleAllow: /
Researcher agentResearcherOperator documentation and our AI traffic board (Attensira MCP) ·

Which advertising agents are documented?

Checks ad landing pages, or reads pages that show ads, for an ad product. Separate from search indexing, so a rule here is an advertising decision.

Which advertising bots fetched attensira.com in the last 30 days?

None of these agents had a request filed on attensira.com in the window. User agents as sent, not checked against address lists.

See which crawlers visit your site.

AI traffic · attensira.com0 of 4 seen
Requests to attensira.com by agent, last 30 days to 4 Oct 2026, and attensira.com's robots.txt rule for each
AgentRequestsOur robots.txt
AdsBot-Google-Mobile0No named group
AdsBot-Google0No named group
Mediapartners-Google0No named group
OAI-AdsBot0No named group
AI traffic board, read over the Attensira MCP · · n=143,601 requests

How do the advertising bots compare?

Each row is transcribed from the operator's own documentation. The attensira.com column is ours: what our live robots.txt says to the agent.

Sorted by verify by, low to high.

  • OAI-AdsBot

    Operator
    OpenAI
    robots.txt
    Not stated
    Verify by
    IP ranges
    attensira.com
    No named group

  • AdsBot-Google-Mobile

    Operator
    Google
    robots.txt
    Named groups only
    Verify by
    IP ranges + reverse DNS
    attensira.com
    No named group

  • AdsBot-Google

    Operator
    Google
    robots.txt
    Named groups only
    Verify by
    IP ranges + reverse DNS
    attensira.com
    No named group

  • Mediapartners-Google

    Operator
    Google
    robots.txt
    Named groups only
    Verify by
    IP ranges + reverse DNS
    attensira.com
    No named group

Each row read from the operator's documentation, 3 Sep 2026 to 4 Sep 2026.

Why does a 'block all bots' rule not stop them?

Google documents AdsBot-Google, AdsBot-Google-Mobile and Mediapartners-Google as special-case crawlers that ignore the global user agent (*). A group has to name the token to reach them. The exemption exists because these agents work under an agreement between your site and the ad product: you bought the ads, or you joined AdSense.

OpenAI states no robots.txt position for OAI-AdsBot, and says it only visits pages submitted as ads on ChatGPT and that its data is not used for training. A group naming it records a preference rather than a documented control.

VerificationAdsBot-Google-Mobile
Reverse DNS ends in
*.google.com
IP range file
special-crawlers.json

A special-case crawler: it resolves under rate-limited-proxy-*.google.com, not googlebot.com, and is listed in special-crawlers.json. A header that gets past ad blockers and bot mitigation on landing pages is worth forging, so verify before granting an exception, and forward-resolve the hostname back to the original address. The AdsBot-Google-Mobile entry, and the method step by step: how to verify a crawler.

Researcher agentResearcherTranscribed from Google documentation ·

What does blocking an ad checker cost?

If you advertise on Google, blocking AdsBot degrades the quality assessment of your own landing pages. Blocking Mediapartners-Google is a decision about your own AdSense inventory. If you run no ads, the documented reason for these visits does not apply to you, which makes a request under these tokens worth verifying before you trust it.

Google's ad agents verify differently from Googlebot: they resolve under rate-limited-proxy hostnames on google.com and are listed in special-crawlers.json. An allowlist built around googlebot.com rejects real AdsBot traffic. OpenAI publishes a separate range file for OAI-AdsBot, so a verified address tells an ad review apart from a training or search fetch.

VerificationMediapartners-Google
Reverse DNS ends in
*.google.com
IP range file
special-crawlers.json

A special-case crawler, so it resolves under the rate-limited-proxy mask on google.com rather than googlebot.com, and appears in special-crawlers.json rather than common-crawlers.json. The Mediapartners-Google entry, and the method step by step: how to verify a crawler.

Researcher agentResearcherTranscribed from Google documentation ·

What else do people ask?

What are advertising bots?
Agents that fetch pages for an ad system: to check the quality of a landing page you advertise, or to read a page so relevant ads can be served on it. They are separate tokens from the search crawlers and have no documented search-indexing role.
Does blocking AdsBot-Google affect my Google rankings?
Google documents AdsBot-Google as checking the quality of Google Ads landing pages and Googlebot as the crawler that builds the search index. They are separate tokens, so a rule naming AdsBot is an advertising decision, not a search one.
Do AdsBot rules need their own group?
Yes. Google states that its special-case ad crawlers ignore the wildcard group, so rules under User-agent: * never reach them. Write a group that names AdsBot-Google, and a separate one for AdsBot-Google-Mobile.
Should I block OAI-AdsBot?
Only if you do not advertise on ChatGPT. OpenAI says it visits only pages submitted as ads there and does not use its data for training, but states no robots.txt position, so a Disallow is a preference rather than a documented control.

Where do these facts come from?

4 claims on this page, each with the page it was read from; last checked .

  1. Google documents that crawling preferences addressed to the AdsBot-Google-Mobile user agent affect Google Ads' ability to check web page ad quality.

    developers.google.com · retrieved

    “affect Google Ads' ability to check”

  2. Google documents its special-case crawlers, giving AdsBot as the example, as ignoring the global robots.txt user agent with the ad publisher's permission.

    developers.google.com · retrieved

    “ignores the global robots.txt user agent (*) with the ad publisher's permission”

  3. Google documents special-case crawlers as using the reverse-DNS hostname form rate-limited-proxy-***-***-***-***.google.com and publishes their address ranges in special-crawlers.json.

    developers.google.com · retrieved

  4. OpenAI documents OAI-AdsBot as the agent used to validate the safety of web pages submitted as ads on ChatGPT.

    developers.openai.com · retrieved

    “used to validate the safety of web pages submitted as ads on ChatGPT”

Want whatever it takes to win the answer?

Start freeBook a demo

7 days free · card required