EmailBison barely does search. Its site has 67 URLs, most of them "EmailBison vs X" posts, and its organic traffic is people typing its name. Its certificate logs say more than its marketing does: almost 700 hostnames show a product built as one isolated instance per customer, often re-skinned onto the agency's own domain.
Footprint
Crawled 5 October 2026 (research/seo-data/emailbison.com.json). The sitemap is complete at 67 URLs.
| Section | URLs | What it is |
|---|---|---|
| /blogs/ | 55 | 19 "emailbison-vs-*" posts, plus deliverability and infrastructure explainers |
| /features/ | 5 | Master inbox, isolated network, sequencing, lead storage, warm-up |
| Core pages | 7 | Home, pricing, developers, security, testimonials, demo, blog index |
| Total | 67 | 54 of 67 lastmod dates fall in September–October 2026 |
The comparison posts are long. EmailBison vs Instantly runs about 3,900 words with BlogPosting markup and a November 2025 date. The non-comparison posts target the vendor's positioning: "dedicated vs shared IP pools", "isolated email IP pools", "dedicated VPC email infrastructure". One case-variant URL (/blogs/emailBison-vs-groove) also returns 200, but it canonicalises to the lowercase version, so it does no harm.
What ranks
Similarweb's free estimate shows about 22K visits, 66% from organic search, across just 91 keywords (third-party panel estimate, July 2026 snapshot). The keywords are brand variants: "emailbison", "email bison", "bison email", "mailbison", "email bison login". That is navigational search, not discovery.
In our search tool (not Google; positions indicative), "emailbison review" returned The GTM Directory's comparison pages, two of EmailBison's own vs-posts (Mailshake, GMass), a Sendkit pricing page and a Prospeo review. The vs-posts do their job: they show up when someone researches the brand.
EmailBison's site exists to answer "is this legit and how does it compare" for buyers who already heard the name from another agency. The demand is generated off-site, in agency circles (Lead-gen agencies).
Programmatic and template plays
There are none. No glossary, no templates, no tools directory, no prompt library. The only repeated template is the vs-post, written for 19 named rivals, from Instantly and Smartlead to Outreach and HubSpot Sales Hub.
AEO posture
- The main site has no llms.txt and no pricing.md. robots.txt is
User-agent: * / Disallow:, which allows everything. - The docs subdomain makes up for it. docs.emailbison.com/llms.txt (5 KB) and llms-full.txt (145 KB) are generated by Mintlify. An agent asked to "integrate with EmailBison" finds the full API workflow docs. An agent asked "what does EmailBison cost" finds nothing machine-readable.
- No MCP endpoint in the docs index or the subdomain list.
- The homepage carries FAQPage markup, and the developers page documents bearer-token auth and points sample requests at
dedi.emailbison.com/api.
Subdomains
This is the interesting part. Certificate transparency logs list 698 names under emailbison.com. We describe the pattern in aggregate and do not list customer hostnames.
| Pattern | Count | What it indicates |
|---|---|---|
ee-<tenant> | 575 | One EmailEngine gateway per tenant |
ee-dedi-<tenant> | 58 | Gateways for dedicated-infrastructure tenants |
<tenant> (bare label) | ~18 | Tenant app hosts; some redirect to a login on the agency's own domain |
<tenant>-overflow, <tenant>custom | ~17 | Overflow capacity and custom-domain hooks |
| Platform hosts | ~30 | docs, dedi, monitoring, search, Sentry, prod and staging warm-up, proxies, partner portal |
The probe sampled the first 150 names alphabetically. Of those, 75 resolved and 53 returned a page. Forty-nine ee- hosts served the default landing page of EmailEngine, the self-hosted IMAP/SMTP-to-API gateway from Postal Systems OÜ. Three bare tenant hosts redirected to a login on an agency's own branded domain, which is white-label in practice (White-label and agency portals).
Stripping the ee-, dedi- and version suffixes leaves roughly 520 distinct tenant labels. Seventy-eight names carry -2 or -v3 style suffixes, which looks like re-provisioning. Certificate logs keep dead hosts, so this is an upper bound on instances ever created, not a customer count.
Two takeaways. First, the "isolated network" claim on the homepage matches the infrastructure: tenants get their own gateways, not just a workspace flag. Second, the white-label layer means many agencies' clients never see the EmailBison brand at all, so the brand earns no search demand from end users. ReachInbox and Zapmail run numbered ee hosts too, with EmailEngine pages on some (see ReachInbox: SEO teardown). The gateway is common plumbing in this tier (Sending architecture).
Off-site
- Directories, not reviews. The GTM Directory and Prospeo profile it. The company page EmailBison notes there is no G2 or Trustpilot base.
- Partner integrations. EmailGuard (placement testing) and ListKit hosts appear in the subdomain list, and OutboundSync powers the CRM sync. Partners' sites carry the backlinks.
- Competitor pages target it. Salesforge and HotHawk publish "EmailBison alternatives" pages (see EmailBison).
Weak spots
- There is nothing to rank for non-brand demand. 67 URLs cannot compete on "cold email software for agencies".
- No machine-readable pricing. Answer engines quote third-party pages, some of them stale on price.
- The architecture is public. Anyone can read the tenant footprint from certificate logs. Competitors can estimate scale and build a prospect list of its agency tenants from those names.
- White-label hides the brand from the clients who would otherwise search for it.
What this means for an entrant
- "EmailBison alternative" and "EmailBison vs Smartlead" are winnable. The incumbent has no page for "alternative" and no reviews base. A neutral, self-serve isolation offer with public pricing can take them (Comparison and alternatives pages).
- Use wildcard certificates for tenant hosts. Per-tenant certificates publish your customer list to anyone reading CT logs. A
*.yourapp.comwildcard, or tenant IDs instead of names, keeps it private (Subdomain strategy). - Docs llms.txt is free AEO. EmailBison's only machine-readable surface is its Mintlify docs. Ship docs plus an MCP server early, because agency operators increasingly run their stack through agents (AEO playbook: being the answer).
- A reply desk overlay can serve EmailBison tenants directly. They are agencies on isolated instances with an API and webhooks, which is exactly the integration surface The reply desk needs.