Automating Semrush keyword monitoring with n8n

Keyword monitoring is only useful when it changes what an operator does next.

This workflow turns keyword data into a stateful monitoring loop: collect snapshots, store the previous state, compare changes, and alert the operator only when a useful threshold is crossed.

Affiliate disclosure: This workflow may link to Semrush through affiliate links. If you click and buy, SearchOps Lab may earn a commission at no extra cost to you.

Goal

Build a small n8n workflow that can answer:

• Which tracked keywords moved meaningfully?
• Which pages need review?
• Which competitors entered or left the SERP?
• Which content updates should be prioritized?
• Which changes are just noise?

The point is not to create more spreadsheet rows. The point is to create an operator queue.

Recommended architecture

Use five components:

1. Keyword source: a curated list of keywords and target pages.
2. SEO data source: Semrush or another SEO data API.
3. State store: SQLite, Postgres, or a managed spreadsheet.
4. Diff logic: compare current and previous snapshots.
5. Alert channel: Telegram, email, Slack, or a task queue.

A spreadsheet is fine for a prototype. SQLite is better once you want history, checks, and review steps.

Minimal table design

A first SQLite version can use two tables:

CREATE TABLE keyword_targets (
  id INTEGER PRIMARY KEY,
  keyword TEXT NOT NULL,
  target_url TEXT,
  country TEXT DEFAULT 'us',
  cluster TEXT,
  status TEXT DEFAULT 'active'
);

CREATE TABLE keyword_snapshots (
  id INTEGER PRIMARY KEY,
  keyword_id INTEGER NOT NULL,
  checked_at TEXT NOT NULL,
  position INTEGER,
  url TEXT,
  competitor_url TEXT,
  notes TEXT,
  FOREIGN KEY(keyword_id) REFERENCES keyword_targets(id)
);

n8n workflow outline

1. Schedule trigger

Run daily or weekly. Start small. A narrow monitored keyword set is more useful than a large noisy export.

2. Load active keyword targets

Read the active keyword list from SQLite, a database, or a controlled Google Sheet.

Required fields:

• keyword,
• country,
• target URL,
• cluster,
• alert threshold.

3. Pull SEO data

Call the selected SEO data source. If using Semrush, keep API credentials in n8n credentials or environment variables, not in node bodies or exported workflow JSON.

4. Store snapshot

Write the result to the snapshot table before deciding what to do. This preserves history and makes debugging possible.

5. Compare against previous snapshot

Useful triggers:

• position changed by more than a set threshold,
• target page dropped out of top results,
• competitor replaced your page,
• URL changed for the same keyword,
• keyword enters striking distance,
• no data returned where data existed before.

6. Send operator alert

A good alert includes:

• keyword,
• previous state,
• current state,
• affected page,
• suspected reason,
• recommended next action.

Bad alert:

Keyword changed.

Good alert:

“seo automation workflows” moved from position 11 to 7. Target page is now close to top 5. Review intro, add comparison table, and check internal links from two related articles.

AEO/GEO extension

Classic keyword monitoring should be paired with answer coverage.

For each priority keyword, add:

• target question,
• entity being explained,
• answer section on the page,
• source-backed claim,
• structured or scannable summary,
• last checked date.

This gives the same workflow value for AI-search visibility: monitor whether the page is still a good answer, not only whether it ranks.

Tool choice

Semrush can be a useful input source when you need SEO data, competitor context, and keyword research in one system.

Review checklist

Before relying on this workflow:

• credentials are stored securely,
• API errors are logged,
• duplicate alerts are suppressed,
• snapshots are retained long enough to compare changes,
• thresholds are documented,
• alert owners know what action to take,
• source notes make it clear which claims came from which export or API response.