example of seo

Every time someone asks me for an example of SEO, they are usually hoping for a tidy checklist. What they actually need is to watch somebody make a decision, act on it, and then show the number that moved afterwards. Last updated August 28, 2026, this article does exactly that. I have pulled five projects out of my own client files from the last three years, changed the brand names for confidentiality, and kept every real detail that matters: what the site looked like before, what we changed, how long the change took to register, and what we got wrong along the way.

I want to set an honest expectation first. In the eleven years I have worked on organic search, I have never once seen a single tactic carry a site on its own. The wins below all came from stacking three or four unglamorous fixes in the right order. If you are looking for the one trick, this is the wrong article. If you want to see how the work actually unfolds, keep reading.

Example One: A Plumbing Company That Grew By Deleting Pages

The client was a regional plumbing company in the Midwest with 412 indexed pages for a business that served nine towns. Somebody had built them a page for every possible combination of service and location: "emergency drain cleaning Fairview", "emergency drain cleaning Northbrook", and so on for hundreds of variants. The pages were 180 words each, and 74 percent of the text was identical between them.

Their organic sessions had been flat at roughly 1,900 per month for two years. Google Search Console showed 340 pages receiving zero impressions in a 90-day window. That was the signal. When a third of a small site is invisible, the problem is not that you need more content, it is that the content you have is diluting itself.

We consolidated 412 pages down to 38. Nine genuine location pages, each rewritten to 900 or so words with real details: the technicians who cover that area, photographs of jobs done there, the municipal water quirks of that town, and a genuinely different set of customer quotes. Then twelve service pages, a handful of resource articles, and the standard trust pages. Everything else received a 301 to its closest surviving relative.

Traffic dropped 14 percent in the first three weeks. That is the part nobody puts in a case study, and it is the part that makes clients panic. By week nine, sessions had climbed to 3,100. By month six, they were at 5,400, and the phone calls attributed to organic had gone from about 22 a month to 71. The lesson is that thin duplication is not neutral. It actively costs you. We rebuilt the surviving pages on a lean template as part of a broader website design refresh so the new copy actually had room to breathe.

Example Two: An On-Page SEO Fix Worth 60,000 Sessions

This is my favourite example of SEO because the change took one afternoon. A B2B software company had a documentation section that ranked for hundreds of long-tail queries. Every single page carried the same title tag pattern: "Docs | BrandName". No topic, no keyword, no differentiation.

We wrote unique title tags for 240 documentation pages, pulling the actual H1 concept into position one and keeping the brand at the end. We also rewrote the meta descriptions for the top 60 pages by impression volume, focusing on stating what the page lets you accomplish rather than describing what the page is.

Average click-through rate across those URLs went from 1.4 percent to 3.9 percent over ten weeks. Impressions barely moved. Clicks went from roughly 8,000 a month to just under 23,000. Annualised, that fix was worth about 60,000 extra sessions at a cost of one person's afternoon.

Example Three: Technical SEO On A JavaScript Site That Would Not Index

A direct-to-consumer furniture brand launched a new storefront and lost 68 percent of organic revenue in five weeks. The design was beautiful. The problem was that product listing pages rendered entirely client-side, and the category navigation was built with click handlers instead of anchor tags.

I ran a crawl with JavaScript rendering disabled and got exactly four crawlable URLs from the homepage. Googlebot can render JavaScript, but rendering is queued and expensive, and a link that does not exist in the DOM as an href is not a link at all no matter how well it renders.

The fix had three parts. First, every navigational element became a real anchor with a real href. Second, category and product pages moved to server rendering so the primary content and internal links existed in the initial HTML response. Third, we cut the largest contentful paint on mobile from 4.8 seconds to 1.9 by deferring a chat widget and a review script that together weighed 780 kilobytes.

Recovery took four months, and the site finished 23 percent above its pre-migration organic revenue. If you are building on a modern framework, this class of problem is entirely avoidable at the architecture stage, which is why I push clients towards teams that do proper Next JS web development rather than bolting search considerations on afterwards. The same caution applies to any single-page build, and I have seen the identical failure in projects handed to general React JS web development teams who were never told organic traffic mattered.

Example Four: Keyword Research That Started With Sales Calls, Not Tools

A managed IT services firm came to me with a keyword list their previous agency had produced. It had 1,400 terms sorted by search volume, headed by "IT support" at 33,000 monthly searches. They had written nine articles against that list in a year and generated four leads.

I did something different. I asked for recordings of thirty sales calls and read the transcripts. What prospects actually said, over and over, was things like "our server room floods every spring", "we failed a cyber insurance questionnaire", and "our last provider took four days to answer a ticket". None of those phrasings appeared in the keyword list.

We built content around eleven of those problems. The queries had volumes between 40 and 320 a month. The article about failing a cyber insurance questionnaire ranked third within seven weeks and produced 19 qualified demo requests in its first quarter. Total organic sessions rose only 31 percent that year. Pipeline attributed to organic rose 240 percent.

Example Five: Internal Linking On A 6,000-Page Publisher

A niche publisher in the outdoor equipment space had good content and terrible distribution of authority. Their homepage had a domain-level authority profile that any competitor would envy, and their best commercial pages sat five clicks deep with two internal links each.

We mapped every URL, its organic entrance volume, and its internal link count. Then we built what I call a hub correction: for each of the twelve highest-value commercial pages, we identified the fifteen most-trafficked informational articles that were topically adjacent and added one contextual link from each, placed inside a sentence that a reader would actually want to click.

That is 180 links, all editorial, all manually placed, all with varied anchor text. Nothing else changed. Over the following four months, the twelve target pages gained an average of 6.2 positions on their primary term, and revenue from that cluster rose 58 percent.

What These Examples Have In Common

Look across all five and you will notice none of them involved buying links, none involved publishing volume for its own sake, and none produced results in under six weeks. What they shared was a diagnosis step. In every case we found a specific mechanical reason the site was underperforming before touching anything.

They also shared measurement discipline. I set a baseline in Search Console, annotated the date of the change, and held the rest of the site steady long enough to attribute the result. When a client changes eight things in one sprint, you learn nothing, and next quarter you repeat the guesswork. Teams running structured digital marketing programmes tend to be better at this because they are already used to isolating variables across channels.

The third commonality is less comfortable. Every one of these sites had already spent money on SEO before they came to me, and in four out of five cases that money went into content production while an underlying structural problem sat untouched. Writing more articles on a site that cannot be crawled properly is like adding rooms to a house with no foundation.

Mistakes I Made On These Projects

On the plumbing consolidation, I redirected 340 URLs in a single deployment. That was wrong. It made the traffic dip steeper and harder to read, and if something had broken I would have had no way to isolate it. I now stage large redirect projects in three or four batches a fortnight apart.

On the furniture migration, I spent two weeks arguing about page speed before I checked crawlability. Speed was a real issue but it was the second issue. I lost a fortnight of recovery time because I anchored on the metric that had a nice dashboard instead of the problem that was actually blocking indexation.

On the publisher project, I initially wrote the 180 internal links myself in a spreadsheet without reading the host articles properly. Six of them landed in paragraphs where the link made no sense, and the editor rightly rejected them. Now I read the target paragraph before writing anchor text, every time.

How To Build Your Own Example

Start by exporting sixteen months of Search Console data at page level. Sort by impressions and look for pages with high impressions and click-through rates under 2 percent. Those are title tag and intent-match problems, and they are the fastest wins available to you.

Next, crawl your own site with a tool that respects robots directives and check three things: how many clicks from the homepage your money pages sit at, how many pages return a non-200 status, and how many pages have zero internal links pointing at them. That crawl usually surfaces the structural issue within an hour.

Then look at your top five competitors for one commercial term and read their pages properly rather than scoring them with a tool. Ask what question the page answers that yours does not. In my experience the answer is almost never "they used the keyword more times". It is usually specificity: real prices, real timelines, real photographs, real names.

Finally, pick one change, ship it alone, annotate the date, and wait eight weeks. The discipline of shipping one thing at a time is what turns activity into evidence. Sites that need supporting assets to make those pages competitive, whether that is diagrams, comparison charts or a proper infographic design treatment, should budget for them upfront rather than publishing bare text and hoping.

Frequently Asked Questions

Closing Thoughts

The most useful example of SEO is not the one with the biggest number attached. It is the one where you can trace a line from a diagnosis to a specific change to a specific outcome. Four of the five projects here produced their results from work that could be described in a single sentence, and in every case the hard part was figuring out which sentence.

If you take one thing away, make it this: measure before you build. Spend the first two weeks understanding what is broken and the following six months fixing it in the right order. That sequence is unremarkable, it is not what most agencies pitch, and in my experience it is the only thing that reliably works.