Weekly striking distance SEO briefs in Linear

Every Tuesday, scan Google Search Console for keywords stuck on page two and file ready-to-action content briefs as Linear issues for your SEO team.

Agentic Task
Google Search ConsoleLinearMarketingAI ReportsResearch & Monitoring
PromptCreate

Every Tuesday at 8am in my local timezone, run a striking distance SEO analysis and file content briefs as Linear issues. This is an agent-based workflow because the clustering and brief drafting is judgment work, not a fixed pipeline.

Step 1. Pull the last 28 days of search performance from Google Search Console using Search Analytics Query, grouped by both query and page. Use the most recent complete 28 day window. Search Console data lags 2 to 3 days, so end the window a few days before today.

Step 2. Filter the rows to where average position is between 8 and 20 and impressions are at least 200. These are the striking distance opportunities.

Step 3. Cluster the surviving queries by topical intent. Group each cluster under the best matching landing page, which is the page on my site that already collects most of the impressions for that cluster.

Step 4. Score each cluster by impressions multiplied by the gap between expected CTR for position 5 (use roughly 14 percent) and the cluster's current actual CTR. This is the impact heuristic.

Step 5. Pick the top 5 clusters by impact score.

Step 6. For each top cluster, call Inspect URL on the target page in Google Search Console. If the page is not in an indexed status, skip that cluster and substitute the next best one.

Step 7. For each surviving cluster, draft a concise content brief in Markdown with these sections: target query cluster (primary query plus 3 to 8 supporting queries); target page URL and its current average position; why it is stuck (pick the most likely reason among intent mismatch, thin content, missing sections, or weak title and meta); and 2 to 3 concrete optimization moves covering on-page edits, internal link sources from specific other pages on my site, and FAQ or schema additions.

Step 8. For each brief, call Create Issue in Linear in my SEO team. Title is the primary query for the cluster. Description is the full brief in Markdown. Priority is set by impact score: highest impact cluster = Urgent, next two = High, remaining = Normal.

If no clusters survive the filters and the indexing check, file a single Linear issue summarizing what was scanned and why nothing qualified this week, so the cadence stays visible to the team.

What does this prompt do?

  • Pulls the last 28 days of search performance and surfaces queries hovering between positions 8 and 20, where small wins move the most traffic.
  • Groups related queries by intent and matches each cluster to the right landing page on your site.
  • Drafts a short content brief for the top five opportunities, covering why the page is stuck, what to add, and which internal links to point at it.
  • Files each brief as a Linear issue in your SEO team with priority set by the estimated traffic impact.

What do I need to use this?

  • A Google Search Console login with access to your verified site.
  • A Linear workspace and an SEO team to receive the issues.

How can I customize it?

  • Change the day or time the report runs. The default is Tuesday morning.
  • Tighten or loosen the position and impression filters to match your traffic volume.
  • Pick a different Linear team, or change how priority maps to the impact score.

FAQs

What is a striking distance keyword?
A keyword where your page already ranks on the edge of page one, usually positions 8 to 20. These are the highest leverage SEO wins because small edits often push them into the top five.
How many briefs will I get each week?
The agent picks the five highest impact clusters by default so the work stays focused. You can ask for more or fewer when you set it up.
Does it skip pages that are not indexed?
Yes. Before filing a brief, the agent checks the target page's indexing status in Google Search Console and drops any cluster whose page is not indexed.
How fresh is the data?
Google Search Console data lags two to three days, so the report covers a rolling 28 day window ending a few days before each run.
What if no opportunities qualify in a given week?
You still get a short Linear issue summarizing what was scanned and why nothing made the cut, so the cadence stays visible to your team.

Related templates

Find the customers stuck contacting support again and again

A board that ranks the people who opened three or more separate support conversations this month, reads their threads, and files the real fix.

Kustomer
Linear
General Input Database
App
Turn shipped Linear work into Intercom product announcements

A board your product marketer opens on every ship day to turn finished engineering tickets into announcements customers actually read in your Messenger.

Intercom
Linear
Slack Bot
+1
App
Voice agent QA review board for your Hume EVI calls

Open one board each morning, see which voice calls went badly, replay the exact moment the caller got frustrated, and file the fix.

Hume
Linear
Slack Bot
App
Close the loop between Front tickets and Linear bug fixes

See every customer waiting on a bug fix, file the ticket without creating a duplicate, and tell them the moment engineering ships it.

Front
Linear
App
Open a Heroku release war room the moment production looks wrong

See every recent deploy across all your Heroku apps in one timeline, then roll back, restart, or file an incident without leaving the screen.

Heroku
GitHub
Linear
App
Find the themes Help Scout tags miss and file them in Linear

Pick a date range, see which support topics are climbing fastest, read the real customer threads behind them, and file the worst ones as tickets.

Help Scout
Linear
App

Stop letting page two keywords sit there.

Connect Google Search Console and Linear once, and Geni files your five best SEO opportunities as briefs every Tuesday morning.