Entity (SEO)

Keywords are strings; entities are things. When an assistant weighs "Summit Roofing," it connects the website, the Google Business Profile, the reviews, the directory listings, and any press into one identity — if the data agrees. Mismatched names, old addresses, and duplicate profiles fracture the entity, and fractured entities lose to boring, consistent competitors.

The resolution problem is harder than it sounds, and it is the reason consistency pays. A system encountering "Summit Roofing," "Summit Roofing LLC," "Summit Roofing & Exteriors," and "Summit Roofing Co." across four sources has to decide whether that is one business or four. It decides using the fields that match: name, address, phone, domain. Each disagreement lowers confidence, and low confidence shows up as an assistant hedging, naming a competitor it is surer about, or merging you with a similarly named business two states away.

Entity thinking also explains why some businesses rank for terms their pages barely mention. Once a system is confident that a business is a personal injury firm in Tampa, that classification informs everything, including queries the site never targeted. Conversely, a business whose identity is ambiguous has to re-earn relevance page by page, keyword by keyword.

Common fracture points are predictable: a rebrand where the old name lingers on directories, a move where the old address never got corrected, a second Google profile created by a well-meaning employee, a tracking phone number published on one listing, and franchise or multi-location setups where corporate and local data disagree.

Entity hygiene is unglamorous: one exact business name everywhere, one address format, schema markup that states identity explicitly, profiles that link back. It is also the foundation everything else in AI visibility stands on — NAP consistency is the maintenance routine, and a knowledge panel is the visible symptom that it worked.