Skip to content

About

An engineering practice that publishes its own homework

GEO builds and operates AI search visibility infrastructure. The same team that writes the measurement writes the schema, the llms.txt files and the comparison pages — which is why the numbers are held to a standard you can check.

  • Founded 2026
  • Independent practice
  • Formulas published
  • Limits disclosed

Who we are

Small, technical, and deliberately narrow

GEO is an independent AI search engineering practice. It exists because the buying decision moved upstream of the website, and the tools watching that shift were either generic rank-tracking ports or dashboards that counted mentions without weighting what those mentions were worth.

The practice is intentionally narrow: measure how AI surfaces describe a brand, prove why a competitor was chosen, and then either hand over the assets or ship them. The platform and the service run on the same data, so there is never a question about whose dashboard is the truth.

It is also deliberately small. Every engagement is scoped so that the person who does the technical work is the person who reports on it, which is what makes the managed tier an engineering service rather than an account-management layer.

01

Publish the formula, not just the number

Every score on the marketing site is the score the product computes, including the position weight, the five stance multipliers, the normalisation denominator and the alert thresholds. A metric nobody can audit is a metric nobody should trust.

02

State the limits where they will be read

Weekly cadence rather than live monitoring, a forecast that is a model rather than a measurement, extracted rather than human-verified stance, drafts rather than published outreach. These are on the site, not buried in a footnote.

03

Never invent a fact to fill a template

Generated assets use only observations from your crawl and citation data. Unverified facts are emitted as explicit placeholders, and a verification script fails the build if a fabricated pricing default ever reappears.

04

Refuse the guarantee

No vendor controls six independent AI surfaces. We commit to measurement — a locked baseline and a measured after-value — because that is the only claim that survives contact with the next cycle.

Verification

What “verified” means here, concretely

Every factual claim on this site was checked against the implementation before publication. These are the mechanisms that keep it that way.

Claims read from the code, not from a brief

Scoring multipliers, alert thresholds, audit point allocations, tier rankings, effort estimates, plan prices and MCP tool names in the copy are taken from the constants the product executes.

Assertions are executable

The repository ships verification scripts covering the action-tier engine, the defamation radar, the reporting and conversion layer, the landing content and link integrity. A constraint that matters has a test that fails when it breaks.

Illustrative data is labelled in place

Every example visual on the marketing surfaces carries an inline note stating that it is illustrative and explaining where a real reading comes from. No example is presented as a customer result.

Structured data matches the rendered page

FAQ answers, pricing and service descriptions are generated from the same modules that render the HTML, so the version an answer engine quotes cannot drift from the version a human reads.

The limits we publish on purpose

A technical evaluator will find these anyway. Publishing them first is both more honest and more persuasive.

  • Engine answers are collected on a weekly cycle, not continuously

    Run generation, extraction, scoring, drift detection and remediation drafting are automated. Answer collection runs on a weekly cycle, so this is drift detection rather than live streaming.

  • The forecast is a model, not a measurement

    Missed-shortlist estimates use 4–10 monthly buyer evaluations per tracked decision-stage query. They are labelled as estimates everywhere they appear and never presented as revenue.

  • Stance and sentiment are extracted, not human-verified

    They are produced by a structured extraction pass and can be corrected by you at any time from the prompt matrix — which immediately recomputes the affected snapshot.

  • Outreach assets are drafts you publish

    Community and editorial drafts are generated for review. Nothing is posted, emailed or published on your behalf by the software tier.

Short answer

Who is behind this?

Who runs GEO?

GEO is the AI search visibility practice of For Your Reach, founded in 2026. It builds and operates the AI Visibility Tracker and delivers managed implementation sprints, so the measurement and the implementation come from the same team rather than from two vendors.

How is the marketing site itself built?

The same way the product advises: fully server-rendered with no client hydration on the marketing surfaces, explicit crawler permissions for retrieval bots, machine-readable briefs at llms.txt and llms-full.txt, JSON-LD for the organisation, software offer, service, FAQs, how-to steps and defined terms, and a capability manifest for autonomous agents.

Practice questions

How we work

Answers about the practice rather than the product.

How do you avoid overstating what the platform does?

By publishing the boundaries. The platform states that answers are collected on a weekly cycle rather than live, that the forecast is a model rather than a measurement, that stance and sentiment are extracted rather than human-verified, and that outreach assets are drafts you publish. Every limitation is on the site, not in a footnote.

Where does the example data on this site come from?

The visuals on the marketing pages are labelled illustrative in place. The scoring formulas, thresholds, tier ranking, audit point allocation and plan structure shown are the literal values the product uses, taken from the implementation rather than from marketing estimates.

Who is behind GEO?

GEO is the AI search visibility practice of For Your Reach. It builds and operates the tracking platform and delivers the managed implementation sprints, which is why the people who write the schema are the same people who built the measurement that proves it worked.

Talk to the team

Ask us the hard question first

If you have already been pitched a guaranteed AI visibility increase, bring it to the call. We will tell you which parts of it are measurable and which parts are theatre.