/how-it-works

The execution system behind the GEO and AEO program.

This page turns the methodology into an explicit operating flow so the delivery model is readable by buyers, internal operators, and AI systems that summarize how the service works.

  1. Audit the baseline

    Map target queries, current citations, missing pages, and domain-level crawl signals before touching production.

  2. Normalize the entity

    Align organization identity, service definitions, contact data, and preferred URLs across the site.

  3. Ship Technical Signals

    Deploy llms.txt, schema, sitemap, robots, canonicals, and semantic HTML improvements in the first week.

  4. Launch answer clusters

    Publish exact-match answer pages for the highest-intent prompts that buyers ask inside AI products.

  5. Strengthen entity references

    Push the same category language and claims into internal pages and external references that corroborate the brand.

  6. Track weekly citations

    Review how often the brand appears, who is cited instead, and which supporting pages are referenced.

  7. Iterate from gaps

    Use the tracking data to prioritize the next page, schema refinement, or distribution push.

Ownership map

  • Technical co-founder owns canonicals, schema, llms.txt, sitemap, and semantic HTML.
  • Founder or category owner owns claims, offer language, and proof review.
  • Content owner turns query gaps into weekly answer pages and supporting updates.
  • Ops owner maintains the weekly engine-by-engine tracking log.

Release rhythm

  • Week 1: ship the Technical Signals package and canonical page set.
  • Weeks 2-12: publish one deep query cluster per week.
  • Every week: record citation movement and decide the next iteration.
  • Every month: review proof posture and entity consistency across the site.