NG
NeameGraph
for Shepherd Neame
Digital Discovery Report
LIVE DATA · Friday 3rd July 2026 to Friday 10th July 2026 · generated Friday 10th July 2026 12:45am
Period WeekFortnightMonthQuarterYear CSV for this period
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 Friday 3rd July 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; a figure we cannot yet evidence is a named gap, never an invention.

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
219
Yext field changes detected this week
▲ 7% vs prior week

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
TBC
calls and booking clicks
named gap: lands with Yext Analytics or the Google feed
TBC
voucher and menu engagement
named gap: GA4 events partial across estates

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?"

50
schema updates generated this week · 41 pubs
▲ 163% vs prior week
50
of those pushed live to Drupal
36 engine runs completed this week
228
open data fixes for the web team · 50 pubs
the fix list, live from the hygiene sweep

Live from last night's run: 239 pubs scanned · 1031 page outcomes: 0 queued, 1 blocked, 1030 skipped/ignored. 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-09) · 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?"

0
website changes detected this week
detector last logged a change 2026-05-21
0
changes in the prior week
same watch, previous window
TBC
web-team tickets closed (Halo)
named gap: plugs in via Halo API or the weekly export

No website changes were logged this week. The change detector last wrote on 2026-05-21 after logging 0 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 week
EstateSchema updatesReading
Managed pubs42Highest content churn; updates follow real page changes.
Tenanted pubs8Includes the tenanted new-homes group.
Whole estate50Prior week: 19. 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.

NeameGraph · built for Shepherd Neame by PubAgent Limited
Live edition · generated Friday 10th July 2026 12:45am