Linear integration

SEO reporting data in Linear

GSC Wizard watches your Google Search Console data and opens a Linear issue when something needs fixing: a traffic drop, a page that fell out of Google’s index, a Core Web Vitals regression or a broken redirect after a migration. The team that can fix it gets the problem in its own triage, with the numbers and a link to the report.

Included in every GSC Wizard plan and the 7-day trial. Nothing to install in Linear beyond approving the app.

A Linear issue created by GSC Wizard from a traffic anomaly: the title Clicks anomaly on example.com, actual and expected clicks, High priority, an SEO label and a link back to the anomaly report
A traffic anomaly as a Linear issue, written by GSC Wizard (illustration with example data).

The short answer

Linear has no built-in Search Console data. GSC Wizard adds it in the form engineering teams act on: one issue per SEO problem, created in the team you choose.

  1. Connect Linear under Account, Slack, Teams & Webhooks in GSC Wizard, and approve the workspace.
  2. Pick a team, an optional label, the alert types and a minimum severity.
  3. Create a test issue to see it work. Real alerts follow within minutes of detection.
Why put SEO data in Linear

An SEO problem is a ticket nobody wrote

Most search losses are fixed by engineers: a release that dropped a canonical tag, a redirect map with holes, a template that made pages slow. The SEO report that spots it usually sits in a dashboard or a chat thread that the engineering team never opens.

The evidence travels with the issue

Every issue carries the numbers behind the alert: actual against expected clicks, the affected URL, the before and after values. Nobody has to log in to an SEO tool to understand the ticket.

Priority from the severity

Critical alerts become Urgent issues, high becomes High, medium Medium and low Low, so an SEO problem is sorted against the rest of the team’s work in the same way.

One click back to the report

The report the alert came from is attached to the issue, already filtered to the property, so whoever picks it up can see the trend before and after the fix.

What lands in Linear

The SEO alerts you can route to a team

Each team picks its own alert types, so indexing and migration problems can go to the platform team and content decay to the content team.

AlertWhat the issue tells the team
Traffic anomaliesA day when clicks, impressions, CTR or position fell outside the expected range, with the actual and expected values.
Sustained traffic shiftsThe date a property’s traffic moved to a new level and stayed there, the kind of change a release or an algorithm update causes.
Indexing warningsA page you track that Google dropped from its index or stopped crawling, with the URL.
Core Web Vitals regressionLCP, INP or CLS moving from good to worse in the Chrome UX Report, with the old and new values.
Content decayA page or query losing clicks week after week, with the click change and how far its position slipped.
Migration issuesNew redirect problems or a stalled recovery after a site move, from the daily re-check of a saved migration.
Rank changesTracked keywords that moved in or out of the positions you care about.
Merchant CenterFeed Score drops and high-potential products that are not eligible for free listings.
Broken Google connectionThe Google account behind your data needs signing in again, before reports go stale.

The full list, with how each detector works and when it runs, is in the alerts documentation.

Setup

Connected in a minute

You need a GSC Wizard account with your Search Console properties connected and an active plan or trial, and permission to install apps in your Linear workspace.

  1. 1

    Connect Linear

    In GSC Wizard, open Account → Slack, Teams & Webhooks and click Connect Linear. Linear asks which workspace to add GSC Wizard to; approve it and you are back in GSC Wizard.

  2. 2

    Choose the team and the alerts

    Pick the team, an optional label such as SEO, the alert types and a minimum severity. Add one row per team to split the work, for example indexing to the platform team and content decay to the content team.

  3. 3

    Create a test issue

    The send button on the row creates a test issue in the team, so you know it works before the first real alert. From then on, every matching alert becomes an issue within minutes of detection.

Permissions

It creates issues and does nothing else

GSC Wizard asks Linear for two permissions: read, to list your teams and labels in the picker, and issues:create, to create the alert issue and its link back to the report. It never reads, edits or deletes the issues already in your workspace.

No duplicates, no noise

An alert becomes one issue per team, and a retry after a Linear outage cannot open a second one. Each team row can be paused, resumed or deleted at any time.

Disconnect in one click

Disconnecting in GSC Wizard revokes the access at Linear and deletes the tokens. Removing the app in Linear works too: GSC Wizard is told at once and stops. Tokens are encrypted at rest.

Alerts in Linear, reports where people read them

Linear is for work, so GSC Wizard sends it the findings that need someone to act. The weekly and monthly SEO reports, with headline numbers, winners and losers and ranking movers, go to the places people read: a Slack or Microsoft Teams channel, or a shared report for clients. Many teams use both: the report says how search is doing, the Linear issue makes sure the problem in it gets fixed.

Same data, other tools

Not on Linear?

The same alerts post to Slack and Microsoft Teams, and reach anything else through signed webhooks. In Jira, the GSC Wizard app for Jira shows Search Console numbers for the URLs in an issue. To ask questions about the data instead, connect it to an AI assistant through the GSC MCP server.

Frequently asked questions

Can I get Google Search Console data into Linear?

Yes, with GSC Wizard. Connect your Search Console properties to GSC Wizard, connect your Linear workspace, and pick a team. Every SEO alert you route to that team, such as a traffic anomaly, a deindexed page or a Core Web Vitals regression, becomes a Linear issue with the numbers behind it and a link to the report.

Which SEO alerts can become Linear issues?

Traffic anomalies, sustained traffic shifts, indexing warnings, Core Web Vitals regressions, content decay, migration issues, rank changes, Merchant Center feed problems and broken Google connections, among others. Each team chooses its own alert types and a minimum severity.

How is the priority of the issue decided?

From the alert’s severity: critical becomes Urgent, high becomes High, medium Medium and low Low. Informational alerts, such as a Google algorithm update, get no priority.

Can I send weekly SEO reports to Linear?

Not as issues. A report is information and an issue is work, so GSC Wizard sends Linear the findings that need someone to act. Scheduled weekly and monthly reports go to Slack, Microsoft Teams or a shared client report.

What can GSC Wizard do in my Linear workspace?

It asks for two permissions: read, to list your teams and labels, and issues:create, to create the alert issue and its link. It never reads, edits or deletes the issues already in your workspace, and you can disconnect it at any time from GSC Wizard or from Linear.

Will a busy week flood my backlog?

You decide how much arrives. Pick only the alert types a team owns, raise the minimum severity, and tune the detectors’ sensitivity in GSC Wizard. An alert is created once per team, and a team row can be paused when you need quiet.

Do I need a paid plan?

The Linear integration is part of every GSC Wizard plan and works during the 7-day free trial. In Linear, you need permission to install apps in the workspace.

Put your SEO problems in front of the people who fix them

Connect Search Console to GSC Wizard, connect Linear, and pick the alerts each team should own.

Search Console tips in your inbox

Practical GSC and GA4 workflows, product updates and SEO experiments. No spam, unsubscribe anytime.