Basic scanSoftware and storefront · Storefront property/Scanned 7 Sept 2026, 19:49 UTC/1 browser pass
seconddoor.io
A software and storefront hybrid with strong machine discoverability but no agent checkout path for product purchases.
Older scan
This report was produced by an earlier version of the scanner. Some findings may not match how the site is measured now.
Narrow. Both audiences hit roughly the same walls.
No issues were written
This scan did not gather enough evidence to rank what is costing you most. The dimension scores below reflect only what was actually observed. Running the scan again usually fixes it.
This is a basic scan, so it raises the three issues the deterministic evidence supports. A deep scan sends two agents over the site and raises up to ten, each with cited evidence and the screens to prove it.
Deep scans need an account. Accounts are free.
A deep scan walks the site with two agents, records cited evidence and screenshots, and keeps a mission timeline. It comes with the paid plans. Making an account costs nothing and gives you one basic scan a month.
Get full access
The score and the audit trail stay public. The evidence and the files open with an account.
For finding out where you stand.
- 1 basic scan a month
- 3 prioritised fixes, with evidence
- No watched domains
- Your latest report
For one site you care about.
- A deep scan every week, another when your site changes, and 3 on demand
- Every fix the scan finds, not three
- Fixes reopen when a release undoes them
- 1 watched domain, checked every day
- Competitor comparison, 2 per domain
- 12 months of history
For a portfolio and a release cadence.
- A deep scan every week, another when your site changes, and 10 on demand
- Every fix the scan finds, not three
- Fixes reopen when a release undoes them
- 5 watched domains, checked every day
- Competitor comparison, 5 per domain
- All history
What the agents checked
The audit trail behind every number above. Not measured is not zero.
Machine discoverability
Robots.txt names and allows 14 AI crawlers including GPT, Claude, Perplexity and Gemini. A real browser is served normally. Sitemap lists 91 URLs. Homepage carries 6 schema.org types. Llms.txt published.
4 observations recorded.
Programmatic onboarding
A machine readable API spec is published.
3 observations recorded.
Pricing legibility
6 prices readable without JavaScript on the pricing page: $0, $29, $99, $249, $2,500 and one more. No tier gated to sales or demo. FAQ markup present. Prices are legible to both humans and machines reading the raw HTML.
2 observations recorded.
Agent-aware instrumentation
MCP manifest published at /.well-known/mcp.json. AI plugin manifest at /.well-known/ai-plugin.json. OpenAPI spec at /openapi.json. Robots.txt explicitly names 14 AI crawlers and allows them. Full instrumentation for agent integration.
4 observations recorded.
Machine-fetchable trust
Security.txt published with machine contact route. Returns policy at /refunds reads as text without JavaScript. Shipping policy not found at standard paths. Homepage answers automated requests.
3 observations recorded.
Commercial rails
Prices published in raw HTML on the pricing page. Self serve signup form reachable in 2 steps from homepage with 2 required fields. No UCP manifest, no payment processor detected, no agent checkout path.
4 observations recorded.
Steps to first value
Signup form is 2 steps from the homepage. Form asks for work email and password, both required. Google single sign on offered. No payment required to sign up. Evaluators reach the signup page quickly.
1 observation recorded.
Required fields
2 of 2 form fields are required: work email and password. Both inputs carry validation rules. Google SSO option avoids password entry entirely. Minimal friction on the signup path.
1 observation recorded.
Verification walls
No verification requirement appears on the signup page itself. Single sign on option bypasses email verification entirely. Email verification may occur after submission but was not observed in this scan.
1 observation recorded.
Error recovery
Both form inputs carry validation rules and constraints. 2 of 2 inputs have validation. No inline error containers or live regions observed. Validation is present but error messaging detail was not measured.
1 observation recorded.
We sent a buying agent. 18 requests, in order
It got through 16 of 18.
The agent got through 16 of 18 requests, but could not find out whether verified agents are recognised. It came up empty on 1 other check too.