Service
GEO: the half of AI visibility that is actually configurable.
A growing share of answers is assembled by a model instead of clicked in a list. What changes is the reader: the same page has to be extractable, unambiguous and identifiable for something that never sees the layout. That half is configuration work. The answer itself is not.
What this involves
-
Content in a form that survives extraction
One claim per heading, facts in text rather than only inside an image, and sentences that still mean something once they are lifted out of the paragraph around them. Nothing that hangs on a pronoun pointing three lines up.
-
A machine-readable copy from the same source as the visible one
schema.org as JSON-LD, generated from the same data the page renders from, so the two cannot drift apart. Where markup and visible text are maintained separately they diverge, usually at the moment somebody edits one of them.
-
One entity, one identifier, referenced instead of repeated
The organisation gets a stable identifier and every page points at it rather than restating who you are. A model left to reconcile five slightly different self-descriptions will pick one of them, and it will not ask which was current.
-
Crawler access rules written down instead of defaulted
Which agent may fetch which paths is your decision, put into robots directives explicitly, including the agents you want kept out. It is a request rather than a fence: it binds the operators who choose to honour it, and we say so instead of selling it as a lock.
-
Addresses that do not move
Canonical addresses, and redirect maps kept for old paths. An answer that names your page is worth nothing if the address behind it has stopped resolving, so moving a page is a step with a redirect in it rather than a rename.
What we use
-
Machine-readable content
- schema.org
- JSON-LD
-
Entity identity
- stable @id references
- sameAs to profiles you own
-
Access rules
- robots.txt
- per-agent directives
-
Page structure
- heading hierarchy
- self-contained answers
-
Address stability
- canonical addresses
- nginx redirect maps
Is this the problem you have?
If it is adjacent rather than exact, say so anyway — the useful conversations usually start that way.