Glossary

Optimising content and structured data so that answer engines such as ChatGPT, Perplexity and Google's AI Overviews cite the business as a source.

The number of clicks from the homepage to a given page. The architecture caps this at three for every node (Architecture Section 3.3).

The second-level domain for Kenyan commercial entities, registered through KeNIC. A .co.ke domain is an explicit signal of local establishment (Architecture Section 4.2).

A set of Google metrics measuring loading performance (Largest Contentful Paint), interactivity (Interaction to Next Paint) and visual stability (Cumulative Layout Shift). Haryes builds every page to pass all three on a mid-tier Android device on a Kenyan mobile connection.

Making a business unambiguously identifiable to search and AI systems as a single entity, through a consistent name, address and phone number, a connected schema graph, and a well-populated sameAs array.

The Kenya Revenue Authority's electronic Tax Invoice Management System. VAT-registered businesses, including online sellers, must issue eTIMS-compliant electronic invoices.

A near-synonym for AEO: structuring a site and its entity so generative AI search systems retrieve and attribute its content.

The extent to which a page adds something (data, analysis, first-hand experience) not already available on the pages already ranking. Every Haryes page must carry at least one element of it (Architecture Section 14).

The Kenya Network Information Centre, the registry responsible for the .ke country-code top-level domain and its second-level domains including .co.ke.

The time from navigation start until the largest content element in the viewport is rendered. The Haryes performance budget is an LCP under 2.0 seconds.

Name, Address, Phone number. Keeping these byte-identical across the website, Google Business Profile and every directory is the foundation of local SEO (Architecture Section 2.2).

A page with no internal links pointing to it. The architecture forbids publishing any node with fewer than three internal inbound links (Architecture Section 3.4).

A page that summarises a broad topic and links down to detailed spoke pages. A pillar summarises; it never out-details its own spokes (Architecture Section 6.2).

When two or more pages on the same site compete for the same head query, splitting link equity and confusing search engines about which to rank. The architecture enforces one query, one URL.

Safaricom's developer API for M-Pesa, providing STK Push, Paybill and Till payment collection, B2C disbursement, and transaction status and reversal endpoints.

A set of Schema.org structured-data blocks connected by @id references so that every page's markup resolves back to one Organization entity (Architecture Section 11).

A group of pages tightly interlinked around one theme (typically a hub, pillar pages and spoke pages) that concentrates topical relevance and internal link equity on the subject.

A page that answers one specific head query in depth, links up to its pillar and across to sibling spokes. One query, one URL.

An M-Pesa payment method where the customer receives a prompt on their phone to authorise payment by entering their PIN, rather than manually entering a Paybill or Till number.

The degree to which a website is recognised by search engines as a comprehensive, trustworthy source on a subject, built by covering a topic in connected depth rather than publishing isolated pages.