jobs.workable.com
success
Claude Code
intent

What does jobs.workable.com do and who is it for? Explain it back to me.

14steps
62.9sduration
$0.6134cost
119,280tokens
22 steps8 reasoning steps3 searches
home
home
docs
llms.txt
/workable-ai
search
docs
search
search
/free-trial
/product
/how-it-works
/features
/recruiting-software
100%
on-site discovery
82%
reliability
36%
link following
path origin
  • previous resource36%
  • prior knowledge64%
insight

The agent successfully assembled a comprehensive explanation of Workable by combining prior knowledge with targeted fetches of core pages (homepage, features, pricing, AI product, about, free trial) and the llms.txt file. The site's main navigation and structured content were reasonably discoverable, but pricing details did not fully render in fetches, forcing reliance on third-party sources cited in the final response. The agent correctly identified the jobs.workable.com subdomain as a candidate-facing job board rather than the main product, though this relationship required inference rather than explicit documentation on the landing pages.

  • ›Step [9] (llms.txt) was the richest single source, providing official positioning ('recruiting and HR software'), use cases, and feature categories (ATS, sourcing, pipeline management, AI-assisted hiring). This file is agent-optimized and immediately clarified the platform's scope.
  • ›Steps [1], [3], [13], [14], [20] returned HTML that loaded successfully but truncated to 4400 characters, limiting access to full page content. Meta descriptions (fetched in these steps) were valuable but insufficient—pricing page HTML did not render the actual plan details, forcing the agent to rely on external review sites (Pin, G2, Capterra) rather than primary source.
  • ›The site does not publish a dedicated page explicitly explaining the relationship between workable.com (product) and jobs.workable.com (job board). The agent inferred this from subdomain structure and search context rather than finding it documented; this is a discovery gap for agents exploring the domain.
  • ›Pricing information in the final answer came almost entirely from third-party sources (steps [15], [17], [19] web search results), not from the official pricing page fetch [5]. The llms.txt file itself acknowledged this limitation by recommending users 'check the official pricing page for current information'—a helpful pointer but admission that llms.txt does not contain pricing data.
  • ›Competitors and differentiation were also sourced through web search (steps [15], [17]) rather than from Workable's own site, indicating the site does not publish competitive analysis or explicit differentiation statements in readily-fetchable form.

See every agent that visits jobs.workable.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →