linear.app — AI Site Grade

Analysis

The site's most advanced AI-native positioning — the "issue tracking is dead" manifesto and the agent-as-teammate platform — is invisible to the cold LLM knowledge base, which still describes Linear as a "project management and issue tracking platform."

Crawler Access

All major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider) receive 200 OK with full HTML content from Cloudflare. No UA-based blocking exists. The robots.txt is minimal — a single User-Agent: * rule disallowing /api/ and /cdn-cgi/ — with no AI-bot-specific directives at all. The llms.txt is present and comprehensive: 9,443 bytes covering documentation, AI features, integrations, and analytics, all with .md links to docs pages. This is an unusually mature AI-crawler posture.

Cold-Knowledge Gap

The cold LLM knows Linear as a "project management and issue tracking platform" used by startups, founded in 2019 by ex-Uber engineers, with keyboard-first design. This description is stale by at least 18 months. The site now positions itself as "the product development system for teams and agents" — a fundamental repositioning away from issue tracking. The homepage headline reads "The product development system for teams and agents" repeated three times. The March 2026 post "Issue tracking is dead" (referenced on /now but timing out on fetch) codifies this shift. The cold model has zero awareness of Linear Agent, Linear Diffs, Code Intelligence, the MCP server, or the agent marketplace with Cursor, Codex, GitHub Copilot, Devin, and Sentry integrations.

Schema Posture

Despite sophisticated content, zero JSON-LD schema appears on the homepage, pricing page, features page, agents page, security page, or blog index. No Organization, SoftwareApplication, FAQPage, Product, or WebSite schema is present. The site relies entirely on semantic HTML and Open Graph tags. For an AI-native product company, this is a surprising omission — structured data would directly reinforce the "product development system" positioning in knowledge graph contexts.

External Signals

DNS TXT records reveal domain verification for Anthropic, OpenAI, Cursor, Notion, Slack, Stripe, LaunchDarkly, and MongoDB — confirming deep integration partnerships. Customer stories feature OpenAI (3,000+ users), Ramp (60% of PRs authored by their internal agent Inspect), Coinbase, and Cursor. The changelog shows rapid shipping: Linear Diffs (May 2026), Code Intelligence (May 2026), Project Slack channels (May 2026), Releases (April 2026). The blog references press appearances with Anthropic, Sequoia Capital, and Raycast. The site claims "more than 33,000 companies" as customers.

Findings

1. Cold LLM knowledge describes Linear as a project management and issue tracking platform, missing its AI-native repositioning High

   The cold LLM knowledge base describes Linear as a 'project management and issue tracking platform' used by startups, founded in 2019 by ex-Uber engineers. This description is stale by at least 18 months. The site now positions itself as 'the product development system for teams and agents', with features like Linear Agent, Linear Diffs, Code Intelligence, MCP server, and integrations with Cursor, Codex, GitHub Copilot, Devin, and Sentry. The cold model has zero awareness of these AI-native capabilities.

   What to change: Publish structured data (JSON-LD) describing the platform as a product development system with AI agent capabilities. Ensure the llms.txt and other discoverable content explicitly state the new positioning. Consider submitting updated descriptions to LLM knowledge bases.

2. Zero JSON-LD schema present on any key page Medium

   Despite sophisticated content, no JSON-LD schema (Organization, SoftwareApplication, FAQPage, Product, or WebSite) appears on the homepage, pricing page, features page, agents page, security page, or blog index. The site relies entirely on semantic HTML and Open Graph tags. For an AI-native product company, this omission misses an opportunity to reinforce the 'product development system' positioning in knowledge graph contexts.

   What to change: Add JSON-LD structured data for Organization, SoftwareApplication, and WebSite schema on all key pages. Include properties for AI features, integrations, and agent capabilities.

3. Key manifesto page 'Issue tracking is dead' times out for crawlers High

   The page at /now/issue-tracking-is-dead, which codifies Linear's repositioning away from issue tracking, consistently times out (ReadTimeout) when fetched. This prevents AI crawlers from indexing the content, making the manifesto invisible to LLMs.

   What to change: Investigate and resolve the timeout issue for /now/issue-tracking-is-dead. Ensure the page loads reliably for all crawlers. Consider adding a fallback or caching layer.

4. Developers page times out for crawlers Medium

   The /developers page, which likely contains API documentation and developer resources, times out (ReadTimeout) when fetched. This blocks AI crawlers from accessing developer-focused content.

   What to change: Investigate and resolve the timeout issue for /developers. Ensure the page loads reliably for all crawlers.

5. Customers page times out for crawlers Medium

   The /customers page, which lists customer stories, times out (ReadTimeout) when fetched. This prevents AI crawlers from indexing social proof content.

   What to change: Investigate and resolve the timeout issue for /customers. Ensure the page loads reliably for all crawlers.

6. Robots.txt lacks AI-bot-specific directives Low

   The robots.txt file contains only a single User-Agent: * rule disallowing /api/ and /cdn-cgi/. No AI-bot-specific directives (e.g., for GPTBot, ClaudeBot, PerplexityBot) are present. While this does not block AI crawlers, it misses an opportunity to guide them to the most relevant content.

   What to change: Add AI-bot-specific directives to robots.txt to allow or disallow specific paths for AI crawlers, and consider adding a crawl-delay directive.

7. No external mentions of Linear's AI repositioning found in web search Medium

   Web searches for 'Linear.app AI agents issue tracking 2025 2026', 'Linear issue tracking dead AI agents 2026', and similar queries returned zero results. This indicates that Linear's AI-native positioning has not yet been picked up by external sources, limiting its visibility in LLM training data.

   What to change: Increase PR and content marketing efforts to generate external coverage of Linear's AI features and repositioning. Publish guest posts, press releases, and case studies that highlight the agent platform.

What's working

• Comprehensive llms.txt file with documentation links — The llms.txt file is present and comprehensive at 9,443 bytes, covering documentation, AI features, integrations, and analytics, all with .md links to docs pages. This is an unusually mature AI-crawler posture that helps LLMs discover key content.
• All major AI crawlers receive full HTML content with no blocking — All tested AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended, OAI-SearchBot, ChatGPT-User, anthropic-ai, Applebot-Extended, Bytespider) receive 200 OK with full HTML content from Cloudflare. No UA-based blocking exists, ensuring AI crawlers can index the site's content.
• Domain verification for multiple AI and tool partners — DNS TXT records reveal domain verification for Anthropic, OpenAI, Cursor, Notion, Slack, Stripe, LaunchDarkly, and MongoDB, confirming deep integration partnerships that strengthen external signals.
• Customer stories with high-profile AI-native companies — Customer stories feature OpenAI (3,000+ users), Ramp (60% of PRs authored by their internal agent Inspect), Coinbase, and Cursor, providing strong social proof for AI-native positioning.
• Changelog shows rapid shipping of AI-related features — The changelog shows rapid shipping of AI-related features: Linear Diffs (May 2026), Code Intelligence (May 2026), Project Slack channels (May 2026), Releases (April 2026), demonstrating active development in the AI space.
• Dedicated 'Linear for Agents' page with clear positioning — The /agents page (301 words) explicitly positions Linear as a platform for AI agents, describing integrations with Cursor, Codex, GitHub Copilot, Devin, and Sentry. This page is accessible and provides clear content for AI crawlers.
• Homepage clearly states 'product development system for teams and agents' — The homepage headline reads 'The product development system for teams and agents' repeated three times, clearly communicating the new positioning to human visitors and crawlers.