Back to feed

One graph, five sites: how I wired five properties into one AI-searchable network

Cross-property schema, unified footer, canonical person and organization IDs. The network effect between properties is a bigger lever than growth work on any single one.

The short answer Unified Person and Organization JSON-LD across five properties (jlittrell.com, liquorbets.com, buildoutfeed.com, cocktailbarleague.com, and one more), plus a card-grid footer and shared consumer widgets. Every property now reads to Google and AI grounding queries as part of one graph, not five islands.

I linked five of my sites to the same person and organization schema last week. Here is what actually changed.

Five properties. jlittrell.com. liquorbets.com. buildoutfeed.com. cocktailbarleague.com. punchlistnyc.com. All mine. All in the same corner of NYC hospitality. Until last week, an AI answer engine reading any one of them had no reliable way to know the other four existed under the same operator.

The fix took a day of work and it is invisible to a human reader. Every site now emits the same Organization schema with the same @id. Every site cites the same Person as founder with the same @id. Every site links to the other four in the footer. Anywhere Google, Perplexity, ChatGPT, or Claude reads one of them, it sees the graph.

This is not clever. It is the boring thing everyone should be doing and almost nobody does. When an AI grounding query asks "who runs Liquor Bets" the answer is now stitched. Liquor Bets says Jason Littrell. Jason Littrell says Liquor Bets. Punch List says Jason Littrell. Same @id across all of them. The reasoning engine does not have to guess.

The measurable outcome will not show up for weeks. Grounding queries do not spike a dashboard the day you ship. What did show up immediately was the internal traffic. Every issue of The Ops Wire, every market on Liquor Bets, every Punch List report, every BuildoutFeed alert now sends readers across the network with one click. Time on network went up. Subscriber overlap started to compound.

The one piece I got wrong. I built the footer as a bare list of five links on the first pass. It looked like a link farm. Redesigned it as a proper card grid with the tagline for each property. The bare list would have flagged as spammy to Google's algorithmic reviewers. The card grid reads as a network, not a linkroll.

What I learned. The network effect between my own properties is a bigger lever than most of the individual growth work I do on any one of them. I have been treating them like five separate products. They are one product with five surfaces.

What's next. Adding a sixth. Kmsops.com goes in this week. Then the newsletter, theopswire.substack.com, gets the same schema treatment so it reads as part of the graph, not adjacent to it.

PS: The Counsel Room opens July 21. A private room for bar pros who want to charge for what they already know. Pricing playbook, proposal templates, live weekly office hours, and the systems I use to run my consultancy solo. Waitlist is open. jlittrell.com/counsel

PPS: BuildoutFeed watches every NYC restaurant moving through pre-opening. Attorneys, insurance, liquor reps, GCs. One to three signals a day that will move your business forward. buildoutfeed.com

Jason