Linear integration
Linear is on the map, not in the product yet.
SEO problems that need engineering become Linear issues with owners, not lines in a report nobody reads.
How it works
Linear connects with an API key or OAuth against Linear's GraphQL API. When the crawl finds problems that need a developer, broken internal links, pages that have dropped out of the index, and similar technical faults, the pipeline creates a Linear issue in the team you choose, with the URL and the evidence attached.
In the loop, Linear closes a gap most SEO tools leave open: the crawl and measure steps surface technical problems, and instead of parking them in a dashboard, the pipeline routes them to the people who can fix them, in the tracker where engineering work actually gets prioritized. A fixed issue then shows up as a recovered page in the next crawl.
Best forProduct and engineering teams on Linear who want technical SEO fixes triaged like any other bug.
Setup, step by step
- Choose API key or OAuth on the Linear card and authorize the connection.
- Pick the Linear team the pipeline should create issues in.
- Choose default labels and, if you want, a default project for pipeline-created issues.
- Select which finding types create issues, such as broken internal links and deindexed pages.
- Create a test issue to confirm routing, labels, and formatting.
Best practices
Route to the team that owns the site
Issues land best in the team that ships the website. If marketing pages and app pages belong to different teams, connect once per team and split finding types between them.
Label pipeline issues consistently
A dedicated label like seo-fix makes pipeline issues filterable in triage and lets you see at a glance how technical debt from the crawl is trending over time.
Let your triage own priority
We describe the problem and its evidence; your team decides urgency. A deindexed revenue page and a broken link in a footer deserve different treatment, and that call belongs in your triage.
Watch fixes confirm themselves
The next crawl after a fix verifies it: the link resolves or the page returns to the index. You do not need to reopen our dashboards to check, though the confirmation appears there too.
Known issues
What practitioners actually report, from official docs, issue trackers, and community forums.
The API is GraphQL-only
Linear exposes a single GraphQL endpoint rather than REST, so integrations need a proper GraphQL client and typed queries to be reliable.
How we handle itOur client is generated from Linear's published schema and fully typed, so issue creation calls are checked against the real API shape rather than assembled by hand.
linear.app
The API is versionless and evolves in place
Linear does not version its API; changes arrive in place and are announced through the changelog, so an unwatched integration can drift out of date.
How we handle itWe monitor Linear's developer changelog and test against schema changes as they land, so adjustments happen on our side before they ever affect your connection.
linear.app
Questions teams ask
- Will this flood our backlog with issues?
No. You choose which finding types create issues, duplicates are not refiled while an issue is open, and most sites see a handful of technical findings a month, not a stream.
- Can SearchHandled edit or close issues?
The pipeline creates issues and attaches evidence. Your team owns status, assignment, and closure. When a fix is verified by the next crawl, we note the confirmation rather than closing anything ourselves.
- What if we do not use Linear?
The email digest reports the same findings, and the ClickUp, Asana, and Trello integrations can carry fix tasks for teams on those tools instead.
Not connectable yet
Start with the plan, not the connector.
Build a Growth Map from your site to see the work itself. Approved pages can leave through the export or the webhook today, and telling us Linear matters moves it up the rollout.