SEO Case Study: C4 Fire & Security, June to July 2026

C4 Fire & Security’s organic search clicks rose from 258 in June 2026 to 435 in July 2026, and impressions from 17,095 to 38,346, in Google Search Console. That growth came while its blog programme was running. An audit on 10 August then found the site competing with itself. This is what it found, what we changed on 10 and 11 August, and what we can and cannot yet claim.

What was actually wrong with the site’s search visibility?

Traffic was rising, but the site was working against itself. Two pages were competing for the same searches, one service hub had never been discovered by Google despite being live and in the sitemap, and the page indexing report showed that many pages were not indexed at all.

It does not look like a problem. Traffic is not falling. Nothing errors. The site simply performs below what its content deserves, because Google is being asked to choose between two pages that answer the same question, and it keeps choosing badly or splitting the credit between them.

C4 Fire & Security is a fire protection company in the Western Cape, in a trade where the searches are specific and the person making them is usually checking a compliance obligation rather than browsing for ideas. That makes search visibility unusually valuable, and it makes a wasted page unusually expensive, because a page that never surfaces is not a missed impression, it is a missed enquiry from somebody who had already decided to buy. KM Digital Solutions designed, built and still runs this website, so when the audit turned up problems, there was no external party to blame for any of them. The cannibalisation between two guides was diagnosed from a Search Console read on 27 July 2026, and the remaining findings came out of Search Console data pulled on 10 August 2026. Every fix ran against a site we had built ourselves. That is worth stating plainly, because most agency case studies are accounts of rescuing somebody else’s mistakes rather than of finding your own.

What did the audit find?

Three things. A service hub page that was live, in the sitemap and still unknown to Google on 10 August. A near duplicate of that page, self canonical, competing for the same topic. And a set of head terms where two pages were each collecting impressions for the same search, neither ranking as well as one page would have.

Taken separately, none of these is alarming. Taken together they describe a site quietly working against itself. The pattern is worth naming, because it is easy to check on your own site:

• A page Google has never discovered. Live, returns 200, sits in the XML sitemap, and Search Console’s URL Inspection still reports no referring page detected. A sitemap is an invitation, not an instruction. Without internal links pointing at a page, Google frequently never bothers.
• Two pages, one topic. A hub page and an older near duplicate, both self canonical, both eligible, both being weighed for the same searches.
• Split impressions on head terms. The same commercial search returning a guide page in one crawl and the home page in another, with the better page sitting further down. This was the 27 July finding.
• Visibility without clicks. Queries earning very high impressions at position one and almost no clicks, because the answer is being read inside the results page. That is not a failure, but it is worth recognising before you treat it as one.

Diagnosis is the part most SEO reporting skips, and it is the part that decides whether the work is worth anything. Google Search Central’s documentation on consolidating duplicate URLs explains that where several URLs carry the same content, Google identifies which version is objectively the best one to show and consolidates the signals it has for the individual URLs, such as links to them, into that single preferred URL. A duplicate does not sit there harmlessly. We read the Search Console page indexing report for this site line by line rather than looking at the traffic graph, because the traffic graph tells you what happened and the indexing report tells you why. The two categories that matter, Crawled but currently not indexed and Discovered but currently not indexed, are where a site’s wasted work quietly accumulates. On the C4 Fire & Security site, that is exactly where the answer was sitting.

What did we actually change?

We consolidated the duplicate, linked the orphaned hub from the pages that should always have pointed at it, and kept the publishing cadence running. There was no technical rebuild, no new platform and no link buying. The work shipped on 10 and 11 August 2026, after the growth described above had already been measured.

In order:

1. Requested indexing for the orphan, 10 August 2026. The hub page Google had never discovered was submitted for indexing directly through URL Inspection.
2. Resolved the duplicate, 11 August 2026. One page keeps the topic. The near duplicate now 301-redirects to the hub, so the signals stop being divided and start being pooled.
3. Linked the hub, 11 August 2026. The hub received internal links from the pages a reader would naturally travel from.
4. Named the cannibals and reframed the guide, 11 August 2026. Every head term where two pages split impressions was written down beside the page that should own it, and the guide that had been competing with the service page was reframed as top-of-funnel content, so the consolidation had a target rather than a guess.
5. Kept publishing. The blog programme that had been running for months carried on running. It is the reason the top organic landing pages on this site are guides rather than service pages.

We have not published a post-fix figure yet. Every figure quoted here came out of Search Console with its window attached, and all of those windows end before the fixes shipped.

The consolidation step is the one worth understanding properly, because it is counter intuitive: you improve a site by removing pages from contention rather than adding to them. Google’s guidance on consolidating duplicate URLs describes the mechanism directly. Where two pages compete, Google chooses the version it considers the best one to show and consolidates the signals for the set onto that choice, which means the outcome is decided for you unless you decide it yourself. Left alone, Google may pick the older page, the shorter page, or the one with the wrong commercial framing, and it may change its mind between crawls. We make that choice explicit on every site we audit.

What changed in the numbers?

Organic search clicks rose from 258 in June 2026 to 435 in July 2026. Search impressions rose 124%, from 17,095 to 38,346. The source is Google Search Console, and the window is one calendar month compared with the one before it. Those are the headline figures, and the supporting detail below carries its own windows. These figures describe the months before the August fixes; they are not a result of them.

The shape of the change matters more than its size. Impressions grew considerably faster than clicks, which is the signature of a visibility gain arriving ahead of a traffic gain. More searches now return the site at all, and a growing share of them are searches the site had never appeared for. Clicks follow that curve, but they follow it late.

Four supporting figures from the same audit are set out below, each with the window it was measured over. None of them is part of the headline comparison.

Source: Google Search Console, quoted in the audit of the C4 Fire & Security website dated 10 August 2026, with the windows re-checked on 16 September 2026.

What can we not claim yet?

The effect of the 10 and 11 August fixes. A redirect, a set of internal links and an indexing request all need a full Search Console window after the change before anyone can say what they did, and that window has to be measured on its own terms, not read into the growth that came before it. When a post-fix window has been measured and recorded, it will be added here with its dates. Until then, the honest summary is: the blog programme grew the site’s visibility, the audit found structural waste, and the fixes are in place.

What should you do if your site has the same problem?

Check for self competition before you commission anything new. Most sites that feel stuck do not need more content. They need the content they already have to stop arguing with itself, and they need the pages Google has never found to become findable.

The checks below need only Google Search Console access:

Google’s URL Inspection help explains what the referring page field means, and its sitemaps overview is clear that a sitemap helps Google find pages but does not guarantee they will be crawled or indexed.

If that audit finds nothing, your problem is genuinely one of content or authority, and publishing more will help. If it finds two or three of the five, publishing more will make things worse, because every new page joins a queue that is already fighting over the same searches. This is the order we work in on every site: diagnose, consolidate, then publish. Reversing those steps is the single most common way an honest content budget gets wasted, and it is invisible while it is happening, because the page count goes up and everybody feels productive. Our SEO service starts with the audit described here, and where the problems turn out to be structural rather than editorial, the fix usually lands in web development instead of content. For the wider picture, our guide to choosing an SEO agency covers what to ask before you sign anything, our technical SEO checklist covers the indexing checks in more depth, and how long SEO takes explains why a one-month window is a starting point rather than a verdict.

Frequently asked questions

How long did these results take?

The measured change covers one month, June 2026 to July 2026, and it arrived while the blog programme that had been running for months was still running. The audit came afterwards, on 10 August, and the fixes shipped on 10 and 11 August. Their effect has not been published yet, because it needs its own measured window. One month of growth is a data point, not a trend, which is why the supporting figures carry their own dates.

Did the August fixes cause the June to July growth?

No. The June and July figures were measured before the audit and before any fix shipped. The growth came from the publishing programme and from the visibility the site had already earned. The fixes of 10 and 11 August address the waste the audit found, and whatever they do will show in a later window, which will be reported on its own when it has been measured.

Is keyword cannibalisation a real problem, or is it overstated?

It is real, but it is frequently misdiagnosed. Two pages mentioning the same phrase is normal and harmless. The problem exists only when two pages genuinely target the same search intent, and you can confirm that rather than guess: filter the Search Console performance report by the query and check whether the landing page changes across the period. If it does not change, you do not have a cannibalisation problem.

Why do impressions rise faster than clicks?

Because appearing in more searches happens before ranking well in them. A page that moves from nowhere to position twenty earns impressions immediately and almost no clicks. As its position improves, the clicks arrive. A gap between impression growth and click growth is normally a healthy early signal, although it can also mean your titles are being ignored, which is worth checking separately.

Can you do this on a site you did not build?

Yes. The checks are the same on any site with Search Console access. This case is unusual in that KM Digital Solutions designed, built and still runs the C4 Fire & Security website, so the audit was partly an audit of our own earlier decisions. Working on an inherited site changes what is easy to fix, not what needs fixing.

Written by Milan van Wyk, director at KM Digital Solutions, Durbanville, Western Cape. The consolidation mechanism is from Google Search Central’s Consolidate duplicate URLs; the report categories are from the Page indexing report help; the referring page field is from the URL Inspection tool help; the sitemap behaviour is from the sitemaps overview. All Search Console figures were re-checked against the archived audit and the property on 16 September 2026. Published with C4 Fire & Security’s agreement to be named. All sources accessed on 16 September 2026.