SEO LogbookSEO Logbook

SEO Case Study Template: Show What Changed and What Followed

A practical SEO case study template with an evidence worksheet and a filled example. Record the work, compare search results, and write claims you can support.

Amirhossein AmiriSenior SEO specialist and founder of SEO Logbook
7 min read
SEO LogbookSEO Reporting

Template

SEO Case Study Template: Show What Changed and What Followed

A case study is hardest to write when the work went well but nobody kept the record. You have a traffic chart, a few completed tasks, and a client who remembers the project differently. Now you have to reconstruct which page changed, when it went live, and what else happened before the numbers moved.

Collect that evidence while you work. This SEO case study template gives you a record to fill in at implementation, a comparison to complete later, and a way to turn both into a claim a buyer can inspect.

TL;DR

  • Download the SEO case study evidence worksheet. It includes a blank template and a fictional filled example.
  • Save the affected URL, baseline period, exact change, owner, live verification, and source links when work ships.
  • Compare the same Search Console property, search type, page, country, device, and length of time before and after.
  • Report absolute and percentage movement. Record other changes and limits beside the result.
  • Get permission for client names, screenshots, quotes, and performance figures before publication.

Start the record before you need a case study

Choose a project with a clear business problem and one or a small group of pages you can identify. A broad claim such as "we improved the client's SEO" is hard to trace. A page-level record is easier to check.

At the start, save:

FieldWhat to record
Business problemWhat the client needed and why it mattered
Page or page groupExact URL or a fixed list of URLs
BaselineDate range, clicks, impressions, and the relevant search context
ScopeWhat the team planned to change and what it did not control
Evidence sourceSearch Console property, report filter, and link or export

Keep the original numbers. If you later narrow the story to one country or device, save that filter and run the same filter on both periods. Google's Search Console performance guidance explains how to break results down by page, query, and country.

The baseline is the reference point for a later comparison. It is not a promise that the page will improve.

Record what actually went live

Separate a recommendation from an implemented change. A brief may be approved on Monday, the page may go live on Thursday, and a template update may overwrite the title the following week. Your case study needs the live version and date.

For every meaningful change, capture the affected URL, what changed, why, who owned it, approval if required, the live date, and a verification link or screenshot. Add a later recheck date for changes that can be overwritten.

For example:

/integrations/ga4/: Rewrote the title and opening section to match queries about connecting GA4 to the product. Added two relevant internal links. Content lead approved the copy on April 27. SEO verified the live page and title on April 30.

That entry says more than "optimized integrations page." It gives a future writer a specific intervention to connect to the page's history. The same record is useful even if the result turns out to be mixed or inconclusive. My guide to tracking SEO work across URLs and projects covers the broader workflow.

Compare periods that answer the same question

Choose the result metric before writing the headline. For a page case study, Search Console clicks and impressions are often the clearest starting point. CTR and average position can add context. Qualified leads or revenue need evidence from analytics, a CRM, or another business system.

Use equal-length before and after windows. Exclude the implementation day if the page changed partway through it. Keep the same page, search type, country, and device filters. Note when the after period is still incomplete or Search Console data is delayed.

Calculate both forms of movement:

MeasureCalculationWhy show it
Absolute changeAfter minus beforeShows the number of additional or fewer clicks
Relative change(After minus before) divided by beforeShows the change relative to the starting point
CTRClicks divided by impressionsShows how often a search impression became a click

For CTR, describe the difference in percentage points. A move from 2.0% to 2.4% is a 0.4 percentage point increase, not a 0.4% increase. If the before value is zero, leave the relative change blank and show the absolute change.

An adjacent 28-day comparison is useful for a first read. Check seasonality, query mix, other site edits, launches, and Google updates before you turn it into a confident story. Google's traffic investigation guide recommends comparing similar periods and checking whether a pattern also appears year over year. A before-and-after chart shows sequence; it does not isolate cause.

Filled example: a page refresh with a second change

Illustrative example only. Cedarline Analytics is fictional. The dates and figures below are invented to show how to use the template. They are not customer results.

EvidenceFilled record
GoalGet more qualified search visits to the GA4 integration page
URLhttps://example.com/integrations/ga4/
BaselineApril 1 to April 28, 2026; Google Web Search; United States; all devices
WorkTitle and opening section rewritten, two internal links added
Owner and live checkSEO lead; published April 29; title and copy verified April 30
Other changeA navigation link to the page was added May 5
ReviewApril 30 to May 27, 2026; same filters and 28-day length
Search Console measureBeforeAfterChange
Clicks120150+30 (+25.0%)
Impressions6,0006,200+200 (+3.3%)
CTR2.0%2.4%+0.4 percentage points

The page received 30 more clicks in the following 28 days. The title and copy refresh may have contributed, but the May 5 navigation change also affected how people and crawlers reached the page. The record supports a description of the work and the observed movement. It does not support "our copy refresh caused a 25% increase" or a revenue claim.

Turn the record into a short case study

Here is copy the fictional team could use after checking the numbers and obtaining publication approval:

Cedarline Analytics wanted more relevant search traffic to its GA4 integration page. On April 29, the team updated the page title and opening copy and added two internal links. The live changes were checked the next day. In the following 28 days, Google Search clicks to the page rose from 120 to 150, a gain of 30 clicks or 25%, while impressions increased from 6,000 to 6,200. A navigation link was also added during the review period, so these figures describe the page's movement after the work rather than the effect of one edit alone.

That paragraph names the client problem, the work, the period, the magnitude, and the important limit. It gives a buyer something to question. If the buyer asks about leads, the team needs analytics or CRM evidence before adding an answer.

Check the claim before publishing

Use the worksheet's publication fields as a final gate. Ask:

  1. Does each number match a saved source and the stated date range?
  2. Can someone open the URL, task, change record, and live verification?
  3. Did another edit, campaign, release, or search change affect the same period?
  4. Does the headline describe an observation or claim a cause you cannot isolate?
  5. Has the client approved the name, logo, quote, screenshots, and figures you plan to use?

If approval is pending, write the draft and hold publication. If you cannot identify the client, an anonymized case study can still be useful when the work and numbers are precise and you have permission to share them. Never turn illustrative data into a customer success claim.

Use the worksheet or keep the record in your project

The Excel worksheet has a blank page for your next project and a completed fictional example. Fill it in when the change ships, then return when a comparable after period is available. The formulas calculate click and impression movement, CTR, and whether the windows have equal length. The workbook leaves business results and publication approval as explicit human inputs.

If you manage several clients, keep this evidence with the work instead of reconstructing it before every sales call. SEO Logbook connects URL logs, tasks, live checks, and available Search Console comparisons. You can inspect that flow in the live demo. Search Console comparisons give you search movement around a change; leads and revenue still need their own sources.

The case study becomes easy to write when the page, work, verification, comparison, and permission are already in the record.

Related

Related posts