Mental Models for the AI EconomyWeb & AI Search
Your Website Is Not a Stack of Pages. It Is a Knowledge Base.
Entities, relationships, schema, internal links, and answer-ready evidence: the architecture machines need when pages alone are no longer enough.
Most websites are filing cabinets: pages stacked beside pages. Search and AI systems increasingly need something else — a map of the people, products, places, claims, and relationships the pages describe.
From strings to things
Google introduced the Knowledge Graph to understand real-world things and their relationships, not just matching character strings. Google says its knowledge panels are generated automatically from multiple public and licensed sources; organizations can suggest corrections, but they do not control the panel. Google on the Knowledge Graph.
Pages become useful when the relationships are explicit
The architecture in plain English
- Name the canonical entities. One organization, its people, offerings, locations, products, and core concepts.
- Give each a stable home. A durable URL and consistent identity.
- Model relationships. Founder of, offers, located in, authored by, compatible with, supported by.
- Mirror the graph in navigation and internal links. A human should be able to follow the same relationships.
- Declare the model in structured data. Use stable
@idreferences so the same entity is not recreated on every page. - Corroborate externally. Keep facts consistent across authoritative profiles, directories, reviews, and citations.
Why answer engines care
Retrieval systems break pages into passages. A self-contained answer that names the subject, states the claim, and cites the evidence survives that fragmentation better than a paragraph full of pronouns and implied context. Research on knowledge-graph-enhanced retrieval has shown improvements in answer self-containment in the systems tested. EWEK-QA, ACL 2024.
A page is where humans read. An entity graph is how machines keep the facts straight.
What not to claim
Structured data helps machines resolve and disambiguate entities. Google does not confirm schema markup as a direct ranking boost. Entity-first architecture improves clarity and consistency; no markup guarantees a knowledge panel, ranking, or AI citation.
Get the next essay the day it publishes.
A few a month, written from real builds. Unsubscribe in one click.

Performance marketing and search leader who builds — 15+ years in digital growth and product (AT&T/DirecTV, Microsoft, Employbridge, Site Impact), now running his own properties with AI. These essays are field notes from that loop: what AI actually changes about work, product, and the economics underneath. Based in South Florida.
- Web & AI SearchHow to Write a Service Page That Ranks and Gets Cited by AI
One service per page, the service and city in the heading, the answer first, buyer questions as headings, proof, one next step and schema behind it. Seven rules and a quick test.
4 min read - Web & AI SearchNew Website Launch Week: The Checklist That Protects Your Rankings
Get found, lose nothing, test every form and phone link, confirm analytics, then tell Google and every directory. A day-by-day checklist for the week a new site goes live.
4 min read - Web & AI SearchHow HVAC Companies Get More Service Calls from Google and AI
In South Florida every AC call is urgent. Be the obvious answer when it fails: the pages that bring in calls, effortless calling, honest answers and a profile that stays current.
4 min read - Web & AI SearchHow Dental Practices Get More New Patients from Google and AI
Insurance, cost and availability are the three questions every new patient asks first. The pages that answer them, how to handle cost honestly, and the local signals AI assistants read.
4 min read - Product StrategyThe Best Product Decision Might Be a Smaller Bet
When the evidence is thin, conviction is not a substitute for a learning plan. A practical framework for reversible decisions, meaningful experiments, and stopping rules.
8 min read · interactive - Privacy & TrustThe Data You Never Collect Cannot Leak
AI workflows make copying easy and ownership harder. A practical guide to purpose, minimization, retention, and permissions before customer data enters an agent’s context.
8 min read · interactive