Adagio bot - Crawler
Requirements
Section titled “Requirements”Adagio platform complies with the Supply Chain Validation from IAB.
In some situations, your web server might not allow bots to connect and get the content from these files, you can whitelist our bot by:
- Allowing requests with a
User-Agentheader containingAdagiobot(our bot’s completeUser-Agentis:Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Adagiobot/1.0) Chrome/112.0.5615.137 Safari/537.36 - Allowing the CIDR range (IP adresses) listed in this file
Here’s a documentation section you can drop straight in, written for non-technical readers:
🔍 Test if Adagio’s bot can access your file
Section titled “🔍 Test if Adagio’s bot can access your file”If Adagio reports that your ads.txt or app-ads.txt cannot be crawled, you can test it yourself in less than a minute using your computer’s Terminal (Mac) or Command Prompt (Windows).
Step 1 — Open your terminal On Mac: press Cmd + Space, type Terminal, press Enter.
Step 2 — Copy and paste this command, replacing yoursite.com with your domain:
curl -v \ -H 'User-Agent: Mozilla/5.0 AppleWebKit/537.36 (KHTML, like Gecko; compatible; Adagiobot/1.0) Chrome/112.0.5615.137 Safari/537.36' \ https://yoursite.com/ads.txtStep 3 — Read the result
| What you see | What it means | What to do |
|---|---|---|
The content of your ads.txt file |
✅ Our UserAgent isn’t blocked, other issues may be at play | Contact our team to get a more elaborate investigation (e.g. checking that our bot’s IP might not be whitelisted) |
403 Forbidden |
🚫 Your server is explicitly blocking bots | Whitelist Adagio’s User-Agent or IP range (see options below) |
Empty reply from server |
🚫 Your server is silently rejecting the connection | Same — whitelist Adagio’s User-Agent or IP range |
HTTP/2 stream ... PROTOCOL_ERROR |
⚠️ Your server has a configuration issue with its protocol | Contact your hosting provider or IT team — this is a server-side bug |
Could not resolve host |
⚠️ The domain or file path is wrong | Check that ads.txt is published at the root of your domain |