Position Changed but Traffic Didn't — Why?

The 4 reasons position and traffic disconnect

When your rankings in LemRank show a significant change, but your traffic in Google Search Console remains flat, it can be confusing. This discrepancy typically indicates that one of four situations is occurring:

1. The keyword has near-zero search volume.
2. There is a device or country mismatch between your LemRank tracking and Google Search Console data.
3. A SERP feature is stealing clicks that would otherwise go to your organic listing.
4. Your Click-Through Rate (CTR) for that position is significantly below the expected curve.

Understanding which of these reasons applies can help you diagnose and address the issue.

Reason 1: keyword has near-zero volume

A common reason for a ranking change without a corresponding traffic impact is that the keyword in question has very little to no search volume. Search volume estimates provided by keyword tools are directional metrics. A keyword reported with "500/mo" in a keyword research tool might, in reality, deliver a much lower number of actual clicks. For example, if the Search Engine Results Page (SERP) is heavily dominated by paid advertisements, rich snippets, or other SERP features, an organic listing even at position 3 might only generate 50-100 actual clicks per month, despite a higher estimated volume.

If a keyword has an estimated volume of 0-10 searches per month, even a jump from position 10 to position 1 is unlikely to produce a noticeable traffic increase in Google Search Console. Google Search Console itself often filters out low-volume queries, making it difficult to confirm small traffic changes for such keywords.

Reason 2: device or country mismatch

LemRank allows you to track keyword rankings for specific devices (desktop, mobile) and countries. If your LemRank project is configured to track rankings for "mobile - United States," but your primary organic traffic source in Google Search Console is "desktop - United Kingdom," a ranking change in LemRank might not reflect in your overall Search Console traffic.

To verify this, cross-reference the device and country settings within your LemRank project with the segmentation options available in Google Search Console's Performance report. For example, if LemRank shows a rank drop for a mobile keyword in the US, but Search Console shows consistent overall traffic, check Search Console for mobile traffic specifically from the US. If that traffic has also dropped for the specific query, then LemRank's data is accurate. If it hasn't, then the discrepancy might be due to a difference in how Google reports data versus how LemRank tracks it (e.g., Google's internal heuristics for geo-targeting a query).

Reason 3: SERP feature stealing clicks

SERP features are elements on the search results page that provide direct answers, additional information, or alternative interaction methods without requiring a click to an organic website. Examples include Featured Snippets, People Also Ask boxes, Knowledge Panels, map packs, image carousels, and video carousels.

When you rank for a keyword, but a prominent SERP feature appears above or near your organic listing, that feature can "steal" clicks that would otherwise go to your website. Even if your organic position improves, if users find their answers directly within a Featured Snippet, they might not click on any organic results.

Consider this example:

Keyword	Position	Estimated Volume	Traffic Change
how to tie a knot	2	10,000	0

If the SERP for "how to tie a knot" prominently displays a video carousel or a Featured Snippet with step-by-step instructions, users might interact with these features instead of clicking to your site, even at position 2.

LemRank helps you identify the presence of SERP features in the SERP Features column within your keyword table. A significant number of active SERP features for a given keyword can indicate why traffic isn't increasing despite position improvements.

Reason 4: CTR way below curve

Click-Through Rate (CTR) refers to the percentage of users who click on your organic search result when it appears in the SERP. LemRank estimates the expected CTR for a given position based on an internal curve defined by getCtr() in src/lib/ctrCurve.ts. This curve considers factors like position to predict the likelihood of a click.

If your actual CTR is significantly below the expected CTR for your ranking position, an improvement in position might yield less traffic than anticipated. Several factors can contribute to a low CTR, even with good rankings:

• Uncompelling Title Tags or Meta Descriptions: Your snippet in the search results might not be attractive enough to users.
• Irrelevant Content Tease: The automatically generated description or your meta description might not accurately reflect the content or fulfill the search intent.
• Branding: Lesser-known brands may experience lower CTRs compared to established brands, even at the same position.
• SERP Noise: Very busy SERPs with many ads, local packs, or other features can push organic results down, lowering their visibility and implicitly their CTR, even if they technically stay high in "position."

For example:

Keyword	Position	Expected CTR	Actual CTR (GSC)	Traffic Change
best running shoes	3	8.5%	2.1%	0 (or slight)

In this scenario, even with a strong position, if only 2.1% of impressions result in a click (compared to an expected 8.5%), the traffic gain from a position improvement will be minimal.

How LemRank surfaces the actual cause

LemRank provides tools to help you identify which of these four scenarios is at play:

1. Search Volume Data: LemRank displays estimated search volume for each keyword. If a keyword's volume is very low, it immediately signals why traffic might not be moving.
2. Device and Country Tracking: Your project settings clearly define the device and country being tracked. This allows you to compare LemRank's data directly with segmented data from Google Search Console.
3. SERP Feature Tracking: LemRank tracks the presence of various SERP features for your keywords. The SERP Features column in your keyword table will show which features are active, helping you understand if they are diverting clicks. You can click on the SERP icon to view the actual SERP to inspect the features in detail.
4. Estimated vs. Actual CTR: While LemRank does not directly integrate with your Google Search Console data (it does not have access to your actual site's data), it provides expected CTRs based on its internal models. By comparing this expected CTR to your actual CTR data from Google Search Console (available in the "Performance" report), you can identify underperforming snippets. For instance, you can export your Google Search Console query data and sort by impressions. Then, compare the CTR for your top queries against the expected CTR for their reported position. If your site consistently has a lower actual CTR for a given position than what's generally expected, it points to a CTR issue.

By leveraging these features, you can move beyond simple rank tracking to diagnose why ranking changes aren't always translating into direct traffic gains, allowing for more informed SEO strategies.

Related

• How to Improve Organic CTR
• SERP Features Explained