Pageoptimized
Sign inStart
Module 09

Rank tracking and Search Console

Use first-party search performance and controlled rank monitoring together to diagnose demand, visibility, presentation, and page movement.

  • Business owners
  • SEO specialists
  • Reporting teams
  • Agencies
Module case file

Horizon Legal must explain movement, not export positions

The firm tracks 12 keywords weekly while Search Console contains broader query and page evidence. You must use both sources to diagnose one material change.

Rank Tracker
12 keywords; Google; desktop and mobile; weekly
Search Console
11,198 clicks; 366,713 impressions; 3.1% CTR
Change to diagnose
Settlement calculator moved from 4 to 9
Context
Impressions held, so demand loss is not the leading explanation
Your finished deliverable

Produce a dated diagnosis that names the affected cohort, likely cause, confidence, next action, owner, and review date.

Lesson 9.1

Read Search Console dimensions

Avoid diagnosing an aggregate when the movement belongs to a page, query, country, device, or appearance.

Why this matters

Clicks, impressions, CTR, and average position describe different parts of search performance and change with query mix. Segment before explaining.

Build yours

  1. Set a meaningful date comparison.
  2. Review query and page movement.
  3. Segment country, device, and search appearance.
  4. Check whether demand, rank, or presentation changed.
  5. Record data limitations and anonymized-query effects.
Completed example: Horizon Legal

Search Console segment

A broad total is narrowed to the page and query cohort that needs a decision.

Finished output

Period
Jul 22-Aug 18 vs. previous 28 days
Dimensions
US, all devices, query contains settlement calculator
Metrics
132 clicks; 6,200 impressions; 2.1% CTR; 13.1 avg. position
Page
/resources/settlement-calculator/
Decision

Open the page dimension and compare its query mix before changing the page.

Save this in

Saved Search Console observation: Settlement calculator cohort.

Actual product

Find page-level movement

The Pages view connects search movement to the URL that can actually be inspected and improved.

Full sizeOpen product
PageOptimized Search Console pages view with clicks, impressions, CTR, position, and page movement.Open full size
  1. Choose comparison.
  2. Find the affected page.
  3. Inspect its query mix.
  4. Create a verified follow-up.

Before you move on

  • The comparison period is appropriate.
  • The explanation names the segment.
  • Average position is not treated as a fixed rank.
Lesson 9.2

Design the rank-tracking set

Track keywords where controlled observations will change a decision.

Why this matters

Rank tracking samples a market, device, engine, depth, and schedule. It is valuable for chosen cohorts and competitors, not a replacement for first-party performance.

Build yours

  1. Choose approved keywords and target pages.
  2. Set engine, market, device, cadence, and depth.
  3. Add relevant competitors.
  4. Tag by page group or decision cohort.
  5. Document expected volatility and review triggers.
Completed example: Horizon Legal

Decision-ready tracking set

The set is small because every keyword represents a monitored decision.

Finished output

Cadence
Weekly
Engines and devices
Google; desktop and mobile
Keywords
12 approved service, location, and resource terms
Competitors
Two saved search competitors
Tags
Austin, service, resource, high priority
Decision

Do not add every Search Console query; track terms whose movement changes work.

Save this in

Rank Tracker: horizonlegal.com tracking target.

Actual product

Compare rank distribution and competitor movement

Rank Tracker preserves engine, device, market, cadence, competitors, history, and exact tracked URLs in the project.

Full sizeOpen product
PageOptimized Rank Tracker showing position distribution, average position trend, competitors, and tracked keywords.Open full size
  1. Confirm tracking scope.
  2. Review distribution before individual terms.
  3. Open the changed cohort.
  4. Connect the movement to other evidence.

Before you move on

  • Scope is visible.
  • Tracked terms have owners or use cases.
  • The list is not padded with vanity terms.
Lesson 9.3

Diagnose movement

Separate ranking loss, demand change, CTR change, cannibalization, SERP change, and technical failure.

Why this matters

A position change is a signal. Combine tracked history with Search Console, page changes, crawl evidence, competitors, and result features before choosing work.

Build yours

  1. Confirm the affected cohort and duration.
  2. Compare impressions, clicks, CTR, and position.
  3. Inspect target URL changes and cannibalization.
  4. Review competitors and result features.
  5. Choose fix, test, monitor, or no action.
Completed example: Horizon Legal

Settlement calculator movement diagnosis

Rank and Search Console evidence are read together.

Finished output

Tracked position
4 to 9
Impressions
Held during the change
Interpretation
Ranking loss is more likely than demand loss
Checks
Page changes, cannibalization, SERP composition, technical state
Confidence
Medium until those checks are complete
Decision

Open a diagnosis task; do not immediately rewrite or create a duplicate page.

Save this in

Work Queue: Diagnose settlement calculator loss, review Aug 28.

Before you move on

  • The diagnosis uses more than one signal.
  • Short-lived volatility is not overreacted to.
  • The action matches the evidence.
Lesson 9.4

Report the decision, not the export

Communicate what changed, why it matters, what is known, and what happens next.

Why this matters

A useful report connects completed work, observed movement, confidence, and next action. It does not hide uncertainty behind a dashboard screenshot.

Build yours

  1. Lead with the outcome or decision.
  2. Show the smallest useful evidence view.
  3. State scope and uncertainty.
  4. Name completed and pending work.
  5. Assign the next review date.
Completed example: Horizon Legal

Decision report

The report states what changed, what it means, and what happens next.

Finished output

Observation
Calculator rank fell from 4 to 9 while impressions held
Meaning
Visibility loss, not evidence of lower demand
Action
Review page changes and competing URLs
Owner
SEO lead; due Aug 26
Review
Weekly rank run plus 28-day Search Console cohort
Decision

Report the decision and confidence; attach detailed rows as evidence, not as the report itself.

Save this in

Client Proof block linked to the Work Queue task and source views.

Before you move on

  • The reader can make a decision.
  • Metrics retain context.
  • Next action has an owner.
Primary references

Verify the practice at the source.

Practices and source links reviewed August 2026.