Linear App Audit

Observed Behavior: The interactive product demo embedded on the Features page registers keyboard shortcuts (e.g., C to create an issue, X to select) that fire even when the demo iframe does not have explicit focus, hijacking the user’s browser-level keyboard behavior on the marketing page itself.

Technical Root Cause: The event listener is attached to document.addEventListener('keydown', ...) at the top level without checking document.activeElement or whether focus is inside the demo container. Because the demo is rendered inline (not inside an iframe with a separate document context), keystrokes propagate to it from anywhere on the page.

Business Impact: Users attempting to use browser shortcuts like Cmd+F (find) or simply typing into the contact form accidentally trigger demo actions, creating a confusing and broken experience on the very page meant to showcase the product’s polish.

Remediation Path: Scope all keyboard listeners to fire only when document.activeElement is within the demo’s root container element. Add a visible “Click to interact” overlay that grants focus to the demo region, following the pattern used by embedded code playgrounds like CodeSandbox.

Observed Behavior: The Changelog page uses infinite scroll to load older entries. After loading approximately 40 entries, the scroll listener stops firing and no further content loads. Refreshing the page resets to the top with no way to deep-link to older entries.

Technical Root Cause: The Intersection Observer monitoring the sentinel element at the bottom of the list is being disconnected after a failed fetch (likely a timeout on the API response for older, larger payloads), and no retry logic re-attaches the observer.

Business Impact: Evaluators researching Linear’s shipping velocity — a common due-diligence step for engineering leaders — cannot access the full history. The changelog is also a key SEO asset for long-tail queries like “Linear GitHub integration update,” and unreachable entries cannot be indexed.

Remediation Path: Replace infinite scroll with paginated routes (/changelog?page=2) that are individually indexable. Add retry logic with exponential backoff if the fetch fails, and re-attach the observer after a successful retry.

Observed Behavior: The animated product UI in the homepage hero section — showing issues flowing through a board — exhibits visible frame drops and stuttering on standard 60Hz monitors, particularly in Firefox on Windows.

Technical Root Cause: The animation uses JavaScript-driven requestAnimationFrame loops to animate CSS transform properties on dozens of simultaneously moving elements. The paint complexity exceeds the frame budget on non-ProMotion displays, especially when the browser’s compositor is under load from other tabs.

Business Impact: The hero is the first thing visitors see. Jank on a site that sells speed and performance directly contradicts the brand promise, causing immediate credibility erosion with the technical audience that evaluates tools this closely.

Remediation Path: Convert the animation to a pre-rendered Lottie or video asset with a transparent overlay for interactivity. Alternatively, reduce the number of simultaneously animated DOM nodes and use CSS will-change: transform to hint compositor promotion.

Observed Behavior: On the enterprise “Contact Sales” form, entering a personal email (e.g., gmail.com) and then correcting it to a corporate email does not always update the auto-detected “Company” field, which was pre-filled from the initial email domain.

Technical Root Cause: The Clearbit Reveal (or similar enrichment) lookup fires on the onBlur event of the email field. If the user changes the email and tabs directly to the next field without re-blurring the email input, the enrichment data from the first lookup persists in the form state.

Business Impact: Sales development reps receive leads with mismatched company names (e.g., “Google LLC” paired with a gmail.com address), requiring manual research and delaying response time on high-value enterprise inquiries.

Remediation Path: Trigger the enrichment lookup on both onBlur and onChange (debounced at 500ms). Clear any previously enriched company data as soon as the email field value changes, and re-run enrichment only after the input stabilizes.

Observed Behavior: The Features page uses a vertical scroll-snap layout to lock each feature section (Issues, Cycles, Projects, Roadmaps) into the viewport one at a time. On macOS trackpads, the momentum scrolling frequently overshoots, snapping the user two sections ahead and forcing them to scroll back to read the section they intended.

Technical Root Cause: The CSS scroll-snap-type: y mandatory combined with macOS’s momentum scroll physics creates an inherent conflict — the browser interprets a normal swipe as intending to traverse multiple snap points because the deceleration curve extends well beyond a single section’s height.

Business Impact: Users skip critical feature explanations, particularly the Cycles and Roadmaps sections that differentiate Linear from free alternatives. Missing these sections weakens the perceived value during the evaluation phase.

Remediation Path: Switch from mandatory to proximity snap behavior, which only snaps when the user is already close to a snap point rather than forcing a lock. Alternatively, remove scroll-snap entirely and use Intersection Observer to trigger entrance animations, preserving the visual effect without hijacking scroll control.

Observed Behavior: On iPad and Android tablets in portrait orientation, the four pricing tiers (Free, Standard, Plus, Enterprise) are laid out in a horizontal row that overflows the viewport. There is no visual indicator that the user can scroll horizontally to see the Plus and Enterprise tiers.

Technical Root Cause: The pricing grid uses display: flex with flex-wrap: nowrap, and no scroll affordance (like a fade gradient or arrow indicators) is applied to signal the overflow to the user.

Business Impact: Tablet users — often executives reviewing tools during meetings — only see the Free and Standard tiers, completely missing the Plus and Enterprise offerings. This directly reduces enterprise lead generation from a key decision-maker device class.

Remediation Path: On viewports between 768px and 1024px, stack the tiers vertically or use a tabbed interface. If horizontal layout is retained, add a subtle gradient fade on the right edge and left/right navigation arrows to communicate scrollability.

Observed Behavior: The /method page — Linear’s long-form brand manifesto — is a single, continuous scroll of approximately 5,000 words with no table of contents, section links, or progress indicator. Users cannot link to or return to a specific section.

Technical Root Cause: The page is rendered as a single content block without heading IDs or any anchor-link generation, despite having clearly delineated sections with H2 headings.

Business Impact: The Method page is frequently shared in engineering Slack channels and blog posts. Without anchor links, references are imprecise (“scroll about halfway down”), reducing shareability and return visits to specific arguments.

Remediation Path: Add id attributes to each H2 heading, implement a sticky sidebar table of contents on desktop, and add a floating progress bar on mobile. Ensure heading anchors are included in the URL hash for deep linking.

Observed Behavior: Searching for an integration that does not exist (e.g., “Basecamp”) in the Integrations directory returns a blank white area with no messaging, no suggestions, and no path forward.

Technical Root Cause: The search filter simply hides non-matching cards using CSS display: none. When zero cards match, the container is empty and no conditional “no results” component is rendered.

Business Impact: Users evaluating whether Linear supports their toolchain get a dead end with no guidance. Instead of learning that they can build a custom integration via the API, they assume compatibility doesn’t exist and may move on to a competitor.

Remediation Path: Render a “No integrations found” state that includes: (1) a suggestion to check spelling, (2) a link to Linear’s API documentation for custom integrations, and (3) a “Request an integration” link that feeds into the product feedback pipeline.

Observed Behavior: Linear’s free tier is remarkably generous (unlimited members, 250 issues), but the pricing page presents all four tiers with equal visual weight. The Free tier’s card does not emphasize what is included — it reads like a stripped-down version rather than a strong starting point.

Technical Root Cause: The pricing card component uses the same layout and typographic hierarchy for all tiers, treating features as a checklist rather than highlighting the unique value proposition of each tier to distinct buyer personas.

Business Impact: Teams that would convert faster by starting free and upgrading organically instead stall on the pricing page trying to justify the Standard tier upfront. The free-to-paid upgrade path — Linear’s most efficient growth loop — is underutilized.

Remediation Path: Redesign the Free tier card to lead with “Get started with your whole team — no credit card required” and explicitly list the generous limits (unlimited members, 250 active issues). Add a prominent “Start free” CTA that outweighs the visual weight of the paid tiers, and include a “Most teams start here” badge.

Observed Behavior: Linear has no dedicated landing page comparing itself to Jira, despite “Jira alternative” being one of the highest-volume search terms in the project management category. The only mention is a brief line in the FAQ.

Technical Root Cause: Marketing strategy focuses on Linear’s own brand narrative (the Method) rather than addressing the specific pain points that drive teams away from incumbent tools.

Business Impact: Teams actively searching for a Jira replacement land on competitor comparison pages (Shortcut vs Jira, Asana vs Jira) that do exist and capture that high-intent traffic. Linear misses a critical acquisition channel.

Remediation Path: Create a dedicated /compare/jira landing page that addresses specific migration concerns: data import, workflow mapping, keyboard shortcuts parity, and real customer migration stories. Target the page for “Jira alternative,” “switch from Jira,” and “Linear vs Jira” queries.

Observed Behavior: After clicking “Start building” on the homepage, the user must complete a 5-step onboarding wizard (name, URL slug, invite teammates, choose plan, customize) before seeing the actual product interface. The entire flow takes 2-3 minutes even when skipping optional steps.

Technical Root Cause: The onboarding flow was designed to maximize workspace customization upfront, collecting data that could be deferred (like team invitations and plan selection) until after the user has experienced the core product.

Business Impact: Every additional step before the user sees the fast, fluid issue board — Linear’s primary differentiator — increases the risk of abandonment. Users who signed up to “feel” the speed never get there.

Remediation Path: Reduce the mandatory onboarding to 2 steps: workspace name and user role. Pre-populate a sample project with demo issues so the user lands in a working board within 30 seconds. Defer team invitations, plan selection, and customization to contextual prompts after the user has created their first issue.

Observed Behavior: The “Contact Sales” button on the Enterprise tier leads to a generic form with no indication of what happens next — no mention of response time, no calendar booking option, and no indication of whether a demo will be offered.

Technical Root Cause: The enterprise lead form follows a conventional pattern without optimizing for the anxiety of the buyer, who wants to know they will get a fast, relevant response rather than entering a black-hole sales queue.

Business Impact: Enterprise evaluators who are comparison-shopping between multiple tools may skip the form if they can get a faster response (like an instant Calendly booking) from a competitor.

Remediation Path: Replace the generic form with a two-option layout: (1) “Book a 15-min demo” with an embedded Calendly widget for immediate scheduling, and (2) “Tell us about your team” for async inquiries. Add a line: “We respond within 4 business hours.”

Observed Behavior: The Changelog is rendered as a single, infinitely scrolling page. Individual entries (e.g., “Linear 2024.12 — Triage Improvements”) do not have their own URLs, canonical tags, or structured data. Google indexes the Changelog as one monolithic page.

Technical Root Cause: The changelog is rendered client-side from a single API endpoint that returns all entries, without generating discrete routes for each release.

Business Impact: Linear misses hundreds of long-tail keyword opportunities. Queries like “Linear Figma plugin integration” or “Linear cycle automations” could each rank individually, driving high-intent organic traffic from engineering leaders evaluating specific capabilities.

Remediation Path: Generate individual, server-rendered pages for each changelog entry (e.g., /changelog/2024-12-triage-improvements). Add Article JSON-LD schema with datePublished and headline fields. Keep the scrollable overview page as an index, but link each entry to its canonical individual page.

Observed Behavior: The homepage <head> contains basic og: meta tags but no JSON-LD structured data. Google has no machine-readable signal that Linear is a software application with specific pricing, platform support, and a rating.

Technical Root Cause: Structured data implementation was not part of the original site build, and the Next.js layout does not include a JSON-LD injection component.

Business Impact: Linear’s search result for branded queries shows a plain blue link, while competitors with SoftwareApplication schema display rich snippets including pricing, ratings, and platform availability — pulling higher click-through rates from the same SERP.

Remediation Path: Add a SoftwareApplication JSON-LD block to the homepage specifying applicationCategory: "Project Management", operatingSystem: ["Web", "macOS", "Windows", "iOS", "Android"], and offers with pricing for each tier. Include aggregateRating if review data is available from G2 or Capterra.

Observed Behavior: All integration pages (e.g., Linear + GitHub, Linear + Slack, Linear + Figma) use the same title tag pattern: “Integrations | Linear” rather than unique, keyword-targeted titles like “GitHub Integration for Linear | Connect Your Repos.”

Technical Root Cause: The dynamic route for integration pages uses a static <title> tag from the layout component rather than dynamically injecting the integration partner’s name into the title.

Business Impact: Google treats pages with identical titles as near-duplicates, suppressing most of them from search results. High-intent queries like “Linear Slack integration” are won by competitors or third-party blog posts instead.

Remediation Path: Dynamically generate unique title tags per integration page following the pattern: [Partner Name] Integration | Linear — [One-line benefit]. Update meta descriptions similarly to target the specific integration + project management keyword cluster.

Observed Behavior: Linear’s blog posts about product updates (e.g., “Introducing Triage”) mention features by name but do not link to the corresponding feature pages on the marketing site (e.g., /features/triage). The posts are self-contained with no outbound internal links.

Technical Root Cause: Blog content is authored in a CMS (likely Contentful or similar) where the writers do not have easy access to the current marketing site URL structure, and no automated linking plugin is in place.

Business Impact: Blog posts accumulate backlinks and domain authority from external sources, but none of that link equity flows to the commercial feature pages that need to rank for competitive terms like “issue triage tool” or “project cycle planning software.”

Remediation Path: Implement an automated internal linking system that detects feature-related keywords in blog content and injects contextual links to the corresponding marketing pages. Retroactively add links to the top 20 highest-traffic blog posts.