The way people find a pub has changed. They ask their phone, they tap a map, and a machine reads our pubs before a person ever does. This report follows that trail across our 275 pubs and asks three plain questions. Is our data ready for the machines. Are we being found. And once found, do people act. It rebuilds itself from live data, so the numbers are today's, not last month's. Every real number carries where it came from. The figures shown in violet are examples, there to show what a chapter looks like once its feed is switched on. They are never real numbers.
"Are our pubs present and correct on the surfaces where people look?"
Our listings are the shop window on the surfaces people actually use, the map and the search box. NeameGraph keeps them syndicated through Yext and checks every field overnight, so the window stays clean. Last night it updated 2 facts and added 0. The views and taps behind those listings, how many people looked and asked for directions, live in Yext as well. NeameGraph already reads Yext every night, so those numbers plug straight into this chapter. No new supplier, nothing to wait for.
"Once found, do people act: directions, calls, bookings?"
Being found is only half the job. The other half is what people do next, ask for directions, tap to call, book a table. We already know the appetite is there. Close to a hundred thousand people asked their phone the way to one of our pubs in a single quarter. The calls and bookings behind that number come down the same Yext pipe as chapter one, so they land here the moment we turn them on.
"Is the foundation sound, current, and fixing itself faster than it breaks?"
Here is last night's sweep. Run summary unavailable.. Across the crawled estate, 928 pages sit amber and 104 red, and none are green yet. That is not bad news. It is the starting line this report exists to move. On the average pub, 66% of the essential search fields are filled in, geo essentials 12%, and every pub is still short of at least one. The fix list is real work, not decoration.
"What actually changed on our pub websites, and what did the engine do about it?"
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".
This is the drop-in working live, right here in your browser. Pick your weekly Monday board export or your Halo ticket export and the report reads it on the spot. No upload, no waiting, nothing leaves this page. It is the same reader that runs every night, shown so you can see how your own week would land.
| 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). |
How it works, in plain terms. Gather the numbers, compare them against the period before (and the same period last year, once a year of history has built up), tell the story chapter by chapter, and file every edition so nothing is ever lost. The button up top hands you this period as a spreadsheet for the weekly report. Found and Chosen fill out as the Yext view figures are switched on. Ready and What changed are live today.