Rank tracking records where a page appears for selected searches under defined conditions. It is useful for monitoring visibility and investigating changes. It cannot, on its own, show that an SEO change caused more revenue.
Table of Contents
Define the monitoring scope
Record the search engine, exact query, country or location, language, device, tracked URL, observation frequency and start date. Keep brand and non-brand queries distinguishable. A position observed in one setting does not describe every searcher’s result.
Choose queries that relate to the offers and questions the website actually serves. Preserve the original tracking list when making comparisons, and record additions separately so a larger query set does not appear to be organic growth.
Understand Search Console’s average position
Search Console averages position across recorded impressions. Its calculation uses the topmost position for the relevant property or page in each observation. Result layouts and aggregation affect interpretation.
A tracker typically samples a configured query and setting at particular times. It can disagree with Search Console without either measurement describing the same population. Compare each tool within its own scope.
Investigate a change before assigning a cause
- Check whether tracking settings, the query list or the reporting period changed.
- Identify the affected queries and owning pages.
- Check availability, indexing directives, canonicals and important content changes.
- Review changes in search-result formats and competing pages.
- Compare exposure, clicks and site outcomes over suitable periods.
Record hypotheses as hypotheses. A competitor’s new page, a search update or your own edit may coincide with a change without proving why it happened.
Report the business context
Pair rankings with relevant impressions, clicks and landing-page visits. Then examine received enquiries, validity, suitability and sales where those stages are measured. A movement from one position to another does not establish a proportional change in traffic or customers.
Check sample size, seasonality and the sales cycle. Explain missing data and unvalidated event definitions rather than presenting every tracked interaction as a lead.
Keep a useful change log
For each important change, record the date, affected pages, intended effect, responsible person and review window. Preserve comparable exports. Do not change titles every day in response to a small number of observations.
Use the keyword research guide when the monitoring list needs review. Use difficulty estimates for research questions, keeping them separate from observed positions.
