> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Position Trend, Google Search Console > Tracks how your average organic ranking position moves over time across the selected period. How to read it, why it matters, and how to act on it. **Card class:** [Sensitivity](/nerve-centre/overview#card-classes-explained) • **Category:** [Ranking Analysis](/nerve-centre/connectors#connectors-by-type) > The week-by-week storyline of where you sit in Google's organic results: rising, flat, or slipping. ## At a glance > **Position Trend** plots your **average organic position from Google Search Console as a time series across the selected period**, so SEO and content teams can see direction at a glance rather than a single snapshot. Average position is reported on Google's scale where **1 is the top of the results and higher numbers are further down**, so a falling line is good news and a rising line is a warning. The card is a sensitivity-tracked trend: it watches the slope, not just the latest value. | | | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **What it tracks** | The Search Console **average position** metric, sampled at each interval and drawn as a line so you can read the trajectory. Source `detail`: *"Position Trend for the selected period."* The value is the impression-weighted mean position of every result your site appeared for. | | **Data source** | Google Search Console Search Analytics, the same `position` figure exposed under **Performance on Search results**, pulled through the Search Analytics API and aggregated by Vortex IQ across the chosen window. | | **Direction** | Lower is better. Position 1.0 is the top organic slot; position 8.0 is mid page-one; anything above \~10 means you have slipped to page two or beyond for the weighted average. | | **Sensitivity bands** | `gsc_position`: an average around **10 or better reads healthy (green)**, drifting toward **30 reads poor (red)**. The amber zone in between is "watch this". | | **Time window** | Follows the dashboard period selector. No fixed alert window is configured on this card; it is a trend, read alongside the alert cards below for hard triggers. | | **Alert trigger** | None set on this card directly. For a fired alert on sharp ranking loss, pair with [Ranking-Drop Alert](/nerve-centre/kpi-cards/google-search-console/ranking-drop-alert). | | **Roles** | owner, marketing, seo | ## Calculation Search Console reports **average position** as the mean of the highest position your site reached for each query and date combination, weighted by impressions. For a single result, the position is its rank on the results page when it was shown (counting from the top, so position 3 means the third organic listing). Search Console then averages those positions across every impression in the period. Vortex IQ reads this `position` metric from the Search Analytics API for each interval in the selected window and draws the sequence as a line. Two points worth holding in mind: * The metric is **impression-weighted**, so a single high-volume head term sitting at position 4 moves the line far more than a hundred long-tail terms sitting at position 40. A "worsening" average can simply mean you started ranking (and so collecting impressions) for a new batch of low-position long-tail queries. * Position is reported to one decimal place. Small wobbles of 0.2 to 0.5 between intervals are normal sampling noise, not movement worth acting on. The sensitivity bands (`gsc_position`) exist to separate noise from a real slide. Filtering matters: the line you see reflects whatever scope the dashboard is set to (search type, country, device if applied). An aggregate "all of web search" line behaves very differently from a "mobile, GB only" line. ## Worked example A UK homeware brand running editorial content alongside its product catalogue connects Google Search Console. The dashboard is set to the last 12 weeks, web search, all devices. The Position Trend line reads: | Week ending | Average position | Reading | | ----------- | ---------------- | ------------------------------------------- | | 04 May 26 | 8.4 | Healthy, solid page-one weighted average | | 11 May 26 | 8.6 | Flat, within noise | | 18 May 26 | 8.5 | Flat | | 25 May 26 | 11.2 | Slip onto page two for the weighted average | | 01 Jun 26 | 13.7 | Continuing to drift down | | 08 Jun 26 | 14.1 | Stabilising but well below baseline | Three observations the SEO lead drew from this: 1. **The slip is real, not noise.** A move from 8.5 to 11.2 in one week is roughly 2.7 positions, far outside the 0.2 to 0.5 wobble band. The line crossed out of the green zone toward amber, which is exactly what the `gsc_position` sensitivity is calibrated to flag. 2. **Splitting the line by query type found the cause.** Re-running the view filtered to non-branded queries showed the slide concentrated in a cluster of buying-guide articles. Branded queries held at position 1.2 throughout. The cause was a Google core update that re-ranked editorial content; the product pages were untouched. Pair with [Branded vs Non-Branded](/nerve-centre/kpi-cards/google-search-console/branded-vs-non-branded) to make this split routine. 3. **The weighted-average trap.** Part of the drop was benign: the brand had just published 30 new long-tail articles that started ranking around position 25 to 35. Those new low-position impressions dragged the average down even though nothing existing had moved. [Position Distribution](/nerve-centre/kpi-cards/google-search-console/position-distribution) confirmed the head terms were stable and the new mass sat in the tail. **Rule of thumb.** Watch the slope over three or more intervals, not week-to-week jitter. A sustained rise of two positions or more, especially one that pushes the line out of the green band, warrants a query-level and page-level drill-down before you conclude rankings are genuinely falling. ## Sibling cards SEO teams should reference together | Card | Why pair it with Position Trend | | ---------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- | | [Average Position](/nerve-centre/kpi-cards/google-search-console/average-position) | The single-number companion. Position Trend shows the line; Average Position shows the current headline figure. | | [Position Histogram](/nerve-centre/kpi-cards/google-search-console/position-histogram) | Shows the spread of queries across position buckets, so you can tell whether a moving average is the head shifting or the tail growing. | | [Position Distribution](/nerve-centre/kpi-cards/google-search-console/position-distribution) | Breaks the same data into ranges (1 to 3, 4 to 10, 11+) to separate page-one strength from deeper pages. | | [Ranking-Drop Alert](/nerve-centre/kpi-cards/google-search-console/ranking-drop-alert) | The fired-alert sibling. When this trend slides, the alert card tells you whether it crossed a hard threshold. | | [Ranking Volatility](/nerve-centre/kpi-cards/google-search-console/ranking-volatility) | Quantifies how jumpy your positions are, useful for deciding whether a dip is noise or a real move. | | [Position Change](/nerve-centre/kpi-cards/google-search-console/position-change) | Period-over-period delta per query, the natural drill-down once the trend turns. | | [Branded vs Non-Branded](/nerve-centre/kpi-cards/google-search-console/branded-vs-non-branded) | Splits the trend so a non-branded slide is not masked by stable branded terms. | | [Clicks Trend](/nerve-centre/kpi-cards/google-search-console/clicks-trend) | The downstream impact. Falling positions usually drag clicks down a step later. | ## Reconciling against the source **Where to look in Google Search Console:** > Open **Performance on Search results**, tick the **Average position** metric, and set the date range to match the dashboard window. The chart Search Console draws is the native equivalent of this card. The headline "Average position" figure above the chart is the period mean for the same scope. To reconcile cleanly, match four things between the two views: | Setting | What to check | | ---------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | **Search type** | Search Console defaults to "Web". If you have filtered the dashboard to Image, Video, or News, switch the Search Console tab to match. | | **Country / device filters** | Any filter applied in Vortex IQ must be applied as a Search Console filter too, otherwise the aggregates differ. | | **Date range** | Use identical start and end dates. Search Console's "last 3 months" preset is a rolling window, not calendar months. | | **Property scope** | A domain property aggregates all subdomains and protocols; a URL-prefix property does not. Confirm you are comparing the same property type. | You can also pull the same numbers programmatically from the **Search Analytics API** (`searchanalytics.query` with `position` requested), which is the exact source Vortex IQ reads. API and UI agree when the dimensions and date range match. **Why the figures may legitimately differ:** * **Data delay.** Search Console data is typically **2 to 3 days behind**. The most recent interval on the card may still be filling in and can shift slightly over the following days. * **Anonymised queries.** Search Console drops rare queries to protect user privacy, so query-level totals never fully reconcile to the property-level average. The property-level average position you compare against is the safe baseline. * **Row caps.** The Search Console UI caps tables at **1,000 rows**. If you reconcile by exporting query rows and re-averaging, you will be missing the long tail and your hand-computed average will not match. Always compare against the property-level "Average position" figure, not a re-average of exported rows. * **Weighting.** The average is impression-weighted by date and query. A naive average of positions you see in a table is unweighted and will not match. ## Known limitations / FAQs **Why did my average position get worse right after I published a lot of new content?** Almost always the weighted-average trap. New pages tend to enter the index at low positions (20 to 40), and those fresh low-position impressions pull the mean down even though nothing existing has slipped. Check [Position Distribution](/nerve-centre/kpi-cards/google-search-console/position-distribution): if the head buckets are stable and the tail has grown, your existing rankings are fine. **Is a lower number better or worse?** Lower is better. Position 1.0 is the top organic result. The line falling is good; the line rising means you are drifting down the page. **The card says position 9 but I see my page at the top when I search. Which is right?** Both, in their own way. Search Console reports an impression-weighted average across every query, country and device where you appeared, plus personalisation and location affect what you personally see. A manual search from your own browser is one sample; the card is the aggregate of thousands. **How current is this line?** Expect the last 2 to 3 days to be incomplete because of Search Console's processing delay. Treat the most recent interval as provisional and read the trend from the settled intervals behind it. **Why doesn't this card have an alert?** Position Trend is a sensitivity-tracked trend, designed for reading direction. For a hard, fired alert when rankings drop sharply, use [Ranking-Drop Alert](/nerve-centre/kpi-cards/google-search-console/ranking-drop-alert), which watches for threshold-crossing moves rather than slope. **Should I worry about a 0.4 position wobble between two weeks?** No. Wobbles of a few tenths are normal sampling noise. The sensitivity bands and the slope over three or more intervals are what matter. Act on sustained moves of two positions or more, not single-interval jitter. *** ### Tracked live in Vortex IQ Nerve Centre *Position Trend* is one of hundreds of KPI pulses Vortex IQ tracks across Google Search Console and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.