CONTENT CREATION

Catch Keyword Drift and Realign Page Intent

Weekly, it reads which queries each page ranks for, detects when a page's winning queries have drifted away from its original intent.

CategoryContent Creation
Enginesim
Difficultyadvanced
Triggerschedule
Steps6
Setup~25 min

How it runs

The automated pipeline, trigger to output.

  • TriggerWeekly schedule fires
  • ActionQuery per-page Search Console metricsPostgreSQLPostgres
  • LogicDetect query drift and low CTR pages
  • ActionPull current page contentFirecrawl
  • ActionDraft intent-realignment briefOpenAI
  • OutputCreate Linear issue for content teamLinearLinear

What it does

Pages often start ranking for queries they were never written for. This workflow spots that drift — where impressions concentrate on terms the page only loosely addresses — and produces a brief to realign the page with the intent it's actually capturing, recovering clicks left on the table.

When to use it

Use it when pages get impressions but weak click-through, a classic sign that the page ranks adjacent to demand without satisfying it. Ideal for teams mining Search Console data who want intent-led rewrites instead of keyword stuffing.

How it works

  1. 1A weekly schedule starts the run.
  2. 2A Postgres query pulls per-page query, impression, and CTR data from your synced Search Console export.
  3. 3A logic step finds pages where top-impression queries diverge from the page's stated topic and CTR lags the position benchmark.
  4. 4Firecrawl pulls the current page content for context.
  5. 5OpenAI drafts a re-optimization brief: revised title and H1 options, sections to add for the drifted queries, and intent-match notes.
  6. 6The brief is created as a Linear issue in the content team's project, labeled by opportunity size.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect PostgresAny Postgres URL — query, write, migrate.
  2. 2
    Connect FirecrawlCrawl, scrape, structured extract.
  3. 3
    Connect OpenAIModels, embeddings, files.
  4. 4
    Connect LinearIssues, projects, cycles, triage.
  5. 5
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  6. 6
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  7. 7
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.