I've written before about AI search and why real work beats shortcuts. I stand by all of it. But I want to go a level deeper today, because there's a concept most people in my industry still talk around instead of about.

Graphs.

Not charts. Graphs in the computer science sense: nodes and connections. Things, and the relationships between things. Every system that decides whether your business gets found is a graph. There are several of them, they work differently, and you engineer for each one differently. If you understand that, the whole AI search conversation stops being scary and starts being a to-do list.

This is the original. Google built its empire on it. Every page on the web is a node. Every link is a connection. PageRank was just a way of asking the graph: who points at you, and do the people pointing at you matter?

Twenty-five years of SEO tactics, good and bad, were attempts to engineer this graph. Real ones earned links by being useful. Fake ones built private blog networks to counterfeit connections. The graph got smarter, the counterfeits got caught, and the businesses built on them burned. I've watched that cycle at least four times.

The link graph still matters. But it's no longer the whole game. It might not even be the main game.

Graph two: the knowledge graph

In 2012 Google announced "things, not strings." Instead of matching keywords, it started building a database of entities. People, places, businesses, products, and the facts connecting them. That knowledge graph now holds billions of entities and hundreds of billions of facts, and here's the part that should get your attention: Google's AI is trained on it. So when Gemini or AI Overviews answers a question, it's reading from that graph.

This is where most contractors are losing without knowing they're playing.

Your business is either a clear node in that graph or it's noise. And I see the same mistakes constantly. The company is "Quick's Heating & Cooling" on the website, "Quicks Heating and Cooling LLC" on Google Business Profile, "Quick's HVAC" on Facebook. To a human, that's obviously one company. To an entity resolution system, that might be three weak nodes instead of one strong one.

So let's talk about entities, because this word is about to matter to your business whether you like it or not.

An entity is anything a machine can identify as one distinct thing. A person. A company. A place. A service. A product line. Not a keyword, a thing. "Furnace repair" is a string. Your company, which does furnace repair in three counties and has since 2004, is an entity. The whole shift in search over the last decade has been machines learning to work with things instead of strings. And your job now is to make sure the machines know exactly which thing you are.

Every business has a set of entities that matter, and most contractors have never mapped theirs:

Your company. The main node. It needs one canonical name, one exact spelling, used everywhere without exception. Website, Google Business Profile, Facebook, Yelp, license filings, truck wraps. Every variation you allow splits your signal.

Your people. The owner is an entity. So is your lead tech with the master license. When your about page names real people with real credentials, and those names show up consistently in reviews, videos, and local press, the machines connect person to business and both nodes get stronger. Faceless companies make weak entities.

Your services. Furnace installation is a different entity than duct cleaning. A separate page for each real service, marked up with schema, tells the graph exactly what you do instead of making it guess from a wall of text on one page.

Your places. Every town you serve is an entity the machines already know cold. Your job is to build the edge between your node and those town nodes. Real location pages, real service area data in your markup, real reviews that mention the town by name.

Your affiliations. The brands you install, the certifications you hold, the associations you belong to. Rinnai is a strong entity. Bosch is a strong entity. When your site and their dealer locator both confirm the relationship, you inherit a little of that strength. This is why I tell contractors their manufacturer relationships are an SEO asset most of them never use.

Then you connect it all. Schema markup on your site declaring what each entity is. The sameAs property linking your website to your profiles so machines know they're all one thing. An about page that functions as your entity's home base: plain, factual, machine-readable statements about who you are, what you do, where, and since when.

Engineering this graph isn't glamorous. It's consistency and structure, applied everywhere, forever. Entity recognition doesn't happen overnight either. Get the signals consistent and it typically takes months, not days, for the graph to consolidate around you. Which is exactly why it's defensible. Your competitor can't buy it in a weekend.

Boring? Absolutely. It's plumbing. But you'd never tell a homeowner the plumbing doesn't matter because nobody sees it.

Graph three: the trust graph

This one is the reviews, citations, mentions, and third-party proof surrounding your business. Google Maps runs on it. And increasingly, AI assistants lean on it hard, because when someone asks Claude or ChatGPT who to call for a dead furnace, the model isn't just reading your website. It's looking for independent confirmation that you're real, local, and good.

Real reviews from real customers. Mentions from your local paper, your suppliers, your manufacturer's dealer locator, your chamber of commerce. Each one is an edge in the graph connecting your node to sources the machines already trust.

You cannot fake this one at scale anymore. People try. Fake review farms are just the trust graph's version of a PBN, and they end the same way.

Graph four: the retrieval graph

This is the newest one, and it lives inside the AI systems themselves. When an AI assistant answers a question, it retrieves content, maps how the pieces relate, and assembles a response from the sources it can actually parse and verify. Some of the newer retrieval systems literally build a graph of concepts from the documents they read.

What that means practically: structure is no longer just for humans. Content that answers the question directly, defines terms plainly, and states facts a machine can lift cleanly gets cited. Content that buries the answer under 800 words of throat-clearing doesn't. I've spent my whole career saying keep it simple, make it look beautiful, have it work. Turns out the machines agree with the first part.

Why I'm telling you this

Because "AI is changing search" is true but useless. It doesn't tell you what to do Monday morning. Thinking in graphs does.

Audit your entity. Is your business one consistent node or five contradictory ones? Fix your structured data. Earn edges in the trust graph the only way that works: by doing good work and getting it confirmed by people and platforms that matter. Write content that a machine can quote and a homeowner can understand.

None of this is a hack. That's the point. Every graph I just described has one thing in common: it's a map of reality. The link graph maps who vouches for you. The knowledge graph maps who you are. The trust graph maps whether you deliver. You engineer your position in these graphs by making the reality better and then making the reality legible.

The tactics people used to fake their way through the link graph don't transfer to the new graphs. But the fundamentals transfer perfectly. Be real. Be consistent. Be clearly good at something specific.

The web was always a graph. Now everything reading the web is one too. Make sure you're a node worth connecting to.