AEO (Answer Engine Optimization)
The practice of organizing a business entity, page purpose, supporting evidence, and conversion path so information can be retrieved and used to answer a question directly, as described in the HGM AEO architecture guide.
Answer engine
A system that answers a question directly rather than returning a list of pages. Answer engine optimization prepares the underlying information so an answer engine can retrieve it and cite the source page.
CopyGraph
A Graph Series product for content work and governance, including editorial briefs, content reviews, provenance, and sponsored-content preparation.
Entity
A distinct thing a page describes, such as an organization, brand, person, service, product, location, or page. Entity architecture separates these so each real-world thing has one controlled identity.
Entity architecture
The model that defines the entities, identifiers, attributes, and relationships that make a site internally coherent, before knowledge-graph work implements the broader connected representation.
GEO (Generative Engine Optimization)
Optimization for generative and AI-driven search experiences, so the business and its pages are represented accurately in generated answers. HGM offers GEO alongside AEO as an implementation service.
Graph Series
The HGM product family that brings schema, search, and content intelligence into related products: SchemaGraph, SearchGraph, and CopyGraph, coordinated by the proposed Search Intel OS.
Holistic SEO
An approach that treats technical access, useful content, entity clarity, user experience, and measurement as a connected system, to support qualified discovery and a credible next action.
Knowledge graph
A connected representation of entities and their relationships, with validation and a consumption layer, built from an approved entity model so information can be inspected and reused.
llms.txt
A machine-readable reference file that points language models to the key pages of a site. The HGM llms.txt lists the Graph Series, services, plans and access, and contact pages.
Schema markup (structured data)
A machine-readable description of visible information and relationships on a page. It describes the entity the page represents using appropriate types, properties, and stable references, and never adds facts the page does not support.
SchemaGraph
A Graph Series product for the schema and entity validation layer: inspecting repeated identities, unresolved references, and schema-to-content consistency.
SearchGraph
A Graph Series product for the search-evidence workflow: collecting and reporting discovery and performance evidence from sources such as Search Console.
Search Intel OS
The proposed HGM orchestration layer that coordinates recommendations, approvals, and actions across the Graph Series workflows while keeping publishing and spending under explicit approval.
Citation
A reference to a source that supports a claim. A citation lets a reader or a system trace a statement back to the evidence it rests on, which is how an answer engine decides whether a claim is worth repeating.
Entity disambiguation
The work of separating one business, person, or place from others that share its name, so each one resolves to a single identity. Consistent names, addresses, and sameAs references are the signals that make the separation hold.
JSON-LD
A format for expressing structured data as a JSON block inside a page, using the vocabulary at schema.org. HGM pages use JSON-LD to describe the business, its products, and its pages so search and answer systems can read them directly.
sameAs
A schema.org property that lists the other web addresses that refer to the same entity, such as a business’s profiles on other platforms. Matching sameAs references help systems confirm that two descriptions belong to one business.
BreadcrumbList
A structured-data list that records the path from a site’s home page to the current page. BreadcrumbList markup lets search systems show that path in results and confirm where a page sits in the site.
FAQPage
A structured-data type for a page that asks and answers questions. FAQPage markup pairs each question with its answer so search and answer systems can present the answer directly.
Terms used across the guides are defined here. See the blog for the guides that use them.