Independent comparison reference
People needed to compare versions of a product. I built pages from shared records, measured the search results, and added checks to catch bad data.
I built and maintain this project. I am withholding its name and address; the results and my ownership are stated directly.
- 14,135Google and Bing search clicks
- 464,504search-result appearances, summed across both engines
- 23,055GA4 Organic Search sessions
Complete months: April–September 2026. Search data: Google Search Console and Bing Webmaster Tools. Sessions: Google Analytics 4 Organic Search. These measures differ; growth has no proven cause here.
The reader's question
A reader had narrowed a choice but still needed to see which version offered which features. The useful unit was a side-by-side comparison with consistent definitions, not another general overview.
The system I built
The first pages carried facts directly in their markup, which made corrections slow and inconsistent. I rebuilt them around structured records. A template now reads the same fields for the comparison, supporting explanation and FAQ; validators check missing values, ranges, duplicates and disagreements between sources before publishing.
One later error showed that a shared field can still be read differently by two parts of a site. I traced the value through every consumer and added cross-view checks. The deploy also compares built content with the live version, so a data correction changes only the pages that actually need it.
What happened
From April through September 2026 it earned 14,135 search clicks, including 14,104 from Bing. That split matters: the result is substantial, but one search engine carries almost all of it.
- April 2026428
- May 20261,101
- June 20262,103
- July 20262,846
- August 20264,142
- September 20263,515
Bar lengths compare months within this project. The table gives exact values for clicks, appearances and sessions.
| Month | Search clicks | Search appearances | Organic sessions |
|---|---|---|---|
| 428 | 14,818 | 647 | |
| 1,101 | 31,826 | 1,809 | |
| 2,103 | 61,230 | 3,468 | |
| 2,846 | 93,820 | 4,577 | |
| 4,142 | 134,556 | 6,633 | |
| 3,515 | 128,254 | 5,921 |
What I corrected
An early spot check found errors across the initial hand-entered pages. I stopped patching page by page, normalized the records, and rebuilt from one source. A later malformed record still produced an indexable page, so I moved the thin-page sweep ahead of release. The open risk is that validation can establish consistency without proving every external fact is correct.
What the data does and does not say
The search totals establish that people reached the site, and the organic sessions measure visits under GA4's channel rules. They do not establish why one engine favored it or prove that a particular change produced the traffic. I will not turn that uncertainty into a success story about a tactic.
Daily property rows through September 30, 2026. Google data through 2026-10-20; Bing through 2026-10-18; GA4 through 2026-10-22. Property labels are withheld.