Skip to content
Hussh
Connect MCP

AI & Search Engine Discoverability Framework

Public design and guidelines for Hussh One's discoverability architecture, aligning traditional SEO with Answer Engine Optimization (AEO) for LLMs and crawler-friendly discovery.

Concept

TL;DR: The framework and architectural design governing Hussh One's web-presence discoverability, balancing private, credentialed product areas with open, highly crawlable, structured knowledge graph assets for human and AI search engines.

Status as of 2026-07-18: see body.

Relations

Status as of 2026-07-18: see body.

Overview

Discoverability in the personal agent era requires a dual-track strategy. Traditional Search Engine Optimization (SEO) targets human search queries on legacy engines, while Answer Engine Optimization (AEO) targets crawler bots, LLMs, and conversational reasoning agents (like Perplexity, ChatGPT, Gemini, and Claude) that curate information dynamically for their users.

The Hussh One Discoverability Framework provides a structured, crawlable, and semantic footprint. It serves clear, plain-text definitions to AI engines and rich, interactive web pages to humans—all while maintaining absolute boundaries around user-private data vaults.

In today's release, SEO has been expanded to support per-ZIP local landing pages and geolocation directory searches, offering an optimized, long-tail discoverability layer for human-facing search and answer engine crawlers.

Dual-Audience Architecture: UX vs. AX

To succeed in both tracks, the architecture separates human User Experience (UX) from Agent Experience (AX):

  1. User Experience (UX): Interactive, pixel-perfect layouts designed according to the Apple Summer 2026 HIG. These are fully indexable, optimized for Core Web Vitals, and built for humans to explore and understand.
  2. Agent Experience (AX): Plain-text, machine-readable representations of the exact same content. This allows automated AI assistants to instantly parse Hussh products, principles, and pricing without navigation overhead or layout noise.

The Discoverability Triad

The AEO and SEO footprint consists of three primary, machine-readable assets served at the domain root:

  • AI-Crawler Friendly robots.txt: Explicitly welcomes major AI answer-engine crawlers (e.g., GPTBot, ClaudeBot, PerplexityBot, Google-Extended) to explore public educational and research assets, while strictly cordoning off private or authenticated product prefixes.
  • llms.txt Routing Hub: Serves a clean, hierarchical markdown map at /llms.txt of the entire website. This file provides short, informative descriptions of every public page, facilitating rapid agent synthesis.
  • Dynamic, Non-Orphaned Sitemap: Guarantees 100% of public informational routes are indexed under /sitemap.xml. An automated coverage guard test enforces that no public page is ever orphaned or excluded from the sitemap. This includes comprehensive indexing of all public rich media files (such as campaign explainer and life-moment films).

Long-Tail Discovery & Geolocation Directory (New Primitives)

To maximize physical and regional discoverability, the search console integrates long-tail landing systems:

  • Per-ZIP Local Landing Pages: Dynamically generates search engine-friendly, hyper-local pages mapping directly to United States ZIP codes. These pages act as highly targeted entry-points for local RIA searches.
  • Geolocation Directory Finder: Implements a direct browser and crawler-friendly discovery loop. Unlike traditional ZCTA centroids, it performs hyper-local ranking using exact live-GPS positioning to match queries with nearby registered advisor locations, with zero dead-ends and continuous session-state persistence.

Canonical Structured Data & Ontology Alignment

To ensure search engines and answer engines index Hussh concepts with absolute semantic precision, the public web-pages inject canonical JSON-LD Schema structures:

  • Canonical Origin Locking: Anchors all structured nodes to the authoritative https://hushh.ai base domain to prevent duplicate indexing across test or UAT environments.
  • Multi-Node @graph Structures: Combines Organization, WebSite, and SoftwareApplication into a unified graph representing Hussh, the One application, and the specialized agents.
  • FAQPage Schema Injector: Dynamically injects structured FAQ patterns containing the canonical Hussh platform ontology (Hussh -> One -> {Kai, Nav}), ensuring accurate rich snippets in search results.

Sources