Scan report ·

hims.com

Invisible. Agents can't meaningfully engage with this storefront.

E
26 / 100
Invisible
Aisle Storefront · Simulated twin
This scan found 6 weaknesses an agent would hit at checkout, so we planted the same mechanisms in a simulated storefront. Watch an agent shop it, or send your own.
Aisle Max · Remediation packet
Every fix this scan flagged, one card at a time: ranked by points per effort, with copy-paste snippets, per-fix downloads, and a plan your AI coding agent can execute.
Discoverability
D
8 / 20
Machine Readability
E
1 / 20
Transactability
E
4 / 20
Agent Posture
D
7 / 15
Trust Signals
E
2 / 10
Agent-Native Content
E
4 / 15

Narrative

Hims scores 26 out of 100 and lands in the Invisible band, which is the correct verdict for a site whose front door literally returned a 403 to our scanner. The paradox is that Hims did the polite thing in robots.txt, explicitly allowing GPTBot, ClaudeBot, PerplexityBot, Google-Extended, CCBot, anthropic-ai, Applebot-Extended, Bytespider, and Amazonbot, and then blocked those same agents at the edge. It is the online equivalent of putting a welcome mat outside a locked door. Until that contradiction is resolved, nothing else in this report matters.

The single most expensive finding is bot detection posture. Out of 32 fetches, 21 returned 403 and only 8 succeeded, a 66 percent block rate that torched the entire agent posture dimension. The forbidden list is telling: https://hims.com/, /cart, /terms, /privacy, /about, /sitemap.xml, /.well-known/ai-plugin.json, and /llms.txt were all denied. This is not selective defense against scrapers, this is a blanket denial that includes the very files an agent needs to understand who Hims is and what it sells. The downstream damage is enormous, because it cascaded into failures on structured data, sitemap quality, price transparency, merchant verifiability, and return policy checks that could not even be evaluated.

Second, the sitemap situation. https://hims.com/sitemap.xml returned 403, so the zero score on sitemap quality is not a content problem but an access problem. The robots.txt declares https://www.hims.com/sitemap.xml (note the www), which may resolve differently, but an agent that starts from the apex domain will hit the wall. Zero out of 4 points, and zero discoverability for any crawler that plays by the rules.

Third, structured product data is nonexistent. Zero of 10 sampled URLs returned Product schema, zero returned Offer schema, and the sample includes drug information pages like /drugs/info/biotin and comparison pages like /drugs/compare/rogaine-vs-minoxidil where Product or Drug schema would be entirely appropriate. Even the two pages where price appeared in rendered HTML ("less than $2/day" on the lidocaine comparison, "about $8" on biotin) surfaced it as prose inside a paragraph rather than as marked-up Offer data. An agent trying to compare Hims to a competitor has nothing structured to grab.

Fourth, the transactability collapse. Cart and checkout both returned 403, which zeroed out checkout flow structure, guest checkout, and price transparency. The one bright spot, a partial credit on machine-native payment rails and full credit on Shopify cart API pattern detection, is essentially the scanner inferring what should be possible under the hood. That capability is invisible to any agent that cannot get past the front door.

Finally, the content quality is actually the good news buried in this report. Specification completeness, conversational descriptions, and decision-support metadata all scored in the partial band, with high-signal quotes from the sertraline and biotin pages. Hims writes for humans well, which means the raw material for agent-native content exists. It is just wrapped in a bot wall and stripped of schema.

The biggest opportunity is straightforward: whitelist the AI crawlers you already told robots.txt you welcome, then add Product and Offer schema to the drug pages, and Hims moves from Invisible to competitive in a single sprint.

DDiscoverability

Robots, sitemap, agent endpoints. gappy.

AI crawler posture: 6/6
https://hims.com/robots.txt
1.1 · 6/6
×
Structured product data coverage: 0/6
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
1.2 · 0/6
×
Sitemap quality: 0/4
https://hims.com/sitemap.xml
How to fixPro
1.3 · 0/4
!
Agent-specific endpoints: 2/4
https://hims.com/.well-known/ai-plugin.json
How to fixPro
1.4 · 2/4

EMachine Readability

Schema coverage, raw-HTML price, inventory, variants. broken.

×
Price in raw HTML: 0/8
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
2.1 · 0/8
×
Product attributes structured: 0/6
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
2.2 · 0/6
×
Inventory signals: 0/5
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
2.3 · 0/5
Variant handling: 1/1
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
2.5 · 1/1

ETransactability

Checkout flow, guest, transparency, payment rails, cart API. broken.

×
Checkout flow structure: 0/6
How to fixPro
3.1 · 0/6
×
Guest checkout availability: 0/4
How to fixPro
3.2 · 0/4
×
Price transparency signals: 0/4
How to fixPro
3.3 · 0/4
!
Machine-native payment rails: 1/3
How to fixPro
3.4 · 1/3
Cart API accessibility: 3/3
3.5 · 3/3

DAgent Posture

Bot detection, CAPTCHA, rate limiting, stated agent policy. gappy.

×
Bot detection aggressiveness: 0/6
How to fixPro
4.1 · 0/6
CAPTCHA prevalence: 4/4
4.2 · 4/4
Rate limiting posture: 3/3
4.3 · 3/3
×
Stated agent policy: 0/2
How to fixPro
4.4 · 0/2

ETrust Signals

Return policy, merchant verifiability, price history, third-party anchors. broken.

×
Return policy machine-readable: 0/3
How to fixPro
5.1 · 0/3
×
Merchant verifiability: 0/3
How to fixPro
5.2 · 0/3
Price history signals: 2/2
5.3 · 2/2
×
Third-party trust anchors: 0/2
How to fixPro
5.4 · 0/2

EAgent-Native Content

Specs, descriptions, decision support, delivery, stability, absence of manipulation. broken.

!
Specification completeness: 2/4
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
6.1 · 2/4
!
Conversational product descriptions: 1/2
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
6.2 · 1/2
!
Decision-support metadata: 1/3
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
6.3 · 1/3
×
Delivery date transparency: 0/2
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
6.4 · 0/2
×
Price stability signals: 0/2
sample · https://www.hims.com/drugs/compare/rogaine-vs-minoxidil
How to fixPro
6.5 · 0/2
×
Absence of manipulation tactics: 0/2
How to fixPro
6.6 · 0/2