Same category
vouchgeo.com
Tracks how AI assistants mention a brand across multi-question buying conversations

Done-for-you Google Workspace and Microsoft 365 inboxes on your own domains for cold email
PureMail is a done-for-you cold email infrastructure service. It provides Google Workspace and Microsoft 365 mailboxes on the customer's own domains, with SPF, DKIM, DMARC and MX records configured and every inbox connected to a sequencer such as Instantly or Smartlead. The homepage states that setup takes about four hours and that inboxes start from $2.90 each. The service is aimed at outbound and cold email teams that need sending inboxes. The input does not describe a team, customers in detail, or an account signup process beyond the order links.
“PureMail is a done-for-you cold email infrastructure service that provides Google Workspace and Microsoft 365 mailboxes on a customer's own domains, set up with SPF, DKIM, DMARC and MX records and connected to sequencers, from $2.90 per inbox.”
Simulated from the response GoodForBotsBot received on , not a live answer from any AI assistant.
The homepage text covers cold email infrastructure, Google Workspace and Microsoft 365 inboxes, DNS authentication, setup steps, and a comparison of buying inboxes directly, using SMTP providers, and using a done-for-you provider. The starting price of $2.90 per inbox, the roughly four-hour setup time, and a claim of 59% less than Google or Microsoft retail appear as plain text. Review counts from G2 and SourceForge and a figure of 70,000+ inboxes are also present. The llms.txt file adds tiered per-inbox prices of $3.30 for 10, $3.10 for 30 to 100, and $2.90 for 101 or more, a 10-inbox minimum, monthly billing, and a list of product, comparison and directory pages. The JSON-LD adds the organisation name, a support email address, and a set of cold email FAQ answers. The homepage excerpt itself contains no contact address, and the input was truncated before the rest of the page.
A model reading only this input cannot see the full pricing page, so plan details beyond the three per-inbox tiers are unknown. It cannot tell the support hours or channels beyond what the JSON-LD and llms.txt state. The truncated homepage leaves its later sections unread, including any terms beyond the listed ones.
Good for Bots report
robots.txt is present and valid. robots.txt is valid, with 1 user-agent group.
Sitemap is present and parses. Sitemap declared in robots.txt, listing at least 200 URLs.
Describes itself to machines with schema.org JSON-LD. 3 of 4 pages read pass; 1 partly. The page at /directory/category/inbox-providers/ declares BreadcrumbList, ItemList but names none of them, so the markup asserts that something exists without saying what.
Content is marked up so a reader can find it. All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
Navigation links expose usable destinations. 18 of 18 assessed homepage navigation links expose usable destinations.
Links and buttons have accessible names. 318 of 318 assessed homepage links and buttons have a nonempty accessible name.
Form fields have names and recognizable semantics. 10 of 10 assessed homepage form fields meet the static naming and field-semantics checks.
Controls expose roles, states and relationships. 405 of 405 assessed homepage controls and role declarations meet the static role, state and relationship checks.
Each page declares one usable canonical URL. All 4 pages read pass. The homepage declares itself as its canonical URL.
Section links reach an element on the page. Both pages read pass. The homepage has 2 section links, and every one reaches an element on the page.
llms.txt is present and well formed. /llms.txt is well formed: 210 links across 6 sections.
llms.txt is descriptive, not a bare link list. /llms.txt is descriptive: a summary plus descriptions on 99% of links.
Serves markdown at its own URL. No /llms-full.txt and no markdown versions linked from llms.txt. +12.5 with its prompt.
Serves markdown when asked for it. None of the 4 pages read pass. Asking the homepage for markdown still returns text/html. +10 with its prompt.
States a position on AI crawlers. robots.txt names no AI crawlers, so every operator has to guess. +5 with its prompt.
Declares AI usage preferences. No usage declaration found in robots.txt or the final successful homepage response header. +2.5 with its prompt in Pro.
Advertises machine-readable resources with typed links. None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere. +1.3 with its prompt in Pro.
Earned
The whole readable base above the line, 19 of the 50 agent-layer points below it.
3 prompts away
Still open
Behind the checks below, with prompts in Pro.
For the owner of puremail.ai
They are in the owner view, ready to paste into Claude Code, Cursor or Codex, beside the badge and rescans.
Select a check to see what we found and how it is graded.
Readable base
50 / 50
3.3 of 3.3 points.
robots.txt is valid, with 1 user-agent group.
8.3 of 8.3 points.
Sitemap declared in robots.txt, listing at least 200 URLs.
8.3 of 8.3 points.
3 of 4 pages read pass; 1 partly. The page at /directory/category/inbox-providers/ declares BreadcrumbList, ItemList but names none of them, so the markup asserts that something exists without saying what.
10 of 10 points.
All 4 pages read pass. The homepage marks its content root, its heading outline and its landmarks.
4.2 of 4.2 points.
318 of 318 assessed homepage links and buttons have a nonempty accessible name.
2.5 of 2.5 points.
10 of 10 assessed homepage form fields meet the static naming and field-semantics checks.
2.5 of 2.5 points.
405 of 405 assessed homepage controls and role declarations meet the static role, state and relationship checks.
1.7 of 1.7 points.
All 4 pages read pass. The homepage declares itself as its canonical URL.
0.8 of 0.8 points.
Both pages read pass. The homepage has 2 section links, and every one reaches an element on the page.
Agent layer
18.8 / 50
11.3 of 11.3 points.
/llms.txt is well formed: 210 links across 6 sections.
7.5 of 7.5 points.
/llms.txt is descriptive: a summary plus descriptions on 99% of links.
0 of 12.5 points.
No /llms-full.txt and no markdown versions linked from llms.txt.
0 of 10 points.
None of the 4 pages read pass. Asking the homepage for markdown still returns text/html.
0 of 5 points.
robots.txt names no AI crawlers, so every operator has to guess.
0 of 2.5 points.
No usage declaration found in robots.txt or the final successful homepage response header.
0 of 1.3 points.
None of the 4 pages read pass. The homepage's links are all ordinary page furniture; none point an agent anywhere.
Penalties
− 0
Penalty: 0 of 15 points.
Our crawler reaches the page without being challenged.
Penalty: 0 of 20 points.
Nothing on the homepage tells a crawler to skip it or to withhold its snippet.
Penalty: 0 of 25 points.
The captured homepage HTML contains 3813 content words; completeness is not assessed.
Penalty: 0 of 25 points.
robots.txt allows every known search and user-fetch crawler to reach the homepage.
Penalty: 0 of 10 points.
The homepage is served over HTTPS and returns HTTP 200.
Penalty: 0 of 3 points.
The homepage provides both a non-empty title and meta description.
Penalty: 0 of 3 points.
The homepage is reached in 0 redirects.
Penalty: 0 of 3 points.
The homepage reached a plain crawler in 213 ms.
Agent capabilities
0 of 11 · no points
Each one found adds +1 to the badge.
Adds +1 to the badge when found.
No API catalog published.
Adds +1 to the badge when found.
No /auth.md published.
Adds +1 to the badge when found.
No AI Catalog published, so no MCP server card can be discovered.
Adds +1 to the badge when found.
No A2A Agent Card at /.well-known/agent-card.json, and none listed in an AI Catalog.
Adds +1 to the badge when found.
No usable Agent Skills index was found at either well-known path or in the AI Catalog.
Adds +1 to the badge when found.
No WebMCP declarations were found in the collected HTML or inline scripts. External scripts were not inspected.
Adds +1 to the badge when found.
No Web Bot Auth key directory at /.well-known/http-message-signatures-directory.
Adds +1 to the badge when found.
No HTTP 402 payment challenge on the homepage or robots.txt, and no manifest at /.well-known/x402.
Adds +1 to the badge when found.
No ACP discovery declaration established at /.well-known/acp.json.
Adds +1 to the badge when found.
No UCP discovery declaration established at /.well-known/ucp.
Adds +1 to the badge when found.
No public AMP discovery declaration established. Private or hidden agents may not advertise one to our crawler.
It decides which conditional checks apply. “Not established” means no proof in what we read, not proof of absence.
Access & usage policy
GoodForBotsBot received HTTP 200 via a direct request. No indexing restriction was observed in the supported homepage directives.
Sampled URL: https://puremail.ai/
Rules for the sampled URL, read the way RFC 9309 reads them. These are declarations, not access tests.
| Crawler | Purpose | Declared access | Score effect | Rule that applies |
|---|---|---|---|---|
| Our crawler, measured | ||||
| GoodForBotsBotGood for Bots | Site diagnostics | FetchedHTTP 200, direct | Not scored | robots.txt admitted our crawler |
| Search and AI answers | ||||
| OAI-SearchBotOpenAI | AI search | Allowed | None | Not named; User-agent: * applies |
| Claude-SearchBotAnthropic | AI search | Allowed | None | Not named; User-agent: * applies |
| PerplexityBotPerplexity | AI search | Allowed | None | Not named; User-agent: * applies |
| MistralAI-IndexMistral | AI search | Allowed | None | Not named; User-agent: * applies |
| Kimi-SearchBotMoonshot AI | AI search | Allowed | None | Not named; User-agent: * applies |
| Amzn-SearchBotAmazon | AI search | Allowed | None | Not named; User-agent: * applies |
| Meta-WebIndexerMeta | AI search | Allowed | None | Not named; User-agent: * applies |
| ExaSearchBotExa | AI search | Allowed | None | Not named; User-agent: * applies |
| AIWebIndexLyrenth | AI search | Allowed | None | Not named; User-agent: * applies |
| DuckAssistBotDuckDuckGo | AI search | Allowed | None | Not named; User-agent: * applies |
| ShapBotParallel | AI search | Allowed | None | Not named; User-agent: * applies |
| YandexAdditionalYandex | AI search | Allowed | None | Not named; User-agent: * applies |
| GooglebotGoogle | Search | Allowed | Not scored | Not named; User-agent: * applies |
| BingbotMicrosoft | Search | Allowed | Not scored | Not named; User-agent: * applies |
| , all allowed | ||||
| Fetches a person asked for | ||||
| ChatGPT-UserOpenAI | User fetch | Allowed | None | Not named; User-agent: * applies |
| Claude-UserAnthropic | User fetch | Allowed | None | Not named; User-agent: * applies |
| Perplexity-UserPerplexity | User fetch | Allowed | None | Not named; User-agent: * applies |
| MistralAI-UserMistral | User fetch | Allowed | None | Not named; User-agent: * applies |
| Kimi-UserMoonshot AI | User fetch | Allowed | None | Not named; User-agent: * applies |
| Amzn-UserAmazon | User fetch | Allowed | None | Not named; User-agent: * applies |
| Diffbot-UserDiffbot | User fetch | Allowed | None | Not named; User-agent: * applies |
| Meta-ExternalFetcherMeta | User fetch, Agent | Allowed | None | Not named; User-agent: * applies |
| , all allowed | ||||
| Model training, never scored | ||||
| GPTBotOpenAI | AI training | Allowed | None | Not named; User-agent: * applies |
| ClaudeBotAnthropic | AI training | Allowed | None | Not named; User-agent: * applies |
| MistralAI-TrainingMistral | AI training | Allowed | None | Not named; User-agent: * applies |
| KimiBotMoonshot AI | AI training | Allowed | None | Not named; User-agent: * applies |
| AI2BotAi2 | AI training | Allowed | None | Not named; User-agent: * applies |
| Applebot-ExtendedApple | AI training | Allowed | None | Not named; User-agent: * applies |
| Webzio-extendedWebz.io | AI training | Allowed | None | Not named; User-agent: * applies |
| Google-ExtendedGoogle | AI training, Grounding | Allowed | None | Not named; User-agent: * applies |
| Meta-ExternalAgentMeta | AI training, Product improvement | Allowed | None | Not named; User-agent: * applies |
| AmazonbotAmazon | AI training, Product improvement | Allowed | None | Not named; User-agent: * applies |
| CCBotCommon Crawl | Open dataset, AI training | Allowed | None | Not named; User-agent: * applies |
| , all allowed | ||||
| Agents, extraction and others | ||||
| FirecrawlAgentFirecrawl | Extraction | Allowed | Not scored | Not named; User-agent: * applies |
| WebzioWebz.io | Extraction | Allowed | Not scored | Not named; User-agent: * applies |
| , all allowed | ||||
The robots.txt groups behind this table
User-agent: * Allow: /
https://puremail.ai/robots.txt
How to read this table
Each row says what robots.txt asks of that crawler. It does not show whether the crawler obeys, or how a firewall treats it. We measured only our own request.
Refusing search or user-fetch crawlers costs points under AI crawler access. Refusing training crawlers costs nothing.
Indexing directives, Content-Signal and AIPREF preferences are in the tabs below.
GoodForBotsBot received HTTP 200 via a direct request.
Declared allow · Scan admission
The recorded robots admission decision allowed our crawler to proceed.
GoodForBotsBot admission along the homepage request chain
https://puremail.ai/
Observed · Direct request
Our request received HTTP 200. A status alone does not identify a WAF.
Our recorded direct transport attempt; intermediate attempt URLs are not retained
https://puremail.ai
HTTP 200
Observed · Final homepage response
GoodForBotsBot received HTTP 200 via a direct request.
homepage response
https://puremail.ai/
HTTP 200 Transport: direct
Serves the homepage over HTTPS with HTTP 200Serves our crawler without a challenge
No indexing restriction was observed in the supported homepage directives.
Not observed · Homepage directives
No indexing restriction was observed in the supported homepage directives.
homepage response
https://puremail.ai/
Scoped instructions were recorded; see their values and recipient support below.
Observed · Meta robots
This declares a snippet instruction for the named recipients. The value is not a claim about citation by every AI operator.
This response only
https://puremail.ai/
max-snippet: -1
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: search; applicable robots group/path and this response's header
https://puremail.ai/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: ai-use; applicable robots group/path and this response's header
https://puremail.ai/
No applicable preference for this use was established.
Unstated · AIPREF Content-Usage
No applicable AIPREF preference was established for this purpose.
Purpose: train-ai; applicable robots group/path and this response's header
https://puremail.ai/
In its category
The prompts in the owner view would take PureMail to 96, 3rd in its category.
To the prompts →Category average 58. The percentile appears once the catalogue holds a few hundred sites.
Every scan is kept. Pro draws the history as a chart →
The homepage and up to three pages from the sitemap and homepage links. Structured data, page structure, Markdown negotiation and typed links check each page read and take the median page; other checks read the homepage.
More like PureMail:SaaS & Web AppsMarketingSalesB2B
Same category
vouchgeo.com
Tracks how AI assistants mention a brand across multi-question buying conversations
Same category
talhabashir.com
Free online calculators and tools for US taxes, mortgages, business and personal finance
Also B2B
submityourstartup.now
Free weekly launch directory where early-stage founders list startups and are ranked by votes
Also Marketing
brivoy.com
Community site where makers launch new products and early adopters discover them
Also Marketing
contentspilot.com
AI co-pilot that plans, drafts and schedules Instagram carousels and posts in brand style
Do you run puremail.ai? Open the owner view → Removing the listing is free. Remove →