How to Track Keyword Rankings by Landing Page Instead of Keywords Alone

A useful ranking report should tell you which page needs work and why. If it only shows green and red arrows beside keywords, your team still has to translate those movements into an editing, technical, or internal-linking task.

Page-first tracking closes that gap. You keep the keyword evidence, but organize the report around the URLs you can actually improve. That makes three decisions easier: which pages are declining, where the wrong page is gaining visibility, and which pages deserve the next optimization sprint.

Make the landing page the unit of action

Tracking rankings by landing page means grouping query-level performance under the URL intended to satisfy those queries. Each page gets a performance summary, supporting keyword evidence, and a next action.

Suppose a SaaS comparison page targets “help desk software comparison” and several closely related searches. One query improves while three weaken. A keyword-only report presents four separate movements; a page-level report asks whether the comparison page is losing relevant visibility overall.

Keep two URL fields: the intended URL from your content strategy and the observed or reported URL from your data source. Without that distinction, a different page can start ranking and your report will treat it as success for the original page.

Also retain a fixed group of priority queries for each URL. Google Search Console’s average position summarizes the results represented in the selected data. A page’s average can worsen when it starts appearing for additional, lower-ranking queries, even while its established queries hold steady. Compare those established queries separately before declaring a decline.

Build the page-to-query map before measuring movement

Separate the map from the observations

Use two worksheet tabs. The first records your intended targeting; the second stores what happened over time.

• Query map: priority query, search intent, intended URL, business priority, and page owner.
• Observations: query, observed or reported URL, date or reporting period, country, device, data source, and position. For Search Console observations, include clicks and impressions too.

Assign one intended URL per query within the market and device segment you’re reviewing. This is an operational choice about which page you want to improve; it doesn’t assume Google can only show one page from your site.

Keep the query cohort stable during each comparison. Add newly discovered queries to a separate opportunity list, then deliberately revise the cohort for a future reporting cycle.

Use consistent monitoring settings

For recurring position checks, our ProjectHQ rank tracker automatically monitors keyword positions, retains historical trends, and supports tracking by country, region, and device. Use it to follow your priority queries consistently, then maintain the intended-page map and Search Console page evidence in your worksheet.

Choose the settings your customers actually represent. If you’re evaluating US mobile visibility, keep that segment separate from desktop or another country. Record the source beside every observation so a rank-tracker position never gets mistaken for a Search Console average.

Standardize URL variants only after checking that they represent the same page. Don’t blindly remove parameters or merge similar paths. For changed URLs, preserve an old-to-new mapping; our guide to tracking SEO after a website redesign explains the broader monitoring workflow.

How to track keyword rankings by landing page in Search Console

Start with the page, then inspect its queries

Google’s Performance report supports page and query dimensions alongside clicks, impressions, CTR, and average position. For a manageable set of priority URLs, use this workflow:

1. Open Performance → Search results and select the Web search type.
2. Set your country and device filters. Keep them unchanged throughout the comparison.
3. Compare two completed, equal-length periods. The latest complete 28 days versus the previous 28 days is a practical starting point; seasonal businesses should also consider a year-over-year comparison.
4. Enable clicks, impressions, CTR, and average position, then open the Pages tab.
5. Select the target URL to apply its page filter, then switch to Queries.
6. Export the table and retain the page URL, date ranges, and filter settings alongside the exported rows.

Before comparing periods, add a position-availability flag for each query and period. Google’s Performance report documentation warns that values displayed as “~” or “-” (unavailable) become zeros in downloaded data. Check zero or unavailable exported positions against the report, retain the availability flag, and treat unavailable positions as missing, never as rank zero. Compare positions only when both periods have valid values. Repeat the export and validation for your priority pages, keeping page totals for the summary and query-level evidence for diagnosis.

Search Console average position and a rank-tracker observation answer different questions. As Google’s Performance report documentation explains, Search Console uses the topmost result for the relevant aggregation: property-level reporting uses the highest result from your site, while page-level reporting uses the highest position of that page. The selected grouping therefore matters when comparing averages. A rank-tracker observation checks rankings under the tracker’s configured conditions. Never blend them into one “average rank” column.

Reverse the filters to investigate a page swap

When a priority query weakens, remove the page filter, apply an exact query filter, and open the Pages tab. Compare which URLs received impressions and clicks in each period.

This reveals whether visibility has shifted toward another URL. Inspect shorter date ranges or daily patterns to distinguish sustained replacement from a brief fluctuation. Two URLs appearing in a monthly report doesn’t establish that they repeatedly alternated in the same search results.

Account for canonical URLs and missing queries

Google assigns most Search Console performance data to the canonical URL. Its dimensions documentation explains that even a click on a duplicate URL can be credited to the canonical page. Treat that field as the Search Console reporting URL, rather than proof of the exact URL every visitor landed on.

The query list is also incomplete. Google omits anonymized queries and retains only some data rows; query filtering changes which totals include anonymized activity. As Google explains in its performance-data filtering guide, summing visible query rows won’t necessarily reproduce the chart total. Preserve page totals separately, and mark an absent query as unavailable rather than assuming it lost its ranking.

The weekly report: one row per intended URL

Keep the review sheet short enough to drive decisions. The table below uses hypothetical data; its flags illustrate a reporting model, not universal thresholds.

Intended page	GSC clicks, prior → current	Priority queries worsening	URL mismatch	Status	Next action
/help-desk-comparison	400 → 290	4 of 5	None found	Possible decline	Check indexability and recent changes
/customer-support-software	260 → 180	3 of 5	Blog URL gaining visibility	Possible swap	Inspect query-level URL history
/support-ticket-template	190 → 188	0 of 4	None found	Optimization candidate	Review CTR and search-result presentation

Keep impressions, CTR, the individual query comparisons, and URL observations in the supporting tab. For “queries worsening,” compare the same query, source, country, and device across periods. A numerically higher position means a worse ranking: moving from 4 to 7 is a decline of three places. Label whether the column uses Search Console averages or rank-tracker checks.

Show missing observations separately instead of silently shrinking the cohort. For example, “three worsening, one stable, one unavailable” is more useful than a percentage calculated from whichever queries remain visible.

Add page owner and business priority to the working sheet. If you also track organic landing-page key events in analytics, put them in a separate column with a consistent definition. Those outcomes help prioritize work, but they don’t belong inside the ranking calculation.

Diagnose declines, swaps, and optimization opportunities

A declining URL needs corroborating evidence

A click drop alone doesn’t prove rankings fell. Search demand or CTR could have changed.

Start with the fixed query cohort. If those positions worsen alongside page clicks, inspect impressions and look for a shared timing pattern. Check recent deployments, redirects, indexability, and canonical selection before commissioning a rewrite. A technical change calls for a different response than content that no longer satisfies the query.

If priority rankings remain stable while impressions fall, investigate demand and query mix. If impressions and positions hold but clicks weaken, move to the CTR review instead.

A ranking-page swap needs an intent check

Suppose a blog post begins receiving visibility for a query assigned to a commercial product page. First confirm the pattern under matching filters and across more than one observation. Then inspect the search results: does the query favor educational content, or should your product page genuinely be the stronger destination?

A planned URL migration can explain a replacement. Two distinct, relevant pages receiving visibility can also be legitimate. Flag an unwanted swap when the replacement conflicts with the intended task and the evidence supports a persistent change.

When overlapping pages serve the same purpose, assess differentiation or consolidation. When they serve different purposes, clarify the content focus and internal links. Use our content audit checklist to evaluate those options before redirecting or removing a useful page.

An optimization candidate needs a specific hypothesis

Look for pages with relevant impressions and a fixable weakness. Stable query positions paired with weaker CTR suggest reviewing the search-result presentation. Compare like-for-like queries, devices, and periods rather than applying one CTR benchmark across the site.

Check whether the title accurately promises the answer the page delivers, then inspect competing results and SERP features. Our guide to improving organic CTR without ranking higher develops that workflow.

For a page consistently below stronger results on its priority queries, compare the substance instead. A comparison page might need clearer selection criteria or evidence behind its recommendations. “Improve the comparison criteria” is an actionable brief; “add more keywords” leaves the underlying weakness undefined.

Give the review an owner and a next check

Review priority pages weekly, using longer comparison windows when traffic is sparse. Triage technical losses on business-critical URLs first, persistent unwanted swaps second, and optimization candidates after that.

For every selected page, record the hypothesis, a scoped intervention, the owner, the change date, and the next review date. Keep a change log so later movements can be interpreted alongside what your team actually shipped.

Start with a small set of valuable landing pages and their fixed query cohorts. Expand the report once it reliably produces decisions your team can execute; the useful output is a page-specific task with evidence and someone responsible for completing it.