There is a new visitor reading your website, and it does not scroll, does not click, and does not care about your hero image. It is a language model deciding whether to mention you when someone asks it a question. Search Engine Land's Ray Martinez put the frame perfectly this week: your website is functioning as a public API for your brand, and the machines consuming it either understand what you are, or they route around you.
Most sites are failing that API contract, and not where you would guess.
The gap has a name
Martinez calls them entity gaps: the things that matter to your business that your site never explicitly declares. Schema markup, the structured data vocabulary most teams treat as a rich-results checkbox, is actually the declaration layer. It is how you tell a machine "this is a product, this is its price, this is the organization behind it, and here is how they relate."
The catch is that the standard vocabulary was not written for your niche. Martinez's team audited a university client and found Schema.org offered 23 higher-education entities where comprehensive coverage needed 80-plus. The vocabulary stops where your specialty starts, which means the most differentiated parts of your business / the exact things you want machines to know / are usually the least declared.
His method for finding the gaps is refreshingly concrete: model the entities your business actually consists of, compare that model against what your pages declare and what your content semantically covers, and let software do the comparison. The one-line version of his argument is the best sentence written about AI search this year: visibility is a byproduct of being understood.
Why this is suddenly worth money
Fold in what the trade press has spent the month saying and the stakes get clear. Digiday reports that AI visibility / whether answer engines surface you, cite you, and describe you accurately / has become its own currency, with publishers packaging it into products and a scramble of vendors trying to measure it. Referral traffic from AI assistants is real but small; the visibility itself is the asset. Nobody agrees on how to measure it yet, which is exactly the moment to build the durable input rather than chase the unstable metric.
The durable input is legibility. Rankings were the old game, citations are the new one, and citations flow to entities the machine can identify with confidence. Clean structured data is not a growth hack. It is the difference between being an entity and being a vibe.
The automotive version of this problem is enormous
We spend most of our time in automotive retail, and dealer websites might be the single largest entity gap on the commercial internet. Think about what a dealership actually is to a machine: an organization, with locations and hours, holding an inventory of vehicles, each with a VIN, a trim, a price, an availability status, and a set of offers including financing. Every one of those is an entity with an existing schema type. Almost none of it is declared. The typical vehicle detail page is a rendered template that a human can read and a machine has to guess at.
Here is the part that should bother dealers: the guessing era is ending on a schedule. Shopping assistants are already answering "find me a certified pre-owned SUV under $30k near me." When that answer gets assembled, the machine recommends inventory it can parse. The store whose inventory is machine-legible is in the consideration set; the store whose inventory lives in a JavaScript template is invisible, no matter how good the deal is.
And the unfair advantage is that dealers already have the knowledge graph. It is called your DMS. Your inventory system knows every VIN, price, option package and status change in real time. From our platform work on inventory management, the lesson is blunt: the data is already structured, the website just refuses to say it out loud. Emitting JSON-LD from the same feed that builds the page is plumbing, not research. Pipe what you already know into the format machines read, and your entity gap closes itself nightly.
What to actually do
Inventory your entities before your keywords. List what your business is made of: products, services, people, locations, credentials, relationships. That list, not your keyword research, is the spec for what your site must declare.
Declare the boring stuff completely. Organization, location, product, offer, person. Most sites have gaps in the basics before the exotic stuff even matters.
Extend where you are differentiated. Martinez's point about custom entities is the advanced move: the vocabulary can be extended, and the parts of your business that standard schema cannot describe are usually your moat. Declare them anyway.
Feed it from systems, not by hand. Hand-maintained markup rots. If an entity lives in a database / inventory, staffing, pricing / the markup should be generated from that database on every build.
Then track being understood. Ask the assistants who you are and what you sell. Wrong answers are your entity gaps, ranked by embarrassment.
Our position
Stop optimizing for the rich-results snippet and start writing the API documentation for your own business, because that is what your website is now. The machines answering your customers' questions are not impressed by your design refresh. They are parsing you, and they reward being parseable. Visibility is a byproduct of being understood / so be understood, deliberately, in the format the reader actually reads.