Introduction: why this report exists
Customers now find Shepherd Neame pubs before they ever reach a website.
This edition is generated from live NeameGraph and Yext data for Wednesday 10th June 2026 to Friday 10th July 2026, across 275 active pubs. Three chapters: is our data ready, are we being found, and do people then act. Every figure names its source. Violet figures are sample data: they show what this report looks like once that feed is wired, and are never real numbers.
Chapter one: Found
Presence: where the estate can be discovered
"Are our pubs present and correct on the surfaces where people look?"
285
live entities syndicated via Yext (live API call)
the listings network Yext feeds
231
pubs with a verified Google profile link on record
presence coverage from identity links
911
Yext field changes detected this month
▲ 5594% vs prior month
Presence data is live: the estate's listings are syndicated through Yext and every field change is detected and logged by the nightly harvest (last run: 2 facts updated, 0 added). Performance figures for these listings (views, clicks, direction requests) are a named gap: the Yext Analytics module is not enabled on the account key, verified 09-Jul; enabling it, or the Google feed, unlocks this chapter's outcome numbers.
What to do next: ask Yext support to enable the Analytics API on the account (one setting, no build), or land the Google Business Profile feed. Either fills this chapter with views and actions.
Sources: Yext live entities call · pub_identity_links · yext_harvest_changelog/runs (NeameGraph DB, live)
Chapter two: Chosen
High-intent actions: discovery turning into visits
"Once found, do people act: directions, calls, bookings?"
99,490
direction requests · Dec to Feb (quarterly, cited)
≈ 1,100 people a day asking the way
4,180Sample
calls and booking clicks
illustrative: fills live once Yext Analytics or the Google feed is on
1,260Sample
voucher and menu engagement
illustrative: fills live once GA4 events flow via BigQuery
The quarterly exec numbers prove the demand exists; the live feed for this chapter is the same unlock as chapter one. Until then this chapter carries the cited quarterly figures and states its gaps plainly.
Sources: SN Q1 exec deck slide 3 (Dec 25 to Feb 26) · gaps per citation guard: no anchor, no claim
Chapter three: Ready
The data engine: is the estate machine-readable?
"Is the foundation sound, current, and fixing itself faster than it breaks?"
194
schema updates generated this month · 85 pubs
▼ 87% vs prior month
184
of those pushed live to Drupal
142 engine runs completed this month
228
open data fixes for the web team · 50 pubs
the fix list, live from the hygiene sweep
Live from last night's run: run summary unavailable. Page health across the crawled estate: 928 pages amber and 104 red, with none yet earning green: that is the improvement baseline this report will move. Essential SEO fields are 66% complete on the average pub (geo essentials 12%), and every pub still misses at least one essential field: the fix list is real work, not decoration.
What to do next: nothing to commission. This chapter regenerates itself from the nightly engine; the fix list is the web team's working queue.
Sources: pub_schema_versions · pipeline_run_log (2026-07-10) · v_pub_page_scores · v_pub_scores · v_pub_hygiene_summary (all live)
Chapter four: What changed
The websites themselves: every change the nightly watch caught
"What actually changed on our pub websites, and what did the engine do about it?"
187Sample
website changes detected this month
illustrative: the live counter restarts when the change logger is restored (silent since 2026-05-21)
1,661
changes in the prior month
same watch, previous window
6Sample
web-team tickets closed (Halo)
illustrative from sample-halo-tickets.csv
5Sample
projects on the Monday board
illustrative from sample-monday-projects.csv
No website changes were logged this month. The change detector last wrote on 2026-05-21 after logging 1,661 changes in the window before: seven summer weeks of total silence across the estate needs verifying, so this figure is flagged for a health check rather than read as "nothing changed".
What to do next: plug in Matt's Halo ticket feed (API key from SN IT, or his existing weekly closed-tickets export) so the web team's completed work sits beside the changes the engine caught.
Sources: sentinel_extract_change_log (live) · Halo: named gap pending access
The estate split: schema activity this month
| Estate | Schema updates | Reading |
|---|
| Managed pubs | 120 | Highest content churn; updates follow real page changes. |
| Tenanted pubs | 74 | Includes the tenanted new-homes group. |
| Whole estate | 194 | Prior month: 1,466. Year-on-year column starts Dec 2026 (history begins Dec 2025). |
Source: pub_schema_versions joined to pubs.estate_type (live)
Appendix: how to read this report
Cadence: Scan (collate) then Compare (prior period now; year-on-year from Dec 2026) then Report (narrative per chapter) then History (each edition is filed). The CSV beside this file is the weekly-report export. Found and Chosen complete when Yext Analytics is enabled or the Google feed lands; Ready is fully live today.