What Is Pogo Sticking

Pogo sticking is the pattern where someone clicks a search result, spends a few seconds on the page, then clicks back to the search results and picks a different link. I have seen it described as a 'bounce plus a second click', but that undersells it. The key difference from a bounce is that the user is explicitly dissatisfied — they did not just leave; they left and went looking for a better answer. A bounce can happen when someone finds the exact phone number they needed and leaves satisfied. Pogo sticking is a signal that the page failed the user's intent test.

I used to think pogo sticking was a direct ranking penalty, but Google's John Mueller has publicly stated it is not. The danger is that SEO writers still treat it as one. What matters is what it reveals: a mismatch between the title and the content, a slow page that pushes users away, or a page that requires too much effort to find the answer. If you see pogo sticking in your analytics, do not panic about a penalty. Do look at the page's relevance and speed.

For example, I once worked on a site that had a page titled 'Best Budget Laptops 2025' but the content was a list of laptops over $1,000. The click-through rate was high, but the bounce rate was 80% and the average session duration was under 10 seconds. That is pogo sticking in action. Fixing the title and adding a budget section cut the bounce rate by half within a month.

Pogo sticking matters as a diagnostic tool, not as a direct ranking input. I focus on it when I see a page that has high impressions in Google Search Console but a low click-through rate or a high bounce rate. That combination often means the query matches the title but the page does not deliver. The remedy is almost always a mismatch in search intent.

It matters most for pages where the search intent is hard to nail down — transactional queries for 'buy' may be clearer, but informational queries like 'how to fix a leaky tap' can be satisfied by a video, a step-by-step guide, or a product page. If you are writing for a broad query, you must decide which intent you will serve and then signal that clearly in the title and meta description. I have lost count of how many times I have seen a page that tries to cover all intents and ends up satisfying none.

Pogo sticking also matters for mobile users. On a slow connection, a 3-second delay can increase the chance of a click-back by over 30%. That is why I always check [mobile SEO](/mobile-seo/) alongside content quality. If your site relies on [JavaScript SEO](/javascript-seo/) for rendering, make sure the critical content loads fast — otherwise users will see a blank screen and pogo back instantly.

Another area where I see pogo sticking is in e-commerce product pages. If a user clicks a result for 'blue running shoes' and the page shows a mix of colours with no filter, they will often go back and try another result. That is a [website structure](/website-structure/) problem, not a ranking problem. Fixing the structure and adding faceted navigation can turn that pogo-stick into a conversion.

I used to treat pogo sticking as a direct ranking factor. I would run a [technical SEO audit](/technical-seo/) and flag any page with a high bounce rate as being 'penalised by pogo sticking'. That was wrong. Google has repeatedly said it is not a signal in the algorithm. What I should have been doing was using it as a user experience signal to improve the page.

I also conflated pogo sticking with dwell time. Dwell time is the time a user spends on a page before returning to the SERP. Pogo sticking is specifically the behaviour of clicking back and then clicking another result. A user can have a short dwell time and still be satisfied — they found the answer quickly. Pogo sticking implies dissatisfaction. That distinction matters because it changes how you interpret the data.

Another mistake: I thought pogo sticking was only caused by poor content. I ignored page speed. I once spent two weeks rewriting a page to reduce bounce rate, only to find that the real issue was a 6-second load time on 3G. A [Core Web Vitals](/core-web-vitals/) audit revealed the problem immediately. After optimising images and removing a render-blocking script, the bounce rate dropped by 40% without a single word change.

Finally, I used to obsess over pogo sticking on every page. Now I know it only matters for high-traffic, intent-driven queries. For navigational queries like 'Facebook login', pogo sticking is rare because the intent is clear. For informational queries on a topic you cover well, a small amount of pogo sticking is normal. Do not over-optimise — just fix the obvious mismatches.