Linear
← board · linear.app · #20 of 33
Ready with a few material gaps
- B
- Grade
- 57
- Agent readiness
- Board average 73
Scanned 2 hours ago
Every outstanding fix in one prompt for your coding agent. Rescan →
Task
What does linear.app do and how do I use it? A fetch-only agent finds out.
12 fetches6 found6 missing
- /robots.txt⋯/sitemap.xml
- /llms.txt⋯/llms-full.txt
- /pricing
- /docs
- /openapi.json
- mcp.json⋯MCP initialize
- /privacy · /terms
every path the scanner fetched · replayed deterministically, no LLM
Evaluator notes
A fetch-only agent reached linear.app over HTTPS in 515 ms and identified it from its title as “Linear – The system for product development”. The copy is readable without JavaScript (405,763 chars of visible text, 32.1% of HTML). It found pricing and docs. It looked for an OpenAPI spec and an MCP server and found none.
Critical access needs attention
Whether an ordinary agent can enter, read, and operate the public site.
- ✓4 / 4 passedAgents can reach the site
Crawler access and bot defenses.
- ✓2 / 2 passedCore content is available
Useful content remains accessible without a fragile browser-only path.
- ~1 / 2 passedNavigation fails safely
Redirects and missing pages give agents a recoverable path.
- ~2 / 3 passedControls are understandable
Forms and interactive controls expose usable names and structure.
Fix these gaps first
Critical access gaps come first, then the biggest remaining points.
- 01OpenAPI spec discoverableAgent-ready
Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
+7 pts - 02Analytics installedMeasured
Install analytics (PostHog, Plausible, GA4) before spending on traffic.
+6 pts - 03Structured data (JSON-LD)Agent-ready
Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
+4 pts - 04Agent manifest (MCP, A2A or ai-plugin)Agent-ready
Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
+2 pts - 05Agent-friendly 404sCritical access
Return a real 404 for paths that do not exist; a 200 app shell makes every wrong guess look like a page.
+2 pts
Audit the checks behind the score
Grouped by what they measure. Not-applicable checks are excluded from scoring.
Crawlable5 of 5 passed · 19/19 pts›
- ✓Served over HTTPS5/5
https://linear.app/
- ✓Responds in under 1.5s5/5
515 ms to first byte
- ✓robots.txt present2/2
User-Agent: * Disallow: /api/ Disallow: /cdn-cgi/ Allow: /api/og/ Sitemap: https…
- ✓sitemap.xml present2/2
/sitemap.xml → 200
- ✓Homepage is indexable5/5
HTTP 200
Metadata7 of 7 passed · 24/24 pts›
- ✓Title tag 10–70 characters5/5
"Linear – The system for product development" (43)
- ✓Meta description 50–160 characters5/5
"Purpose-built for planning and building products with AI agents." (64)
- ✓Canonical URL set3/3
https://linear.app
- ✓Exactly one H14/4
1 × <h1>: "The product development system for teams and agentsThe produ…"
- ✓Mobile viewport set3/3
width=device-width, height=device-height, initial-scale=1, viewport-fit=cover
- ✓Language declared2/2
<html lang="en">
- ✓Favicon declared2/2
/favicon.ico?v=2
Shareable3 of 3 passed · 14/14 pts›
- ✓Open Graph title, description and image8/8
title, description, image
- ✓Twitter/X card type set3/3
twitter:card = summary_large_image
- ✓Links to X or LinkedIn3/3
1 social link(s)
Converts3 of 3 passed · 17/17 pts›
- ✓Clear call to action8/8
4 CTA(s), e.g. "Sign up"
- ✓Pricing page linked6/6
→ /pricing
- ✓HTML under 2 MB3/3
1233 KB of HTML
Measured0 of 1 passed · 0/6 pts›
- ✕Analytics installed0/6
no analytics tag detected
→ Install analytics (PostHog, Plausible, GA4) before spending on traffic.
Agent-ready11 of 19 passed · 26/46 pts›
- ✕Structured data (JSON-LD)0/4
no JSON-LD
→ Add SoftwareApplication or Organization JSON-LD so search engines and agents can read what you are.
- ✓Machine-readable pricing3/3
/pricing lists prices as text
- ✓llms.txt present1/1
/llms.txt → 200, 4000+ chars
- ✕llms-full.txt present0/1
no /llms-full.txt
→ Publish /llms-full.txt with the full docs inlined, so agents can read everything in one fetch.
- ✓AI crawlers allowed in robots.txt2/2
none of 9 known AI crawlers blocked
- ✓No noai / TDM reservation2/2
no opt-out signals
- ✕Serves markdown on request0/1
Accept: text/markdown → text/html; charset=utf-8
→ Return text/markdown when the Accept header asks for it; agents skip the HTML entirely.
- ✕OpenAPI spec discoverable0/7
no /openapi.json or /.well-known/openapi.json
→ Publish your OpenAPI spec at /.well-known/openapi.json so agents can call you without reading docs.
- ✕Agent manifest (MCP, A2A or ai-plugin)0/2
no manifest at /.well-known/{mcp,agent,ai-plugin}.json
→ Publish an MCP server manifest or A2A agent card under /.well-known/ so agents can find your tools.
- ✓Docs or API link from the homepage3/3
homepage links to docs / API
- ✓Content readable without JavaScript3/3
405,763 chars of visible text, 32.1% of HTML
- ✓Semantic landmarks (main, single H1)3/3
<main> present, 1 × <h1>
- ✓Images have alt text2/2
32/32 images have alt
- ◐Form fields are labelled1/2
2/5 fields have a label, name or aria-label
→ Give every input a name and a label; an agent filling the form needs both.
- ✓Descriptive link text2/2
0/76 links say "click here" / "learn more"
- ✕Agent-friendly 404s0/2
a nonexistent path returned HTTP 200
→ Return a real 404 for paths that do not exist; a 200 app shell makes every wrong guess look like a page.
- —Trust pages (privacy, terms, security)n/a
- ✕Organization schema complete0/2
no Organization in JSON-LD
→ Give the Organization JSON-LD a name, url, logo, description and sameAs links.
- ✓llms.txt says what you are and links out2/2
4000+ chars, has H1, has links
- ✓Contact route discoverable2/2
mailto:, /contact or /support link found
APIn/a›
- —Spec parses and declares a versionn/a
- —Operations have summaries and operationIdsn/a
- —Error responses documentedn/a
- —Auth scheme declaredn/a
- —Versioned paths or serversn/a
- —Spec within a model context budgetn/a
MCPn/a›
- —Server answers initializen/a
- —Tools listedn/a
- —Tools carry descriptionsn/a
- —Tool parameters have schemasn/a
AI visibility
Do AI assistants actually recommend Linear? Grounded LLM checks plus ecosystem presence, folded into the score.
- ✕Category share of voice0/6
not in the shortlist; assistants name: Here, Notion, This, Todoist, For, Slack
Publish comparison and use-case content so AI assistants have grounds to recommend linear.app for its category.
- ✓Brand name discoverability3/3
Linear (linear.app) is a fast, minimal, and opinionated project management and issue tracking tool built specifically for software and produ
- ✕Wikipedia / Wikidata presence0/2
no matching article
A neutral Wikipedia or Wikidata entry anchors your brand for every assistant.
- ✓SDK package on npm1/1
npm: @linear/sdk
- ✕Listed in the MCP registry0/1
not listed
Publish your MCP server to registry.modelcontextprotocol.io so agents can find it.
Linear is not consistently named by AI assistants in project management shortlists and lacks a Wikipedia entry or MCP registry listing. However, its brand name is discoverable, and an official SDK package is available on npm.
AI-analyzed 2 hours ago · cached 7 days · grounded via web search
The report is free. Visibility is the bid.
Linear sits at #20 of 33. $1 moves it above Plausible.
Fixed something? Scan again.
One scan per site every 10 minutes. Snapshot 2026-08-25T11:39:32.491Z.