TL;DR: When a buyer asks ChatGPT, Gemini or Google's AI Overviews for a recommendation, the answer is assembled from content those systems can find, read and trust. Businesses that own deep, structured content on their own domain get named. Businesses that rent their visibility mostly do not. We have been building that kind of content system for dealerships since long before AI search existed, and it turned out to be exactly what AI search rewards. It deserves a name: Discovery Infrastructure.
For most of the last twenty years, getting found online meant ranking. You wanted to be one of the ten blue links on the first page, and an entire industry grew up around moving you a few positions higher.
That is no longer the whole game. A growing share of buyers now ask a question and get an answer. Not ten links. An answer, usually naming two or three businesses, written in plain language by an assistant that read the web on the buyer's behalf.
If you are one of the names, you are in the conversation before the buyer has visited a single website. If you are not, you are not in second place. You are simply absent.
Strip away the hype and an AI assistant needs four things from a business before it will confidently name it.
None of that can be bought as an ad. You cannot purchase a citation. The only way to earn one is to have built the material in advance, on a domain you control, about the things buyers actually ask.
I started WebStager in 2005. We were building dealer websites by 2008 and working with auto dealers in earnest by around 2010. OneBigBroadcast came out of that work as a way to describe what we were really doing: publishing a business's knowledge from one place and broadcasting it everywhere buyers were looking. The OneBigBroadcast newsroom itself has archived posts going back to July 2010.
At the time, the industry standard was a dealer website with an inventory feed, a staff page, and maybe one blog that published whenever someone had a spare afternoon. We made a different set of decisions, and over the next few issues of this publication I am going to walk through them one at a time. Four of them matter most.
1. Many engines, not one blog. Every site we built could run multiple independent publications, each with its own address, archive and subject, instead of one blog competing for one publishing slot.
2. The content lives on the client's own domain. Not on a vendor's platform, not on a listing site, not in a social feed that resets every day. On the business's own address, where every piece adds to an asset they keep.
3. The salesperson is a publisher. Each person on the floor can have a profile, their own picks, their own content and their own reviews, all on the store's domain, so buyers can choose a person before they ever walk in.
4. Inventory is content. Every unit gets a crawlable page that earns its own entry in search, instead of disappearing into an application that search engines struggle to read.
Every one of those decisions was unfashionable when we made it. Every one of them maps almost exactly onto what generative search now rewards: depth, ownership, attribution and specificity.
A thesis like this is cheap without evidence, so here is some, with the sources stated.
That last one is the reason most businesses underestimate all of this. If your reporting only counts form fills, most of the work your website does is invisible to you. Buyers research, compare, decide, and then walk in or phone. And when they arrive from an AI assistant, the visit often carries no referrer at all, so standard analytics files it as direct traffic. The channel is working and the dashboard says nothing happened.
Because categories get named by whoever explains them first, and right now this one is still forming. Vendors are starting to sell an "AI discovery layer" as a bolt-on. I think that framing gets it backwards. Discovery is not a layer you add on top of a website. It is the structure underneath it.
Here is the definition I am working from:
Discovery Infrastructure is the set of owned content systems, structured data and distribution that make a business findable, readable and citable by people, search engines and AI assistants, measured against what actually sells.
Every word in that sentence is doing work. Owned rules out rented reach. Systems rules out one-off campaigns. Citable is the AI part. Measured against what actually sells is the part almost everyone skips.
It is not an ad product. Paid placement can rent you attention for as long as you keep paying, and that has its place, but it builds nothing that persists.
It is not a plugin. You cannot install authority.
And it is not "AI-written content." Machines can help produce material faster, and we use them for exactly that, but volume without substance is noise, and answer engines are getting better at ignoring noise every month. The architecture is the point. The writing has to be worth citing.
Five questions. Answer them honestly.
If most of your answers are no, you are renting your visibility. That was survivable when search meant ten blue links. It is much less survivable when the answer only has room for three names.
If you want a quick read on where you stand, our free Digital Scope scores your business across these areas in a few minutes, with your result on screen the moment you finish.
This publication, Built Early, is where I will make the argument properly, one decision at a time. The next issues cover each of the four decisions above in detail. Alongside it, The Build Log will document what we are shipping as we ship it, and Field Notes will report what the data shows on live dealer sites, with client identities withheld and every figure sourced.
We were right early. Now it is time to be clear about why.
TL;DR: For years the easy path was to publish where the audience already was: listing sites, social feeds, vendor platforms. We kept putting our clients' content on their own domains instead, so every piece added to an asset they owned. AI assistants now cite domains that have consistent, specific content behind them, which makes rented visibility a weaker position than ever.
There has always been a shortcut in digital marketing. Instead of building an audience on your own address, you publish where the audience already is. Third-party listing sites. Social platforms. A vendor's network. It works quickly, and for a while it can work well.
The catch is who keeps the value. We decided early that the content we produced for a business would live on that business's own domain. Not on our platform, not on a marketplace, not in a feed that resets every morning. On their address, building their asset.
When you pay for visibility on someone else's platform, you are renting. The traffic arrives as long as the payments continue. The platform builds its own authority and its own search ranking from your listings and your content, and it also sells the same buyer to your competitor down the road.
Stop paying and the traffic stops that day. Nothing you built stays with you.
Content on your own domain behaves differently. Every useful page adds to a body of work that search engines index, link to and revisit. It keeps working after you stop adding to it. A good article written three years ago can still be bringing in buyers today.
The agency version of this is a choice about whose asset you are building. Many marketing arrangements are structured, deliberately or not, so that the provider ends up holding the valuable parts: the content library, the audience, the platform it runs on. If the client leaves, they start again from nothing.
We went the other way. The content goes on the client's domain, under the client's name. The engines, the archives and the search history belong to the business. That makes us easier to leave, which is exactly why we think it is the right model. The work should be good enough that clients stay because it keeps paying off, not because leaving would cost them their history.
When an AI assistant names a business, it is drawing on what it can read about that business across the web, and the business's own domain is where the most specific, authoritative version of that story should live.
If the best material about your business lives on a listing site, the listing site gets the credit. If your expertise is scattered across social posts that age out in a day, there is very little for an assistant to find, let alone cite. If your own domain carries deep, current, specific content under your name, you are giving the assistant a clear source to attribute.
There is also a measurement benefit. When the content and the visits happen on your domain, you can see what readers do next: whether they go on to look at inventory, which pages they return to, and which of those visits connect to sales. On someone else's platform, that trail ends at their door.
Ask yourself one question: if every paid listing and every vendor arrangement ended tomorrow, what would still be bringing buyers to you next month?
If the honest answer is very little, your visibility is rented. That is a business decision you are allowed to make, but it should be a decision, not an accident.
You do not have to abandon every platform to fix this. Rented channels can stay in the mix. The goal is to make sure the asset ends up on your side.
None of this requires a bigger budget. It requires deciding where the value of the work you already pay for should end up.
Owned content compounds. Rented reach resets. We put our clients' work on their own domains because it was the only arrangement where the value accumulated for them. In a world where AI assistants decide which handful of businesses to name, that accumulated value is the difference between being cited and being invisible.
This is part of the Right Early series in Built Early. Want to see how much of your own visibility you actually own? Take the free Digital Scope.
TL;DR: Buyers do not want to be handed to whoever is up next. They want to walk in and ask for someone by name. We built salesperson profiles, salesperson content and salesperson reviews on the dealership's own domain so buyers could choose a person before they visit. That same structure is what search engines now call experience and expertise, and what AI assistants look for when they decide who to trust.
Walk into most dealerships and the website has a staff page: a grid of photos, names and phone numbers. It proves people work there. It does nothing to help a buyer choose one of them.
Years ago we decided the salesperson should be treated as a publisher, not a headshot. Every person on the floor could have their own profile on the dealership's site, carrying their own vehicle picks, their own content and their own reviews.
Big purchases are made with people. A buyer who has already read a salesperson's walkaround of the exact trim they want, seen a dozen reviews from customers that person sold to, and noticed they know the difference between two configurations is not arriving cold. They are arriving with a decision half made, and they ask for that person by name.
That conversation is shorter, warmer and more likely to close than anything a lead form produces.
Profiles on the store's domain. Each salesperson gets a real page, not a card on a staff wall. It carries their picks from current inventory, what they write, and what their customers say about them.
Content from the sales floor. Your salespeople already know things buyers want to know: which trim is worth the money, what to buy for pulling a fifth wheel in winter, what changed between model years. That knowledge usually gets given away one conversation at a time and never written down. Written down, published to their profile, it ranks in search, gets cited by AI assistants, and makes the salesperson the person the buyer asks for.
Reviews attributed to the person. When a deal closes, a review request goes to the customer, ideally with a photo of their new vehicle. The review lands on that salesperson's profile and on the dealership's review page. A review attached to the store is social proof. A review attached to the person who sold the vehicle is a reason to ask for them.
When salespeople build their following on personal social accounts, everything walks out the door when they leave: the content, the conversations, the reputation. The dealership paid to build it and keeps nothing.
When the profile, the content and the reviews live on the dealership's domain, the store keeps the asset. The salesperson gets the credit while they are there, and the business keeps the history. That is the difference between a team that compounds and one that resets every time someone changes jobs.
Search engines have spent years trying to measure experience and expertise: real people, with real knowledge, saying specific things under their own name. AI assistants inherit that instinct. When an assistant decides whether to trust a source, named people with consistent, specific content and verifiable reviews are a far stronger signal than anonymous brochure copy.
A dealership that has turned its sales floor into a set of credible, named publishers has built exactly that signal, at the scale of its whole team.
This is where most dealer software dies, and it is almost never the software's fault. A tool goes in, a few people try it, nobody is measured on it, and within six weeks it is quietly abandoned. The store concludes the idea does not work.
The fix is unglamorous: management visibility. A sales manager needs to see, week by week, who published, who requested reviews, who posted inventory, and who did not. Once that view exists, adoption stops being a matter of nagging and becomes a number on a screen. The conversation with the sales floor shifts from effort to results, and the people who do the work get the credit for it.
That is why we pair the profiles, content and review engine with a sales console. Publishing tools without a management view are on a timer. With one, they compound.
A salesperson sells a truck on Tuesday. That evening the customer gets a review request tied to that salesperson and that vehicle, and sends back a few lines and a photo in the driveway. By Thursday the review is on the salesperson's profile and the dealership's review page.
The same salesperson spends ten minutes writing up why a particular trim suits buyers who tow, linked to two units in stock. It publishes to their profile and to the dealership's buyer education engine.
A month later, a buyer two towns over asks an AI assistant which local dealer knows heavy trucks. The assistant has specific, named, recent material to draw on. The buyer arrives asking for that salesperson.
Your people are your most underused content source and your strongest trust signal. Give them a place to publish on your domain, attach their reviews to their names, and make sure the business keeps what they build.
We built it that way because buyers choose people. It turns out the machines learned to do the same.
This is part of the Right Early series in Built Early. Want to see how your own site scores on sales team trust? Take the free Digital Scope.
TL;DR: Most business websites run one blog, which means one voice, one publishing queue and one bottleneck. We built sites that run several independent publications at once, each with its own address, archive and subject. Search engines later called the idea topic clusters, and AI assistants now reward it, because depth on a subject is what earns a citation.
The standard business website has a page called Blog. Everything goes into it: company news, product announcements, advice, staff updates, the occasional seasonal post. It publishes when someone has time, which in practice means rarely.
We made a different call years ago. Instead of one blog, the sites we build can run as many independent publications as the business needs. We call them engines. Each one has its own address, its own archive, its own subject and its own rhythm.
One blog creates three problems that compound over time.
It caps coverage. Every topic competes for the same publishing slot. Buyer education waits behind company news. The deep, specific pieces that answer real questions never get written because there is always something more urgent in the queue.
It blurs the subject. To a search engine, and now to an AI assistant, a blog that covers everything is not an authority on anything. A post about a service special sits next to a post about a staff barbecue sits next to a detailed buying guide. The signal is diluted.
It creates a single point of failure. When the one person who writes the blog gets busy, publishing stops entirely, and the site starts to look abandoned to the systems that decide what to trust.
When a dealership runs separate engines, the picture changes. One engine might cover model news. Another covers buyer education: which trim is worth it, what towing figures actually mean, what to look for in a used unit. Another covers commercial and fleet. Another covers service. Another carries the sales team's own picks and walkarounds.
Each engine builds depth on its own subject. Each runs in parallel, so a busy month in one area does not stop the others. And each has a clean address that tells search engines and AI systems exactly what it is about.
That is what the search industry later started calling topic clusters: a body of connected content that demonstrates depth on a subject, rather than scattered posts that each stand alone. We did not call it that at the time. We just built the publishing system so that depth was the natural result.
One dealer content library we measure, publishing two to three posts a week across its engines, pulled more than 100,000 non-branded search impressions in a ninety day window. (Source: Search Console, one dealership client, 90 days.)
Non-branded is the part that matters. Those are buyers who were not searching for the dealership by name. They were asking questions about vehicles, features and decisions, and the dealership's own content was there with the answer.
When an AI assistant decides which businesses to name, it is looking for exactly what multiple engines produce: sustained, specific, current material on a subject, from an identifiable source, on a stable domain.
A single blog with forty posts across twenty topics gives an assistant very little to work with. Several engines, each with a deep archive on one subject, give it something it can read, trust and cite.
There is a practical point too. Separate engines make it easier to see what is working. When you can tell which publication brings readers who go on to look at inventory, you know where to put the next hour of effort. That measurement loop is a subject for a future issue.
A few quick checks, no tools required.
There is no fixed formula, but a dealership might run something like this:
Each one has a clear audience and a clear job. Together they cover the whole buying cycle, from the first question months out to the week a buyer is choosing between two specific units.
Publishing capacity is architecture, not willpower. If your site is built so that everything competes for one slot, you will always publish less than you should, on fewer subjects than your buyers care about.
Build the structure so depth happens by default. That was right a decade ago, and it is more right now.
This is part of the Right Early series in Built Early. Want to see how your own site scores on content and discovery? Take the free Digital Scope.
© 2026 One Big Broadcast | All rights reserved
