{"id":143,"date":"2026-05-06T08:20:28","date_gmt":"2026-05-06T13:20:28","guid":{"rendered":"https:\/\/tampawebtech.com\/news\/?p=143"},"modified":"2026-05-06T08:58:09","modified_gmt":"2026-05-06T13:58:09","slug":"google-fan-out-ai-architecture","status":"publish","type":"post","link":"https:\/\/tampawebtech.com\/news\/google-fan-out-ai-architecture\/","title":{"rendered":"Google Fan Out AI Architecture"},"content":{"rendered":"\n<!-- ============================================================\n  TWT NEWS ARTICLE\n  Title: What Google's Fan-Out Architecture Means for Your AI Citation Strategy\n  Category: AEO \/ GEO\n  Author: David Chamberlain\n  Source: Search Off the Record, Episode 109, \"How Search Is Changing\"\n          Guests: Martin Splitt (Google DevRel) + Nikola Todorovic (SafeSearch engineering lead, Zurich)\n  CSS prefix: .twt-fo-\n  PASTE VIA: WordPress Code Editor (Ctrl+Shift+Alt+M) \u2192 Custom HTML block\n  NOTE: No phone number in CTA \u2014 TWT News site rule\n  ============================================================ -->\n\n\n<!-- BLOCK 1: HERO -->\n\n\n<style>\n.twt-fo-hero {\n  background: linear-gradient(135deg, #0b3d91 0%, #3232a4 60%, #1e73be 100%);\n  padding: 72px 48px 64px;\n  text-align: center;\n}\n.twt-fo-hero__inner { max-width: 800px; margin: 0 auto; }\n.twt-fo-hero__eyebrow {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 13px; font-weight: 600;\n  letter-spacing: 0.12em; text-transform: uppercase;\n  color: #00b4d8; margin: 0 0 22px 0;\n}\n.twt-fo-hero h1 {\n  font-family: 'DM Serif Display', serif;\n  font-size: clamp(30px, 5vw, 46px);\n  font-weight: 400; color: #fff;\n  line-height: 1.2; margin: 0 0 22px 0;\n}\n.twt-fo-hero__deck {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 19px; color: rgba(255,255,255,0.88);\n  line-height: 1.65; max-width: 640px;\n  margin: 0 auto 28px;\n}\n.twt-fo-hero__byline {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 14px; color: rgba(255,255,255,0.6);\n}\n@media (max-width: 600px) {\n  .twt-fo-hero { padding: 52px 24px 48px; }\n  .twt-fo-hero__deck { font-size: 17px; }\n}\n<\/style>\n<div class=\"twt-fo-hero\">\n  <div class=\"twt-fo-hero__inner\">\n    <p class=\"twt-fo-hero__eyebrow\">AEO \u00b7 GEO \u00b7 Google Search Architecture<\/p>\n    <h1>What Google&#8217;s Fan-Out Architecture Means for Your AI Citation Strategy<\/h1>\n    <p class=\"twt-fo-hero__deck\">A Google search engineer just explained, on the record, how AI Overviews actually retrieves content. The mechanism validates exactly why thin pages get filtered out \u2014 and why owned technical depth survives.<\/p>\n    <p class=\"twt-fo-hero__byline\">Tampa Web Technologies \u00b7 David Chamberlain<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 2: LEAD -->\n\n\n<style>\n.twt-fo-lead { background: #fff; padding: 60px 48px; }\n.twt-fo-lead__inner { max-width: 720px; margin: 0 auto; }\n.twt-fo-lead h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 28px; font-weight: 400;\n  color: #3232a4; margin: 0 0 20px 0;\n}\n.twt-fo-lead p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 18px; color: #222;\n  line-height: 1.75; margin: 0 0 20px 0;\n}\n.twt-fo-lead p:last-child { margin: 0; }\n.twt-fo-lead__dropcap {\n  font-family: 'DM Serif Display', serif;\n  font-size: 58px; color: #0b3d91;\n  float: left; line-height: 0.88;\n  padding: 8px 10px 0 0; margin: 0;\n}\n@media (max-width: 600px) {\n  .twt-fo-lead { padding: 44px 24px; }\n  .twt-fo-lead p { font-size: 17px; }\n  .twt-fo-lead__dropcap { font-size: 46px; }\n}\n<\/style>\n<div class=\"twt-fo-lead\">\n  <div class=\"twt-fo-lead__inner\">\n    <p><span class=\"twt-fo-lead__dropcap\">T<\/span>he AEO conversation has spent a lot of time on outcomes \u2014 which pages get cited, which engines favor owned content, how citation share breaks down by vertical. Less time has been spent on the mechanism. How does Google&#8217;s AI Overviews actually decide what it reads?<\/p>\n    <p>In May 2026, Google&#8217;s Search Off the Record podcast published Episode 109, &#8220;How Search Is Changing.&#8221; The guest was Nikola Todorovic, who leads SafeSearch engineering at Google&#8217;s Zurich office and has been part of Google&#8217;s search organization for fifteen years. In the conversation, he explained, clearly and on the record, how AI Overviews processes a query \u2014 including a mechanic called fan-out that gets very little coverage outside of Google&#8217;s own engineering circles.<\/p>\n    <p>The fan-out explanation has direct implications for AEO strategy. It is not abstract. It tells you specifically why certain pages survive AI retrieval filtering and why others do not.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 3: THE FAN-OUT EXPLAINED -->\n\n\n<style>\n.twt-fo-fanout { background: #f7f8f9; padding: 60px 48px; }\n.twt-fo-fanout__inner { max-width: 820px; margin: 0 auto; }\n.twt-fo-fanout h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 32px; font-weight: 400;\n  color: #0b3d91; margin: 0 0 22px 0;\n}\n.twt-fo-fanout p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: #222;\n  line-height: 1.75; margin: 0 0 20px 0;\n}\n.twt-fo-fanout__pullquote {\n  border-left: 4px solid #f97316;\n  padding: 20px 28px;\n  margin: 32px 0;\n  background: #fff;\n  border-radius: 0 6px 6px 0;\n}\n.twt-fo-fanout__pullquote p {\n  font-family: 'DM Serif Display', serif;\n  font-size: 21px; color: #0b3d91;\n  line-height: 1.55; margin: 0 0 10px 0;\n  font-style: italic;\n}\n.twt-fo-fanout__pullquote cite {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 13px; color: #666;\n  font-style: normal;\n}\n@media (max-width: 600px) {\n  .twt-fo-fanout { padding: 44px 24px; }\n  .twt-fo-fanout h2 { font-size: 26px; }\n  .twt-fo-fanout__pullquote p { font-size: 18px; }\n}\n<\/style>\n<div class=\"twt-fo-fanout\">\n  <div class=\"twt-fo-fanout__inner\">\n    <h2>The fan-out mechanic, explained by Google<\/h2>\n    <p>Here is what Todorovic described. When a user submits a query to Google&#8217;s AI Overviews, the system does not run a single retrieval against that exact query. It identifies additional related sub-queries that could yield results relevant to the original request. It then fires those sub-queries in parallel. All of the retrieved content comes back and AI Overviews synthesizes from across those results to produce the final summary.<\/p>\n\n    <div class=\"twt-fo-fanout__pullquote\">\n      <p>&#8220;A fan out is when you have your own search query, but then we might identify some additional search query that will yield the results that can be relevant for your original search query as well. And then we can fork and in parallel do the retrieval for multiple search queries.&#8221;<\/p>\n      <cite>\u2014 Nikola Todorovic, SafeSearch Engineering Lead, Google Zurich \u00b7 Search Off the Record, Episode 109<\/cite>\n    <\/div>\n\n    <p>The practical result: a single user query is not a single retrieval event. It is several. Each sub-query runs against Google&#8217;s standard ranking and indexing infrastructure \u2014 the same systems that power organic search. AI Overviews then operates as a synthesis layer on top of whatever those retrievals return.<\/p>\n    <p>Todorovic was clear that the underlying retrieval and ranking in AI Overviews is &#8220;old school&#8221; \u2014 the same indexing and ranking systems that have always existed. The AI component is specifically the synthesis step: combining what it finds across those pages into a coherent response. The retrieval filter is the existing search stack. The AI layer does not read the broader web; it reads what the retrieval layer surfaces.<\/p>\n    <p>This matters because it means AI Overviews citation behavior is not arbitrary. It is constrained by the same signals Google&#8217;s ranking infrastructure has always used \u2014 with an additional layer of extraction quality on top.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 4: WHAT THIS MEANS FOR CITATION FILTERING -->\n\n\n<style>\n.twt-fo-filter { background: #fff; padding: 60px 48px; }\n.twt-fo-filter__inner { max-width: 820px; margin: 0 auto; }\n.twt-fo-filter h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 32px; font-weight: 400;\n  color: #3232a4; margin: 0 0 22px 0;\n}\n.twt-fo-filter h3 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 22px; font-weight: 400;\n  color: #0b3d91; margin: 28px 0 12px 0;\n}\n.twt-fo-filter p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: #222;\n  line-height: 1.75; margin: 0 0 18px 0;\n}\n.twt-fo-filter__cards {\n  display: grid;\n  grid-template-columns: 1fr 1fr;\n  gap: 20px; margin: 32px 0;\n}\n.twt-fo-filter__card {\n  background: #f7f8f9;\n  border-radius: 8px;\n  padding: 26px 28px;\n  border-top: 3px solid #1e73be;\n}\n.twt-fo-filter__card--warn { border-top-color: #f97316; }\n.twt-fo-filter__card h4 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 18px; font-weight: 400;\n  color: #0b3d91; margin: 0 0 10px 0;\n}\n.twt-fo-filter__card--warn h4 { color: #c2410c; }\n.twt-fo-filter__card p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 15px; color: #444;\n  line-height: 1.65; margin: 0;\n}\n@media (max-width: 640px) {\n  .twt-fo-filter { padding: 44px 24px; }\n  .twt-fo-filter h2 { font-size: 26px; }\n  .twt-fo-filter__cards { grid-template-columns: 1fr; }\n}\n<\/style>\n<div class=\"twt-fo-filter\">\n  <div class=\"twt-fo-filter__inner\">\n    <h2>Why thin pages get filtered out before the AI sees them<\/h2>\n    <p>The fan-out architecture creates a two-stage filtering problem for any page trying to earn an AI citation.<\/p>\n    <p>Stage one: the page has to survive Google&#8217;s standard ranking retrieval for not just the primary query, but potentially several sub-queries generated from it. A page that ranks marginally for the head term may not surface at all for the more specific sub-queries the fan-out generates.<\/p>\n    <p>Stage two: once retrieved, the AI synthesis layer has to be able to extract something useful from the page. Todorovic described AI Overviews as operating on &#8220;snippets, the titles, and additional context it can get out of those pages.&#8221; That is the synthesis layer working with what it can actually read \u2014 not with the full page, but with extractable content.<\/p>\n\n    <div class=\"twt-fo-filter__cards\">\n      <div class=\"twt-fo-filter__card\">\n        <h4>Pages that survive both stages<\/h4>\n        <p>Deep owned content with clear heading structure, direct answers in early content, schema markup, and strong topical alignment to the specific sub-queries the fan-out is likely to generate.<\/p>\n      <\/div>\n      <div class=\"twt-fo-filter__card twt-fo-filter__card--warn\">\n        <h4>Pages filtered at stage one or two<\/h4>\n        <p>Thin content that ranks on domain authority alone, pages without extractable structure, and broadly optimized content that does not align tightly enough to the sub-query variants a fan-out produces.<\/p>\n      <\/div>\n    <\/div>\n\n    <p>This is consistent with what our 550-citation B2B industrial study found: owned content with high Page Structure Scores dominated citation share at 48.3%, while trade publications \u2014 typically well-ranked in organic search \u2014 came in at only 6.5% of citations with the lowest mean PSS of any ownership type. Domain authority is getting pages retrieved. Extraction quality is determining which ones get cited.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 5: QUERY LENGTH AND THE SIGNAL THIS SENDS -->\n\n\n<style>\n.twt-fo-query { background: #0b3d91; padding: 64px 48px; }\n.twt-fo-query__inner { max-width: 760px; margin: 0 auto; }\n.twt-fo-query h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 30px; font-weight: 400;\n  color: #fff; margin: 0 0 22px 0;\n}\n.twt-fo-query p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: rgba(255,255,255,0.88);\n  line-height: 1.75; margin: 0 0 18px 0;\n}\n.twt-fo-query__stat {\n  background: rgba(255,255,255,0.08);\n  border: 1px solid rgba(255,255,255,0.18);\n  border-radius: 8px;\n  padding: 28px 32px;\n  margin: 32px 0;\n  display: flex; gap: 24px; align-items: flex-start;\n}\n.twt-fo-query__stat-num {\n  font-family: 'DM Serif Display', serif;\n  font-size: 52px; color: #06d6a0;\n  line-height: 1; flex-shrink: 0;\n}\n.twt-fo-query__stat-label {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: rgba(255,255,255,0.85);\n  line-height: 1.6; padding-top: 6px;\n}\n@media (max-width: 600px) {\n  .twt-fo-query { padding: 48px 24px; }\n  .twt-fo-query h2 { font-size: 25px; }\n  .twt-fo-query__stat { flex-direction: column; gap: 12px; }\n  .twt-fo-query__stat-num { font-size: 40px; }\n}\n<\/style>\n<div class=\"twt-fo-query\">\n  <div class=\"twt-fo-query__inner\">\n    <h2>Longer queries generate more sub-queries \u2014 and more chances to be filtered<\/h2>\n    <p>Todorovic noted a second finding from Google&#8217;s internal data that compounds the fan-out dynamic. User query length is increasing. More people are typing longer, more detailed prompts into Google as they realize AI features can handle them.<\/p>\n\n    <div class=\"twt-fo-query__stat\">\n      <div class=\"twt-fo-query__stat-num\">\u2191<\/div>\n      <div class=\"twt-fo-query__stat-label\">Average query length is growing, per Google internal data. Longer queries give the fan-out system more signals to generate more specific sub-queries \u2014 increasing both the opportunity to appear and the risk of being filtered if content is too thin or too broad.<\/div>\n    <\/div>\n\n    <p>A longer query gives the fan-out system more material to work with. It can identify more directions, generate more sub-queries, and retrieve from more angles. For a brand with deep owned content organized around specific sub-topics, this is an opportunity \u2014 more sub-queries means more chances for relevant pages to surface. For a brand with thin category-level content, longer queries generate sub-queries that the thin content cannot answer, and those pages never enter the synthesis pool.<\/p>\n    <p>The implication for content architecture: organizing around specific sub-topics, use cases, or specifications is not just good SEO practice. It is directly aligned with how fan-out generates sub-queries and what the AI synthesis layer can extract when it finds those pages.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 6: THE PSS CONNECTION -->\n\n\n<style>\n.twt-fo-pss { background: #f7f8f9; padding: 60px 48px; }\n.twt-fo-pss__inner { max-width: 820px; margin: 0 auto; }\n.twt-fo-pss h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 30px; font-weight: 400;\n  color: #3232a4; margin: 0 0 22px 0;\n}\n.twt-fo-pss p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: #222;\n  line-height: 1.75; margin: 0 0 18px 0;\n}\n.twt-fo-pss__table {\n  width: 100%; border-collapse: collapse;\n  font-family: 'DM Sans', sans-serif;\n  font-size: 15px; margin: 28px 0;\n  border-radius: 8px; overflow: hidden;\n}\n.twt-fo-pss__table thead tr {\n  background: #0b3d91; color: #fff;\n}\n.twt-fo-pss__table th {\n  padding: 13px 18px; text-align: left;\n  font-weight: 600; font-size: 12px;\n  text-transform: uppercase; letter-spacing: 0.06em;\n}\n.twt-fo-pss__table td {\n  padding: 12px 18px; border-bottom: 1px solid #ebebeb;\n  color: #333;\n}\n.twt-fo-pss__table tr:last-child td { border-bottom: none; }\n.twt-fo-pss__table tr:nth-child(even) { background: #fff; }\n.twt-fo-pss__table tr:nth-child(odd) { background: #f7f8f9; }\n.twt-fo-pss__table td:first-child { font-weight: 600; color: #0b3d91; }\n@media (max-width: 600px) {\n  .twt-fo-pss { padding: 44px 24px; }\n  .twt-fo-pss h2 { font-size: 25px; }\n  .twt-fo-pss__table { font-size: 13px; }\n  .twt-fo-pss__table th, .twt-fo-pss__table td { padding: 10px 12px; }\n}\n<\/style>\n<div class=\"twt-fo-pss\">\n  <div class=\"twt-fo-pss__inner\">\n    <h2>The five PSS pillars map directly to what fan-out retrieval rewards<\/h2>\n    <p>The Page Structure Score rubric used in our B2B industrial citation study was developed before this Google explanation was available. The fan-out architecture Todorovic described validates why each pillar matters at the mechanism level.<\/p>\n\n    <table class=\"twt-fo-pss__table\">\n      <thead>\n        <tr>\n          <th>PSS Pillar<\/th>\n          <th>Why it matters in a fan-out system<\/th>\n        <\/tr>\n      <\/thead>\n      <tbody>\n        <tr>\n          <td>Answer extraction<\/td>\n          <td>The synthesis layer reads snippets and early content. If the answer isn&#8217;t in the first extractable content block, AI Overviews may not surface it even if the page was retrieved.<\/td>\n        <\/tr>\n        <tr>\n          <td>Content formatting<\/td>\n          <td>Heading structure and list organization give the synthesis layer clear signals about what each section answers \u2014 critical when sub-queries are more specific than the original prompt.<\/td>\n        <\/tr>\n        <tr>\n          <td>Technical readability<\/td>\n          <td>Pages that render poorly or have heavy JavaScript-dependent content may be retrieved but fail at the extraction stage. The synthesis layer works with what it can actually read.<\/td>\n        <\/tr>\n        <tr>\n          <td>Schema markup<\/td>\n          <td>Structured data provides unambiguous signals about page type and content classification \u2014 helping the retrieval system match pages to sub-queries accurately.<\/td>\n        <\/tr>\n        <tr>\n          <td>Topical alignment<\/td>\n          <td>Fan-out generates sub-queries from the original prompt. Content that covers specific sub-topics rather than broad categories is more likely to align to one or more of those sub-queries.<\/td>\n        <\/tr>\n      <\/tbody>\n    <\/table>\n\n    <p>The mean PSS across all 547 citations in the study was 32\u201335 depending on engine. Pages that earned citations without strong PSS tended to be dominant brands with no real competition in the query set \u2014 where the retrieval filter had few alternatives. For competitive verticals, higher PSS correlated with citation presence across multiple engines.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 7: AI MODE VS AI OVERVIEWS -->\n\n\n<style>\n.twt-fo-aimode { background: #fff; padding: 60px 48px; }\n.twt-fo-aimode__inner { max-width: 760px; margin: 0 auto; }\n.twt-fo-aimode h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 30px; font-weight: 400;\n  color: #0b3d91; margin: 0 0 22px 0;\n}\n.twt-fo-aimode p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: #222;\n  line-height: 1.75; margin: 0 0 18px 0;\n}\n.twt-fo-aimode__split {\n  display: grid;\n  grid-template-columns: 1fr 1fr;\n  gap: 20px; margin: 32px 0;\n}\n.twt-fo-aimode__box {\n  background: #f7f8f9;\n  border-radius: 8px; padding: 26px 28px;\n}\n.twt-fo-aimode__box h3 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 20px; font-weight: 400;\n  color: #3232a4; margin: 0 0 12px 0;\n}\n.twt-fo-aimode__box p {\n  font-size: 15px; color: #444; margin: 0;\n}\n@media (max-width: 600px) {\n  .twt-fo-aimode { padding: 44px 24px; }\n  .twt-fo-aimode h2 { font-size: 25px; }\n  .twt-fo-aimode__split { grid-template-columns: 1fr; }\n}\n<\/style>\n<div class=\"twt-fo-aimode\">\n  <div class=\"twt-fo-aimode__inner\">\n    <h2>AI Overviews vs. AI mode \u2014 a different retrieval posture<\/h2>\n    <p>Todorovic drew a distinction between AI Overviews and Google&#8217;s newer AI mode that matters for AEO planning. AI Overviews is the fan-out system on top of standard search \u2014 retrieval first, synthesis second. AI mode is described as having &#8220;a bigger platform for its own&#8221; \u2014 it still uses Google&#8217;s search infrastructure and still produces citations, but it has more autonomy and is designed for longer multi-turn conversations.<\/p>\n\n    <div class=\"twt-fo-aimode__split\">\n      <div class=\"twt-fo-aimode__box\">\n        <h3>AI Overviews<\/h3>\n        <p>Fan-out from standard search. Retrieval runs through existing ranking infrastructure. Synthesis layer operates in a constrained space on top of those results. Cited sources are largely determined by what organic retrieval surfaces first.<\/p>\n      <\/div>\n      <div class=\"twt-fo-aimode__box\">\n        <h3>AI mode<\/h3>\n        <p>Still search-based with fan-out and linked citations, but with a larger autonomous platform. Designed for multi-turn conversation. Todorovic describes it as &#8220;no longer in isolation&#8221; \u2014 it has more surface area to operate across.<\/p>\n      <\/div>\n    <\/div>\n\n    <p>For B2B industrial brands, the near-term priority is AI Overviews, because it touches the highest volume of queries and draws from the same retrieval system as organic search. The content architecture that improves AI Overviews citation share \u2014 deep owned content, strong PSS, tight topical alignment \u2014 also builds the foundation for AI mode as it scales.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 8: WHAT TO DO -->\n\n\n<style>\n.twt-fo-action { background: #3232a4; padding: 64px 48px; }\n.twt-fo-action__inner { max-width: 760px; margin: 0 auto; }\n.twt-fo-action h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 30px; font-weight: 400;\n  color: #fff; margin: 0 0 22px 0;\n}\n.twt-fo-action p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: rgba(255,255,255,0.88);\n  line-height: 1.75; margin: 0 0 18px 0;\n}\n.twt-fo-action__steps {\n  counter-reset: twt-fo-steps;\n  list-style: none;\n  padding: 0; margin: 28px 0;\n}\n.twt-fo-action__steps li {\n  counter-increment: twt-fo-steps;\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: rgba(255,255,255,0.9);\n  line-height: 1.65;\n  padding: 16px 0 16px 52px;\n  border-bottom: 1px solid rgba(255,255,255,0.12);\n  position: relative;\n}\n.twt-fo-action__steps li:last-child { border-bottom: none; }\n.twt-fo-action__steps li::before {\n  content: counter(twt-fo-steps);\n  position: absolute; left: 0; top: 16px;\n  width: 32px; height: 32px;\n  background: #f97316;\n  border-radius: 50%;\n  font-family: 'DM Sans', sans-serif;\n  font-size: 15px; font-weight: 700;\n  color: #fff;\n  display: flex; align-items: center; justify-content: center;\n  line-height: 32px; text-align: center;\n}\n.twt-fo-action__steps li strong { color: #06d6a0; }\n@media (max-width: 600px) {\n  .twt-fo-action { padding: 48px 24px; }\n  .twt-fo-action h2 { font-size: 25px; }\n}\n<\/style>\n<div class=\"twt-fo-action\">\n  <div class=\"twt-fo-action__inner\">\n    <h2>The practical checklist from this architecture<\/h2>\n    <p>The fan-out mechanic is not a reason to chase sub-keywords as individual targets. It is a reason to build content with enough depth and specificity that sub-queries \u2014 wherever they land \u2014 find a page on your site that can answer them.<\/p>\n    <ol class=\"twt-fo-action__steps\">\n      <li><strong>Map your sub-topics, not just your head terms.<\/strong> For every primary category query your brand wants to own, identify the more specific questions that a fan-out is likely to generate. Build content that addresses each directly.<\/li>\n      <li><strong>Put the answer in the first extractable block.<\/strong> The synthesis layer reads snippets and early page content. If your answer is buried in paragraph seven, it may not reach the synthesis pool even if the page was retrieved.<\/li>\n      <li><strong>Structure matters more than word count.<\/strong> Clear heading hierarchy signals to both the retrieval and synthesis systems what each section covers. A well-structured 800-word page outperforms a poorly structured 3,000-word page in AI extraction.<\/li>\n      <li><strong>Schema closes the loop.<\/strong> Structured data \u2014 Article, Product, FAQ \u2014 gives the retrieval system unambiguous classification signals that help match your pages to the right sub-queries in the fan-out.<\/li>\n      <li><strong>Technical rendering is not optional.<\/strong> If your page requires JavaScript to display its primary content, the synthesis layer may retrieve a shell and extract nothing useful. Test for crawlable, rendered content.<\/li>\n    <\/ol>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 9: METHODOLOGY \/ SOURCE NOTE -->\n\n\n<style>\n.twt-fo-meth { background: #0b3d91; padding: 60px 48px; }\n.twt-fo-meth__inner { max-width: 760px; margin: 0 auto; }\n.twt-fo-meth h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 26px; font-weight: 400;\n  color: #fff; margin: 0 0 18px 0;\n}\n.twt-fo-meth h3 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 19px; font-weight: 400;\n  color: #00b4d8; margin: 24px 0 10px 0;\n}\n.twt-fo-meth p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 16px; color: rgba(255,255,255,0.82);\n  line-height: 1.7; margin: 0 0 14px 0;\n}\n.twt-fo-meth a { color: #00b4d8; text-decoration: underline; }\n@media (max-width: 600px) { .twt-fo-meth { padding: 44px 24px; } }\n<\/style>\n<div class=\"twt-fo-meth\">\n  <div class=\"twt-fo-meth__inner\">\n    <h2>Sources and methodology<\/h2>\n\n    <h3>Search Off the Record, Episode 109 \u2014 &#8220;How Search Is Changing&#8221;<\/h3>\n    <p>Google&#8217;s Search Off the Record podcast, hosted by Martin Splitt (Developer Relations). Guest: Nikola Todorovic, SafeSearch Engineering Lead, Google Zurich. Published May 2026. The fan-out explanation, AI Overviews architecture description, query length finding, and AI mode distinction referenced in this article are drawn from that episode. All characterizations are paraphrased from the transcript; no extended quotes are reproduced.<\/p>\n\n    <h3>Tampa Web Technologies 550-citation B2B industrial study<\/h3>\n    <p>Queries were run across ChatGPT, Perplexity, and Gemini between late 2025 and early 2026. Each citation was classified by ownership type and scored against a five-factor Page Structure Score rubric measuring answer extraction, content formatting, technical readability, schema markup, and topical alignment. Sixteen B2B industrial verticals were included. The PSS correlations and ownership distribution figures cited in this article come from that dataset.<\/p>\n\n    <h3>Limitations<\/h3>\n    <p>The TWT study covers 550+ citations in B2B industrial verticals specifically. Findings should not be generalized to consumer, entertainment, or healthcare-consumer categories. PSS is a proprietary working rubric, not a peer-reviewed measure. The Google podcast episode reflects one engineer&#8217;s framing of AI Overviews architecture; Google does not publish a formal technical spec of the fan-out system for external use.<\/p>\n  <\/div>\n<\/div>\n\n\n<!-- BLOCK 10: CTA \u2014 NO PHONE (TWT NEWS RULE) -->\n\n\n<style>\n.twt-fo-cta {\n  background: #f97316;\n  padding: 60px 48px;\n  text-align: center;\n}\n.twt-fo-cta__inner { max-width: 640px; margin: 0 auto; }\n.twt-fo-cta h2 {\n  font-family: 'DM Serif Display', serif;\n  font-size: 28px; font-weight: 400;\n  color: #fff; margin: 0 0 14px 0; line-height: 1.25;\n}\n.twt-fo-cta p {\n  font-family: 'DM Sans', sans-serif;\n  font-size: 17px; color: rgba(255,255,255,0.92);\n  line-height: 1.65; margin: 0 0 28px 0;\n}\n.twt-fo-cta__btn {\n  display: inline-block;\n  background: #fff;\n  color: #c2410c;\n  font-family: 'DM Sans', sans-serif;\n  font-size: 16px; font-weight: 700;\n  padding: 15px 32px;\n  border-radius: 6px;\n  text-decoration: none;\n  letter-spacing: 0.02em;\n}\n.twt-fo-cta__btn:hover { background: #0b3d91; color: #fff; }\n@media (max-width: 600px) {\n  .twt-fo-cta { padding: 48px 24px; }\n  .twt-fo-cta h2 { font-size: 24px; }\n}\n<\/style>\n<div class=\"twt-fo-cta\">\n  <div class=\"twt-fo-cta__inner\">\n    <h2>Audit your AI citation architecture<\/h2>\n    <p>Tampa Web Technologies measures your real citation share across ChatGPT, Perplexity, and Gemini \u2014 and diagnoses exactly where your content is getting filtered before it reaches the synthesis layer.<\/p>\n    <a href=\"https:\/\/tampawebtech.com\" class=\"twt-fo-cta__btn\">Talk to Tampa Web Technologies<\/a>\n  <\/div>\n<\/div>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>AEO \u00b7 GEO \u00b7 Google Search Architecture What Google&#8217;s Fan-Out Architecture Means for Your AI Citation Strategy A Google search engineer just explained, on the record, how AI Overviews actually retrieves content. The mechanism validates exactly why thin pages get filtered out \u2014 and why owned technical depth survives. Tampa Web Technologies \u00b7 David Chamberlain [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":145,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[115,114],"tags":[],"class_list":["post-143","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-analysis","category-ai-news"],"_links":{"self":[{"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/posts\/143","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/comments?post=143"}],"version-history":[{"count":1,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/posts\/143\/revisions"}],"predecessor-version":[{"id":144,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/posts\/143\/revisions\/144"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/media\/145"}],"wp:attachment":[{"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/media?parent=143"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/categories?post=143"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/tampawebtech.com\/news\/wp-json\/wp\/v2\/tags?post=143"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}