Monitor GSC queries with target positions and drop alerts

Google Search Console reports an average position for the real impressions your pages received. Content monitoring shows when those pages change. The GSC Query Monitor connects them: choose important queries, set a target for each, and compare adjacent windows from the daily Search Console import. When a query crosses the configured line, an alert lands in Telegram or Slack with the measured reason.

What it does in one sentence

Keep a watchlist of queries per site. After the GSC import, 2-UA checks each query against two rules — a target average position and a sudden drop step — and sends one consolidated alert per site if any query crosses a threshold.

Two alert rules, both off by default

Each watched keyword has two independent triggers — and both are configurable per keyword:

• Target position threshold. Set a number — say 10. If the keyword's average position over a rolling window (default 7 days) is worse than that target, the keyword fires an alert. Averaging smooths out single-day spikes from Google ranking volatility.
• Drop-step alert. If today's position is at least N positions worse than yesterday's reading, fire. Default step is 10 — a full page of search results. This catches sudden falls even when the average is still on target. Available on paid plans.

Both rules read from the same Search Console data — so there is no extra fetcher or scraping. Average position is impression-weighted and may vary by page, device, country, location, and search history. GSC commonly reports with a 2–3 day delay, so this is not a fixed live SERP position.

Site-wide and per-page modes

A keyword can be tracked in two modes:

• Site-wide (default) — 2-UA aggregates positions across every page that ranks for that query. Best for keywords where Google may shift the landing page over time, or when you simply care that something from your site holds the position.
• Page-bound — pin the query to one tracked URL. This isolates the GSC rows for a landing page instead of combining every URL that received impressions for the query.

In site-wide monitoring, the current and previous values are impression-weighted across all matching landing-page rows. Multiple URLs are evidence to review for possible cannibalization, not an automatic diagnosis.

What the notification looks like

Alerts are aggregated per site — one message lists every keyword that crossed a threshold, regardless of how many. Two real-shape examples:

🔻 GSC query alert: 1 query below target — https://example.com

· "best seo monitoring tool" — avg position 14.2 over 7 days is below target 10

Open dashboard: https://2-ua.com/site/123/keywords

🔻 GSC query alert: 3 queries below target — https://example.com

· "best seo monitoring tool" — avg position 14.2 over 7 days is below target 10
· "website change tracker" — position dropped by 11.5 (from 4.5 to 16.0)
· "competitor seo watch" — avg position 22.0 over 7 days is below target 15

Open dashboard: https://2-ua.com/site/123/keywords

The message goes to all configured destinations for the site — Telegram chats, Slack channels, or both. There is also a 24-hour cooldown per keyword, so a single regression cannot turn into a flood. Cooldown is consumed only when the message is actually delivered, so quiet hours and template filters do not silently swallow alerts.

Plan-aware limits

GSC query monitoring is plan-aware:

• Free 7-day trial — up to 5 watched keywords per site, 14-day position history, threshold alert only.
• Monitor — essential monitoring and threshold alerts.
• Growth — expanded monitoring with threshold and drop-step alerts.
• Enterprise / Giga plans — start at 100 keywords per site and 120-day history, then scale with the selected tier.

Position history is retained for the period above. Older rows are trimmed automatically once a day.

Monitored queries are not lost in the long tail

The daily import takes the top 5 000 search rows for each site. On large sites a target keyword can easily fall outside that window — historically that meant no data, ever. To prevent this, after the bulk fetch 2-UA loops through every active watched keyword on the site and runs a targeted GSC query for any keyword that did not appear in the bulk rows. The result is filed into the same table as the bulk import, so the threshold and drop-step rules always have data to evaluate.

How alerts are computed

1. Every morning at 04:00 UTC, the GSC import pulls date / query / page / device / country rows for the latest available reporting date.
2. At 04:30, the keyword check service walks every active watched keyword on every confirmed site.
3. For each keyword, it computes the average position over the configured window and compares the latest day's position to the previous reading on file.
4. If a rule is triggered and the site's alert policy allows the event right now (no quiet hours, no template suppression), the keyword is added to the per-site dispatch list.
5. One consolidated message is sent and the per-keyword cooldown timestamp is updated.

The 04:45 UTC retention job then trims any history rows older than the plan limit.

How to start

1. Open Site → GSC Query Monitor from the per-site overview.
2. Add a query and choose a target position (the lower, the stricter).
3. Optionally set the averaging window (1–30 days) and the drop-step threshold.
4. Optionally bind the keyword to a specific tracked URL on the site for page-bound monitoring.
5. Wait for the next nightly import. Status updates the next morning.

Telegram and Slack delivery use the same routing as every other site notification — no extra setup needed if your site already has notifications wired up.

When to use this versus the GSC overlay

The GSC integration in 2-UA overlays clicks, impressions, CTR, and average position with content-change markers — that view is for diagnosis. GSC Query Monitor is for routing. If you want to investigate why traffic moved, use the GSC chart. If you want to be told when a selected query needs attention, add it to the monitor. Most teams use both: the chart to debug, the monitor to be paged.