Valid markup makes a page eligible for a feature, and eligible is not shown. Wooler Woodfired, a pizza restaurant in Northumberland, added structured data for its opening hours, its menu and its reviews in March 2026. All three validated with no errors. Three types were marked up and one feature appeared.
Opening hours appeared, the menu did not, and review stars were withdrawn. Nothing was wrong with any of the three, which is the fact worth having before spending an afternoon on this: the markup is a claim in a format, and whether the claim earns a different looking listing is decided elsewhere and not published.
What each of the three did
The opening hours appeared within about two weeks, in the local listing rather than in the ordinary result, showing open until 10pm on a Friday evening. That is the one clear win and it came from the least glamorous of the three types.
Structured data
Valid against shown, for three types marked up on one afternoon
All three sat in the valid column and only one stayed in the shown column, with no report explaining the gap.
The feature appears
- Local listing hours
- Syntax errors rejected
The feature does not appear
- Restaurant menu
- Self-serving reviews
- Unparseable blocks
The top left cell is the only one anybody aims at and the bottom left is where most valid markup sits. Nothing published explains why the menu landed in the lower cell.
The menu markup validated and has never produced anything visible. Menu features exist and appear for some restaurants; nothing in any report says why not this one, and the honest position after five months is that nobody at Wooler knows.
The review stars appeared for three weeks and then stopped. Self serving review markup stopped being shown for most page types, which is the change to know about: reviews collected and published by a business about itself have been treated differently from reviews on a third party site for several years, and marking them up does not reverse that.
What it buys, and what it does not
A rich result changes the shape of the listing, not the position. Wooler's position for pizza wooler was 3.1 in February and 3.0 in June, and the clicks rose by about a fifth when the hours appeared. That is a genuine gain and it is a click gain, in the same family as the most valuable line on the page rather than in the family of things that move a ranking.
Impact
What a rich result buys, and what stays put
The visible hours changed the listing shape and lifted clicks, while the page's actual search rank barely moved.
- What it buysListing shape and click gain
- Richer local listing shape
- Clicks rose by about a fifth
- Footer hours mirrored in markup
- What it does not buyPosition and hidden ratings
- Position moved from 3.1 to 3.0
- No ranking lift on its own
- Invisible plugin ratings fail
Rich result effect
Both the visible footer and the markup must match whenever kitchen hours change on a Tuesday.
Mark up what is visible on the page, and only what is visible. This is the rule that keeps the whole thing honest and it is also the one that gets broken most, usually by a plugin marking up an aggregate rating that appears nowhere. Wooler's hours are in the footer of every page and in the markup; the two agree, and if the kitchen changes on a Tuesday both have to change.
Where this stalls: the report that says valid
The report shows valid items, not shown items. Search Console has a section for each structured data type reporting counts of valid, warning and error items, and a page can sit at valid forever without ever having earned a feature. Somebody reading that report reasonably concludes the work is done and the feature is coming.
Verification
Where checking stalls when a report only counts valid items
Syntax checks and valid counts stop short of confirming whether a feature ever showed up in search.
- Generic schema validatorConfirms legal syntax without testing feature rules.
- Rich Results TestChecks feature eligibility, replacing the tool retired in 2020.
- Search Console valid reportCounts valid, warning, and error items, never shown features.
- Monthly live searchThe only check that tells you whether the feature actually appears.
Eligibility and appearance are separate states, and only the first shows up in the report.
Check it with the Rich Results Test, not with a validator. A generic schema validator says whether the syntax is legal; the Rich Results Test says which features this specific markup is eligible for, which is a different and more useful question. It is free, and it replaced the Structured Data Testing Tool that Google retired in 2020 and handed to schema.org, so a tutorial pointing at that one is pointing at a different organisation's product.
The second half of the check is to search for the page and look, once a month, because eligibility and appearance are different states and only one of them is reported.
The format, and the size of the job
JSON-LD in the head is the format everything documents now. Markup embedded in the page's own tags still works and is harder to keep correct, because a designer moving a block moves the markup with it. Wooler's is 40 lines in the head of the template, and the only thing that ever breaks it is the hours changing.
Priority
Where 40 lines of JSON-LD sit in the order of work
Structured data changes how a listing looks after the fundamentals are in place, not before.
- Links pointing at the siteWhat carries authority to the pages that need to compete.
- Substantive pages and clear titlesWhat separates a page that ranks from one that merely exists.
- 40 lines of JSON-LD in the headEasier to keep accurate than markup woven into layout blocks.
- One afternoon for one featureTracked in Search Console alongside clicks, the tip of page control.
An afternoon for one feature is a fair trade once titles, pages, and links are already doing their job.
The size of the job is worth stating plainly: an afternoon for a restaurant, and it earned one feature. That is a reasonable trade and it is not the item to do first on a site with a weak title, thin pages or nobody linking to anything, which are what separates a page that ranks from one that exists and sending authority where you want it.
Search Console reports the valid counts and the clicks either side of a change, free, replacing the keyword data Google removed from analytics in 2011. Both numbers above came from it, and neither of them explains the menu.
Structured data is the tip of what a single page controls about its own ranking, and it is the only item in that list which changes what the result looks like rather than what the page says.