A professional-services practice, US Southeast
An owned visibility stack — Search Console, answer-engine probes, a citation board, and a machine-readable site graph — with no rented pixel and no ranking claim.
- Assistants probed each week
- 3
- Owned citation board
- 1
- Third-party pixels installed
- 0
The practice needed to see whether search and answer engines could name it, without installing a third-party tracker or buying a mention it could not contract. The engagement was an owned visibility stack: daily query and impression sync, weekly probes across three assistants, a citation board for directory and entity hygiene, and an llms.txt plus schema graph the crawlers could actually read. Outcomes are delivery facts. Traffic and mention-rate figures were left off the record on purpose.
- 01Owned measurement first
Wired Search Console into a private store the operator can export. No GA4, no Meta pixel, no session replay. If a signal could not live in owned data, it was not a signal.
- 02Probe the assistants a buyer uses
Weekly prompts against Claude, ChatGPT, and Gemini — named at rank, or not named. A miss became a content brief, not a screenshot in a deck.
- 03Citation board, not a backlink package
NAP consistency, directory presence, and sameAs hygiene tracked as a queue the operator works. The lever no on-page rewrite can fake.
- 04Machine-readable site graph
llms.txt, per-pillar FAQs, Service and FAQPage JSON-LD, offering and resource URLs. Schema restates the visible page. Nothing fabricated for a city without an office.
The stack makes naming possible. It does not contract a mention.
Source notes redacted · Client identification withheld by agreement