T20 SEO experiment results readout
SEO experiment results readout
What finished SEO experiments and technical fixes showed this period, and what Northfield Search recommends rolling out, extending or stopping. Prepared across our active clients from the shared experiment and opportunity tracker.
The view below is our live measurement follow-up list. It holds every opportunity currently Measuring or Won across our clients, so you can see what just finished and what is still running. Rows with a past review date are ready for a verdict; we cover those first below.
Before you share this page with a client
This view lists results for every client we serve, not only yours. Before sending this page to anyone outside your own team, switch the embed to a view filtered to your client, or copy the page and filter that copy.
Sample template: the firm, people, clients and figures are fictional, and the embedded view holds synthetic sample records.
Live example from the Dashboards app, shown with Alder & Ash Home's demo data.
Results and verdicts
| Experiment | Client | Baseline | What we recommend | Verdict |
|---|---|---|---|---|
| Location page template | Harbor Lane | 310 clicks a month | Keep the new template and roll it out to the remaining locations | |
| Help article snippet answers | Acme | 90 clicks a month | Keep the list-format answers and apply them to five more help articles | |
| Sitemap cleanup | Northstar | 4,100 redirected or missing URLs | Keep sitemap generation limited to indexable URLs | |
| Consultation page rewrite | Redwood Advisory | 1.9% conversion rate | Keep the first-call outline and add it to the service pages |
All four finished items this period cleared their measurement window with a clean result. Not every experiment ends this way: declined and stopped items are tracked separately in the opportunity log and are outside this view because it only shows Measuring and Won.
What to watch before the next readout
| Experiment | Client | Status | Review by |
|---|---|---|---|
| Comparison page refresh | Beacon | Small effort refresh, watching click trend | Oct 15, 2026 |
| Guide title tag test | Cobalt Labs | Testing question-style titles on 10 guides against 10 controls | Oct 20, 2026 |
| Mobile menu crawl fix | Juniper Studio | Menu now renders in the initial HTML; watching indexed page count | Oct 6, 2026 |
| Case study hub | Beacon | 8 weeks post-launch | Nov 2, 2026 |
| Lodge booking page speed | Summit Ridge | Images compressed, availability widget deferred | 4 weeks after release |
| Fall planting guide refresh | Pine Hollow | Extended window because of a tracking gap | Nov 10, 2026 |
Limitation: tracking gap on the Pine Hollow guide refresh
The analytics tag was missing from the fall planting guide for 9 days after the Sep 2 refresh. What this means: the first 9 days of post-refresh data are unreliable and will be excluded from the comparison. What we did: extended the measurement window to Nov 10, 2026. Owner: Leo Hart, confirming the tag fires correctly before the next refresh ships.
We only roll a pattern out to more pages once we have a clean read. A rushed rollout on noisy data costs more time later than waiting two extra weeks.
What happens after a roll out verdict
How this readout is produced
- Baselines and results come from the client's analytics and search console accounts, or from the crawl log noted on the opportunity record.
- Verdict rules: Roll out means the result held at or above the hypothesis for the full measurement window. Extend means the window needs more time or more sample size. Stop means the result did not clear baseline and the change is reverted.
- Limitations: a tracking gap, a site release during the window, or a seasonal spike can all distort a reading; we note these next to the affected item rather than silently excluding them.
How to use this template
Duplicate this page once per reporting period. Replace these values; if a required value is missing, write Needs review next to it instead of guessing.
| Variable | Meaning | Required |
|---|---|---|
{{client.name}} | Client the readout covers, when shared with one client | Required |
{{readout.period}} | Reporting period the readout covers | Required |
{{experiment.verdict}} | Roll out, extend or stop, for each finished experiment | Required |
{{experiment.baseline}} | Baseline metric value recorded before the change | Required |
{{limitation.description}} | Any tracking gap or data issue affecting a result, with owner | Optional |
{{readout.next_date}} | Date of the next scheduled readout | Optional |
Never present a Measuring item as a finished result; keep it in the "still measuring" table until its window closes.