Results & case studies

Results need a source.
Work needs a record.

A search screenshot, an engineering release and a client growth study answer different questions. Here is what the available evidence can—and cannot—show.

Existing project evidence

The supplied Search Console snapshot.

This image was present in the original website files. The owner authorised its publication. The figures below reproduce the view in the source; they are not described as a growth uplift.

Owner-supplied Search Console snapshot

Search performance,
with the source in view.

28-day view shown in the source image. The original image is shown below so the reported figures can be read in context.

81.4KTotal clicks
491KTotal impressions
16.6%Average CTR
3.4Average position
Supplied Google Search Console screenshot showing a selected 28-day view: 81.4K clicks, 491K impressions, 16.6% average CTR and 3.4 average position
Owner-supplied screenshot, published with permission. Property identity and project scope are not disclosed. These are figures for the period shown, not a before-and-after uplift or revenue attribution.

What is visible

The screenshot shows Google Search Console’s search-performance report with a 28-day selection, total clicks, total impressions, average CTR and average position. Its plotted series can be inspected in the original image.

What remains undisclosed

The property identifier is cropped out. The delivery scope, baseline and causal relationship between the work and the figures are not documented here. We do not attach the image to a fabricated client, testimonial, AI citation or revenue claim.

More supplied source images

Separate snapshots.
Separate reporting periods.

These original assets are published with the same limitations. They are not added together, attached to invented clients or treated as a before-and-after comparison.

Snapshot 2: 19.6K clicks · 120K impressions · 7-day view
Owner-supplied Search Console 7-day view: 19.6K clicks, 120K impressions, 16.4% average CTR and 3.2 average position
Owner-supplied screenshot, published with permission. Property identity and project scope are not disclosed. These are figures for the period shown, not a before-and-after uplift or revenue attribution.
Snapshot 3: 25.8K clicks · 6.23M impressions · 3-month view
Owner-supplied Search Console 3-month view: 25.8K clicks, 6.23M impressions, 0.4% average CTR and 7.4 average position
Owner-supplied screenshot, published with permission. Property identity and project scope are not disclosed. These are figures for the period shown, not a before-and-after uplift or revenue attribution.
Snapshot 4: 3.11K clicks · 877K impressions · 7-day view
Owner-supplied Search Console 7-day view: 3.11K clicks, 877K impressions, 0.4% average CTR and 7.4 average position
Owner-supplied screenshot, published with permission. Property identity and project scope are not disclosed. These are figures for the period shown, not a before-and-after uplift or revenue attribution.

First-party implementation

Radian Ranks: the website
behind this page.

This is an internal website implementation example. The changes can be reviewed in the project; it is not a claim of client traffic or commercial growth.

radianranks.com First-party engineering example
Radian RanksRadian Ranks
Indexable HTMLAccessible enquiriesReviewed releases
Our own website · implementation example

Radian Ranks.
A website we can open up.

Explore the architecture, content decisions, enquiry flow and release checks behind this website. The published example describes implementation work; it does not claim client traffic or revenue growth.

Explore the implementation record

The constraint

The original website combined a static HTML mirror, unused application bundles, repeated service templates and marketing claims without a consistent evidence trail. The public enquiry flow needed clear validation and delivery states.

The implementation

Indexable HTML, individually composed core pages, contextual metadata, appropriate schema, canonical routing and a qualified enquiry flow. The light identity stays consistent while page structures follow their subject.

The acceptance checks

Inspect the published HTML, links and structured data. Exercise required fields and failure states, review representative viewports and run accessibility and build checks. Report local lab measurements separately from field performance.

The deployment still needs configured delivery credentials and a real inbox-receipt check. Local controlled provider tests do not prove production email delivery.

The standard for a complete client study

What a performance claim
needs behind it.

Evidence required before publishing a client outcome
Part of the studyWhat must be known
Client and permissionThe real business or approved anonymisation, the right to publish and the agency’s actual role.
Starting pointThe relevant baseline, affected pages or campaigns and the business constraint.
DeliverySpecific content, technical or acquisition changes, dates and responsibility.
MeasurementThe source, date range, conversion definition and treatment of seasonality, promotions and tracking gaps.
InterpretationWhat the data supports, what remains uncertain and what cannot be attributed to the engagement.
Educational example: a canonical finding.

The technical SEO audit walkthrough demonstrates investigation and acceptance checks using an explicitly hypothetical store. It is useful for understanding the handover, and is labelled separately from client results.

Start with a useful conversation

Bring a real question.
We’ll start with the evidence.

Send your website and the question you need answered. We’ll review the public pages and discuss a sensible next step.

  • A focused public-site review. No passwords needed.
  • No paid engagement until scope and fees are agreed.
  • UK and Australian enquiries welcome.
Website SEO auditFree review

Find your next SEO opportunity.

Tell us about your website. We’ll review the key issues and help you understand what to fix next.

Technical SEOContent & structureEnquiry paths
Optional budget context

No payment details. No account login needed.
A focused review; implementation is scoped separately.