AEO · 10 February 2026 · 9 min read
Site architecture for AI search
Deep nested URLs hurt AI extraction. Flat hub and spoke architectures consistently outperform.
AI engines crawl quickly and prefer architectures where every important page is two clicks from the homepage. Flat sites with clear hubs get cited more often than deep sites with comparable content quality.
Principles
Work through these steps in order. Each one builds on the last, so resist skipping ahead even if a step feels familiar.
- Two click rule: every commercial page reachable from the homepage in two clicks.
- Hub pages for every major topic, linking to all sub pages.
- Stable URL slugs (avoid dates or auto numeric IDs).
- Breadcrumbs on every page with BreadcrumbList schema.
Hub and spoke in practice
A hub page introduces a topic broadly and links out to every related sub page. The pattern gives engines a clear map of the topic and keeps every important page within reach of the homepage.
- Each hub links down to every sub page it covers, in a visible on page section.
- Each sub page links back up to its hub near the top of the content.
- Hubs sit no more than one click from the homepage or main navigation.
- Avoid orphan pages that no hub or sub page links to.
Migrating a deep site to a flatter structure
Restructuring an existing deep site is a redirect heavy project, so plan it carefully rather than moving URLs casually.
- Map every existing URL to its new, flatter equivalent before changing anything.
- Set up 301 redirects for every moved URL, never a blanket redirect to the homepage.
- Update internal links to point directly to new URLs rather than relying on redirects.
- Monitor Search Console coverage for a spike in errors after launch.
Questions
Not directly, but deep, poorly linked pages are crawled less often and discovered less reliably, which reduces the odds of being seen at all.
As a working guide, keep important commercial and cornerstone content within two clicks. Anything deeper should have a clear reason to be there.
They help by making the page's place in the site's topic structure explicit, which supports both navigation and entity context.