Field Notes: Building a Topical Cluster Architecture for AI Search Visibility

We restructured our blog from a flat list of 100 posts into 10 topical clusters with hub-and-spoke architecture. Here is why, how, and what changed.

The problem: our 100 blog posts covered AI, resumes, security, content creation, and more — but they were just a chronological list. AI models like ChatGPT, Gemini, and Perplexity could not easily determine that our site is an authority on any specific topic.

The solution: group posts into 10 topic clusters (AI & Technology, Resume & Career, ChatGPT & AI Usage, Screenshots & Device Tips, Social Media, Digital Products, Content Creation, SEO & Web, Making Money Online, Security & Privacy). Each cluster has a hub page that provides a definitive overview and links to all spoke articles.

The hub page structure: each hub includes a title, description, a 2-3 sentence definitive answer (the kind AI models extract for citations), a list of related topic clusters for cross-linking, and a grid of all articles in that cluster.

We added three types of structured data to every page: FAQ schema (so AI can extract the question and answer), Article schema (for publisher and author metadata), and BreadcrumbList schema (for navigation context). The Organization schema on the root layout maps all 9 properties in our network.

The result: our sitemap now includes 10 topic hub pages plus the topics index, giving search engines and AI crawlers a clear entity map of our content. Each hub page acts as a "source of truth" that AI models can cite.

Practical takeaway: Topical clusters with hub-and-spoke architecture create entity maps that AI models can parse. Each hub needs a definitive 2-3 sentence answer, structured data (FAQ + Article + BreadcrumbList), and cross-links to related clusters. This is the foundation of GEO (Generative Engine Optimization).