Is thumbtack.com agent ready?
thumbtack.com is not yet agent ready: it scores 42/100 (grade D) on the w2agent rubric. Weakest areas: Agent Discovery (0), Structured Data (25), Agent Auth (27), Agent Protocols (27).
How thumbtack.com compares
Better than 33% of measured sites
vs other Next.js sites: better than 13% of 334 Next.js sites
Next.js median: 56/100
Among 1299 websites measured under rubric v3.0
Changed since last check
+25 points since the previous check (2026-09-15)
Fixed: Public API surface, FAQ content, Content length, XML sitemap exists, Developer portal, Content accessible without JS, robots.txt exists, Citation readiness, Lists and tables for structured info, Reachable as Google-Agent, Reachable as ChatGPT-User, Reachable as Perplexity-User
Regressed: Response time
Changed: Answer-first content (fail → partial), OpenGraph meta tags (fail → partial), Semantic HTML elements (fail → partial), Canonical URLs (fail → partial), Appropriate Schema.org type (fail → partial), Heading hierarchy (fail → partial), Schema.org JSON-LD present (fail → partial)
Files added: robots.txt, sitemap.xml
Category scores
Agent protocol panel
- A2A agent cardNot found
- OAuth discoveryNot found
- MCP discoveryNot found
- llms.txt validityNot measured
Check results
Bot Accessibility
- ✓No error status codespass
- ~Response timepartial
- ✓XML sitemap existspass
- ✓AI agent accesspass
- ✓Edge treatment of agent user-agentstracked, not scoredpass
- ✓robots.txt existspass
- ✗Content negotiation (Markdown)fail
- —Declared AI usage preferencestracked, not scoredskip
Structured Data
- ~OpenGraph meta tagspartial
- ~Semantic HTML elementspartial
- ~Appropriate Schema.org typepartial
- ~JSON-LD validpartial
- ~Heading hierarchypartial
- ~Schema.org JSON-LD presentpartial
- ✗Schema.org completenessfail
Content Quality
- ✓FAQ contentpass
- ~Answer-first contentpartial
- ✓Content lengthpass
- ✓Token efficiency (HTML-to-text ratio)pass
- ✗Freshness signalsfail
- ✗Author attributionfail
- ✓Citation readinesspass
- ✓Lists and tables for structured infopass
Agent Discovery
- —llms.txt follows specskip
- ✗llms.txt existsfail
- —MCP server cardtracked, not scoredskip
- ✗Markdown alternate linksfail
- ✗/.well-known/agent-card.jsonfail
- —llms.txt links resolveskip
Agent Protocols
- ✗Discoverable API endpointsfail
- ✗MCP endpointfail
- ✗Action schemasfail
- —/.well-known/ucpskip
- ~Structured formspartial
- —WebMCP imperative APItracked, not scoredskip
- —WebMCP declarative APItracked, not scoredskip
- ✓Reachable as Google-Agentpass
- ✓Reachable as ChatGPT-Userpass
- ✓Reachable as Perplexity-Userpass
Agent Auth
- —MCP authorization (401 challenge → protected resource metadata)skip
- ✗PKCE S256 supportfail
- ✓Public API surfacepass
- —Client ID Metadata Documents (bonus)skip
- ✗OpenAPI specificationfail
- ✗Agent/bot auth documentationfail
- ✗OAuth discovery chain (RFC 9728 → RFC 8414)fail
- ✓Developer portalpass
- ✗Scoped API permissionsfail
- ✗API catalog (RFC 9727)fail
- —Agent operator signing directorytracked, not scoredskip
Technical
- ✓HTTPSpass
- ✓UTF-8 charsetpass
- ~Canonical URLspartial
- ✓Mobile viewportpass
- ✓Content accessible without JSpass
- ✗Security headersfail
Other
- ✗nextjs-metadata-apifail
- ~nextjs-static-generationpartial
- ✗nextjs-well-known-servedfail
- —local-business-hours-jsonldskip
- —local-business-nap-structuredskip
- —local-business-booking-accessibleskip
Score history
- 42/100 · rubric v3.0
- 17/100 · rubric v3.0
- 34/100 · rubric v2.0
- 34/100 · rubric v2.0
- 35/100 · rubric v2.0
- 34/100 · rubric v2.0
- 32/100 · rubric v2.0
- 35/100 · rubric v2.0
- 20/100 · rubric v2.0
- 20/100 · rubric v2.0