Snippet A/B Planner
CTR Growth Engine — find hidden CTR growth potential, track snippet A/B tests and compare results before/after by position.
How to use
Analyzing...
How to Run a Snippet A/B Test
- Connect Google Search Console — the Planner surfaces pages where your CTR is significantly below the expected benchmark for your ranking position.
- Pick a page from the opportunity list — prioritise by the highest estimated lost clicks.
- Click Start Test and record your current title and meta description as the control variant.
- Write a new title or description, deploy it to your site, and record the change date in the test log.
- Wait at least 14–28 days for GSC data to stabilise — short windows produce unreliable results due to traffic volatility.
- Return to the Planner and click Complete Test — compare CTR before and after to measure the lift.
- If CTR improved, keep the new snippet. If not, hypothesise why and run the next variant.
Why Snippet Testing Beats Guessing
Most SEO teams never systematically test their title tags and meta descriptions. They optimise once during content creation and then forget. But a 1-percentage-point CTR improvement on a page with 10,000 monthly impressions means 100 extra free clicks every month — compounding across all your pages, this is one of the highest-ROI levers in organic search.
The challenge is knowing which pages to prioritise. The Snippet Planner uses GSC data to rank pages by the gap between actual and expected CTR. This removes the guesswork: you work on the pages with the biggest provable opportunity first.
Recording the exact change date matters because GSC data typically lags 2–3 days and search engines may take a week or more to re-index and re-rank after a snippet change. Without a log, you cannot cleanly isolate the effect of your snippet change from organic ranking fluctuations.
Frequently Asked Questions
How long should I run a snippet test?
Does changing the title affect rankings?
What makes an effective title tag?
Next step