<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
  <title>Hayden Schuster: writing</title>
  <link>https://haydenschuster.com/writing/</link>
  <atom:link href="https://haydenschuster.com/feed.xml" rel="self" type="application/rss+xml"/>
  <description>Building systems that get brands found, understood, and chosen across search and AI.</description>
  <language>en-us</language>
  <lastBuildDate>Sun, 11 Oct 2026 00:00:00 GMT</lastBuildDate>
  <item>
    <title>The recommendation layer: how AI picks which brands to name</title>
    <link>https://haydenschuster.com/writing/the-recommendation-layer/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/the-recommendation-layer/</guid>
    <pubDate>Sat, 18 Jul 2026 00:00:00 GMT</pubDate>
    <description>How ChatGPT, Gemini and Google&#39;s AI Mode pick which brands make the answer, the three tests content must pass, and data from a fan site.</description>
    <content:encoded><![CDATA[<aside class="post-aside" aria-label="Being real for a second">
<p class="post-aside-label">Being real for a second</p>
<p>I miss the old web. Ten results, six open tabs, the click a good page actually earned. I didn't ask for a machine middleman, and some days I still resent it. But somewhere between the resentment and the client work, I noticed something: this era rewards exactly the things I got into SEO for. <strong>Real data, honest sourcing, structure that respects the reader.</strong> The tricks are dying and the craft is getting promoted. So no, I don't love the landscape. I love what it demands.</p>
</aside>
<p>Picture someone buying an espresso machine. Five years ago they typed &quot;best espresso machine under $500,&quot; opened six tabs, and argued with themselves for a week before deciding. Now they ask ChatGPT and get three machines ranked with reasons, because the model has already read the reviews, compared the specs, and made the call for them. In <a href="https://www.orbitmedia.com/blog/ai-vs-google/">Orbit Media's March 2026 survey of 1,110 US adults</a>, 55 percent said AI chat was their primary or frequent tool for research.</p>
<p>Here's the honest part most posts skip: that same survey found Google usage hasn't declined, which means this is less a replacement story than an addition story. The shift is what people have always done when choice gets overwhelming: they borrow judgment from something they trust, and the trusted something just stopped being human. <strong>A new decision-maker showed up between your customer and your website</strong>, and it never scrolls, never gets bored, and has never once been charmed by a hero image.</p>
<p>That new reader is the problem I spend my working weeks on. I build AI visibility systems for enterprise brands, and this post is the mental model behind the work I publish at <a href="https://haydenschuster.com/">haydenschuster.com</a>: what the recommendation layer is, how it behaves differently on every surface, and the loop I use to win it. And instead of hypotheticals, I'm going to show you the receipts.</p>
<div class="post-data">
<p class="post-data-label">Dungeon data: crawlerscookbook.com</p>
<p>Meet the lab: <a href="https://crawlerscookbook.com/">The Crawler's Cookbook</a>, my for-fun fan site for the Dungeon Crawler Carl books, where I test everything before it goes near a client. In the archived October 7 Bing AI Performance export, its Book 9 release-date question drew <strong>6,746 citations</strong> at a <strong>47.59 percent citation share</strong>. The site's reading-order guide appeared in the page citation report too. Those are separate reports. One shows how people ask; the other shows which page Bing cited. Put them together and the next page idea is less of a guess.</p>
</div>
<h2 id="who-makes-the-decision-now"><span class="sec-n" aria-hidden="true">01</span>Who makes the decision now?</h2>
<p>The searching didn't change much. The deciding changed completely.</p>
<figure class="post-fig pframe post-fig--inline post-fig--diagram" id="fig-recommendation-old-vs-ai-search" style="--frame: var(--field); --frame-shadow: var(--piece-s)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/old-search-vs-ai-search-recommendation-layer-480.webp 480w, https://haydenschuster.com/assets/post-images/old-search-vs-ai-search-recommendation-layer-960.webp 960w, https://haydenschuster.com/assets/post-images/old-search-vs-ai-search-recommendation-layer-1254.webp 1254w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/old-search-vs-ai-search-recommendation-layer-480.jpg" width="1254" height="1254" alt="Diagram of old search versus AI search. Old search runs search, click, compare, decide. AI search runs ask, then a recommendation layer where AI reads several sources and returns a checked shortlist, then decide." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 1</span> Old search ran search, click, compare, decide, and the person did every step. AI search puts a recommendation layer between the question and the decision. <a class="post-fig-full" href="https://haydenschuster.com/assets/post-images/old-search-vs-ai-search-recommendation-layer-1254.webp">Open it full size</a></figcaption></figure><div class="post-table"><table>
<thead>
<tr>
<th>Step</th>
<th>Classic search</th>
<th>AI search</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Step">Scans the options</td>
<td data-label="Classic search">You</td>
<td data-label="AI search">The model</td>
</tr>
<tr>
<td data-label="Step">Compares them</td>
<td data-label="Classic search">You</td>
<td data-label="AI search">The model</td>
</tr>
<tr>
<td data-label="Step">Judges trust</td>
<td data-label="Classic search">You</td>
<td data-label="AI search">The model</td>
</tr>
<tr>
<td data-label="Step">Makes the call</td>
<td data-label="Classic search">You</td>
<td data-label="AI search">The model</td>
</tr>
<tr>
<td data-label="Step">Checks out</td>
<td data-label="Classic search">You</td>
<td data-label="AI search">Increasingly, the agent</td>
</tr>
<tr>
<td data-label="Step">Visits your site</td>
<td data-label="Classic search">Everyone</td>
<td data-label="AI search">Almost no one</td>
</tr>
</tbody>
</table></div>
<p>Every row in that table used to be your customer's job. Search Engine Land calls this territory the <a href="https://searchengineland.com/ai-decision-layer-agentic-commerce-481862">AI decision layer</a>, where AI weighs trust, relevance, and authority before deciding who makes the shortlist, and losing here means the customer never learns you existed.</p>
<p>The checkout row is the newest and, for ecommerce, the biggest. Google <a href="https://developers.googleblog.com/under-the-hood-universal-commerce-protocol-ucp/">introduced the Universal Commerce Protocol</a> in January 2026 with Shopify, Target, Walmart and other partners. In May, it <a href="https://blog.google/products-and-platforms/products/shopping/shopping-updates-google-marketing-live/">announced Universal Cart checkout with Google Pay and Merchant Center AI performance insights</a>, with the checkout features and reporting rolling out rather than available to every merchant at once. The direction is clear: when a shopper can buy from an AI answer, inclusion affects more than a click.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-is-the-recommendation-layer"><span class="sec-n" aria-hidden="true">02</span>What is the recommendation layer?</h2>
<p>The recommendation layer is the space between a person's question and the answer an AI gives them. It's where ChatGPT, Gemini, Perplexity, Copilot, and Google's AI Mode fetch sources, weigh them, and choose which brands and pages get into the answer. In classic search your job ended at ranking, but here ranking is only the audition, and getting chosen is the job.</p>
<p>If you think your rankings have this covered, they don't. <a href="https://ahrefs.com/blog/ai-search-overlap/">Ahrefs tested 15,000 prompts</a> and found only 12 percent of links cited by ChatGPT, Gemini, and Copilot rank in Google's top 10 for the same prompt, and around 80 percent do not rank in Google's top 100 for the original query. <strong>Your rank tracker is watching one store while the model shops in several.</strong></p>
<figure class="post-fig pframe post-fig--inline post-fig--diagram" id="fig-recommendation-layer-diagram" style="--frame: var(--field); --frame-shadow: var(--piece-s)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/recommendation-layer-inputs-steps-outputs-480.webp 480w, https://haydenschuster.com/assets/post-images/recommendation-layer-inputs-steps-outputs-960.webp 960w, https://haydenschuster.com/assets/post-images/recommendation-layer-inputs-steps-outputs-1568.webp 1568w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/recommendation-layer-inputs-steps-outputs-480.jpg" width="1568" height="1003" alt="Infographic of the recommendation layer. Inputs: retrieved sources, user context, model knowledge and trust signals. The layer's four steps: evaluate, weigh, decide, recommend. Outputs: AI answers, citations and brand mentions, where only the most trusted and relevant make it through." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 2</span> Inside the recommendation layer: what goes in, the four steps the model runs, and what comes out. Most sources are retrieved; few are recommended. <a class="post-fig-full" href="https://haydenschuster.com/assets/post-images/recommendation-layer-inputs-steps-outputs-1568.webp">Open it full size</a></figcaption></figure><div class="post-data">
<p class="post-data-label">Dungeon data: the decoupling, live</p>
<p>One question proves the split. In Bing's AI answers, the fan site holds <strong>68 percent of the citations</strong> for &quot;dungeon crawler books in order&quot; (Bing AI Performance, data through August 26, 2026), the exact question its reading-order guide exists to answer. No rank tracker would ever show you that. Watch only rankings and you'd miss it entirely. Read Search Console for search demand, Bing's AI report for citations, and the answer itself for context. One scoreboard is not the whole game.</p>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="one-layer-five-landscapes"><span class="sec-n" aria-hidden="true">03</span>One layer, five landscapes</h2>
<p>&quot;AI search&quot; isn't one thing. Each surface retrieves differently, trusts differently, and rewards different work, and treating them as one blob is how teams end up optimizing for none of them.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Surface</th>
<th>What it is</th>
<th>What we can verify</th>
<th>What to do</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Surface">AI Overviews</td>
<td data-label="What it is">Google's summary above results <a href="https://haydenschuster.com/writing/answer-first-content/">on some queries</a>.</td>
<td data-label="What we can verify"><a href="https://developers.google.com/search/docs/fundamentals/ai-optimization-guide">Google says</a> it uses Search ranking and index systems; an <a href="https://ahrefs.com/blog/ai-search-overlap/">Ahrefs study</a> found about 76 percent of cited URLs in Google's top 10.</td>
<td data-label="What to do">Keep the answer clear on the page, earn the ranking, then check the overview itself.</td>
</tr>
<tr>
<td data-label="Surface">AI Mode</td>
<td data-label="What it is">Google's conversational search experience.</td>
<td data-label="What we can verify"><a href="https://developers.google.com/search/docs/fundamentals/ai-optimization-guide">Google describes</a> related-query fan-out using its Search index.</td>
<td data-label="What to do">Follow the real questions past the head term. Answer the useful follow-ups where they belong.</td>
</tr>
<tr>
<td data-label="Surface">ChatGPT, Gemini and Claude</td>
<td data-label="What it is">Assistants people ask directly.</td>
<td data-label="What we can verify">Their web retrieval differs and changes. <a href="https://help.openai.com/en/articles/12627856-publishers-and-developers-faq">OpenAI documents</a> its search crawler and third-party results; <a href="https://www.anthropic.com/news/web-search">Anthropic documents</a> Claude's web search without naming a permanent index provider.</td>
<td data-label="What to do">Test the questions, inspect the citations, and make sure documented crawlers can reach the source.</td>
</tr>
<tr>
<td data-label="Surface">Copilot</td>
<td data-label="What it is">Microsoft's assistant across its products.</td>
<td data-label="What we can verify"><a href="https://blogs.bing.com/webmaster/2026/2/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview/">Bing Webmaster Tools</a> reports citations across Copilot, Bing AI answers and select partners; its grounding queries are a sample.</td>
<td data-label="What to do">Read the cited URLs and question patterns. Citation count is not a ranking position.</td>
</tr>
<tr>
<td data-label="Surface">Perplexity</td>
<td data-label="What it is">An answer engine that cites sources.</td>
<td data-label="What we can verify"><a href="https://www.perplexity.ai/en-GB/hub/blog/architecting-and-evaluating-an-ai-first-search-api">Perplexity describes</a> its crawler and indexing fleet; Ahrefs found about one in three citations in Google's top 10 for the same prompt.</td>
<td data-label="What to do">Keep the source reachable; look at the pages it actually cites.</td>
</tr>
</tbody>
</table></div>
<figure class="post-fig pframe post-fig--inline post-fig--screenshot post-fig--surfaces" id="fig-recommendation-ai-surfaces" style="--frame: var(--field); --frame-shadow: var(--piece-j)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/google-ai-overview-example-480.webp 480w, https://haydenschuster.com/assets/post-images/google-ai-overview-example-960.webp 960w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/google-ai-overview-example-480.jpg" width="960" height="478" alt="A Google AI Overview for the search 'ai overviews': an AI-written summary at the top of the results, with its source links in a panel on the right." loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/google-ai-mode-example-480.webp 480w, https://haydenschuster.com/assets/post-images/google-ai-mode-example-960.webp 960w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/google-ai-mode-example-480.jpg" width="960" height="614" alt="Google AI Mode answering the search 'google' in a conversation, with quick web results above the answer and a panel of seven sources on the right." loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/chatgpt-prompt-box-480.webp 480w, https://haydenschuster.com/assets/post-images/chatgpt-prompt-box-960.webp 960w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/chatgpt-prompt-box-480.jpg" width="960" height="173" alt="The ChatGPT prompt box under the heading 'Where should we begin?', with 'What are chatbots' typed in." loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/gemini-prompt-box-480.webp 480w, https://haydenschuster.com/assets/post-images/gemini-prompt-box-960.webp 960w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/gemini-prompt-box-480.jpg" width="960" height="251" alt="The Gemini prompt box under the greeting 'What can I help with, Hayden?'" loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/copilot-prompt-box-480.webp 480w, https://haydenschuster.com/assets/post-images/copilot-prompt-box-960.webp 960w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/copilot-prompt-box-480.jpg" width="960" height="263" alt="The Microsoft Copilot message box under the greeting 'Hi Hayden, what should we dive into today?'" loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/perplexity-prompt-box-480.webp 480w, https://haydenschuster.com/assets/post-images/perplexity-prompt-box-960.webp 960w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/perplexity-prompt-box-480.jpg" width="960" height="331" alt="The Perplexity search box under the heading 'What do you want to know?', with Search and Computer options." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 3</span> What the five landscapes look like: Google's AI Overview and AI Mode, then the prompt boxes of ChatGPT, Gemini, Copilot and Perplexity. Screenshots from the original post, published July 18, 2026.</figcaption></figure><p>The overlap figures in that table are <a href="https://ahrefs.com/blog/ai-search-overlap/">Ahrefs data</a>, and the spread is the point. AI Overviews cited Google's top-ranking pages much more often than the assistants in that study. But citation overlap does not reveal each provider's internal plumbing. Build for access, evidence and a good answer; then read the actual citations. One ranking report cannot speak for five surfaces.</p>
<div class="post-data">
<p class="post-data-label">Dungeon data: a fan-out in the wild</p>
<p>Bing's grounding-query export for the fan site includes many ways of asking when the next book arrives. A single head keyword hides those follow-up questions. The variants are the outline: check whether the Book 9 page answers each form fans actually use.</p>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="a-mention-is-not-a-citation"><span class="sec-n" aria-hidden="true">04</span>A mention is not a citation</h2>
<p>A mention is the model saying your name, while a citation is the model pointing at your content as the source. Here's the shape of each, using a real page from <a href="https://haydenschuster.com/portfolio/checkmytap/">CheckMyTap, one of my sites</a>.</p>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Mention:</strong> the model working from memory</p>
<blockquote>
<p>&quot;Several independent sites publish city-level water quality data.&quot;</p>
</blockquote>
<p>The category exists in the model's memory, assembled from what <strong>other people</strong> wrote, and it comes with no guaranteed name, no link, and no path back to any particular site.</p>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Citation:</strong> the model using your evidence</p>
<blockquote>
<p>&quot;<a href="https://checkmytap.com/">CheckMyTap</a>'s Phoenix page lists the city's measured hardness, lead, and PFAS readings [checkmytap.com].&quot;</p>
</blockquote>
<p>That citation can only exist because <strong>the real readings sit on the page</strong>. The model is staking its answer on data nobody else assembled, and the credit and the path back come with it.</p>
</div>
</div>
<p>Most brands celebrate the first one and stop. Screenshots are not a strategy, and the two don't reliably travel together:</p>
<div class="post-stat">
<p><span class="post-stat-n">62%</span> of AI citations are &quot;ghost citations&quot;: the AI links a site as a source but never says the brand's name, per <a href="https://www.semrush.com/blog/the-ghost-citations-study/">Kevin Indig and Semrush's analysis of 3,981 domain appearances</a> across ChatGPT, Gemini, AI Overviews, and AI Mode.</p>
</div>
<p>A real recommendation is both at once: the model says your name <strong>and</strong> uses your content as the proof. Being named without being cited means the model is repeating your reputation rather than your facts, and being cited without being named means you did the work and got none of the credit.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-three-tests-your-content-has-to-pass"><span class="sec-n" aria-hidden="true">05</span>The three tests your content has to pass</h2>
<p>Every AI answer runs your content through three checks, in order, and failing one means the rest don't matter. If you know my Found, Understood, Chosen framework, this is the same system pointed at a new judge: visibility is Get Found, verifiability is Get Understood, quotability is Get Chosen.</p>
<figure class="post-fig pframe post-fig--inline post-fig--diagram" id="fig-recommendation-three-tests" style="--frame: var(--field); --frame-shadow: var(--piece-s)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/three-things-ai-needs-from-your-content-480.webp 480w, https://haydenschuster.com/assets/post-images/three-things-ai-needs-from-your-content-960.webp 960w, https://haydenschuster.com/assets/post-images/three-things-ai-needs-from-your-content-1448.webp 1448w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/three-things-ai-needs-from-your-content-480.jpg" width="1448" height="1086" alt="Infographic titled The 3 Things AI Needs From Your Content. A question goes to an AI model, which tests content for visibility, verifiability and quotability before using it in an answer. Visibility: can the model find you. Verifiability: can the model trust you. Quotability: can the model use you in the answer. Fail one and AI may skip your content; win all three for a better chance to shape the answer." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 4</span> The three tests on one page: visibility (can the model find you), verifiability (can it trust you) and quotability (can it use you in the answer). Fail one, and the model may skip your content. <a class="post-fig-full" href="https://haydenschuster.com/assets/post-images/three-things-ai-needs-from-your-content-1448.webp">Open it full size</a></figcaption></figure><h3>1. Visibility: can I even get to this?</h3>
<p>Visibility means the model can reach and retrieve your content when it goes looking, which makes it a question about retrieval rather than rankings. If robots.txt blocks AI crawlers they can't read you, and if your words only appear after scripts load, some systems see an empty page, which is why my technical foundations work starts with what survives a raw crawl. The model also doesn't limit itself to your site; it leans on the places it already trusts, like review platforms, forums, Reddit, and YouTube, so sometimes the fastest win isn't on your domain at all.</p>
<p><strong>Pass it when</strong> AI crawlers are allowed on purpose, your key content lives in the raw page code, and you show up on the third-party sources models pull from in your category.</p>
<div class="post-data">
<p class="post-data-label">Dungeon data: passing visibility</p>
<p>Every page ships as plain, static HTML, so nothing important waits on JavaScript, and robots.txt is open on purpose rather than by accident. Each meaningful deploy pings Bing through IndexNow, a fast way of telling Bing a page changed. That gives Bing a fresh URL to crawl; it does not guarantee a citation in Copilot or any other assistant.</p>
</div>
<h3>2. Verifiability: can I trust this enough to repeat it?</h3>
<p>Verifiability means the model can check your claims before repeating them. Think of it as the world's most nervous librarian: repeating something wrong is expensive, so it favors content it can trace. This is where your moat does the work, because the data only you have, assembled the way only you assembled it, is the one claim a model can verify against you and nobody else. It's why CheckMyTap opens every city page with that city's actual readings, and why modern search systems need consistent, checkable facts about who you are everywhere they look. The <a href="https://arxiv.org/abs/2311.09735">original GEO research from Princeton, Georgia Tech, and IIT Delhi</a> found that citing credible sources inside your own content was a top tactic for AI visibility, which is worth reading twice: citing others makes you more citable.</p>
<p><strong>Pass it when</strong> claims link to named sources, content carries a real byline instead of &quot;admin,&quot; and your site, profiles, and listings all agree on who you are.</p>
<div class="post-data">
<p class="post-data-label">Dungeon data: passing verifiability</p>
<p>Structured data (machine-readable labels for the series, the books, and the author) ties every fact to sources like Wikipedia and Goodreads, so the model always meets one consistent story. The build enforces honesty too: an automated check <strong>fails the deploy if a stale fact leaks</strong> into a page, and in the last content review, five proposed pages were killed because their facts couldn't be verified against a primary source. The nervous librarian gets a site that never lies to it.</p>
</div>
<h3>3. Quotability: can I lift a clean answer out of this?</h3>
<p>Quotability means one of your sentences still makes sense when lifted into an answer. The <a href="https://arxiv.org/html/2311.09735v3">Princeton-led GEO study</a> built a 10,000-query benchmark and evaluated tactics on its 1,000-query test split. In its experimental answer engine, statistics, quotations and cited sources improved visibility, with the best result near 40 percent on one measure; keyword stuffing did little. Your customers have written quotable material too. A review with a name and a specific experience can say more than a line of marketing copy. The difference is easier to see than explain:</p>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label">What most pages write</p>
<blockquote>
<p>In today's competitive landscape, choosing the right solution can feel overwhelming, which is why it's important to consider a variety of factors.</p>
</blockquote>
</div>
<div class="post-compare-item">
<p class="post-compare-label">What machines quote: a real line from this post</p>
<blockquote>
<p>Only 12 percent of links cited by ChatGPT, Gemini, and Copilot rank in Google's top 10 for the same prompt.</p>
</blockquote>
</div>
</div>
<p><strong>Pass it when</strong> every section opens with a complete, specific, standalone claim, which is the whole idea behind <a href="https://haydenschuster.com/writing/answer-first-content/">answer-first structure</a>. The first sentence above contains zero facts a model could repeat; the second gives the reader a sourced finding they can check.</p>
<div class="post-data">
<p class="post-data-label">Dungeon data: passing quotability</p>
<p>Every book page opens like a stat sheet: narrator, page count, release date, and best seller position in one liftable passage. FAQ answers open standalone, and that FAQ page is the site's top click earner on Google with <strong>695 clicks in three months</strong>. The split shows up in the data too: the interactive class quiz wins the clicks (a 16.6 percent click rate, visitors averaging two-plus minutes), while the reference pages win the citations. Build both, and know which prize each one is chasing.</p>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-the-research-says-works"><span class="sec-n" aria-hidden="true">06</span>What the research says works</h2>
<p>The <a href="https://arxiv.org/html/2311.09735v3">GEO paper</a> (Aggarwal et al., KDD 2024) evaluated content tactics on a 1,000-query test split of its 10,000-query benchmark. In that experimental setting, adding verifiable detail and quotations improved its visibility measures.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Tactic</th>
<th>In practice</th>
<th>Result</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Tactic">Add statistics</td>
<td data-label="In practice">Specific numbers over vague claims. &quot;Removes 99 percent&quot; beats &quot;highly effective.&quot;</td>
<td data-label="Result">Among the biggest gains tested</td>
</tr>
<tr>
<td data-label="Tactic">Cite sources</td>
<td data-label="In practice">Link claims to named, credible references inside the content.</td>
<td data-label="Result">Top performer, biggest lift for lower-ranked pages</td>
</tr>
<tr>
<td data-label="Tactic">Add quotations</td>
<td data-label="In practice">Quote named experts directly, with attribution.</td>
<td data-label="Result">Strong, consistent lift</td>
</tr>
<tr>
<td data-label="Tactic">Keyword stuffing</td>
<td data-label="In practice">Cramming the phrase in over and over. The old playbook.</td>
<td data-label="Result">Made visibility worse</td>
</tr>
<tr>
<td data-label="Tactic">Persuasive fluff</td>
<td data-label="In practice">Confident marketing language with nothing checkable behind it.</td>
<td data-label="Result">No meaningful gain</td>
</tr>
</tbody>
</table></div>
<p><strong>Notice what this post is doing.</strong> The answer sits at the top, every stat names its source, and the highlighted sentences are the ones a machine could lift whole. That's the three tests applied to the post about the three tests.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="geo-is-seo"><span class="sec-n" aria-hidden="true">07</span>GEO is SEO</h2>
<p>Time to kill the laziest myth in the industry while we're here.</p>
<p>Look back at everything above and notice what it's made of. Crawlability and rendering are technical SEO. Entities, structured data, and consistent facts are the understanding layer SEO has been building for a decade. Answer-first content matched to real intent is what good SEO content always was, and it's the whole reason Found, Understood, Chosen maps onto this so cleanly. GEO is SEO. The fundamentals didn't change; the judge did. So no, SEO is not dying. <strong>It has never been more essential</strong>, because the machine now reads everything before your customer reads anything, and the discipline that decides what machines find, understand, and choose is the one this industry has been practicing all along.</p>
<p>What did change is that it stopped being a solo sport. The models lean on Reddit threads, reviews, and YouTube, which is social and community's turf. Retrieval depends on rendering, structured data, and index pings, which is the developers' turf. The moat data comes from strategy and product, and the measurement loop touches analytics. The brands winning this run SEO as a cross-functional system rather than a department, because if your SEO team, your developers, and your social team don't share a roadmap, the model meets three different versions of your brand and trusts none of them. The machines will answer either way. The question is whether they answer from verified sources or from noise, and <strong>making sure it's the former is the job</strong>. That's why this work matters more now, not less.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-loop-i-run-for-enterprise-brands"><span class="sec-n" aria-hidden="true">08</span>The loop I run for enterprise brands</h2>
<p>Every enterprise program I run settles into the same four-beat loop, and it works at any size.</p>
<p><strong>Listen.</strong> Run the real questions buyers ask, on a schedule, across ChatGPT, Gemini, Perplexity, and Google's AI surfaces, and track two things separately: whether the brand is in the answer, and whether the brand's own content is the source. A brand the model describes is at the mercy of its loudest reviewer, while a brand the model cites is telling its own story.</p>
<p><strong>Mine.</strong> The dashboards are a content calendar wearing a scorecard costume. Every question, sub-search, and grounding query the brand hasn't directly answered becomes a brief.</p>
<p><strong>Answer.</strong> Rewrite the pages that matter so each section opens with the answer, turn the mined sub-questions into FAQ entries that actually resolve them, and publish the moat data only this brand has.</p>
<p><strong>Verify.</strong> Watch mentions and citations move separately on each surface over the following weeks. When citations rise but mentions stay flat, the content is trusted and the brand framing needs work; when mentions rise without citations, the brand has fame and no receipts. The split tells you what to fix next, winners get the next round of investment, and the loop starts again.</p>
<p>Every green box in this post is that loop running on my own hobby site, with Bing's grounding report as the citation scoreboard. <a href="https://thequackreport.com/">The Quack Report</a> runs the same playbook on Oregon football history, keeping every rivalry record and season result at its own citable address, and CheckMyTap runs it on city water data. The subjects have nothing in common, but the three tests are identical.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="your-dashboards-are-a-content-strategy"><span class="sec-n" aria-hidden="true">09</span>Your dashboards are a content strategy</h2>
<p>Most teams read these four tools as report cards, but the better read is that each one hands you the next thing to write. It helps to know why measurement is hard in the first place: someone asks ChatGPT, gets your brand, then googles your name, and your analytics logs a branded search. <strong>The AI's fingerprints are nowhere in the data</strong>, so you triangulate.</p>
<h3>Peec AI: what to answer next</h3>
<p>Feed <a href="https://peec.ai/">Peec AI</a> your buyer questions and it runs them across ChatGPT, Perplexity, Gemini, and Google's AI surfaces on a schedule, tracking whether you appear, how you're framed, and which sources shaped each answer, and it exposes the fan-out queries behind each one.</p>
<p><strong>The move:</strong> Those fan-outs and tracked questions are a ready-made FAQ outline. Answer each one directly on your site and you're covering demand your keyword tools will never show you.</p>
<p><strong>Blind spot:</strong> Scheduled test prompts, not real user sessions.</p>
<h3>Bing Webmaster Tools: what retrieval already likes</h3>
<p>Microsoft's <a href="https://blogs.bing.com/webmaster/2026/2/Introducing-AI-Performance-in-Bing-Webmaster-Tools-Public-Preview/">AI Performance report</a>, introduced in February 2026, shows page-level citations across Copilot, Bing AI answers and select partners, plus a sample of grounding queries. It's a free look at where pages were cited and what the system was trying to answer, and it's the source of the citation numbers in this post.</p>
<p><strong>The move:</strong> Treat grounding queries as briefs. Read the cited page and the question together, then improve the answer or build the missing page. Test ChatGPT separately; Bing citations do not tell you which sources ChatGPT used.</p>
<p><strong>Blind spot:</strong> Microsoft's ecosystem only. No click data yet.</p>
<h3>Google Search Console: how people phrase it now</h3>
<p>Google folds AI Overviews and AI Mode into the standard performance report, so you read it through patterns. <a href="https://haydenschuster.com/writing/impressions-up-clicks-flat/">Impressions climbing while clicks stay flat</a> deserve an investigation, not an instant AI win label: inspect the queries and live results. On the fan site, one character page pulled <strong>87,923 impressions in three months at a 0.35 percent click rate</strong>. That proves demand and thin click-through; the result page tells you where the answer went. My approach to <a href="https://haydenschuster.com/writing/search-console-visibility-dashboard/">using GSC as a visibility dashboard</a> matters more now, not less.</p>
<p><strong>The move:</strong> Mine the query report for the longer, question-shaped queries showing up against each template. Those are prompts in disguise, and they track exactly how search behavior is shifting. Give every one a direct on-page answer.</p>
<p><strong>Blind spot:</strong> No dedicated AI report. You're inferring from blended data.</p>
<h3>GA4: which pages convert the machine's clicks</h3>
<p><a href="https://support.google.com/analytics/answer/9164320?hl=en">GA4 added an AI Assistant channel in May 2026</a>. It groups recognized assistant referrers; <a href="https://support.google.com/analytics/answer/9756891?hl=en">Google's channel definition</a> excludes AI Overviews and AI Mode, so I still inspect session sources and use a custom group when I want to include more referrers. On the fan site, the AI channel catches about a hundred sessions a month (155 in the 30 days to July 17), which is real but a fraction of what the citation data shows upstream. <a href="https://www.seerinteractive.com/insights/case-study-6-learnings-about-how-traffic-from-chatgpt-converts">Seer Interactive's single-client case study</a> measured ChatGPT referrals converting at 15.9 percent against 1.76 percent for Google organic from October 2024 through April 2025. That comparison describes one client and one period; it does not predict the conversion rate for another site.</p>
<p><strong>The move:</strong> Run landing page by AI source. The pages already earning AI clicks and conversions are your template, so make the rest of the site look like them.</p>
<p><strong>Blind spot:</strong> Undercounts hard. Many AI visits arrive with no referrer and get logged as Direct.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="bringing-it-together-the-build-sheet"><span class="sec-n" aria-hidden="true">10</span>Bringing it together: the build sheet</h2>
<p>Three tests, the real assets that pass them, and the data that finds your priority one work. This is the sheet the whole post has been building toward.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>The test</th>
<th>What you actually build</th>
<th>The data that finds your P1s</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="The test">Visibility</td>
<td data-label="What you actually build">Open crawler access, key content in the raw page code, and presence on the review sites, forums, and channels models already trust in your category.</td>
<td data-label="The data that finds your P1s">A crawl with scripts off, Bing's cited-URL gaps, and Peec's source lists showing which domains shape your category's answers.</td>
</tr>
<tr>
<td data-label="The test">Verifiability</td>
<td data-label="What you actually build">Moat data: the readings, pricing, and test results only you have. Plus consistent brand facts everywhere and real bylines on everything.</td>
<td data-label="The data that finds your P1s">Peec's framing and source reports. If the model describes you from someone else's words, that page is the P1.</td>
</tr>
<tr>
<td data-label="The test">Quotability</td>
<td data-label="What you actually build">Answer-first openers, real review pull quotes with attribution and markup, spec tables in plain HTML, and FAQ entries built from fan-outs.</td>
<td data-label="The data that finds your P1s">Fan-out queries, GSC's question-shaped queries, and Bing's grounding queries: the exact sentences to write next.</td>
</tr>
</tbody>
</table></div>
<div class="post-data">
<p class="post-data-label">What I look for in the Dungeon data</p>
<p>A grounding query can show an answer drawing on a nearby page while the site has no dedicated answer. Check the cited URL, the question and the page. If the gap is real, move the answer up the build queue. The report shows what was cited, not why Bing chose it.</p>
</div>
<p>That's the priority rule, and it holds across every program I run, whatever the industry: P1 is wherever a surface already wants you but can't use you. That means grounding events that never become citations, mentions that never come with citations, and questions sitting in your own data that nothing on your site answers. Fix the pull before you build more push. This is the same system behind my modern search portfolio work, just written down.</p>
<p>The companion rule matters just as much: a winner is a map for the next build. When a page starts earning citations, the data clustering around it (the fan-out phrasings, the grounding queries, the question-shaped searches) is the machine handing you the outline for the next FAQ entry, the next post, and the next topic cluster. Prioritize those neighbors and double down, because the surface has already voted, and expanding a proven winner beats guessing at a new one every time. It's why the fan site's release date winner sits inside a whole books cluster: reading order, recaps, a page per book, each catching another question from the same pool of demand. Gaps tell you where to start. Winners tell you where to build.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="where-do-you-start"><span class="sec-n" aria-hidden="true">11</span>Where do you start?</h2>
<p>In this order, because each step is cheap and each one makes the next one smarter.</p>
<ol>
<li><strong>Run your own answers, manually, today.</strong> Put your 20 real buyer questions through ChatGPT, Gemini, and Perplexity and screenshot everything, which gives you a free baseline showing whether you're mentioned, cited, both, or invisible.</li>
<li><strong>Check that the machines can reach you.</strong> Review robots.txt for AI crawler rules you didn't know you had, and load key pages with scripts off. If the content disappears, so do you.</li>
<li><strong>Rewrite your most important pages <a href="https://haydenschuster.com/writing/answer-first-content/">answer first</a>.</strong> Open every section with one standalone, specific sentence, and put a number in it wherever the truth allows one.</li>
<li><strong>Make yourself checkable.</strong> Link claims to sources, put real names on content, and make every description of your brand agree with itself.</li>
<li><strong>Then build the stack and run the loop.</strong> Use Peec for answers, Bing for citations, GSC for phrasing, and GA4 for the money end, and run the loop: listen, mine, answer, verify.</li>
</ol>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-decides-who-ai-recommends"><span class="sec-n" aria-hidden="true">12</span>What decides who AI recommends</h2>
<p>The decision moved. People still search, but AI answers now help them read and compare before they reach a site. The surfaces behave differently: Google's AI Overviews overlap heavily with top results in Ahrefs' study, while Google's AI Mode can fan out into related queries. The assistants need their own citation checks. With agentic checkout rolling out through UCP and Universal Cart, the answer is starting to double as the store shelf.</p>
<p>Being named is awareness and being cited is trust; a real recommendation is both at once, and the data says the two rarely travel together on their own.</p>
<p>Three tests decide everything: whether the model can reach you, verify you, and quote you. GEO is SEO pointed at a new judge, your dashboards hand you the roadmap when you read them as inputs instead of report cards, P1 is wherever a surface already wants you but can't use you, and every win maps the next one. Bing's October export counted 6,746 citations against one Book 9 release-date question on my hobby fan site. The excuse shelf is empty.</p>
<p>The ten blue links gave everyone a shot, but the recommendation layer only has room for the sources it trusts. Be one of them.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Personal audit: where AI output fails</title>
    <link>https://haydenschuster.com/writing/personal-audit/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/personal-audit/</guid>
    <pubDate>Wed, 04 Mar 2026 00:00:00 GMT</pubDate>
    <description>What broke on three AI-built reference sites in early 2026: fabricated data, secondary sources, incomplete answers and broken launches.</description>
    <content:encoded><![CDATA[<p>With everything going on, it's time I had a real conversation with myself. A personal audit of some early failures and critical mistakes, if you will.</p>
<p><strong>I have made so many mistakes.</strong> I'm a solo operator with my side projects. Learning new tools and new ways of thinking is hard. Things go wrong. There's an extreme learning curve with all this crazy new technology shit, and there's so much I still have to learn. <strong>But doing and experimenting in new ways is how you get better</strong>, and mistakes happen. So let's talk about it, so maybe someone else can avoid my early pitfalls.</p>
<p>It surely isn't always sunshine and rainbows, like everyone seems to be selling with their bullshit OpenClaw agentic Twitter bots right now. It's exhausting.</p>
<p>So, there's this version of the AI + SEO conversation that's all about speed. How fast you can produce content, how many pages you can generate, and how quickly you can scale a site from zero to thousands of URLs. I get it, it's exciting, new, it allows the handcuffs to come off. I'm guilty of this excitement myself. I've made mistakes trying to scale too fast multiple times on my early projects. It's natural, I think.</p>
<p>The real problem with AI at scale is that <strong>the output looks correct when it isn't.</strong> Language models are trained to produce plausible text. Plausible and accurate are not the same thing, and on reference sites, the gap between the two has real consequences if not done right. Sometimes, you layer shit code, you double down on a broken system, and you get caught in the &quot;how am I ever going to financially recover from this&quot; mode 5 months from now when you can't edit your website because of the mistakes at the start.</p>
<p>Over the past two months I built a few programmatic reference sites: <a href="https://checkmytap.com">CheckMyTap</a> (water quality data for 1,000 US cities), <a href="https://gageref.com">GageRef</a> (welding electrode specs and hydraulic fitting data), <a href="https://wireref.com">WireRef</a> (NEC electrical code reference for all 50 states), and a couple more I'll go public with once I'm ready. <strong>Each one required enough SEO expertise to know when the AI output was wrong.</strong> That knowledge is the only reason the sites are accurate today. None of them are perfect, but all of them are significantly improved from the start of the project.</p>
<h2 id="what-broke-ranked-by-severity"><span class="sec-n" aria-hidden="true">01</span>What broke, ranked by severity</h2>
<p>Here's what catching the errors actually looked like. Ranked by severity 🫠:</p>
<ol class="ranked">
<li id="fabricated-data"><strong>Fabricated source data published as fact.</strong> AI-generated contaminant values presented as real utility measurements on health-critical pages. Are you serious right now? I had no idea. I thought I was careful. Nope. I didn't have my system in place to catch this. I didn't realize AI was fabricating data at scale.</li>
<li id="secondary-sources"><strong>Safety-critical specs sourced from secondary sites.</strong> Welding amperage values and hydraulic fitting mappings pulled from aggregators rather than the governing standards, wrong in ways that don't fail obviously. I didn't confirm the pulled sources were legitimate.</li>
<li id="incomplete-data"><strong>Incomplete data presented as complete.</strong> Correct NEC values published without the derating step that determines the number that actually matters for most installations.</li>
<li id="indexation-signals"><strong>Broken indexation signals at launch.</strong> Sitemap pointing to the wrong domain structure, canonical conflicts with the host's URL handling. Should have caught this before launch but it slipped through the cracks somehow.</li>
<li id="orphan-pages"><strong>Orphan pages and broken navigation shipped on day one.</strong> Pages with no inbound links and navigation referencing pages that didn't exist yet, on every page, for every early visitor. I thought I made sure no thin content slipped, but I didn't have specific "what is thin content" markdown skills to confirm. So when it checked, it "passed," but that was not good enough.</li>
<li id="no-validation-layer"><strong>No validation layer in the build system.</strong> No preflight checks, no post-operation integrity checks, no output verification before deployment. When I jumped to other chats, I lost the latest files and latest work, and it then built on old work. This happened multiple times, confusing me.</li>
<li id="broken-search"><strong>Broken search features shipped on launch. Twice.</strong> On-site search is the first thing a user tries when they can't find something. Shipping it broken sends a bad trust signal, and it failed on two separate launches before I treated it as a required preflight check rather than something to verify "after things settle."</li>
<li id="mobile-unverified"><strong>Mobile usability was not entirely verified before launch.</strong> Desktop looked fine. I didn't check my mobile compatibility close enough until after the fact. On sites where the primary use case is someone on a job site pulling up a spec, that's not a minor oversight.</li>
<li id="data-in-templates"><strong>No separation between data and templates.</strong> Early builds had values hardcoded into templates. When a data error surfaced, fixing it meant a rebuild. The right structure is a clean separation: data sources that can be corrected, updated, or extended independently of the templates that render them. At scale, everything that isn't connected that way becomes a maintenance problem that compounds.</li>
</ol>
<p>Unacceptable errors, truly baffling. Fixing these wasn't easy. Each one set me back big. And, it was embarrassing. I'm glad I caught these early on.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-fix-a-memory-layer"><span class="sec-n" aria-hidden="true">02</span>The fix: a memory layer</h2>
<p>One thing I do now that I didn't do at the start: <strong>I write retrospectives after every project and feed them back into future sessions as structured context.</strong> What went wrong, what the root cause was, hard rules that came out of it, and things to watch for next time.</p>
<p>The mechanics matter here. These are structured markdown files loaded into project context before any new work starts, the same way a CLAUDE.md file works in agentic coding environments: <strong>persistent instructions that survive session resets and prevent the model from reverting to defaults.</strong> The goal is the same whether you're building code or content at scale. You're prompting from an accumulated set of constraints that the system already knows to respect.</p>
<p>What I've learned is that the highest-leverage layer is <strong>the project instructions:</strong> the rules about sourcing, the validation requirements, the things that must be true before any output ships. These should be defined before the first session starts, not discovered through failure. And they should be modular. A sourcing standard for YMYL content is a different rule set from a structural validation checklist, which is different from a content architecture spec. When they're separate, they can be updated independently. When they're combined into a single document that grows without discipline, they start competing for the model's attention and some rules get missed.</p>
<p>The other pattern I've internalized: <strong>friction is a signal.</strong> When I find myself correcting the same type of mistake across sessions, that correction belongs in the persistent layer, not in the next prompt. The retrospective is the mechanism that captures it. The project instructions are where it lives permanently. What this means in practice is that the mistakes I made on the first site didn't repeat on the second, and didn't repeat on the third. Each build started with a richer constraint set. Each one was measurably cleaner.</p>
<p>I put the checks this led to on <a href="https://haydenschuster.com/systems/#promises">my systems page</a>, next to the kinds of errors they can catch and the ones that still need my judgment.</p>
<p>The retrospectives for these three projects are what made this post possible. They're also what made the fourth and fifth projects meaningfully better than the first three.</p>
<p>I'm still actively working on improving this part of the system. I have a lot to learn and a long way to go. This is priority one for me right now. But this is a start.</p>
<p>Okay, now, let's go through some of these, and I'll tell you how I caught and fixed them:</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="round-numbers-are-a-fabrication-signal"><span class="sec-n" aria-hidden="true">03</span>Round numbers are a fabrication signal</h2>
<p><strong>Language models produce plausible numbers. Real data sources produce precise ones.</strong> That gap is the tell, and it's easy to miss when you're moving fast. Didn't know this 🙂</p>
<p>The first version of <a href="https://checkmytap.com">CheckMyTap</a> had AI-generated contaminant estimates (lead, PFAS, nitrate, chlorine, hardness, TDS) across 1,000 city pages. The values were geographically consistent. Soft-water cities showed low hardness. Southwest cities showed high. They felt right in the way that well-calibrated fabrications do. I truly didn't know any better. Thought they were accurate. Double checked as well, just in the wrong way.</p>
<p>Real water quality data comes from lab instruments. It has decimal precision because that's what the measurement actually produced. AI estimates produce round numbers because round numbers are what a language model reaches for when no specific source exists. When I cross-referenced a single city against its actual Consumer Confidence Report, four of six values were materially wrong. Lead overstated by nearly 3x. Nitrate overstated by 14x. The site had been live for 11 days at that point.</p>
<p>The SEO frame here is survivability. YMYL content with no traceable primary source fails Google's quality evaluation regardless of how clean the architecture is. Data provenance is an SEO requirement before it's an ethical one. The two are not separate concerns.</p>
<p>Fixing it meant going back to primary sources: downloading CSVs directly from EPA SDWIS and UCMR5, cross-referencing against EWG's tap water database, and running values against multiple sources to catch discrepancies before they went back live. I used other AI tools as part of the cross-examination process, specifically to flag where values across sources diverged rather than to generate new ones. Every city page now cites its sources explicitly. The rule that came out of it: if you can't name the primary source for every value before the page is built, you're not ready to build the page.</p>
<p>That rule now lives in the project context files that load at the start of every new build. It's enforced before the first session starts.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="wrong-within-range-is-the-hardest-failure-to-catch"><span class="sec-n" aria-hidden="true">04</span>Wrong within range is the hardest failure to catch</h2>
<p>Obvious errors get reported and corrected. <strong>Errors that are plausible but wrong propagate indefinitely because nothing breaks visibly.</strong> Users don't flag them, the site keeps ranking, and the information stays wrong.</p>
<p>On <a href="https://gageref.com">GageRef</a>, the original welding electrode data had amperage values that were 10 to 15% high on specific rod diameters. Not wildly off. Within the range most welders operate in day to day. But not what AWS A5.1 and A5.18 actually specify, because the values had been sourced from secondary aggregator sites rather than the governing standards directly. The aggregators were wrong. The error was subtle enough that nothing about the page signaled a problem.</p>
<p>The catch was source audit, not welding domain expertise: the same SEO lens that evaluates whether a page has a defensible information advantage. A reference site that can't identify its primary source for each data point is a repackage of whatever the aggregators already published, with no new signal for search and no reason to be trusted over them.</p>
<p>Fixing it meant going to the standards directly: downloading and cross-referencing AWS A5.1, A5.18, and SAE J514, confirming values against multiple sources, and rebuilding the affected data. Multiple AI tools were used to cross-examine outputs against each other, which surfaces disagreement between sources faster than manual comparison alone. Every value on GageRef now cites its source standard explicitly. The methodology page names those standards because that attribution is what makes the site a reference rather than an aggregator, for users and for search systems evaluating whether the content has genuine information gain.</p>
<p>The constraint that came out of this also lives in the project files now: secondary sources can inform structure, never values on a reference page.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="an-incomplete-reference-is-its-own-category-of-wrong"><span class="sec-n" aria-hidden="true">05</span>An incomplete reference is its own category of wrong</h2>
<p>There's a failure mode that isn't fabrication and isn't secondary sourcing: <strong>presenting correct but incomplete data as if it's the full answer. Super hard to catch because the values themselves check out.</strong></p>
<p><a href="https://wireref.com">WireRef</a> launched with accurate NEC ampacity values from Table 310.16. Most reference sites stop there, and stopping there is the problem. An installation also has to account for temperature correction, conductor-count adjustment where they apply, and the equipment's termination rating. Under <a href="https://docinfofiles.nfpa.org/files/AboutTheCodes/70/70_A2025_NEC_P01_FD_PIResponses.pdf">NEC 2023 section 110.14(C)(1)</a>, the default for equipment on circuits rated 100 A or less, or marked for 14 AWG through 1 AWG conductors, is the 60°C ampacity unless the equipment is listed and identified for a higher temperature. For circuits over 100 A or equipment marked for larger conductors, the default is 75°C unless it is listed and identified otherwise. A conductor's 90°C insulation rating alone does not make the 90°C table value the usable answer.</p>
<p>The SEO problem is trust compression. When a user applies the answer and gets a different result in the field, the site loses the one thing that makes reference content rank over time: being the source people rely on. Incomplete reference that looks complete produces exactly that outcome, and it does it quietly.</p>
<p>The fix was structural and required starting over on the data layer. The original build had values tied directly to templates: ampacity numbers baked into the page generation logic rather than living in a separate, queryable source. That architecture worked until something needed to change, at which point changing one value meant touching the template, and touching the template meant risking the presentation of every other value on every page that used it. One correction could fragment the output in ways that weren't immediately visible.</p>
<p>The rebuild separated the concerns cleanly. All NEC data was restructured into JSON files where each wire gauge entry carried its own complete record: base ampacity by temperature rating, the applicable correction factors, the bundling adjustment, and the 110.14(C) termination limit that determines the number an installer actually uses. Templates don't make calculations or carry values. They read from the JSON, apply the display logic, and surface the chain in sequence with the governing code section named at each step. When a data point needs to change now, it changes in one place and propagates correctly across every page that references it. No template surgery, no risk of partial updates, no fragmented output.</p>
<p>That separation is the architecture that should have existed from day one. Building it correctly after the fact is more expensive than building it correctly first, but it meant every subsequent improvement to WireRef like new wire gauges, updated state code profiles, new page types, could be added without touching the display layer at all.</p>
<p>WireRef also launched with build failures that had nothing to do with data accuracy: 17 orphan pages, broken navigation, no sitemap, no robots.txt. Those went into the preflight checklist. They don't ship anymore because the checklist won't let them.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-failures-that-had-nothing-to-do-with-ai"><span class="sec-n" aria-hidden="true">06</span>The failures that had nothing to do with AI</h2>
<p>Three of the items on the ranked list above are <strong>build and launch failures, and they're worth separating because the cause is different and so is the fix.</strong></p>
<p><strong>Search features shipped broken. Twice.</strong> On-site search is the first thing a user reaches for when they can't find something from navigation. On two separate launches I shipped it in a broken state, caught it after the fact, and fixed it reactively. The failure is that I treated feature verification as something to do after launch rather than before. Search is now a required checklist item that gets confirmed working on staging before anything goes live. Not because it's hard to check, but because I've now proven I won't check it unless it's required.</p>
<p><strong>Mobile usability wasn't verified before launch.</strong> Desktop looked fine. I assumed that was enough. On reference sites where a significant portion of the audience is on a job site or in a field environment pulling up a spec from their phone, that assumption is wrong in a way that matters. A welder checking electrode amperage mid-job isn't at a desk. An electrician looking up ampacity at a panel isn't either. The use case is mobile-first, whether the builder thought about it or not. Every new template and every new interactive feature now gets verified on mobile before it ships. It's a use case requirement I should have internalized from the first build.</p>
<p><strong>Data was hardcoded into templates.</strong> This one compounded every other mistake. When a data error surfaced like fabricated values, wrong specs, incomplete reference, etc., fixing it meant touching the templates themselves, not just the data. The presentation logic and the data it was rendering lived in the same place, which meant a correction to one value carried the risk of breaking how every related value displayed. At scale, that's a trap. The correct architecture is a clean separation: data lives in JSON files or structured sources that can be corrected, extended, and updated independently, and templates read from those sources without carrying values themselves. When that separation exists, a data fix is one change in one file that propagates correctly everywhere. When it doesn't, a data fix is a surgical operation on a template that was never designed to be edited that way. Every build now starts with that separation defined before any page generation begins. It's the starting constraint.</p>
<p>The common thread across all three: I was optimizing for getting something live. These are the mistakes that happen when launch is the goal instead of a milestone.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-every-failure-had-in-common"><span class="sec-n" aria-hidden="true">07</span>What every failure had in common</h2>
<p>The failures above are different technical problems with the same underlying cause. <strong>AI produces output that looks correct at the surface level, and surface-level inspection passes it.</strong> Catching what's wrong requires knowing what the authoritative version looks like. Not in water chemistry or welding metallurgy per se, but in how search systems evaluate trustworthiness for that type of content.</p>
<p>That's the job: <strong>defining what makes content credible in a given space before any page is built, then holding the output to that standard.</strong></p>
<p>The sites exist because AI made the execution faster. They're accurate because that standard came first. <strong>And they'll keep compounding because every failure now becomes a constraint that ships with the next build.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="case-studies-for-each-site"><span class="sec-n" aria-hidden="true">08</span>Case studies for each site</h2>
<p>The full architecture, data sourcing decisions, and build approach for each project are documented.</p>
<ul>
<li><a href="https://haydenschuster.com/portfolio/checkmytap/">CheckMyTap</a>: 1,000+ city pages built from EPA, EWG, and UCMR5 data. Programmatic architecture, YMYL sourcing standards, 4-layer content structure.</li>
<li><a href="https://haydenschuster.com/portfolio/wireref/">WireRef</a>: NEC electrical reference with 6 page types, 50-state code coverage, and a data architecture rebuilt around the full derating chain.</li>
<li><a href="https://haydenschuster.com/portfolio/gageref/">GageRef</a>: Welding electrode specs and hydraulic fitting data sourced directly from AWS A5.1, A5.18, and SAE J514. Primary source attribution on every value.</li>
</ul>
<p>Cheers to the next expensive lesson learned!</p>
]]></content:encoded>
  </item>
  <item>
    <title>SEO strategy vs SEO systems: why strategy fails without structure</title>
    <link>https://haydenschuster.com/writing/seo-strategy-vs-seo-systems/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/seo-strategy-vs-seo-systems/</guid>
    <pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate>
    <description>The difference between SEO strategy and SEO systems, side by side, and why a site&#39;s growth stalls when the plan has no structure under it.</description>
    <content:encoded><![CDATA[<p>Most SEO problems are not caused by content or keywords alone. They happen when strategy exists without structure to support it.</p>
<p>After working on complex websites, I see the same structural patterns appear:</p>
<ul>
<li>No consideration for how people actually search</li>
<li>No consideration for how modern search interprets intent</li>
<li>Structure built around selling instead of solving problems</li>
<li>No clear path from learning to decision</li>
<li>Architecture that works early but breaks as the site grows</li>
</ul>
<p>These are rarely content problems. They are usually signs that strategy exists, but the underlying system does not.</p>
<p>In SEO terms, strategy is the design. Systems are the foundation. If the structure is weak, better content and better design only hide the problem temporarily. This is the same idea that shaped how I rebuilt my own site in <a href="https://haydenschuster.com/writing/building-a-search-system/">Building a search system: how I structured my new site</a>.</p>
<h2 id="the-difference-in-two-sentences"><span class="sec-n" aria-hidden="true">01</span>The difference in two sentences</h2>
<p>SEO strategy defines direction. SEO systems make that direction repeatable.</p>
<p>Strategy decides what you want to build. Systems determine whether it holds together as the site grows.</p>
<p><strong>If strategy is the blueprint, systems are the concrete.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-is-seo-strategy"><span class="sec-n" aria-hidden="true">02</span>What is SEO strategy?</h2>
<p>SEO strategy is planning and prioritization.</p>
<h3>What SEO strategy answers</h3>
<ul>
<li>What topics matter most?</li>
<li>Who are we trying to reach?</li>
<li>What should we build first?</li>
<li>What does success look like?</li>
</ul>
<h3>How strategy connects to search intent</h3>
<p>Strategy depends on understanding how people search and how needs change across a journey. For deeper context, see <a href="https://haydenschuster.com/writing/search-behavior/">Search Behavior and Intent</a> and <a href="https://haydenschuster.com/writing/search-intent/">4 Types of Search Intent</a>.</p>
<h3>Where SEO strategy runs out</h3>
<p>Strategy depends on consistent execution. As a site expands, decisions multiply. Without structure, the original plan slowly breaks down.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-are-seo-systems"><span class="sec-n" aria-hidden="true">03</span>What are SEO systems?</h2>
<p>SEO systems are structure and consistency.</p>
<h3>What SEO systems determine</h3>
<ul>
<li>How pages are organized</li>
<li>How new content fits into the site</li>
<li>How pages connect to each other</li>
<li>How decisions repeat over time</li>
<li>How growth happens without breaking architecture</li>
</ul>
<h3>SEO systems in practice</h3>
<p>This is the foundation behind my SEO Systems portfolio work, including <a href="https://haydenschuster.com/portfolio/technical/">Technical Foundations and Site Systems</a> and <a href="https://haydenschuster.com/portfolio/content/">Content Strategy and Architecture</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="seo-strategy-and-seo-systems-side-by-side"><span class="sec-n" aria-hidden="true">04</span>SEO strategy and SEO systems side by side</h2>
<div class="post-table"><table>
<thead>
<tr>
<th>SEO strategy</th>
<th>SEO systems</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="SEO strategy">Defines direction</td>
<td data-label="SEO systems">Creates consistency</td>
</tr>
<tr>
<td data-label="SEO strategy">Sets priorities</td>
<td data-label="SEO systems">Makes execution repeatable</td>
</tr>
<tr>
<td data-label="SEO strategy">Usually created at the beginning</td>
<td data-label="SEO systems">Exists for the life of the site</td>
</tr>
<tr>
<td data-label="SEO strategy">Changes as goals change</td>
<td data-label="SEO systems">Improves as the site grows</td>
</tr>
<tr>
<td data-label="SEO strategy">Relies on people following the plan</td>
<td data-label="SEO systems">Relies on structure rather than memory</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-this-distinction-matters"><span class="sec-n" aria-hidden="true">05</span>Why this distinction matters</h2>
<p>Many websites see early growth and then slow down. The foundation was incomplete.</p>
<p>As more pages are added, inconsistency increases. Internal linking drifts. Page types blur together. Architecture becomes harder to maintain. Systems reduce that entropy. They make growth stable instead of fragile.</p>
<h3>Systems scale with complexity</h3>
<p>This becomes especially visible in larger environments, which is why system design becomes central in <a href="https://haydenschuster.com/portfolio/enterprise/">Enterprise SEO</a> and in the <a href="https://haydenschuster.com/writing/enterprise-seo/">Enterprise SEO blog section</a>.</p>
<h3>Measurement as part of your system</h3>
<p>Visibility trends help reveal whether structure is working, which is the idea behind using Search Console as a visibility framework in <a href="https://haydenschuster.com/writing/search-console-visibility-dashboard/">How to Use Google Search Console as an SEO Visibility Dashboard</a>.</p>
<p>For larger launches or migrations, this thinking becomes repeatable process design, covered in <a href="https://haydenschuster.com/writing/enterprise-launch-seo-systems/">Building Repeatable SEO Systems for Enterprise Website Launches</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-decides-whether-progress-continues"><span class="sec-n" aria-hidden="true">06</span>What decides whether progress continues</h2>
<p>Most SEO advice focuses on one-time improvements. Sustainable growth comes from structures that continue producing clarity over time.</p>
<p>Strategy determines direction. Systems determine whether progress continues when complexity increases.</p>
<p>Structure shapes visibility before design does. Pour the concrete first.</p>
]]></content:encoded>
  </item>
  <item>
    <title>The real goal of technical SEO: clarity for crawlers and humans</title>
    <link>https://haydenschuster.com/writing/technical-seo-clarity/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/technical-seo-clarity/</guid>
    <pubDate>Tue, 10 Feb 2026 00:00:00 GMT</pubDate>
    <description>Technical SEO is more than a checklist of scores. Its job is clarity: what a page is about, how it relates, and why it exists.</description>
    <content:encoded><![CDATA[<p>Both search engines and people struggle with ambiguity. When a website's structure, layout, and internal relationships are unclear, crawlers and users are forced to guess. Over time that uncertainty shows up as indexing problems, ranking instability, and poor user experience.</p>
<h2 id="what-technical-seo-is-for"><span class="sec-n" aria-hidden="true">01</span>What technical SEO is for</h2>
<h3>The three questions technical SEO answers</h3>
<p>Page speed, mobile friendliness, and clean code are important, but they are just one piece of the puzzle. Technical SEO exists to answer three fundamental questions clearly:</p>
<ul>
<li>What is this page about?</li>
<li>How does it relate to other pages?</li>
<li>Why does it exist within the site?</li>
</ul>
<p>If a search engine or user cannot answer these questions quickly, your site has a clarity problem, not just a technical one.</p>
<h3>What clarity looks like on a site</h3>
<p>Clarity in technical SEO shows up through clear hierarchy, predictable URLs, consistent internal linking, logical page templates, and a single unambiguous intent per page. <strong>When these elements align, crawling becomes efficient, indexing becomes accurate, and users feel oriented instead of lost.</strong> This connects directly to how people actually move through decisions online, which is explored further in <a href="https://haydenschuster.com/writing/search-intent/">search intent</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-crawlers-experience-your-website"><span class="sec-n" aria-hidden="true">02</span>How crawlers experience your website</h2>
<h3>Crawlers don't &quot;see&quot; design</h3>
<p>Search engine crawlers interpret your site through:</p>
<ul>
<li>HTML structure</li>
<li>Links and relationships</li>
<li>Status codes</li>
<li>Canonical signals</li>
<li>Metadata and headings</li>
</ul>
<p>If multiple signals conflict, crawlers slow down, re-evaluate, or ignore pages altogether.</p>
<h3>Ambiguity creates crawl waste</h3>
<p><strong>Confusion usually comes from structural issues rather than technical errors.</strong></p>
<p>Multiple URLs serving similar content, inconsistent internal linking, orphaned pages, conflicting indexing signals, or overly complex navigation all increase crawl effort and reduce confidence in the site's structure. These issues become more visible as sites scale.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-people-experience-the-same-problems"><span class="sec-n" aria-hidden="true">03</span>How people experience the same problems</h2>
<h3>Users feel structural confusion immediately</h3>
<p>While crawlers struggle quietly, users react instantly. Signs of poor clarity include:</p>
<ul>
<li>High bounce rates</li>
<li>Short session duration</li>
<li>Low conversion rates</li>
<li>Repeated backtracking</li>
</ul>
<p>If users cannot understand where they are or where to go next, the structure has failed, regardless of how fast the page loads.</p>
<h3>Good technical SEO feels invisible</h3>
<p><strong>The best technical SEO goes unnoticed because everything feels natural.</strong> Navigation flows logically, URLs make sense, and pages answer questions without friction.</p>
<p>That experience comes from deliberate structure.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="reducing-ambiguity-through-site-structure"><span class="sec-n" aria-hidden="true">04</span>Reducing ambiguity through site structure</h2>
<h3>Clear hierarchies beat flat chaos</h3>
<p>A strong structure answers:</p>
<ul>
<li>Which pages are primary?</li>
<li>Which pages support them?</li>
<li>How deep should users and crawlers go?</li>
</ul>
<p>Best practices include:</p>
<ul>
<li>Logical category to subcategory to page paths</li>
<li>Limiting unnecessary depth</li>
<li>Avoiding multiple paths to the same content</li>
</ul>
<h3>URL structure as a clarity signal</h3>
<p><strong>URLs should describe relationships rather than simply contain keywords.</strong> Consistent, hierarchical URLs reinforce meaning and reduce interpretation errors. When structure and content align, both users and search engines understand context more easily.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-internal-links-tell-crawlers"><span class="sec-n" aria-hidden="true">05</span>What internal links tell crawlers</h2>
<h3>Links explain how pages relate</h3>
<p>Internal links tell crawlers:</p>
<ul>
<li>Which pages matter most</li>
<li>How topics connect</li>
<li>Where authority should flow</li>
</ul>
<p>Random or excessive linking creates noise. Intentional linking creates understanding.</p>
<h3>Anchor text as a clarity tool</h3>
<p>Descriptive anchor text reinforces topical relevance. Generic anchors remove context and make relationships harder to interpret. This becomes especially important when aligning pages to intent transitions, as explained in the breakdown of the <a href="https://haydenschuster.com/writing/search-intent/">four types of search intent</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="templates-layouts-and-predictability"><span class="sec-n" aria-hidden="true">06</span>Templates, layouts, and predictability</h2>
<h3>Consistency reduces cognitive load</h3>
<p>Consistent layouts help both crawlers and users predict:</p>
<ul>
<li>Where main content lives</li>
<li>Where supporting information appears</li>
<li>What type of page they are viewing</li>
</ul>
<p>When templates vary without reason, interpretation becomes harder.</p>
<h3>One page, one primary purpose</h3>
<p><strong>Each page should serve one dominant intent.</strong> Mixing informational, commercial, and transactional goals introduces ambiguity for indexing and for users. This matters even more in modern search environments where summaries and AI previews resolve early questions before visits occur.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-technical-signals-have-to-agree"><span class="sec-n" aria-hidden="true">07</span>Why technical signals have to agree</h2>
<p>Key signals must reinforce each other:</p>
<ul>
<li>Title tags</li>
<li>Headings</li>
<li>Internal links</li>
<li>Canonicals</li>
<li>Structured data</li>
</ul>
<p><strong>When signals conflict, search engines hesitate. When they align, confidence increases.</strong> Measurement also becomes clearer because performance reflects intent rather than structural noise.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-clarity-leads-to-long-term-stability"><span class="sec-n" aria-hidden="true">08</span>Why clarity leads to long-term stability</h2>
<h3>Clear sites adapt when algorithms change</h3>
<p>Ranking systems evolve constantly, but clarity remains stable. Sites that clearly explain themselves adapt more easily because crawling is efficient, indexing is accurate, and intent matching stays strong.</p>
<h3>Clarity builds trust</h3>
<p>Search engines reward sites they understand. Over time, clear architecture reduces volatility and improves resilience during updates.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-technical-seo-mistakes-that-reduce-clarity"><span class="sec-n" aria-hidden="true">09</span>Common technical SEO mistakes that reduce clarity</h2>
<ul>
<li>Overusing noindex and canonicals</li>
<li>Creating duplicate content unintentionally</li>
<li>Inconsistent navigation across sections</li>
<li>Ignoring orphaned pages</li>
<li>Chasing tools instead of understanding structure</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-evaluate-your-site-s-clarity"><span class="sec-n" aria-hidden="true">10</span>How to evaluate your site's clarity</h2>
<p>Ask these questions:</p>
<ul>
<li>Can I explain the site structure in one sentence?</li>
<li>Does every page have a clear role?</li>
<li>Are similar pages grouped logically?</li>
<li>Would a new visitor understand where to go next?</li>
</ul>
<p>If the answer is &quot;no,&quot; <strong>clarity is the real issue.</strong> Fix fix fix!</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-technical-seo-comes-down-to"><span class="sec-n" aria-hidden="true">11</span>What technical SEO comes down to</h2>
<p>Technical SEO is about <strong>communication</strong>. Your site must clearly explain itself to machines and humans alike.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-technical-seo"><span class="sec-n" aria-hidden="true">12</span>Questions people ask about technical SEO</h2>
<h3>Is technical SEO only for large websites?</h3>
<p>No. Smaller sites benefit even more from clarity because every page carries more weight.</p>
<h3>Can too many technical optimizations hurt SEO?</h3>
<p>Yes. Over-optimization often introduces conflicting signals and confusion.</p>
<h3>Is internal linking more important than backlinks?</h3>
<p>They serve different roles. Internal linking defines meaning; backlinks reinforce authority.</p>
<h3>How often should site structure be reviewed?</h3>
<p>Anytime content scales, changes intent, or expands into new topics.</p>
]]></content:encoded>
  </item>
  <item>
    <title>What is commercial search intent?</title>
    <link>https://haydenschuster.com/writing/commercial-search-intent/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/commercial-search-intent/</guid>
    <pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate>
    <description>Commercial search intent means the user is comparing options before buying. Query patterns, what a fair comparison page needs, and signs it&#39;s broken.</description>
    <content:encoded><![CDATA[<p>If your product pages rank well but do not convert, or your &quot;best of&quot; guides get traffic but no click-throughs, you likely have a commercial intent structure problem. Users want evaluation frameworks, not just feature lists or single-option pitches.</p>
<aside class="post-aside" aria-label="Quick diagnostic">
<p class="post-aside-label">Quick diagnostic</p>
<p>Check your traffic for queries containing &quot;best&quot;, &quot;top&quot;, &quot;vs&quot;, &quot;comparison&quot;, or &quot;review&quot;. If these pages have high engagement but low conversion or click-through to product pages, your comparison structure is broken. The signals to watch are under <a href="#how-to-diagnose-commercial-page-problems">how to diagnose commercial page problems</a>.</p>
</aside>
<p><em>A note on the numbers: the counts, times and thresholds in this post are my working rules of thumb from building these pages, not published standards. Start from them, then check them against your own data.</em></p>
<h2 id="the-queries-that-signal-commercial-intent"><span class="sec-n" aria-hidden="true">01</span>The queries that signal commercial intent</h2>
<p>The searcher is not just learning (that is informational intent) and not ready to buy immediately (that is transactional). They are evaluating.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Pattern</th>
<th>Example queries</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Pattern">Comparison keywords</td>
<td data-label="Example queries">best CRM for small business, Slack vs Microsoft Teams, top email marketing tools</td>
</tr>
<tr>
<td data-label="Pattern">Review or recommendation</td>
<td data-label="Example queries">running shoes for plantar fasciitis, which project management software, most reliable SUVs 2026</td>
</tr>
<tr>
<td data-label="Pattern">Alternative or competitor</td>
<td data-label="Example queries">alternatives to Salesforce, cheaper than Adobe Creative Cloud, open source CRM options</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-the-searcher-is-doing"><span class="sec-n" aria-hidden="true">02</span>What the searcher is doing</h2>
<p>The user is:</p>
<ul>
<li>Past the learning phase</li>
<li>Building a mental decision framework</li>
<li>Comparing 3 to 7 options actively</li>
<li>Looking for validation and reassurance</li>
<li>Trying to avoid buyer's remorse</li>
<li>Close to making a purchase (days, not months)</li>
</ul>
<p><strong>They need structure, not persuasion.</strong> Help them compare and they will convert.</p>
<h3>Why commercial pages fail</h3>
<p>Most commercial pages fail because they push a single option instead of helping users evaluate fairly. <strong>Users in commercial intent do not trust biased recommendations.</strong> If your &quot;best CRM&quot; article only mentions your product, users bounce. If your comparison page is obviously slanted, credibility drops. Commercial intent requires honest evaluation frameworks with real pros and cons for each option.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-a-good-commercial-page-looks-like"><span class="sec-n" aria-hidden="true">03</span>What a good commercial page looks like</h2>
<p>Evaluation criteria explained upfront. Multiple options presented fairly. Each option has clear pros, cons, pricing, and &quot;best for&quot; scenario. CTAs for each option (not forcing a single choice). Decision framework at the end helps users match their needs to the right tool.</p>
<p><strong>Action step:</strong> Pull up your top comparison or &quot;best of&quot; page. Count how many options you present and whether each has honest pros and cons. If you only show 1 or 2 options or all pros are positive, you are not serving commercial intent. The full checklist is in <a href="#how-to-structure-commercial-pages">how to structure commercial pages</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-structure-commercial-pages"><span class="sec-n" aria-hidden="true">04</span>How to structure commercial pages</h2>
<p>Skip these and users cannot make confident decisions.</p>
<h3>Must have</h3>
<ul>
<li>Clear comparison criteria explained upfront</li>
<li>5 to 7 options presented (not just 1 or 2)</li>
<li>Honest pros AND cons for each option</li>
<li>Pricing information visible (not hidden)</li>
<li>&quot;Best for&quot; scenarios for each option</li>
<li>Comparison table or matrix for side-by-side view</li>
<li>Decision framework or &quot;how to choose&quot; section</li>
<li>CTA for each option (not forcing one choice)</li>
<li>Last updated date for credibility</li>
<li>Methodology or selection process explained</li>
</ul>
<h3>Never include</h3>
<ul>
<li>Only your own product or 1 or 2 options</li>
<li>Fake cons that are actually neutral or positive</li>
<li>Affiliate disclosure buried or hidden</li>
<li>Pushing one option as &quot;the only choice&quot;</li>
<li>Comparison criteria that only your product wins</li>
<li>Outdated pricing or feature information</li>
<li>Missing key competitors users are evaluating</li>
<li>Generic &quot;all options are good&quot; conclusions</li>
<li>Ranking without explaining methodology</li>
<li>Feature lists without context or use cases</li>
</ul>
<aside class="post-aside" aria-label="The trust factor">
<p class="post-aside-label">The trust factor</p>
<p>Commercial intent users are skeptical. They have been burned by biased reviews and fake comparisons. <strong>Building trust at this stage requires transparency about methodology, honest trade-offs, and multiple viable paths forward.</strong> Pages that acknowledge limitations and help users find the right fit (even if it is not your product) earn long-term authority and convert better over time. This is core to effective <a href="https://haydenschuster.com/writing/content-strategy/">content strategy</a> for commercial queries.</p>
</aside>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-commercial-page-types"><span class="sec-n" aria-hidden="true">05</span>Common commercial page types</h2>
<p>Different commercial queries require different comparison structures. Here are the most common formats and what they should prioritize.</p>
<h3>&quot;Best of&quot; roundups</h3>
<p>5 to 7 options ranked or categorized. Each with pros, cons, pricing, best-for scenarios. Comparison table required. Decision framework at end. Updated quarterly minimum.</p>
<h3>Head-to-head comparisons</h3>
<p>Two specific options compared directly. Side-by-side feature comparison. Clear winner for different use cases (not one universal winner). Use when users have already narrowed it to 2 choices.</p>
<h3>Review pages</h3>
<p>Deep dive on single option. Honest assessment of strengths and weaknesses. Who it is best for (and who should avoid). Alternatives mentioned for users it does not fit.</p>
<h3>Alternative pages</h3>
<p>&quot;Alternatives to [Product]&quot; format. Why users look for alternatives. 5 to 7 options with how they differ from original. Price and feature comparison to original product.</p>
<h3>Comparison matrices</h3>
<p>Table-first format. 10 to 20 options compared across key criteria. Filters for narrowing by need. Best for users evaluating many options (e.g., email marketing platforms).</p>
<h3>Pricing comparisons</h3>
<p>Focus on cost analysis. Total cost of ownership, not just list price. Feature-to-price value assessment. When cheaper options are better value vs when premium is worth it.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-diagnose-commercial-page-problems"><span class="sec-n" aria-hidden="true">06</span>How to diagnose commercial page problems</h2>
<p>Your analytics will show specific patterns when commercial pages fail to serve evaluation needs properly.</p>
<h3>High engagement, no click-through</h3>
<p>Users read entire comparison but do not click any CTAs. You likely presented options but did not help them decide. Missing decision framework or &quot;best for&quot; scenarios.</p>
<h3>Traffic but no conversions</h3>
<p>Page ranks well for commercial queries but does not drive conversions. Comparison structure exists but recommendations are not credible or options are outdated.</p>
<h3>Users leave to search competitors</h3>
<p>Exit patterns show users returning to search for specific competitors. You missed key options they are evaluating. Expand comparison to include all major alternatives.</p>
<h3>Low trust signals</h3>
<p>Users comment asking if review is biased or sponsored. Affiliate disclosure is hidden, methodology is unclear, or all options are praised equally. Transparency problem.</p>
<h3>Comparison queries not ranking</h3>
<p>Your product pages rank but comparison pages do not. Google recognizes you are not serving commercial intent properly. Need true comparison structure, not disguised product pages.</p>
<h3>Short time on page despite length</h3>
<p>Page is 2,000+ words but average time is under 60 seconds. Users scan for comparison table or decision framework and do not find it. Structure problem, not content problem.</p>
<aside class="post-aside" aria-label="The fix">
<p class="post-aside-label">The fix</p>
<p>Add or improve your comparison framework. Present 5 to 7 legitimate options with honest pros and cons. Include decision criteria upfront and &quot;how to choose&quot; section at the end. Test by asking: Would I trust this comparison if I did not know who wrote it?</p>
<p>Users who trust your comparison framework return for future buying decisions, building long-term authority.</p>
</aside>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-commercial-intent-differs-from-other-intent-types"><span class="sec-n" aria-hidden="true">07</span>How commercial intent differs from other intent types</h2>
<p>Understanding where commercial intent fits in the <a href="https://haydenschuster.com/writing/search-behavior/">search behavior journey</a> helps you structure pages for each stage.</p>
<div class="post-table"><table>
<thead>
<tr>
<th></th>
<th>Commercial</th>
<th>The other intent</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="">Commercial vs informational</td>
<td data-label="Commercial">User wants to compare CRM options. Query: &quot;best CRM for small business&quot;</td>
<td data-label="The other intent">User wants to learn what CRM is. Query: &quot;what is CRM software&quot;</td>
</tr>
<tr>
<td data-label="">Commercial vs transactional</td>
<td data-label="Commercial">User comparing options. Query: &quot;Salesforce vs HubSpot CRM&quot;</td>
<td data-label="The other intent">User ready to buy. Query: &quot;HubSpot CRM pricing plans&quot;</td>
</tr>
</tbody>
</table></div>
<p>Commercial assumes understanding already exists. <a href="https://haydenschuster.com/writing/informational-vs-transactional-pages/">Informational pages teach fundamentals</a>. Commercial pages assume knowledge and provide evaluation frameworks.</p>
<p>Commercial users need comparison to decide. <a href="https://haydenschuster.com/writing/transactional-pages-fail/">Transactional users need clear path to purchase</a>. Commercial pages present options. Transactional pages drive action on one option.</p>
<aside class="post-aside" aria-label="Commercial intent and content-driven businesses">
<p class="post-aside-label">Commercial intent is the highest-value traffic for content-driven businesses</p>
<p>Users in commercial intent are actively making buying decisions. They are also more likely to return for future comparisons if you build trust. This is why investment in high-quality comparison content yields better ROI than just informational content. Strong commercial intent pages become long-term traffic and revenue drivers.</p>
</aside>
]]></content:encoded>
  </item>
  <item>
    <title>Informational vs transactional pages</title>
    <link>https://haydenschuster.com/writing/informational-vs-transactional-pages/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/informational-vs-transactional-pages/</guid>
    <pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate>
    <description>Informational vs transactional pages side by side: example queries, the structural differences, page outlines for three industries, and build checklists.</description>
    <content:encoded><![CDATA[<p>This is a core principle of <a href="https://haydenschuster.com/writing/content-strategy/">content strategy</a>.</p>
<aside class="post-aside" aria-label="Why this matters">
<p class="post-aside-label">Why this matters</p>
<p>When you mismatch page type to intent, you create friction. Informational users bounce from sales pages. Transactional users abandon education content. Google sees the poor engagement and stops sending traffic.</p>
</aside>
<p><em>A note on the numbers: the counts, times and thresholds in this post are my working rules of thumb from building these pages, not published standards. Start from them, then check them against your own data.</em></p>
<h2 id="what-each-searcher-wants-with-example-queries"><span class="sec-n" aria-hidden="true">01</span>What each searcher wants, with example queries</h2>
<p>The same industry produces both kinds of search. The query tells you which page to build.</p>
<div class="post-table"><table>
<thead>
<tr>
<th></th>
<th>Informational: learn</th>
<th>Transactional: act</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="">The user wants</td>
<td data-label="Informational: learn">Understanding</td>
<td data-label="Transactional: act">To complete a task. They are ready to act</td>
</tr>
<tr>
<td data-label="">Your job</td>
<td data-label="Informational: learn">Educate comprehensively and earn trust so they return when ready to decide</td>
<td data-label="Transactional: act">Reduce friction and provide clear next steps</td>
</tr>
<tr>
<td data-label="">Auto industry</td>
<td data-label="Informational: learn">what is all wheel drive; best SUVs for families</td>
<td data-label="Transactional: act">2024 Honda CR-V price; schedule test drive</td>
</tr>
<tr>
<td data-label="">Heavy equipment</td>
<td data-label="Informational: learn">excavator bucket types explained; compact vs mini excavators</td>
<td data-label="Transactional: act">rent excavator near me; Cat 320 price quote</td>
</tr>
<tr>
<td data-label="">SEO</td>
<td data-label="Informational: learn">what is technical SEO; SEO vs SEM differences</td>
<td data-label="Transactional: act">hire SEO consultant; content strategy packages</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-modern-search-changed-these-page-types"><span class="sec-n" aria-hidden="true">02</span>How modern search changed these page types</h2>
<p><a href="https://haydenschuster.com/writing/why-ai-overviews-appear/">AI Overviews</a> and answer-first search have fundamentally changed what informational and transactional pages need to accomplish.</p>
<h3>Informational pages now compete with instant answers</h3>
<p>Search results increasingly answer basic questions directly inside the SERP. AI Overviews, featured snippets, and knowledge panels resolve early understanding before a click happens.</p>
<p>The role of informational content has shifted. Instead of being the first answer, <a href="https://haydenschuster.com/writing/answer-first-content/">effective content now becomes the next step</a>. Your page must help users move from understanding to application or decision.</p>
<h3>Transactional pages must confirm, not convince</h3>
<p>Modern search surfaces product details, pricing, and availability before users click. <a href="https://haydenschuster.com/writing/transactional-pages-fail/">Transactional pages fail when they assume users need convincing</a> instead of reassurance.</p>
<p>The page should answer: Is this the right option for my situation? Can I trust this business? What happens after I act?</p>
<h3>Intent transitions matter more than ever</h3>
<p>Modern search systems track how users move between informational and transactional queries. <a href="https://haydenschuster.com/writing/intent-transitions/">Misaligned intent transitions kill your content's path to decision</a>. Your site architecture must support natural intent progression.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-core-structural-differences"><span class="sec-n" aria-hidden="true">03</span>The core structural differences</h2>
<p>Get the structure wrong and your content will not perform regardless of how good the writing is.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Element</th>
<th>Informational page</th>
<th>Transactional page</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Element">Primary goal</td>
<td data-label="Informational page">Answer questions completely</td>
<td data-label="Transactional page">Drive decision and capture intent</td>
</tr>
<tr>
<td data-label="Element">Content depth</td>
<td data-label="Informational page">Comprehensive, multi-angle</td>
<td data-label="Transactional page">Focused, decision-oriented</td>
</tr>
<tr>
<td data-label="Element">CTA placement</td>
<td data-label="Informational page">Minimal, low-pressure, bottom of page</td>
<td data-label="Transactional page">Prominent, repeated, above fold</td>
</tr>
<tr>
<td data-label="Element">CTA language</td>
<td data-label="Informational page">Learn more, explore, read the guide</td>
<td data-label="Transactional page">Get started, buy now, sign up free</td>
</tr>
<tr>
<td data-label="Element">Navigation</td>
<td data-label="Informational page">Link to related learning content</td>
<td data-label="Transactional page">Link to product pages and pricing</td>
</tr>
<tr>
<td data-label="Element">Proof elements</td>
<td data-label="Informational page">Citations, studies, expert quotes</td>
<td data-label="Transactional page">Customer logos, testimonials, guarantees</td>
</tr>
<tr>
<td data-label="Element">Visuals</td>
<td data-label="Informational page">Explanatory diagrams and screenshots</td>
<td data-label="Transactional page">Product shots and social proof</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-each-page-looks-like-side-by-side"><span class="sec-n" aria-hidden="true">04</span>What each page looks like, side by side</h2>
<p>Same topic. Different intent. Completely different page architecture. These outlines show what each page type looks like in practice.</p>
<h3>Auto industry: family SUV landing pages</h3>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Informational:</strong> Best SUVs for Families in 2024</p>
<p>Everything you need to know about choosing a family SUV: safety, space, features, and real-world costs.</p>
<ol>
<li>Table of contents: what makes an SUV family-friendly, safety ratings that actually matter, top 8 family SUVs compared, how to decide: new vs used</li>
<li>What makes an SUV family-friendly (400 words): cargo space, third-row seating, safety tech, ease of access, fuel economy expectations</li>
<li>Top 8 family SUVs compared (1,200 words): pros, cons, best-for scenarios for each</li>
<li>How to decide (300 words): budget framework, new vs used considerations, when to lease vs buy</li>
<li>Soft CTA at the bottom of the page: &quot;Ready to shop? Browse our family SUV inventory&quot;</li>
</ol>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Transactional:</strong> 2024 Honda Pilot</p>
<ol>
<li>Hero with &quot;See Inventory &amp; Pricing&quot;</li>
<li>Key features (200 words)</li>
<li>Available trims and pricing</li>
<li>Social proof</li>
<li>Comparison: Pilot vs Highlander, as a quick table</li>
<li>&quot;See available Pilots near you&quot; with &quot;Schedule Test Drive&quot; and &quot;Check Availability&quot;</li>
</ol>
</div>
</div>
<aside class="post-aside" aria-label="Notice the structural difference">
<p class="post-aside-label">Notice the structural difference</p>
<p>The informational page is organized around user questions and education. No CTAs until the bottom. Comprehensive, multi-angle coverage. The transactional page leads with value prop and pricing. Multiple CTAs. Assumes understanding already exists. One teaches. The other confirms and converts.</p>
</aside>
<h3>Heavy equipment: excavator landing pages</h3>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Informational:</strong> Compact vs Mini Excavators: Complete Guide</p>
<p>Learn the real differences, when each type makes sense, and how to choose for your project.</p>
<ol>
<li>Introduction (150 words): define compact and mini excavators; explain when this distinction matters for contractors and project managers</li>
<li>Size and spec comparison (400 words): operating weight ranges, dig depth capabilities, reach specifications, transport requirements, a visual diagram comparing sizes</li>
<li>Best use cases (600 words): mini for residential landscaping, tight urban sites, utility work; compact for commercial excavation, foundation work, larger trenching; real project examples for each</li>
<li>Cost and ownership (400 words): purchase price ranges, rental costs by market, maintenance expectations, fuel efficiency, resale value trends</li>
<li>Decision framework (250 words): how to choose based on project type, frequency of use, operator skill, site constraints</li>
<li>Soft CTA: &quot;Need equipment for your next project? Browse our excavator rental fleet&quot;</li>
</ol>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Transactional:</strong> Compact Excavator Rentals</p>
<p>Daily, weekly, monthly rates. Certified equipment.</p>
<ol>
<li>Hero with &quot;Check Availability&quot;</li>
<li>Equipment specs: operating weight, dig depth, reach, bucket sizes included</li>
<li>Rental pricing: daily, weekly, monthly, delivery</li>
<li>What's included: full fuel tank, 3 bucket sizes, operator manual, 24/7 support line, certified maintenance records</li>
<li>Trust signals</li>
<li>&quot;Reserve your excavator&quot; with &quot;Get Quote&quot; and a phone number</li>
</ol>
</div>
</div>
<h3>SEO services: content strategy landing pages</h3>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Informational:</strong> What Is SEO Content Strategy</p>
<p>How to build content that earns rankings, drives traffic, and supports actual business decisions.</p>
<ol>
<li>Introduction (120 words): define content strategy in SEO context; why it matters beyond keywords; what changes when strategy is missing</li>
<li>Core components (600 words): intent mapping (matching content to search behavior), topical authority (building depth over breadth), internal linking (connecting pages logically), content architecture (organizing for users and systems)</li>
<li>When you need it (300 words): high traffic, low conversions; inconsistent rankings; content cannibalization; scaling challenges; post-algorithm drops</li>
<li>Implementation process (400 words): audit existing content for gaps and overlaps; map user journeys from learning to decision; build pillar-cluster structure; create measurement framework; iterate based on performance</li>
<li>Related resources: how to structure content for modern search, intent alignment framework, internal linking strategy guide</li>
</ol>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Transactional:</strong> Content Strategy Services</p>
<p>Build content that ranks and converts. Focused on intent alignment, topical authority, and measurable results.</p>
<ol>
<li>Hero with &quot;Request Audit&quot;</li>
<li>What you get: complete content audit and gap analysis, intent mapping for your target queries, pillar page strategy and implementation plan, internal linking architecture, performance tracking framework</li>
<li>Who this is for: sites with traffic but no conversions, content teams scaling without systems, post-algorithm traffic recovery, enterprise content migrations, competitive visibility gaps</li>
<li>Client results</li>
<li>Approach: not one-size-fits-all templates; custom strategy based on your users, business model, competitive landscape, and existing content assets</li>
<li>&quot;Start with a content audit&quot; with &quot;Get Started&quot; and &quot;See Case Studies&quot;</li>
</ol>
</div>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="bad-and-good-versions-of-each-page"><span class="sec-n" aria-hidden="true">05</span>Bad and good versions of each page</h2>
<p>Most broken pages fail because they apply transactional tactics to informational queries or bury conversion elements on transactional pages. Here is what that looks like in practice.</p>
<h3>An informational page, done badly and done well</h3>
<p>Query: how does hydraulic excavator work</p>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Broken:</strong> tries to sell before answering the question</p>
<p>Heavy sales language. Equipment pitch in first paragraph. Multiple CTAs before any real education.</p>
<ol>
<li>H1: Rent Professional Hydraulic Excavators Today</li>
<li>Intro: Our fleet makes excavation easy. Call now for same-day delivery.</li>
<li>CTA: Get Quote</li>
<li>Brief hydraulics explanation (150 words)</li>
<li>Another CTA</li>
<li>Why rent from us section</li>
<li>Pricing table</li>
</ol>
<p><strong>Result:</strong> User bounces. They wanted learning content, not a rental page.</p>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Works:</strong> answers the question completely</p>
<p>No product pitch. Comprehensive guide. Educational focus. Soft CTA at the end only.</p>
<ol>
<li>H1: How Hydraulic Excavators Work</li>
<li>Intro: Hydraulic excavators use fluid pressure to power movement. Here is how the system works.</li>
<li>Core components explained (400 words)</li>
<li>How hydraulic systems generate force (300 words)</li>
<li>Types of hydraulic excavators (300 words)</li>
<li>Maintenance and common issues (200 words)</li>
<li>Soft CTA: Need an excavator? See our rental fleet</li>
</ol>
<p><strong>Result:</strong> User gets value, bookmarks page, returns when ready to rent.</p>
</div>
</div>
<h3>A transactional page, done badly and done well</h3>
<p>Query: SEO audit service pricing</p>
<div class="post-compare">
<div class="post-compare-item">
<p class="post-compare-label"><strong>Broken:</strong> buries the pricing</p>
<p>Long educational content. Weak CTAs. User has to scroll forever to find what they came for.</p>
<ol>
<li>H1: Everything You Need to Know About SEO Audits</li>
<li>What is an SEO audit (500 words)</li>
<li>Benefits of SEO audits (400 words)</li>
<li>How to choose an audit service (600 words)</li>
<li>Finally: pricing table at bottom</li>
<li>Weak CTA: Learn more</li>
</ol>
<p><strong>Result:</strong> User leaves to find pricing elsewhere. You lost a ready buyer.</p>
</div>
<div class="post-compare-item">
<p class="post-compare-label"><strong>Works:</strong> shows pricing immediately</p>
<p>Clear packages. Direct CTAs. Removes friction. Objection handling where needed.</p>
<ol>
<li>H1: SEO Audit Pricing</li>
<li>One line: Choose the audit level that fits your site</li>
<li>Pricing table above fold (Basic, Advanced, Enterprise)</li>
<li>CTA: Request Audit</li>
<li>What is included in each package</li>
<li>FAQ addressing price objections</li>
<li>Client results and testimonials</li>
<li>Final CTA: Get Started</li>
</ol>
<p><strong>Result:</strong> User finds what they need instantly. Clear path to conversion.</p>
</div>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-diagnose-intent-mismatch"><span class="sec-n" aria-hidden="true">06</span>How to diagnose intent mismatch</h2>
<p>Your analytics will tell you when a page is misaligned. Watch for these specific signals.</p>
<h3>High bounce, low engagement</h3>
<p>Users land and leave immediately. Time on page under 30 seconds. Scroll depth under 25%. You built a sales page for a learning query.</p>
<h3>High engagement, no conversions</h3>
<p>Users read the whole page but do not click CTAs. Time on page is high but form fills are zero. You built an educational page for a ready buyer.</p>
<h3>Traffic decline after initial ranking</h3>
<p>You ranked well initially but traffic drops over weeks. In my experience, that pattern usually means the page type doesn't match what searchers want.</p>
<h3>Wrong pages ranking for target keywords</h3>
<p>Your transactional page ranks for informational queries or vice versa. Google is guessing because your page signals are confused. Cannibalization likely.</p>
<h3>Users immediately navigate away</h3>
<p>Heat maps show users clicking back to search results or site navigation within seconds. They landed expecting one thing and got another.</p>
<h3>Competitor pages outrank you</h3>
<p>Competitors with worse content rank higher. Look at their page type. If they matched intent better than you, that's often why they win.</p>
<aside class="post-aside" aria-label="The diagnostic process">
<p class="post-aside-label">The diagnostic process</p>
<p>Step one: pull GA4 data for the page. Look at bounce rate, engagement time, scroll depth, and conversion rate. Step two: search the target keyword and examine what type of pages actually rank. Step three: compare your page structure to ranking pages. If you see mismatch, rebuild the page with correct intent architecture.</p>
</aside>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="build-checklists-for-each-page-type"><span class="sec-n" aria-hidden="true">07</span>Build checklists for each page type</h2>
<p>Use these checklists when creating new pages or auditing existing ones. Every item matters.</p>
<h3>Informational page checklist</h3>
<ul>
<li>H1 answers the query directly (what, how, why format)</li>
<li>Introduction explains what the user will learn</li>
<li>Content covers topic comprehensively with multiple angles</li>
<li>Subheadings are questions the user is asking</li>
<li>Examples and screenshots support explanations</li>
<li>No product pitch in first 80% of content</li>
<li>External links to authoritative sources where relevant</li>
<li>Internal links to related educational content</li>
<li>Optional soft CTA at bottom (guide, tool, related resource)</li>
<li>No popups or aggressive conversion tactics</li>
<li>Table of contents for long guides</li>
<li>Conclusion summarizes key takeaways</li>
</ul>
<h3>Transactional page checklist</h3>
<ul>
<li>Clear value proposition above fold</li>
<li>Primary CTA visible without scrolling</li>
<li>3 to 5 key features or benefits with outcomes</li>
<li>Pricing information easily accessible (on page or one click away)</li>
<li>Social proof (logos, testimonials, case study snippets)</li>
<li>Trust signals (guarantees, security badges, certifications)</li>
<li>Objection handling via FAQ or feature details</li>
<li>Comparison to alternatives if relevant to query</li>
<li>Multiple CTAs throughout page (hero, mid-page, bottom)</li>
<li>CTA language is action-oriented (start, try, buy, get)</li>
<li>Mobile-optimized CTA placement and form design</li>
<li>No educational tangents or unnecessary context</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="when-blended-intent-actually-works"><span class="sec-n" aria-hidden="true">08</span>When blended intent actually works</h2>
<p>Some queries have mixed intent. A percentage of users want to learn and a percentage want to buy. You can serve both without breaking the page if you structure it correctly.</p>
<h3>How to spot blended intent</h3>
<p>You see blended intent when:</p>
<ul>
<li>SERP shows mix of guides and product pages</li>
<li>Query includes comparison words (best, top, vs)</li>
<li>Users are in evaluation phase (researching but ready to act soon)</li>
<li>Query implies decision fatigue (too many options)</li>
</ul>
<p>Example blended queries: best used pickup trucks under 30k; skid steer vs compact track loader; top SEO tools for agencies.</p>
<h3>How to structure blended pages</h3>
<p>The approach:</p>
<ul>
<li>Lead with educational content (satisfy informational users first)</li>
<li>Include comparison framework or decision criteria</li>
<li>Transition naturally into product recommendations</li>
<li>Each recommendation has mini product page structure</li>
<li>Clear CTAs on each product but not aggressive</li>
<li>Conclusion offers next step for both user types</li>
</ul>
<aside class="post-aside" aria-label="The blended page structure">
<p class="post-aside-label">The blended page structure</p>
<p>Introduction defines the category and explains what to look for. Criteria section helps users understand how to evaluate options. Recommendations section covers 5 to 10 options with pros, cons, pricing, and best use case for each. Each option gets a direct CTA. Conclusion summarizes and offers two paths: more research (link to guide) or ready to decide (link to top pick).</p>
</aside>
<h3>When blended intent fails</h3>
<p>Do not force blended structure on pure informational or pure transactional queries. If the SERP is all guides, build a guide. If the SERP is all product pages, build a product page. Blended only works when Google itself is showing mixed results and user intent genuinely splits.</p>
<p>Test by looking at your own bounce and conversion data. If informational users bounce and transactional users do not convert, your blend is broken. Split into two separate pages.</p>
]]></content:encoded>
  </item>
  <item>
    <title>What is navigational search intent?</title>
    <link>https://haydenschuster.com/writing/navigational-search-intent/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/navigational-search-intent/</guid>
    <pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate>
    <description>Navigational search intent means the user already knows where to go. Query patterns, what a good navigational page holds, and signs it&#39;s broken.</description>
    <content:encoded><![CDATA[<p>This is fundamentally different from <a href="https://haydenschuster.com/writing/informational-vs-transactional-pages/">informational or transactional intent</a>, where users are still learning or deciding.</p>
<p>If your login pages, download pages, or customer portals have high bounce rates despite strong branded search traffic, you likely have a navigational intent problem. <strong>Users are searching for you by name but abandoning because you are forcing friction where none should exist.</strong></p>
<aside class="post-aside" aria-label="Quick diagnostic">
<p class="post-aside-label">Quick diagnostic</p>
<p>Check your analytics for branded search terms like &quot;[your brand] login&quot; or &quot;[your brand] download&quot;. If bounce rate is above 40% or time on page is under 10 seconds, your navigational pages are broken. The signals to watch are under <a href="#how-to-diagnose-navigational-page-problems">how to diagnose navigational page problems</a>.</p>
</aside>
<p><em>A note on the numbers: the counts, times and thresholds in this post are my working rules of thumb from building these pages, not published standards. Start from them, then check them against your own data.</em></p>
<h2 id="the-queries-that-signal-navigational-intent"><span class="sec-n" aria-hidden="true">01</span>The queries that signal navigational intent</h2>
<p>The searcher wants direct access to a specific page, tool, brand, or destination.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Pattern</th>
<th>Example queries</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Pattern">Brand + action</td>
<td data-label="Example queries">Gmail login, Netflix sign in, Chase bank account</td>
</tr>
<tr>
<td data-label="Pattern">Brand + specific page</td>
<td data-label="Example queries">Amazon returns, Salesforce pricing, Nike store locator</td>
</tr>
<tr>
<td data-label="Pattern">Direct brand names</td>
<td data-label="Example queries">Facebook, YouTube, Twitter</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-the-searcher-has-already-decided"><span class="sec-n" aria-hidden="true">02</span>What the searcher has already decided</h2>
<p>The user has already:</p>
<ul>
<li>Made a brand decision</li>
<li>Decided what action they need to take</li>
<li>Determined which tool or page they need</li>
<li>Committed to using your service or product</li>
</ul>
<p>They are not comparing options. They are not learning. They are not evaluating. <strong>They just want access.</strong></p>
<h3>Why navigational pages fail</h3>
<p>Most navigational pages fail because they add friction where none should exist. Marketing content before login forms. Product tours before account access. Comparison tables when users already chose your brand.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-a-good-navigational-page-looks-like"><span class="sec-n" aria-hidden="true">03</span>What a good navigational page looks like</h2>
<p>Here is what users expect when they search with navigational intent. Notice what is NOT there: no marketing copy, no feature explanations, no product comparisons. Just direct access.</p>
<div class="post-data">
<p class="post-data-label">A sample sign-in page (a made-up product)</p>
<p><strong>ProjectFlow</strong>, Project Management Software</p>
<ul>
<li>Sign in to your workspace</li>
<li>Email address</li>
<li>Password</li>
<li>Sign In</li>
<li>Forgot password? New user? Sign up</li>
<li>or sign in with Google or Microsoft</li>
</ul>
</div>
<p><strong>What makes this work:</strong> Form is above fold. No scrolling required. Zero marketing content. Clear alternatives (forgot password, sign up). Social login options visible. That is it. The user gets access.</p>
<p><strong>Action step:</strong> Open your login or primary access page on mobile right now. Time how long it takes from landing to seeing the login form. If it is more than 2 seconds, you are losing users. The full checklist is in <a href="#how-to-structure-navigational-pages">how to structure navigational pages</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-structure-navigational-pages"><span class="sec-n" aria-hidden="true">04</span>How to structure navigational pages</h2>
<p>Break the rules below and users abandon your page.</p>
<h3>Must have</h3>
<ul>
<li>Primary action or destination above fold</li>
<li>Single clear CTA (login, download, access)</li>
<li>Zero marketing content blocking access</li>
<li>Page loads in under 1.5 seconds</li>
<li>Mobile-optimized forms and buttons</li>
<li>Alternative paths clearly labeled (forgot password, sign up)</li>
<li>Security indicators visible (SSL, trust badges)</li>
<li>Brand consistency with main site</li>
</ul>
<h3>Never include</h3>
<ul>
<li>Feature comparisons or product tours</li>
<li>Marketing copy explaining why to use the product</li>
<li>Popups or interstitials</li>
<li>Newsletter signups before access</li>
<li>Educational content about the tool</li>
<li>Testimonials or social proof</li>
<li>Pricing tables or upgrade prompts</li>
<li>Anything that delays access to destination</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-navigational-page-types"><span class="sec-n" aria-hidden="true">05</span>Common navigational page types</h2>
<p>Different industries and business models have different navigational needs. Here are the most common types and what they should prioritize.</p>
<h3>Login and access pages</h3>
<p>Email and password fields above fold. Social login options. Forgot password link. New user signup path. No marketing content.</p>
<h3>Download pages</h3>
<p>Download button above fold. System requirements clearly visible. File size and version number shown. Alternative download options (different OS, formats).</p>
<h3>Payment and billing portals</h3>
<p>Account login above fold. Direct link to billing section. Payment method update options. Invoice history access. Support contact visible.</p>
<h3>Store locators</h3>
<p>Search by ZIP or location above fold. Map view immediately visible. Store hours and contact info for each location. Directions link.</p>
<h3>Customer service pages</h3>
<p>Phone number above fold. Live chat button visible. Email contact form. Account-specific support login. FAQ section below primary options.</p>
<h3>Order tracking</h3>
<p>Order number input above fold. Email or account login option. Tracking number entry. Order history for logged-in users. Estimated delivery date visible.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-diagnose-navigational-page-problems"><span class="sec-n" aria-hidden="true">06</span>How to diagnose navigational page problems</h2>
<p>Your analytics will show clear patterns when navigational pages are broken. Watch for these specific signals.</p>
<h3>High immediate exit rate</h3>
<p>Users land and leave within 3 seconds without interaction. Your page is forcing them through marketing content when they just want access.</p>
<h3>Low form completion</h3>
<p>Users start login or signup but abandon before submitting. Form is too complex, loads too slowly, or is buried below marketing content.</p>
<h3>Brand searches not converting</h3>
<p>Users search your brand name + &quot;login&quot; or &quot;download&quot; but do not complete actions. They are hitting friction between search and destination.</p>
<h3>High mobile bounce</h3>
<p>Desktop performance is fine but mobile users abandon. Forms are not optimized for mobile or page loads too slowly on mobile connections.</p>
<h3>Users navigate away immediately</h3>
<p>Heat maps show users clicking back to search results or site navigation within seconds. Your landing page does not match their navigational expectation.</p>
<h3>High &quot;forgot password&quot; usage</h3>
<p>Disproportionate use of password reset compared to successful logins. Your login page may be confusing or forcing users through unnecessary steps.</p>
<aside class="post-aside" aria-label="The fix">
<p class="post-aside-label">The fix</p>
<p>Remove everything between the user and their destination. Test the page on slow mobile connections. Measure time from landing to successful access. If it is more than 5 seconds, you have too much friction.</p>
</aside>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-navigational-intent-differs-from-other-intent-types"><span class="sec-n" aria-hidden="true">07</span>How navigational intent differs from other intent types</h2>
<p>Understanding where navigational intent fits in the larger <a href="https://haydenschuster.com/writing/search-behavior/">search behavior landscape</a> helps you build the right page for each user goal.</p>
<div class="post-table"><table>
<thead>
<tr>
<th></th>
<th>Navigational</th>
<th>The other intent</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="">Navigational vs informational</td>
<td data-label="Navigational">User wants access to Gmail. Query: &quot;Gmail login&quot;</td>
<td data-label="The other intent">User wants to learn about email. Query: &quot;how does email work&quot;</td>
</tr>
<tr>
<td data-label="">Navigational vs transactional</td>
<td data-label="Navigational">User wants to access Salesforce. Query: &quot;Salesforce login&quot;</td>
<td data-label="The other intent">User wants to buy Salesforce. Query: &quot;buy CRM software&quot;</td>
</tr>
</tbody>
</table></div>
<p>Navigational pages provide access. <a href="https://haydenschuster.com/writing/informational-vs-transactional-pages/">Informational pages educate</a>. Confuse the two and both audiences fail.</p>
<p>Navigational assumes decision is made. <a href="https://haydenschuster.com/writing/transactional-pages-fail/">Transactional pages drive that decision</a>. Login pages should never pitch products.</p>
<aside class="post-aside" aria-label="Brand strength determines navigational volume">
<p class="post-aside-label">Brand strength determines navigational volume</p>
<p>Navigational intent only exists when users already know your brand. If you are unknown in your market, users will not search for you by name. This is why brand awareness campaigns, <a href="https://haydenschuster.com/writing/content-strategy/">content strategy</a>, and <a href="https://haydenschuster.com/writing/modern-search/">modern search visibility</a> directly impact your ability to capture navigational traffic.</p>
<p><strong>How to measure brand strength:</strong> Track monthly search volume for &quot;[your brand] + [key action]&quot; queries (login, pricing, download, support). If this number is growing month-over-month, your brand awareness is working. If flat or declining, you have a visibility problem before you have a navigational page problem.</p>
</aside>
]]></content:encoded>
  </item>
  <item>
    <title>The 4 types of search intent, and the page each one needs</title>
    <link>https://haydenschuster.com/writing/search-intent/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/search-intent/</guid>
    <pubDate>Sun, 08 Feb 2026 00:00:00 GMT</pubDate>
    <description>The four types of search intent, a real query for each, and which page to build for each one so the click does not bounce.</description>
    <content:encoded><![CDATA[<p>Someone typing into Google, asking ChatGPT, or speaking to a voice assistant has a specific goal. They want to understand something, compare options, get to a known destination, or take action. Your job is to identify that goal and build the right page type to serve it. Get this wrong and nothing downstream matters: no amount of technical optimization or content strategy will fix a page that answers the wrong question.</p>
<p>This page maps all four intent types, the page structure each one requires, and how to diagnose which intent you are dealing with.</p>
<aside class="post-aside" aria-label="Why this matters now">
<p class="post-aside-label">Why this matters now</p>
<p>As search systems evolve toward AI-generated answers and conversational interfaces, intent matching becomes more important, not less. AI systems extract and summarize based on how well your content structure matches the underlying query goal. Pages with clear intent alignment get cited. Pages with muddled intent get skipped.</p>
</aside>
<p><em>A note on the numbers: the counts, times and thresholds in this post are my working rules of thumb from building these pages, not published standards. Start from them, then check them against your own data.</em></p>
<h2 id="which-page-to-build-for-each-intent"><span class="sec-n" aria-hidden="true">01</span>Which page to build for each intent</h2>
<p>Each intent type demands a different page architecture. Building the wrong type is the single most common cause of high-traffic, low-conversion pages.</p>
<div class="intent-cards">
<section class="intent-card intent-card--i" aria-labelledby="intent-informational">
<h3 id="intent-informational">Informational <span>They want to learn</span></h3>
<p>User needs understanding. Your job is to educate completely and earn trust so they return when ready to decide.</p>
<p class="intent-q-label">Example queries</p>
<ul class="intent-q"><li>what is SEO</li><li>how does email marketing work</li><li>best practices for content strategy</li></ul>
<p><strong>Build: educational content.</strong> Comprehensive guides, explanations, how-tos. No sales pitch. Soft CTA at bottom only.</p>
</section>
<section class="intent-card intent-card--o" aria-labelledby="intent-transactional">
<h3 id="intent-transactional">Transactional <span>They want to buy</span></h3>
<p>User is ready to act. Your job is to remove friction and provide clear next steps. No education needed.</p>
<p class="intent-q-label">Example queries</p>
<ul class="intent-q"><li>buy running shoes online</li><li>HubSpot pricing</li><li>schedule consultation</li></ul>
<p><strong>Build: product or service page.</strong> Pricing, features, benefits above fold. Multiple CTAs. Social proof. Direct path to purchase.</p>
</section>
<section class="intent-card intent-card--j" aria-labelledby="intent-navigational">
<h3 id="intent-navigational">Navigational <span>They know where they want to go</span></h3>
<p>User already decided on your brand. Your job is instant access with zero friction. No marketing content needed.</p>
<p class="intent-q-label">Example queries</p>
<ul class="intent-q"><li>Gmail login</li><li>Facebook</li><li>Amazon customer service</li></ul>
<p><strong>Build: access page.</strong> Login form, download button, or portal above fold. No marketing. Get them to the destination in 3 seconds.</p>
</section>
<section class="intent-card intent-card--z" aria-labelledby="intent-commercial">
<h3 id="intent-commercial">Commercial <span>They are comparing options</span></h3>
<p>User is evaluating before buying. Your job is to provide honest comparison frameworks that help them choose confidently.</p>
<p class="intent-q-label">Example queries</p>
<ul class="intent-q"><li>best CRM for small business</li><li>Slack vs Microsoft Teams</li><li>top email marketing tools</li></ul>
<p><strong>Build: comparison page.</strong> 5 to 7 options with pros, cons, pricing. Evaluation criteria. Decision framework. Multiple CTAs.</p>
</section>
</div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="quick-reference-the-page-for-each-intent"><span class="sec-n" aria-hidden="true">02</span>Quick reference: the page for each intent</h2>
<p>Use this as a cheat sheet when deciding which page type to build for a given query.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Intent</th>
<th>User</th>
<th>Goal</th>
<th>CTA</th>
<th>Length</th>
<th>Format</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Intent">Informational</td>
<td data-label="User">Learning</td>
<td data-label="Goal">Educate</td>
<td data-label="CTA">Soft, bottom</td>
<td data-label="Length">800 to 2,000 words</td>
<td data-label="Format">Guides, tutorials</td>
</tr>
<tr>
<td data-label="Intent">Transactional</td>
<td data-label="User">Buying</td>
<td data-label="Goal">Convert</td>
<td data-label="CTA">Multiple, prominent</td>
<td data-label="Length">300 to 800 words</td>
<td data-label="Format">Product, pricing</td>
</tr>
<tr>
<td data-label="Intent">Navigational</td>
<td data-label="User">Navigating</td>
<td data-label="Goal">Access</td>
<td data-label="CTA">One, above fold</td>
<td data-label="Length">Minimal</td>
<td data-label="Format">Login, portal</td>
</tr>
<tr>
<td data-label="Intent">Commercial</td>
<td data-label="User">Comparing</td>
<td data-label="Goal">Guide decision</td>
<td data-label="CTA">Per option</td>
<td data-label="Length">1,200 to 2,500 words</td>
<td data-label="Format">&quot;Best of&quot;, reviews</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-tell-which-intent-a-query-has"><span class="sec-n" aria-hidden="true">03</span>How to tell which intent a query has</h2>
<p>Not sure which intent type a query has? These four questions get you to the right answer fast. When the query does not fit neatly, check the SERP: Google has already classified it based on click behavior.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>The query</th>
<th>Intent</th>
<th>The user</th>
<th>Build</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="The query">Includes your brand name</td>
<td data-label="Intent"><strong>Navigational</strong></td>
<td data-label="The user">Already knows you</td>
<td data-label="Build">Access pages, not marketing pages</td>
</tr>
<tr>
<td data-label="The query">Asks &quot;what,&quot; &quot;how,&quot; or &quot;why&quot;</td>
<td data-label="Intent"><strong>Informational</strong></td>
<td data-label="The user">Wants to learn</td>
<td data-label="Build">Comprehensive educational content with no sales pitch in the first 80%</td>
</tr>
<tr>
<td data-label="The query">Includes &quot;best,&quot; &quot;top,&quot; &quot;vs,&quot; or &quot;review&quot;</td>
<td data-label="Intent"><strong>Commercial</strong></td>
<td data-label="The user">Is comparing options</td>
<td data-label="Build">Honest comparison frameworks with multiple options and clear trade-offs</td>
</tr>
<tr>
<td data-label="The query">Includes &quot;buy,&quot; &quot;price,&quot; &quot;hire,&quot; or action words</td>
<td data-label="Intent"><strong>Transactional</strong></td>
<td data-label="The user">Is ready to act</td>
<td data-label="Build">Product or service pages with clear CTAs and minimal friction</td>
</tr>
</tbody>
</table></div>
<aside class="post-aside" aria-label="When intent is mixed">
<p class="post-aside-label">When intent is mixed</p>
<p>Some queries blend intent types. &quot;Best CRM software pricing&quot; combines commercial (comparison) and transactional (pricing action). When this happens, lead with the dominant intent and bridge to the secondary one.</p>
</aside>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-intent-types-connect"><span class="sec-n" aria-hidden="true">04</span>How intent types connect</h2>
<p>Users rarely stay in one intent type. They move from learning to comparing to buying. Your content strategy needs to bridge these transitions or you lose users at each stage.</p>
<h3>The typical journey</h3>
<p><strong>Stage 1: Informational.</strong> &quot;What is CRM software?&quot; User is learning the category. Build guides that answer comprehensively and link forward to comparison content.</p>
<p><strong>Stage 2: Commercial.</strong> &quot;Best CRM for small business.&quot; User is evaluating options. Build comparison pages with honest trade-offs and CTAs per option.</p>
<p><strong>Stage 3: Transactional.</strong> &quot;HubSpot pricing plans.&quot; User has chosen and wants to act. Build clear, frictionless conversion pages.</p>
<p>Each stage needs internal links to the next. When intent transitions are misaligned, users drop off between stages instead of moving forward.</p>
<h3>Search intent and the marketing funnel</h3>
<p>Marketers talk in funnel stages; searchers type intents. They're the same journey described from two sides, and every stage needs its own kind of page.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Funnel stage</th>
<th>Intent</th>
<th>The reader</th>
<th>Pages to build</th>
<th>What the page must do</th>
<th>Go deeper</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Funnel stage">Top of funnel</td>
<td data-label="Intent">Informational</td>
<td data-label="The reader">Has a question, no shortlist yet</td>
<td data-label="Pages to build">Guides, explainers, how-tos, glossaries</td>
<td data-label="What the page must do">Answer in the first lines, then link to the next question they'll have. No pitch until they've learned what they came for.</td>
<td data-label="Go deeper"><a href="https://haydenschuster.com/writing/informational-vs-transactional-pages/">Informational vs transactional pages</a></td>
</tr>
<tr>
<td data-label="Funnel stage">Middle of funnel</td>
<td data-label="Intent">Commercial</td>
<td data-label="The reader">Knows the options, wants help choosing</td>
<td data-label="Pages to build">Comparisons, &quot;best of&quot; lists, reviews, alternatives</td>
<td data-label="What the page must do">Put the criteria up front, show honest trade-offs, and include options you don't sell.</td>
<td data-label="Go deeper"><a href="https://haydenschuster.com/writing/commercial-search-intent/">Commercial search intent</a></td>
</tr>
<tr>
<td data-label="Funnel stage">Bottom of funnel</td>
<td data-label="Intent">Transactional</td>
<td data-label="The reader">Has decided and wants to act</td>
<td data-label="Pages to build">Product, pricing, booking and contact pages</td>
<td data-label="What the page must do">Confirm the choice instead of re-selling it: price, details and the next step on the first screen.</td>
<td data-label="Go deeper"><a href="https://haydenschuster.com/writing/transactional-pages-fail/">Why transactional pages fail</a></td>
</tr>
<tr>
<td data-label="Funnel stage">After the decision</td>
<td data-label="Intent">Navigational</td>
<td data-label="The reader">Knows exactly where to go</td>
<td data-label="Pages to build">Login, support, account and location pages</td>
<td data-label="What the page must do">Get them there in one step, with nothing in the way.</td>
<td data-label="Go deeper"><a href="https://haydenschuster.com/writing/navigational-search-intent/">Navigational search intent</a></td>
</tr>
</tbody>
</table></div>
<p>The links between the rows matter as much as the rows. A top-of-funnel guide that never points to a comparison loses the reader the moment they're ready to choose. More on that in <a href="https://haydenschuster.com/writing/intent-transitions/">how misaligned intent stalls decisions</a>.</p>
<h3>Where most sites break</h3>
<p><strong>Informational pages with no bridge forward.</strong> The guide is great, but there is no link to comparison or evaluation content. Users learn and leave.</p>
<p><strong>Commercial pages that skip to hard sell.</strong> Instead of honest comparison, the page pushes one option. Users distrust and bounce.</p>
<p><strong>Transactional pages that re-educate.</strong> The user already decided. Explaining &quot;what is CRM&quot; on a pricing page adds friction.</p>
<p>The fix is structural: every page should know its job and link to the appropriate next step in the journey.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="signs-a-page-doesn-t-match-its-intent"><span class="sec-n" aria-hidden="true">05</span>Signs a page doesn't match its intent</h2>
<p>These patterns indicate your pages are not serving the right intent. Each one has a structural fix.</p>
<div class="post-table"><table>
<thead>
<tr>
<th>Signal</th>
<th>What's happening</th>
<th>The fix</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label="Signal">High traffic, low conversions</td>
<td data-label="What's happening">You are ranking for informational queries but building transactional pages. Users wanted to learn but landed on a sales pitch.</td>
<td data-label="The fix">Rebuild as educational content with a soft CTA path forward.</td>
</tr>
<tr>
<td data-label="Signal">High bounce on service pages</td>
<td data-label="What's happening">Your service page ranks for commercial queries (&quot;best X&quot;) but only presents your offering. Users want comparison.</td>
<td data-label="The fix">Restructure as a comparison page, or target more specific transactional queries.</td>
</tr>
<tr>
<td data-label="Signal">Long time on page, no action</td>
<td data-label="What's happening">Users are reading your content but not progressing. Your informational pages likely lack clear internal links to commercial or transactional pages.</td>
<td data-label="The fix">Fix your intent transitions.</td>
</tr>
<tr>
<td data-label="Signal">Rankings but wrong traffic</td>
<td data-label="What's happening">You rank well but attract users at the wrong stage. This is a content-intent alignment problem that requires content strategy work, not more optimization.</td>
<td data-label="The fix">Map your existing pages to intent types and fill the gaps.</td>
</tr>
</tbody>
</table></div>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-audit-your-pages-for-intent-mismatch"><span class="sec-n" aria-hidden="true">06</span>How to audit your pages for intent mismatch</h2>
<p>Step one: pull your top 20 pages by traffic from analytics. Step two: classify each page by which intent type it currently serves. Step three: check the queries driving traffic to each page in Search Console. If the query intent does not match the page type, you have found your problem.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How to structure content for answer-first search</title>
    <link>https://haydenschuster.com/writing/answer-first-content/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/answer-first-content/</guid>
    <pubDate>Sat, 07 Feb 2026 00:00:00 GMT</pubDate>
    <description>When AI Overviews answer the basic question first, a page earns the click by being the next step. The four-part structure, with two worked examples.</description>
    <content:encoded><![CDATA[<p>Increasingly, search results exist to <strong>resolve understanding directly inside the results page itself.</strong> AI Overviews, summaries, comparisons, and expanded SERP features now answer early questions before a visit ever happens. That shift changes what content needs to do to remain valuable.</p>
<p>For years, content succeeded by being the clearest explanation available. Today, explanation alone is often resolved before the click. The role of content has moved forward in the journey.</p>
<p>Instead of being the first answer, effective content now becomes <strong>the next step</strong>.</p>
<h2 id="why-answer-first-search-changes-what-content-is-for"><span class="sec-n" aria-hidden="true">01</span>Why answer-first search changes what content is for</h2>
<p>Answer-first search changes the moment when users need a website. <strong>Early uncertainty is often resolved directly in search results, which means informational content that only defines or explains concepts increasingly competes with summarized answers.</strong></p>
<p>Content now succeeds when it helps users move from understanding toward <strong>application, evaluation, or decision</strong>. The value shifts from explaining what something is to helping users understand what to do next.</p>
<p><strong>This is why some pages <a href="https://haydenschuster.com/writing/impressions-up-clicks-flat/">gain visibility without gaining proportional traffic.</a></strong> The system recognizes relevance and surfaces the content, but users only click once their questions become more specific.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-search-systems-read-a-page-s-structure"><span class="sec-n" aria-hidden="true">02</span>How search systems read a page's structure</h2>
<p>Modern search systems evaluate whether information resolves intent and how clearly information progresses from one idea to the next.</p>
<p>Content that is structured logically becomes easier to interpret. Sections that anticipate follow-up questions signal depth and usefulness. Pages that move naturally from explanation into application provide clearer signals than pages that stop once a definition is complete.</p>
<p><strong>Structure becomes part of meaning.</strong> When information is organized around how people actually learn and decide, both users and systems understand where the content fits within the broader journey.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-definition-first-content-loses-clicks"><span class="sec-n" aria-hidden="true">03</span>Why definition-first content loses clicks</h2>
<p>Definition-first content worked when search results primarily acted as navigation. Users searched, clicked, and learned on the page itself. That relationship weakens when search engines provide definitions directly inside results. Make sure you understand each type of page to avoid search misalignment here: <a href="https://haydenschuster.com/writing/search-intent/">the 4 types of search intent</a>.</p>
<p><strong>A page that only repeats a basic explanation now adds limited value.</strong> The system can summarize that information faster than a user can open a new page. As a result, visibility may increase while engagement remains flat.</p>
<p>The issue is that the content stops at understanding instead of <strong>progressing toward action or decision.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-stronger-content-does-after-the-basics"><span class="sec-n" aria-hidden="true">04</span>What stronger content does after the basics</h2>
<p>Content that performs well in answer-first environments tends to follow a different pattern. It assumes users may already understand the basics by the time they arrive.</p>
<p>Instead of repeating introductory information, <strong>stronger content answers the next question</strong>. It explains how concepts apply in real situations, what variables change outcomes, what mistakes to avoid, and how decisions are influenced by context.</p>
<p><strong>Understanding becomes the starting point, not the destination.</strong> It's a <em>JOURNEY.</em></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-structure-content-around-intent-transitions"><span class="sec-n" aria-hidden="true">05</span>How to structure content around intent transitions</h2>
<p>Intent rarely stops at a single question. <strong>Users move from learning to comparing, from comparing to evaluating, and eventually toward deciding.</strong> Content structure should reflect that movement.</p>
<p>A strong structure establishes shared understanding, introduces real-world implications, explains tradeoffs or variables, and then helps the user understand what comes next.</p>
<p>When these transitions are clear, content remains valuable even when summaries exist above it. Users arrive to apply what they already learned.</p>
<p>Example: Someone searches <strong>&quot;enterprise SEO vs local SEO.&quot;</strong> An AI Overview or summary can explain the difference immediately, so the user already understands the basic definition before clicking anything.</p>
<p>A page structured around intent transitions <strong>explains when each approach breaks down, how business structure changes the strategy, what tradeoffs exist in budget or timeline, and how a company should decide where to invest first.</strong> The definition creates understanding. The structure that follows helps the user move from understanding to evaluation, and eventually toward a decision.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="an-example-how-often-should-a-website-be-redesigned"><span class="sec-n" aria-hidden="true">06</span>An example: &quot;how often should a website be redesigned&quot;</h2>
<p>Consider a search like &quot;<strong>how often should a website be redesigned</strong>.&quot; An AI Overview can explain that most sites are refreshed every few years. That answers the surface-level question and sets a general expectation.</p>
<p>The content that earns engagement goes further. It explains how redesign timing depends on traffic patterns, technical debt, changing search behavior, and whether performance issues come from design or structure. <strong>It helps readers understand when a redesign solves a problem and when it simply hides one.</strong> <strong>The overview delivers the summary. The content delivers judgment.</strong></p>
<p>This is where engagement now shifts. <strong>Users click when they need interpretation and decision-making context, not when they only need a definition.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-internal-links-keep-the-reader-moving"><span class="sec-n" aria-hidden="true">07</span>How internal links keep the reader moving</h2>
<p>Internal linking becomes more important as the first search expands. When users arrive after gaining initial understanding, they often need to move deeper into related questions rather than restart their research.</p>
<p>Linking between articles that represent different stages of intent helps maintain progression. A reader moving from search behavior to content structure to decision-making signals usefulness and topical authority. Structure across pages reinforces structure within pages.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-means-for-content-going-forward"><span class="sec-n" aria-hidden="true">08</span>What this means for content going forward</h2>
<p>AI Overviews and answer-first interfaces raise the standard for content. Content that only explains increasingly competes with summarized answers. <strong>Content that helps users move forward becomes more valuable.</strong></p>
<p><strong>The goal is to remain useful after the first answer has already been given.</strong></p>
<p>When content anticipates the next step, aligns with real search behavior, and connects understanding to decisions, <strong>visibility turns into engagement instead of stopping at awareness.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-readers-still-need-content-after-the-first-answer"><span class="sec-n" aria-hidden="true">09</span>Why readers still need content after the first answer</h2>
<p>Answer-first search changes <strong><em>when users need content, not whether they need it.</em></strong> Understanding increasingly begins inside the results page, which means content must provide something beyond explanation to remain valuable.</p>
<p>The sites that succeed in this environment are the ones <strong>helping users move forward once understanding exists.</strong> Structure, clarity, and progression become the differentiators.</p>
<p>Search is shifting toward understanding first and decision second. Content that supports that transition continues to earn attention because it provides what summaries cannot: depth, context, and direction after the answer.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Why impressions rise while clicks stay flat</title>
    <link>https://haydenschuster.com/writing/impressions-up-clicks-flat/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/impressions-up-clicks-flat/</guid>
    <pubDate>Sat, 07 Feb 2026 00:00:00 GMT</pubDate>
    <description>Why Search Console shows impressions climbing while clicks stay flat, what an impression measures, and four questions to read your own data.</description>
    <content:encoded><![CDATA[<p>Search visibility no longer behaves the way it used to. <strong>Many websites are seeing impressions increase in Google Search Console while clicks remain flat or even decline.</strong></p>
<p>At first glance, this looks like a problem. Rankings improve, visibility grows, yet traffic does not follow. In most cases, nothing is broken. What has changed is how search works and how users interact with information before deciding to click.</p>
<p>This shift is closely tied to how modern search systems prioritize understanding inside the results page itself. <a href="https://haydenschuster.com/writing/answer-first-content/">AI Overviews</a>, expanded SERP features, and answer-first interfaces <strong>increasingly resolve early questions before a visit ever happens.</strong> Visibility still exists, but its role has changed. So we gotta adapt.</p>
<h2 id="what-an-impression-measures"><span class="sec-n" aria-hidden="true">01</span>What an impression measures</h2>
<p><strong>An impression simply means your content was shown. ANYWHERE. It does not mean a user needed to click.</strong></p>
<p>Historically, impressions and clicks moved together because search results functioned primarily as navigation. Users searched, scanned results, clicked a page, and then learned or decided what to do next.</p>
<p>Today, understanding often begins before the click. Search results contain <strong>summaries, comparisons, related questions, and contextual information that help users interpret a topic immediately</strong>. As a result, a page can gain more exposure without generating proportionally more traffic. Visibility and visits are no longer the same signal.</p>
<p>This is why rising impressions alongside flat clicks is increasingly common, especially for informational and research-driven queries.</p>
<p>For example, someone searches &quot;<strong>what is search intent.</strong>&quot; Your page appears in the results (whatever kind, AI overview, snippet, etc.), so it earns an impression. But the user may read an AI Overview or a summary directly on the results page and understand the basic concept without clicking. <strong>Your content was seen, but the question was partially resolved before a visit was needed.</strong></p>
<p><em>There's the disparity.</em></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-this-is-happening-more-often-now"><span class="sec-n" aria-hidden="true">02</span>Why this is happening more often now</h2>
<p><strong>AI Overviews are the clearest example of this shift.</strong> Instead of presenting a list of links and expecting users to assemble an answer themselves, Google (and other search engines) increasingly combs through information across multiple sources and presents a summarized explanation directly in the results page.</p>
<p>It's simple: <strong>when early uncertainty is resolved immediately, fewer users need to click to continue learning.</strong></p>
<p>Many will refine their query, return later in the process, or move directly toward a more specific search.</p>
<p><strong>The click simply happens later in the journey, not at the moment of first exposure.</strong></p>
<p>This reflects a broader transition from navigation-first search to understanding-first search. The results page itself has become part of the learning process.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-rankings-and-traffic-stopped-moving-together"><span class="sec-n" aria-hidden="true">03</span>Why rankings and traffic stopped moving together</h2>
<p>Traditional SEO assumed a simple relationship. Higher rankings produced more clicks, which produced more traffic. <strong>That relationship weakens when part of the intent is satisfied before the visit occurs.</strong></p>
<p><strong>A page can rank higher, appear more frequently, and still receive the same number of clicks because the system has already answered part of the question.</strong> The impression represents awareness, not necessarily a demand for deeper information.</p>
<p><strong>This is especially visible in informational content.</strong> Pages that explain concepts without helping users move forward often see exposure grow while engagement remains flat. The issue is that the content stops at understanding instead of progressing toward action or decision.</p>
<figure class="post-fig pframe post-fig--inline post-fig--illustration" id="fig-impressions-vs-clicks-illustration" style="--frame: var(--field); --frame-shadow: var(--piece-j)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/impressions-rise-clicks-flat-illustration-480.webp 480w, https://haydenschuster.com/assets/post-images/impressions-rise-clicks-flat-illustration-800.webp 800w, https://haydenschuster.com/assets/post-images/impressions-rise-clicks-flat-illustration-1200.webp 1200w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/impressions-rise-clicks-flat-illustration-480.jpg" width="1200" height="720" alt="Illustrated line chart: a tall, jagged purple line labeled Impressions above a nearly flat blue line labeled Clicks." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 1</span> The pattern this section describes, drawn as an illustration rather than real data: impressions swing high while clicks stay near the floor.</figcaption></figure><div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-visibility-builds-familiarity-before-traffic"><span class="sec-n" aria-hidden="true">04</span>How visibility builds familiarity before traffic</h2>
<p>One of the most important changes underneath this shift is that <strong>authority and branding matter more than before.</strong> Users are increasingly exposed to sources inside summaries, related results, and repeated searches before ever clicking a link.</p>
<p>The first interaction becomes awareness rather than a visit.</p>
<p><strong>A user may see a brand referenced multiple times across searches, recognize it later, and only click when they are closer to making a decision. Visibility builds familiarity before it produces traffic.</strong></p>
<p>This changes how authority develops. It is built through consistent exposure, clear explanations, and being associated with reliable information across multiple stages of research. The sites that are remembered are often the ones chosen when understanding turns into action.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-means-for-content"><span class="sec-n" aria-hidden="true">05</span>What this means for content</h2>
<p>AI Overviews and answer-first search change what content needs to do.</p>
<p>Content that only repeats definitions or basic explanations increasingly competes with summarized answers. Content that survives this shift tends to move beyond explanation. <strong>It anticipates the next question, connects understanding to real decisions, and helps users progress forward.</strong></p>
<p><strong>The goal is to be the next step.</strong></p>
<p>When intent transitions are clear and aren't misaligned, content remains valuable even when summaries exist above it. Users arrive to apply what they have already learned.</p>
<p>Compare the differences between <strong><a href="https://haydenschuster.com/writing/informational-vs-transactional-pages/">informational and transactional pages</a></strong> side by side.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="an-example-how-long-does-seo-take-to-work"><span class="sec-n" aria-hidden="true">06</span>An example: &quot;how long does SEO take to work&quot;</h2>
<p>For example, someone searches &quot;how long does SEO take to work.&quot; Your article appears in results, so it earns an impression. The user reads a summarized answer directly on the results page and understands that SEO usually takes several months, so they do not need to click yet.</p>
<p>Later, when the question becomes more specific, such as why timelines differ between sites or what actually slows progress down, they look for deeper explanation. The overview provides the basic expectation. <strong>The content that explains variables, tradeoffs, and next steps becomes valuable when the user moves from understanding to decision-making.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-read-rising-impressions-in-your-own-data"><span class="sec-n" aria-hidden="true">07</span>How to read rising impressions in your own data</h2>
<p>When impressions increase without matching click growth, the correct response is not panic. Ask:</p>
<ul>
<li>Is the query informational or early-stage research?</li>
<li>Is understanding being resolved inside search?</li>
<li>Does the page provide a next step after explanation?</li>
<li>Are users returning later through more specific searches?</li>
</ul>
<p>In many cases, <strong>rising impressions signal growing topical visibility rather than declining performance.</strong> The system is showing your content more often because it recognizes relevance. The opportunity is ensuring that when users are ready to go deeper, your content remains the logical destination.</p>
<p>You can identify this pattern in Google Search Console by comparing rising impressions against stable or declining CTR at the query level, especially for informational searches where average position improves but clicks do not follow. In Ahrefs, look for pages gaining keyword visibility and ranking for more variations of early-stage queries, even when traffic growth remains flat, which often signals expanding topical exposure rather than performance loss.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-are-my-impressions-up-but-clicks-down"><span class="sec-n" aria-hidden="true">08</span>Why are my impressions up but clicks down?</h2>
<p>Impressions increasing while clicks remain flat is often a sign that search behavior and search discovery have changed. <strong>The results page increasingly resolves early questions, which shifts when and why users choose to visit websites.</strong></p>
<p>As search moves toward <strong>understanding first and decision second</strong>, the role of content becomes clearer. Content that only explains becomes easier to replace. Content that helps users move forward becomes more valuable.</p>
<p><strong>Visibility no longer guarantees traffic, but it still builds authority.</strong> Sites that focus on clarity, usefulness, and structured progression will continue to benefit as search evolves, because they provide what summaries cannot: depth, context, and the next step after understanding begins.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Why AI Overviews appear, and what they change</title>
    <link>https://haydenschuster.com/writing/why-ai-overviews-appear/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/why-ai-overviews-appear/</guid>
    <pubDate>Sat, 07 Feb 2026 00:00:00 GMT</pubDate>
    <description>Why Google shows AI Overviews, which searches trigger them, and what they change about clicks, rankings and the content that still earns a visit.</description>
    <content:encoded><![CDATA[<p><strong>Search results no longer exist only to send users to websites. Increasingly, they exist to resolve questions directly inside the results page itself.</strong> That shift changes what visibility means, how users interact with information, and why content that once performed well no longer behaves the same way.</p>
<p>AI Overviews are the clearest example of this shift because instead of presenting a list of links and expecting users to assemble an answer themselves, Google now summarizes information across multiple sources and presents a synthesized response at the top of the page. This change did not appear suddenly. It is the continuation of a longer transition in how search works, and understanding why AI Overviews appear requires understanding both <a href="https://haydenschuster.com/writing/search-behavior/"><strong>how people search</strong></a> and how <a href="https://haydenschuster.com/writing/modern-search/"><strong>modern search systems</strong></a> interpret that behavior.</p>
<h2 id="what-ai-overviews-actually-are"><span class="sec-n" aria-hidden="true">01</span>What AI Overviews actually are</h2>
<p>AI Overviews are generated summaries that appear at the top of some Google search results and combine information from multiple sources to provide a concise answer without requiring users to visit individual pages first.</p>
<p>Unlike featured snippets, which extract content from a single source, AI Overviews <strong>synthesize information across the web</strong>, meaning their goal is not to rank a page but <strong>to resolve a question as efficiently as possible</strong>. They are a new response format.</p>
<figure class="post-fig pframe post-fig--inline post-fig--screenshot post-fig--pair" id="fig-snippet-vs-ai-overview" style="--frame: var(--field); --frame-shadow: var(--piece-j)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/featured-snippet-lease-or-buy-480.webp 480w, https://haydenschuster.com/assets/post-images/featured-snippet-lease-or-buy-523.webp 523w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/featured-snippet-lease-or-buy-480.jpg" width="523" height="406" alt="Google results for 'is it better to lease or buy' with a featured snippet boxed in red: one paragraph quoted from a single personal finance site, with its link underneath, above People Also Ask questions." loading="lazy" decoding="async"></picture><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/ai-overview-lease-or-finance-480.webp 480w, https://haydenschuster.com/assets/post-images/ai-overview-lease-or-finance-622.webp 622w" sizes="(min-width: 1100px) min(470px, 28vw), (min-width: 700px) calc(50vw - 40px), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/ai-overview-lease-or-finance-480.jpg" width="622" height="699" alt="A Google AI Overview for 'is it better to lease or finance': a written answer with Financing and Leasing sections, each listing pros, cons and who it suits best, with small link icons after the claims." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 1</span> Two answers to nearly the same question. The featured snippet quotes one page for 'is it better to lease or buy'. The AI Overview for 'is it better to lease or finance' writes its own answer, with a link icon after each claim pointing to a source. Screenshots from the original post, published February 7, 2026; the Overview's source panel is cropped out.</figcaption></figure><p><strong>Opinion, based on what I'm seeing:</strong> Featured snippets represented an early step toward answer-first search, where Google extracted a single clear answer from a webpage and surfaced it directly in results.</p>
<p><strong>As search systems have evolved, many of the situations where featured snippets once appeared are now handled by AI Overviews and other discovery-focused SERP features</strong> that synthesize information across multiple sources instead of quoting one page. The underlying goal has not changed. Google is increasingly prioritizing resolving intent inside the search experience itself, which shifts visibility away from individual extracted answers toward summarized responses, contextual panels, and expanded discovery elements that reduce the need for users to visit multiple sites before understanding a topic.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="prediction-ai-overviews-look-like-the-next-step-between-traditional-google-search-and-fully-ai-driven-search"><span class="sec-n" aria-hidden="true">02</span>Prediction: AI Overviews look like the next step between traditional Google search and fully AI-driven search</h2>
<p>Instead of moving from search results to websites, users increasingly get answers directly in Google first.</p>
<p>The search results page becomes the place where learning starts, not just where navigation begins. Over time, this can <strong>shift expectations around search itself.</strong> People begin to expect answers immediately, and only visit websites when they want more depth, context, or a next step.</p>
<p>That moves <a href="https://haydenschuster.com/writing/search-behavior/">search behavior</a> closer to how people already use AI platforms like <a href="https://gemini.google.com/">Gemini</a>, <a href="https://claude.ai/">Claude</a>, <a href="https://chatgpt.com/">ChatGPT</a>, and <a href="https://www.perplexity.ai/">Perplexity</a>, where the interaction starts with an answer instead of a list of destinations.</p>
<p>This shift has led to a wave of uneducated commentary claiming that &quot;<em>SEO is dying</em>&quot;. What is actually disappearing is a version of SEO built around repetition instead of usefulness. <strong>SEO is evolving quickly, and has more opportunities today than at any time in the past.</strong> Let's talk about it.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-seo-is-evolving-instead-of-dying"><span class="sec-n" aria-hidden="true">03</span>Why SEO is evolving instead of dying</h2>
<p>As I just mentioned, a growing group is claiming that AI Overviews and AI search mean SEO is dying. <strong>The reality looks closer to the opposite.</strong> What is disappearing is a version of SEO that relied on surface-level optimization, content volume, or repeating information that already exists everywhere else. When search engines begin answering simple questions directly, content that only exists to restate obvious answers naturally loses value. That raises the standard for SEO.</p>
<p>This shift creates a larger opportunity for sites that understand how <a href="https://haydenschuster.com/writing/modern-search/">search is evolving</a>. When basic explanations are summarized inside search results, <strong>the remaining value moves toward content that is genuinely helpful, solves real problems, and helps users move forward instead of stopping at understanding.</strong> SEO becomes less about capturing attention at the top of the funnel and more about being useful once attention exists.</p>
<p>Structure becomes more important as well. Modern search systems need to understand not just what a page says, but how information connects, how intent progresses (<a href="https://haydenschuster.com/writing/intent-transitions/">and misaligned content dies</a>), and where a user goes next. <a href="https://haydenschuster.com/writing/content-strategy/">Content</a> that is clearly organized, aligned to real search behavior, and built around solving problems instead of targeting isolated keywords becomes easier for both users and systems to trust.</p>
<p><strong>In that sense, SEO is maturing.</strong> The advantage shifts toward people who can explain clearly, structure information logically, and create content that remains valuable even after a summary has already answered the first question.</p>
<p>Are you taking advantage of it?</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-google-shows-ai-overviews"><span class="sec-n" aria-hidden="true">04</span>Why Google shows AI Overviews</h2>
<p>AI Overviews appear when Google believes a query requires <strong>explanation rather than navigation.</strong></p>
<p>This typically happens when the question is informational or exploratory, when multiple perspectives or sources are needed, when users are likely to refine their searches after learning something new, or when intent centers on understanding rather than immediate action. From a system perspective, this reduces friction. From a user perspective, it shortens the learning phase. Modern search systems increasingly optimize for <strong>satisfaction instead of clicks</strong>, and if a system can resolve uncertainty directly, it often will. This aligns with a broader pattern where search engines increasingly <strong>model behavior instead of matching keywords alone</strong>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-types-of-searches-trigger-ai-overviews"><span class="sec-n" aria-hidden="true">05</span>What types of searches trigger AI Overviews</h2>
<p>AI Overviews appear most often for queries where users are trying to understand something rather than do something <strong>immediately.</strong></p>
<p>Common patterns include <strong>definitions and explanations, complex or multi-part questions, comparisons, or early-stage research queries</strong>. These are the same moments where users historically clicked multiple results, compared answers, and refined queries repeatedly. AI Overviews compress that process into a single interaction, which is why <strong>informational content is affected most strongly</strong>. When understanding is resolved inside search, fewer clicks are required to continue learning.</p>
<p>Examples of searches that are AI Overview heavy:</p>
<ul>
<li>Definitions and basic explanations (almost exclusively now)</li>
<li>Comparisons between options or concepts</li>
<li>Early-stage research queries</li>
<li>Complex or multi-part questions</li>
<li>Problem understanding searches</li>
<li>Basic informational learning-focused queries</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-ai-overviews-change-click-behavior"><span class="sec-n" aria-hidden="true">06</span>How AI Overviews change click behavior</h2>
<p>One of the most common observations since AI Overviews expanded is that impressions can increase while clicks remain flat or decline.</p>
<p><strong>This is a change in how visibility functions.</strong> Users may read a summary first, refine their query afterward, click later in the research process, or resolve their initial question without leaving the search. In other words, <strong>visibility and visits no longer move together as predictably as they once did</strong>. This mirrors a broader issue seen in informational content where content answers early-stage questions without guiding users toward the next step, causing engagement to stop at understanding rather than progressing toward decisions.</p>
<p>Important note here: <strong>One of the most important changes underneath this shift is that authority and branding begin to matter more</strong>, not less. When users are exposed to answers directly inside search results, they often encounter multiple sources before ever clicking a link. The first interaction becomes awareness rather than a visit. Users may see a brand referenced in an AI Overview, recognize it later during a refined search, and <strong>only click once they are closer to making a decision</strong>. In this environment, visibility builds familiarity before it produces traffic. Sites that consistently provide clear, trustworthy, and helpful information benefit because recognition carries forward into later searches. Authority is built through repeated exposure, consistency, and being associated with reliable explanations across the research process. As a result, branding and topical authority become tightly connected. <strong>The sites that are remembered are often the ones that get chosen for AI Overviews when understanding turns into a final decision.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-rankings-and-traffic-no-longer-move-together"><span class="sec-n" aria-hidden="true">07</span>Why rankings and traffic no longer move together</h2>
<p>Traditional SEO assumed a simple relationship where higher rankings produced more clicks and more traffic. AI Overviews weaken that relationship because when answers appear directly in search, <a href="https://haydenschuster.com/writing/impressions-up-clicks-flat/">ranking improvements may increase exposure without increasing visits.</a></p>
<p>The system has already satisfied part of the intent before the click happens. This is why <strong><a href="https://haydenschuster.com/writing/intent-transitions/">intent alignment</a> matters more than ever</strong>. Content that only explains increasingly competes with summarized answers, while content that helps users move forward in their decision process remains valuable. This is also why <a href="https://haydenschuster.com/writing/informational-content-to-decision/">informational content frequently fails to move users toward decisions</a>. The problem is <strong>missing transitions between understanding and action</strong>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-means-for-content-and-seo-strategy"><span class="sec-n" aria-hidden="true">08</span>What this means for content and SEO strategy</h2>
<p><strong>AI Overviews change what <a href="https://haydenschuster.com/writing/content-strategy/">content</a> needs to do.</strong></p>
<p>Content that survives this shift tends to move beyond basic explanations, anticipate the next question in the journey, connect informational understanding to decision-making, and provide depth or perspective that summaries cannot replace.</p>
<p>This is where content strategy and <a href="https://haydenschuster.com/writing/search-behavior/">search behavior</a> intersect.</p>
<p>When intent transitions are clear, content remains valuable even when summaries exist above it.</p>
<p>Make sure you're matching your content to one of the four main categories: <a href="https://haydenschuster.com/writing/search-intent/">the 4 types of search intent</a>.</p>
<p><strong>The goal is to be the next step</strong>.</p>
<h3>Example: &quot;what is forklift capacity&quot;</h3>
<p>Someone searches &quot;<strong>what is forklift capacity.</strong>&quot;</p>
<p><strong>An AI Overview can explain the definition right away</strong>, so a page that only repeats that definition adds little value. A stronger piece of content goes further. <strong>It explains how forklift capacity affects real decisions, common mistakes people make, and what to consider next.</strong></p>
<p>I would build content that could:</p>
<ul>
<li><strong>Explain how the concept applies in real situations instead of repeating the definition</strong>
<ul>
<li>How does forklift capacity affect real operating conditions? (not just define the term)</li>
</ul>
</li>
<li><strong>Help users understand what to do next after learning the basics</strong>
<ul>
<li>Help buyers understand what to evaluate next, such as load center, attachments, and application requirements</li>
</ul>
</li>
<li><strong>Connect understanding to decisions, outcomes, or next steps in the journey</strong>
<ul>
<li>Provide examples of choosing the right forklift for your business, show how each one fits the need, and link specific inventory</li>
</ul>
</li>
</ul>
<p>The overview gives the basic understanding. <strong>The content helps the user move forward</strong>. That's how you win.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-ai-overviews-mean-for-seo-going-forward"><span class="sec-n" aria-hidden="true">09</span>What AI Overviews mean for SEO going forward</h2>
<p>AI Overviews are a visible signal that <strong>search is changing from directing users toward information to helping users understand information immediately.</strong> The first answer increasingly happens inside the results page itself, which means content that only exists to repeat basic explanations becomes easier to replace.</p>
<p><strong>What remains valuable is content that helps users move forward once understanding begins.</strong> When summaries answer the first question, the role of content shifts toward context, application, and decision-making. The opportunity is the next step.</p>
<p><strong>Search is moving toward understanding first and decision second</strong>. Sites that adapt to that shift by focusing on clarity, usefulness, and structure will not lose visibility. They become more important, because they provide what summaries cannot: depth, perspective, and progression after the answer.</p>
<p>SEO <strong>is becoming more aligned with what it was always supposed to reward</strong>. Create content that genuinely helps people solve problems and move forward. That's how you win.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-ai-overviews"><span class="sec-n" aria-hidden="true">10</span>Questions people ask about AI Overviews</h2>
<h3>What is an AI Overview in Google Search?</h3>
<p>An AI Overview is a generated summary that appears at the top of some search results and combines information from multiple sources to answer informational or complex queries directly within Google.</p>
<h3>Do AI Overviews reduce website traffic?</h3>
<p>They can reduce clicks for early-stage informational queries because some questions are resolved directly in search, but they can also increase visibility and shift clicks toward later stages of the decision process.</p>
<h3>Can websites still benefit from AI Overviews?</h3>
<p>Yes. Pages that provide clear explanations, strong context, and logical next steps are more likely to be referenced or visited after users move beyond initial understanding.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How I structured my old site for search</title>
    <link>https://haydenschuster.com/writing/building-a-search-system/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/building-a-search-system/</guid>
    <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
    <description>The site architecture behind the WordPress version of this site, written ten days after launch: pillars, menus, URLs, redirects, breadcrumbs, speed.</description>
    <content:encoded><![CDATA[<p>When I built this site, I wasn't trying to be clever. <strong>I was trying to be <a href="https://haydenschuster.com/writing/search-behavior/">clear</a>.</strong></p>
<p>I know that good sites are all about <a href="https://haydenschuster.com/writing/content-strategy/">site architecture</a>, structure, and intent. <strong>It's all about designing a <a href="https://haydenschuster.com/systems/">scalable system.</a></strong></p>
<p>So, I built my new site around one core question: <strong>Does this make the site easier to use and easier to crawl?</strong></p>
<p>If we're looking in the mirror, my old site didn't represent the caliber of work I'm capable of. It was time to lock in and use my skills to better represent who I am and what I'm pursuing. <strong>It's time to walk the walk.</strong></p>
<p>Today marks Day 10 of the new site. It's still an infant. In one of my first posts, <strong>I'm breaking down the exact logic I used for launch</strong>.</p>
<p>It's a work in progress, and I'm likely tweaking the code as you read this (sorry).</p>
<h2 id="the-decisions-i-made-at-launch"><span class="sec-n" aria-hidden="true">01</span>The decisions I made at launch</h2>
<ul>
<li><strong>Consolidation</strong>. Moved from multiple fragmented presences into one focused site with a clear purpose</li>
<li><strong>Separation</strong>. The blog exists to educate while the portfolio exists to prove outcomes, keeping intent clear</li>
<li><strong><a href="https://haydenschuster.com/writing/content-strategy/">Structure</a></strong>. The site is built to scale naturally as more content, case studies, and systems are added over time</li>
<li><strong>Let go.</strong> Intentionally retired older content from my past that no longer fits, instead of forcing unnecessary redirects</li>
<li><strong><a href="https://haydenschuster.com/writing/search-behavior/">Clarity</a>.</strong> Every content and structural decision prioritizes clarity</li>
<li><strong>Mobile.</strong> Treating mobile compatibility as a primary design constraint, using selective design choices</li>
<li><strong>Usability.</strong> Added practical usability features such as dark mode, a top-page button, interactive blog elements, audio, video, etc.</li>
<li><strong><a href="https://haydenschuster.com/writing/technical-seo/">Technicals</a>.</strong> Strong technical foundations across literally everything I could think of</li>
<li><strong>Pillar pages</strong>. Established 8 stable blog pillar categories and 6 portfolio pillar categories to anchor the site.</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-i-consolidated-everything-onto-one-site"><span class="sec-n" aria-hidden="true">02</span>Why I consolidated everything onto one site</h2>
<p>Before this site, my work lived in too many places. Different pages, different focuses, and no single source of truth. I had a linktree (why, dumb, I was younger…), I had a separate domain for Rose City Marketing, etc. I consolidated everything into one source of truth because I wanted:</p>
<ul>
<li><strong>One brand</strong> instead of fragments</li>
<li><strong>One domain building authority</strong> instead of several weaker ones</li>
<li><strong>One clear path</strong> from learning to proof to contact</li>
</ul>
<p>That consolidation immediately simplified decision-making. It also made internal linking easier and reduced content overlap. I think it helps make the site feel more intentional instead of patched together.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-think-about-navigation"><span class="sec-n" aria-hidden="true">03</span>How I think about navigation</h2>
<p>Navigation was never about listing everything I offer. It was about <strong>guiding people based on intent.</strong></p>
<p>I designed navigation so someone could answer three questions quickly:</p>
<ul>
<li>What do I do</li>
<li>Where can I learn more</li>
<li>How do I see proof</li>
</ul>
<p>You can see my structure right now in my menu:</p>
<ul>
<li><strong>Home</strong></li>
<li><strong>About</strong></li>
<li><strong>Portfolio</strong>: Portfolio Pillar Pages (eliminated subcategory pages on mobile)</li>
<li><strong>Blog</strong>: Blog Pillar Pages, Blog Posts (eliminated subcategory pages on mobile)</li>
<li><strong>Primary CTA</strong></li>
</ul>
<p>I kept top-level navigation minimal and predictable. I avoided clever labels. The footer handles secondary pages and supporting content, so the main menu stayed clean.</p>
<p>I also thought about pathways. <strong>Someone researching SEO takes a different path than someone ready to hire.</strong> The site supports both without forcing either.</p>
<p>It's mobile optimized, has dark mode, has a CTA to my LinkedIn account, and has a neon green link right to my blog under my name. The mobile nav was a pain in my behind, to put it nicely. Still not very good. Ugh.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-handled-old-content-301-redirects-and-letting-pages-go"><span class="sec-n" aria-hidden="true">04</span>How I handled old content, 301 redirects, and letting pages go</h2>
<p><strong>I do not automatically redirect every page from an old site just because it exists.</strong> Before using a 301 redirect, I look at whether the content still has a clear purpose and whether it actually supports what the site is trying to do now. If a page does not fit the current structure, does not align with user intent, or never moved the needle, <strong>I let it fizzle out instead of forcing it into the new site.</strong></p>
<p>I used free WordPress plugins for this. Super easy to download and use.</p>
<p><strong>When I do use 301 redirects, they are intentional.</strong> I map old URLs to the most relevant current page, not the closest match by keyword. Redirects exist to preserve value and clarity, not to inflate page counts or confuse search engines. If there is no true equivalent, I would rather return a clean 404 than create a misleading redirect.</p>
<p><strong>For example,</strong> on my old site, I had personal blog content. Moving forward, my writing focus is within the SEO industry exclusively. If I write personal stuff in the future, that will be kept somewhere else. That's why I'm okay letting those blog posts fizzle.</p>
<p><strong>This approach keeps the site focused, prevents outdated content from diluting relevance, and makes it easier for modern search systems to understand what still matters.</strong> Not every page deserves to survive, and removing what no longer serves the site is part of maintaining a healthy structure.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-handle-page-speed"><span class="sec-n" aria-hidden="true">05</span>How I handle page speed</h2>
<p>I treat page speed as a usability problem before an SEO metric. <strong>Pages need to load quickly</strong> so people can read, scroll, and interact without friction. I focus on removing what slows pages down instead of stacking performance plugins or obsessing over perfect scores.</p>
<p>That means keeping layouts lightweight, limiting scripts to what actually serves a purpose, compressing images, and avoiding unnecessary third-party tools. If something adds visual flair but hurts load time or readability, it does not stay (usually, I'm weak for my own site). The goal is a fast, stable experience that works well on real devices, not just in testing tools.</p>
<p>Despite the advice, it hurts me to go into <a href="https://pagespeed.web.dev/">PageSpeed Insights</a> right now. Trying to improve. I have work to do. As of 2/6/26 my site is sitting at 6.5s FCP and 10.4s LCP on mobile. This will improve as I solidify my new site.</p>
<h3>My current strategy for improving speed on my WordPress site</h3>
<ul>
<li><strong>AI Diagnostics:</strong> Plug PageSpeed reports into AI to get instant fix-it lists</li>
<li><strong>Selective Loading:</strong> Disable specific scripts and plugins on pages that don't need them (lazy load, for example)</li>
<li><strong>Mobile Blocking:</strong> Hide heavy design elements for mobile users to save bandwidth</li>
<li><strong>Modern Images:</strong> Deliver every image in AVIF or WebP for faster loading</li>
<li><strong>Server Caching:</strong> Use advanced server-side caching to serve pages instantly</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="content-built-around-clear-user-intent"><span class="sec-n" aria-hidden="true">06</span>Content built around clear user intent</h2>
<p><strong>I treat content as a way to follow <a href="https://haydenschuster.com/writing/search-behavior/">user intent</a> as closely as possible. Every page exists to answer a specific question or support a clear next step</strong>, and anything that creates confusion gets removed. I try to avoid mixing intents or forcing extra topics onto a page just to make it longer, but I'm still guilty of this, as we all are. Trying to get better.</p>
<p>When done properly, it keeps the message crystal clear for people and makes it easier for <a href="https://haydenschuster.com/writing/modern-search/">modern search systems</a> to understand exactly what each page is about. The goal is alignment, not volume, so the content stays focused, readable, and easy to interpret.</p>
<p>This is <em><strong>ESPECIALLY</strong></em> true for my initial pillar pages, where user intent is hugely monumental. Blog posts can mix a little, but pillar pages need to stand firm.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-i-use-breadcrumbs"><span class="sec-n" aria-hidden="true">07</span>Why I use breadcrumbs</h2>
<p>I added breadcrumbs site-wide because people get lost on content-heavy sites. <strong>Breadcrumbs give context without clutter</strong>, and also help the algorithms understand intent.</p>
<p>They help readers understand where they are in the site hierarchy, especially on blog posts and portfolio pages. They also reinforce structure for search engines by clearly showing page relationships.</p>
<p>I treat <strong>breadcrumbs as support, not decoration.</strong> They appear where hierarchy matters and stay out of the way elsewhere.</p>
<p>I kept breadcrumbs normal on main pages, but eliminated the current &quot;title&quot; breadcrumb for posts, as these can be long and they just repeat the title directly below. Messy with no real value, cleaned up.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-i-keep-url-structure-simple-and-predictable"><span class="sec-n" aria-hidden="true">08</span>Why I keep URL structure simple and predictable</h2>
<p><strong>I keep URL structure boring on purpose.</strong> URLs exist to describe where a page lives and what it is about, not to be clever or over-optimized. When someone looks at a URL, they should immediately understand the type of content they are landing on.</p>
<p><strong>For pillar pages, I use short, descriptive paths that reflect hierarchy.</strong></p>
<ul>
<li>Blog Index: <strong>/seo-blog/</strong>
<ul>
<li>A blog pillar example: <strong>/seo-blog/modern-search-systems/</strong></li>
</ul>
</li>
<li>Portfolio Index: <strong>/portfolio/</strong>
<ul>
<li>A portfolio pillar example: <strong>/portfolio/modern-search-and-ai-driven-discovery/</strong></li>
</ul>
</li>
<li>Standalone pages example: <strong>/resume/</strong></li>
</ul>
<p>Individual posts currently include dates, like <strong>/2026/01/28/2026-auto-seo-trends-to-take-advantage-of/</strong>.</p>
<p><strong>That structure is a limitation of my WordPress plan, not a strategic choice.</strong> Even so, the slug remains descriptive and intent-focused, which is what matters most. If the platform changes in the future, I would simplify blog URLs further, but I do not let this constraint distort how content is written or organized. I also <strong>de-indexed date archive pages,</strong> 'cause it gets weird if I publish multiple posts in one day.</p>
<p><strong>Overall, the structure is and will stay consistent, especially as the site expands.</strong> Pillars are clean and permanent. H1 intent and most important keywords show up. Supporting content lives where people expect it. That consistency makes navigation easier for users and makes it clearer for modern search systems to understand how pages relate to each other.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-i-split-the-seo-blog-and-the-seo-portfolio"><span class="sec-n" aria-hidden="true">09</span>Why I split the SEO blog and the SEO portfolio</h2>
<p>I separated the <a href="https://haydenschuster.com/writing/">SEO Blog</a> and the <a href="https://haydenschuster.com/portfolio/">SEO Portfolio</a> because they serve completely different jobs.</p>
<p><strong>The blog exists to educate.</strong> It explains concepts, processes, and decisions. It attracts people earlier in their search journey.</p>
<p><strong>The portfolio exists to prove results.</strong> It shows outcomes, not theories.</p>
<p>Mixing those two creates confusion. Separating them made each section stronger and easier to navigate. This was a huge priority site-wide.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-structure-the-seo-blog"><span class="sec-n" aria-hidden="true">10</span>How I structure the SEO blog</h2>
<p>I treat the blog like a <strong>library, not a timeline.</strong></p>
<p>I used a small number of stable pillar categories that represent broad SEO topics. These category pillars act as <strong>anchors and are rarely changed.</strong> You can see these pages in my navigation.</p>
<p>I have my central &quot;<strong>single post</strong>&quot; template, where I add relevant links above and below my individual posts. I also have a &quot;<strong>main blog template</strong>,&quot; which controls my blog index page. This helps, so I'm not starting from scratch every time and can focus on the content itself.</p>
<p><strong>Tags stay secondary.</strong> I use them to connect related ideas across categories, not to replace anything. That keeps tag pages from becoming thin or messy.</p>
<p><strong>Blog templates stay (relatively) consistent</strong>, so readers always know what to expect. Ongoing blog posts continue to follow the same structure, so the library grows without becoming chaotic.</p>
<p><strong>I also made sure to permanently de-index category and tag archive pages that are primarily for breadcrumb organization.</strong> I don't want these competing with my main pillar category pages. Important note.</p>
<p><strong>Search intent is a priority.</strong></p>
<p>Trying to follow my own advice about informational, transactional, navigational, and commercial: <a href="https://haydenschuster.com/writing/search-intent/">the 4 types of search intent</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-interactive-elements-i-added"><span class="sec-n" aria-hidden="true">11</span>What interactive elements I added</h2>
<p>Throughout the site, and especially on my blog, I added some interactive elements like videos, audio, emoji reactions, a comment section, likes, share, etc. to increase community involvement. This is supposed to be fun!</p>
<p>For example, on my homepage, I added an explainer video about what my website is about. On my blog, I added a conversation (it's AI and kind of cheesy, but also insightful and ranks for conversational style keywords). On individual posts, I added emoji reactions, comments (that I need to approve before going live, of course), social share elements, related posts, and that type of stuff. For pillar pages, I made sure to add loop queries of my posts organized by category. Dark mode widget. Back to top widget. etc…</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-structure-my-seo-portfolio"><span class="sec-n" aria-hidden="true">12</span>How I structure my SEO portfolio</h2>
<p>Portfolio pages focused on <strong>clarity and scanning.</strong></p>
<p>I organized work by <strong>service type and outcome</strong> rather than by date. This made it easier for visitors to find examples that matched their situation.</p>
<p><strong>Each portfolio item stayed concise.</strong> It explained the problem, the work, and the result without unnecessary storytelling. Where helpful, pages linked back to relevant blog content for deeper explanation.</p>
<p>I will also be adding case studies in the next few weeks, and just recently added my <a href="https://haydenschuster.com/log/">SEO Decision log</a>, to help with credibility.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-use-pillar-pages"><span class="sec-n" aria-hidden="true">13</span>How I use pillar pages</h2>
<p>Pillar pages are the backbone of the site.</p>
<p><strong>A huge priority of mine is to keep the pillar page content easy to understand for all. I try to simplify things, with internal links to more complex topics. This helps with usability.</strong></p>
<p><strong>For the blog, pillar pages act as topic hubs</strong>. Each pillar covers a broad subject and is linked to related posts that go deeper. This helps readers explore without guessing and helps search engines understand topical relationships.</p>
<p><strong>For the portfolio, pillar pages group proof.</strong> Instead of isolated case studies, related work lived under a shared hub. This makes results easier to compare and reinforces expertise in specific areas.</p>
<p>I still update pillar pages as new content is published, so they stay current and useful.</p>
<p>For all content I create, I make sure to link back to my hub pages whenever relevant.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-handle-on-page-seo-structure"><span class="sec-n" aria-hidden="true">14</span>How I handle on-page SEO structure</h2>
<p>I treat <a href="https://haydenschuster.com/writing/technical-seo/">on-page SEO</a> like a checklist, not a creative experiment.</p>
<p>Every page has:</p>
<ul>
<li>One clear H1 title that matches intent</li>
<li>Logical H2s that map the main sections</li>
<li>H3s/4s only when they add clarity</li>
<li>Title Tag/Meta Descriptions that fit intent (also for social if needed)</li>
<li>Image with alt tags (at least with the main image, I can get lazy on some within the content lol)</li>
<li>Pillar page links when appropriate</li>
<li>Internal links to content that aligns</li>
<li>Widgets like dark mode/up to top of page that help with usability</li>
<li>Search feature on every template</li>
</ul>
<p>I review title tags and meta descriptions manually. I add alt text to my images. I add captions to my videos. I add social share content to pages that need it. I add excerpts when relevant. I do each of these to be accurate first and compelling second. I avoided duplicates and made sure metadata reflects the actual content on the page.</p>
<p>That consistency makes pages easier to scan and easier to maintain long-term, so happy with this.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-i-added-faqs-to-most-pages"><span class="sec-n" aria-hidden="true">15</span>Why I added FAQs to most pages</h2>
<p>FAQs solve real problems.</p>
<p>They answer objections I hear repeatedly or in the industry. They reduce friction before contact. They also <strong>capture long-tail searches naturally</strong> without forcing keywords into the main copy.</p>
<p><strong>I keep FAQs focused and limited.</strong> They support the page instead of bloating it. This approach continues on new pages where it makes sense.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-use-screaming-frog-and-ahrefs"><span class="sec-n" aria-hidden="true">16</span>How I use Screaming Frog and Ahrefs</h2>
<p>Content alone does not <a href="https://haydenschuster.com/writing/technical-seo/">fix technical issues</a>. That's why I ran audits.</p>
<p>With Screaming Frog, I check things like:</p>
<ul>
<li>Broken links</li>
<li>Redirect chains</li>
<li>Missing or duplicate titles and H1s (lots of tools for this though, for individual pages I like the Detailed SEO Extension)</li>
<li>Click depth and orphaned pages</li>
</ul>
<p>With Ahrefs, I monitor overall site health and recurring technical patterns. Plus keyword stuff and content gaps.</p>
<p>These audits help me catch structural problems early and keep the site clean as it grows. It's still very new as of this post!!</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="which-free-wordpress-plugins-i-use"><span class="sec-n" aria-hidden="true">17</span>Which free WordPress plugins I use</h2>
<p><strong>Note:</strong> This is for my &quot;personal account tier, not business tier&quot;. Limited options.</p>
<h3>SEO and performance</h3>
<ul>
<li><strong>Yoast SEO</strong>: The first free all-in-one SEO plugin I used. Handles titles, meta descriptions, XML sitemaps, and readability checks without overwhelming you. Obviously awesome. You know this already.</li>
<li><strong>301 Redirects</strong>: Makes managing redirects dead simple. Essential when consolidating sites or letting old content go.</li>
<li><strong>ShortPixel Image Optimizer</strong>: Automatically compresses images to WebP/AVIF. Set it and forget it, huge help for page speed.</li>
<li><strong>WP-Optimize</strong>: Cleans database, compresses images, and caches pages. One plugin doing multiple speed jobs. I use ShortPixel and WP-Optimize together for images to get free tier complete coverage.</li>
</ul>
<h3>User experience</h3>
<ul>
<li><strong>Darkify</strong>: Added dark mode with one click. Modern users expect it, this delivers it without custom code. This might be my favorite one honestly, so cool!</li>
<li><strong>LuckyWP Table of Contents</strong>: Auto-generates TOCs for long posts. Readers can jump to sections, Google loves the structure. Found out about this one way too late 🙂</li>
<li><strong>Instant Emoji Reactions</strong>: Lets readers react to posts quickly. Low-friction engagement that actually gets used. A lil fun.</li>
</ul>
<h3>Content and layout</h3>
<ul>
<li><strong>TablePress</strong>: Creates clean, sortable tables without fighting with HTML. Perfect for comparison charts and data.</li>
<li><strong>Gutenberg</strong>: WordPress's block editor. Once you learn it, building pages is fast and flexible.</li>
<li><strong>a3 Lazy Load</strong>: Images load as users scroll. Speeds up initial page load without sacrificing content.</li>
</ul>
<h3>Forms and engagement</h3>
<ul>
<li><strong>WPForms Lite</strong>: Contact forms that actually work. Drag-and-drop builder, spam protection included.</li>
<li><strong>Crowdsignal Polls &amp; Ratings</strong>: Quick polls and ratings for reader interaction. Good for &quot;which topic next?&quot; engagement.</li>
</ul>
<h3>Technical essentials</h3>
<ul>
<li><strong>Site Kit by Google</strong>: Connects Analytics, Search Console, and PageSpeed Insights in one dashboard. Pretty sick</li>
<li><strong>Jetpack</strong>: but only for security + performance, not using for their marketing tools. The free version covers backups and basic security.</li>
<li><strong>Akismet Anti-spam</strong>: Stops comment spam</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-keep-the-site-simple-as-it-scales"><span class="sec-n" aria-hidden="true">18</span>How I keep the site simple as it scales</h2>
<p><strong>I did not build a system that needs constant babysitting.</strong></p>
<p>My ongoing approach is straightforward:</p>
<ul>
<li>New pages follow existing templates</li>
<li>Categories rarely change</li>
<li><strong>Pillar pages update automatically when new content is added</strong></li>
<li>Technical crawls happen on a regular schedule</li>
</ul>
<p>Simplicity makes consistency possible.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-every-decision-came-back-to"><span class="sec-n" aria-hidden="true">19</span>What every decision came back to</h2>
<p>I built this site by <strong>removing friction,</strong> not adding features. Every decision comes back to <strong>clarity</strong>. I want people to understand what I do, find what they need quickly, and move through the site without thinking about structure at all. I hope that this goal is a success. <strong>I still have a lot to learn.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-site-architecture-and-seo"><span class="sec-n" aria-hidden="true">20</span>Questions people ask about site architecture and SEO</h2>
<h3>How many categories should a blog have?</h3>
<p>As few as possible while still being useful. Categories should represent major topics, not individual ideas.</p>
<h3>How often should technical SEO audits be run?</h3>
<p><strong>For a growing site, quarterly is usually enough.</strong> More often, if content is published frequently.</p>
<h3>When should I use a 301 redirect instead of letting a page go?</h3>
<p>I use a 301 redirect only when there is a clear, relevant replacement. If a page never served a real purpose or no longer aligns with the site, letting it return a clean 404 is often the better choice.</p>
<h3>Should I update old content or publish something new?</h3>
<p>If the intent already exists on the site, updating and improving content is usually better. New pages should only be created when they serve a distinct purpose.</p>
<h3>How do I avoid keyword cannibalization in site structure?</h3>
<p>I assign one clear intent to each page and avoid creating multiple pages that try to answer the same question in slightly different ways.</p>
<h3>Should category and tag pages be indexed?</h3>
<p>Only if they provide real value on their own. If they exist mainly for organization, I noindex them to avoid thin or competing pages.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Building repeatable SEO systems for enterprise website launches</title>
    <link>https://haydenschuster.com/writing/enterprise-launch-seo-systems/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/enterprise-launch-seo-systems/</guid>
    <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
    <description>How one reusable SEO system carried five enterprise site launches: shared templates, index rules, launch checklists, and devs and PMs in early.</description>
    <content:encoded><![CDATA[<p>Enterprise site launches get messy fast. When you combine large inventories, location-heavy page structures, and multiple teams shipping simultaneously, SEO problems tend to compound instead of staying isolated. That's why it's essential to create a system.</p>
<p>I led SEO across five <a href="https://haydenschuster.com/writing/enterprise-seo/">enterprise</a> site launches for different operating companies within one large company.</p>
<h2 id="how-i-aligned-teams-on-shared-seo-patterns"><span class="sec-n" aria-hidden="true">01</span>How I aligned teams on shared SEO patterns</h2>
<p>To make this work in practice, I partnered early with developers and product managers to <strong>align on a simple, shared set of SEO patterns</strong>:</p>
<ul>
<li>Worked early with developers and product managers to <strong>align on basic SEO patterns</strong> before builds were finalized</li>
<li>Helped define shared expectations around <strong>site structure, breadcrumbs, internal linking, and page templates</strong> to take advantage of <a href="https://haydenschuster.com/writing/modern-search/">modern search systems</a></li>
<li>Partnered with devs on how <strong>content, images, and reusable components should support SEO</strong> without adding complexity</li>
<li>Agreed on consistent handling of <a href="https://haydenschuster.com/writing/technical-seo/">technical SEO</a> best practices for <strong>indexing, robots.txt, XML sitemaps, and canonicals</strong></li>
<li>Focused on keeping things <strong>reusable across launches while allowing flexibility for different operating companies</strong></li>
</ul>
<p><strong>While the specifics varied by operating company, the underlying challenges were consistent.</strong> Large inventories, layered page types, complex location structures, and legacy URLs that still carried value. Instead of approaching each launch as a fresh SEO effort, I focused on building a shared system that could be reused and adjusted as needed. That shift made it easier to address issues earlier in the process and avoid the same problems surfacing after every launch.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-enterprise-launches-break-seo"><span class="sec-n" aria-hidden="true">02</span>Why enterprise launches break SEO</h2>
<p>At scale, SEO problems don't live on single pages. <strong>They live in templates and logic.</strong></p>
<p>One small mistake in a category template or URL rule can affect thousands of pages.</p>
<p>When each launch is treated as a one-off, those mistakes keep repeating. Don't waste time, hit the source! This has to be collaborative between teams, or else you'll fail.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-repeatable-seo-systems-look-like"><span class="sec-n" aria-hidden="true">03</span>What repeatable SEO systems look like</h2>
<p>It came down to agreeing on a few core patterns and sticking to them.</p>
<p>Things like:</p>
<ul>
<li><strong>Consistent and SEO-optimized templates for similar page types</strong>
<ul>
<li>Pages that served the same purpose were built from the same template. Category pages followed one structure. Model pages followed another. Location pages did the same. This made <a href="https://haydenschuster.com/writing/search-behavior/">page behavior</a> predictable for both users and search engines, reduced edge cases, and helped avoid situations where similar pages competed with each other simply because they were built differently.</li>
</ul>
</li>
<li><strong>Clear rules for titles, headings, meta titles/descriptions, and internal link structure</strong>
<ul>
<li>We aligned on how titles and headings should be auto-generated as a baseline and what information they needed to include. Meta titles and descriptions followed simple rules so they stayed descriptive without becoming duplicated or bloated. Internal links followed consistent patterns, so important pages were easy to find, while less important or supporting pages didn't hurt us.</li>
</ul>
</li>
<li><strong>Shared logic for category, model, and location pages</strong>
<ul>
<li>Instead of reinventing these page types for each operating company, we used the same underlying logic and adjusted only where necessary. Category pages rolled up inventory the same way. Model pages followed the same hierarchy for the most part. Location pages used a consistent city and state structure, with localized inventory and widgets for differentiation. This kept the system scalable without forcing every site into an identical experience.</li>
</ul>
</li>
<li><strong>Guardrails to prevent near-duplicate pages from being created unintentionally</strong>
<ul>
<li>As inventory, filters, and locations expanded, it was easy for small variations to create near-duplicate pages. Guardrails helped prevent that through clear URL rules, canonical handling, and limits on how content variations were generated. The goal was to stop duplication from creeping in quietly at scale.</li>
</ul>
</li>
<li><strong>Baseline rules for which page types should be indexed/not indexed</strong>
<ul>
<li>Not every page needed to rank. We aligned on which page types were meant to be indexed and which existed only to support navigation or usability. That helped keep low-value or utility pages out of the index and ensured crawl and ranking signals stayed focused on the pages that actually mattered.</li>
</ul>
</li>
</ul>
<p>Once those patterns were set, teams didn't have to re-litigate SEO decisions on every launch.</p>
<h3>Pre-launch SEO checklist for each launch</h3>
<p>Most SEO issues are easier to prevent than fix. Before each launch, I focused on a short, repeatable checklist to catch systemic problems early and keep launches predictable.</p>
<ul>
<li><strong>URL structure and redirects reviewed:</strong> Confirmed final URL patterns, legacy URL mappings, and redirect logic to avoid broken links or equity loss at launch. Also took a look at breadcrumb structure and <a href="https://haydenschuster.com/writing/content-strategy/">thought creatively about site architecture</a> as a whole.</li>
<li><strong>Template behavior validated:</strong> Checked that category, model, and location templates rendered correctly, followed the agreed structure, and didn't introduce unexpected surprises.</li>
<li><strong>Indexing and crawl controls confirmed:</strong> Verified robots.txt rules, meta robots directives, and canonical game plan to ensure only intended page types were indexable.</li>
<li><strong>Pagination and filtering tested:</strong> Made sure pagination linked cleanly, filters didn't create crawl traps, and primary pages remained the clear SEO targets.</li>
<li><strong>Internal linking checked at scale:</strong> Reviewed how pages linked to each other across templates so key pages were discoverable without over-linking low-value URLs. Also helped document and fix any broken links site-wide and clean up links that didn't make sense for page intent.</li>
<li><strong>Sitemaps validated:</strong> Ensured sitemaps included the right page types, excluded non-indexable URLs, and reflected the final site structure.</li>
<li><strong>Metadata rules spot-checked:</strong> Confirmed title tags, headings, and meta descriptions followed agreed rules and scaled cleanly across page types.</li>
<li><strong>Kept eyes on production stuff:</strong> Made sure staging and production behaved the same from a crawl and indexing perspective to avoid launch-day surprises.</li>
</ul>
<h3>Post-launch SEO checklist for each launch</h3>
<ul>
<li><strong>Crawl and indexation monitored:</strong> Confirmed priority pages were being crawled and indexed as expected after launch.
<ul>
<li>Note: big one is submitting sitemap to GSC ASAP, don't want to waste any time</li>
</ul>
</li>
<li><strong>404s and broken links reviewed:</strong> Checked for unexpected errors caused by redirects, internal links, or missed legacy URLs.</li>
<li><strong>Robots.txt and indexing rules checked:</strong> Ensured no accidental blocks or noindex rules were applied in production.</li>
<li><strong>Canonical behavior spot-checked:</strong> Verified canonical tags resolved correctly and pointed to the intended URLs.</li>
<li><strong>Pagination and filters observed:</strong> Confirmed pagination and filtering did not create new crawl paths or indexed variants.
<ul>
<li>Screaming Frog and Ahrefs are both good for this</li>
</ul>
</li>
<li><strong>Sitemaps checked:</strong> Ensured sitemaps reflected live URLs and excluded non-indexable pages</li>
<li><strong>Internal linking reviewed:</strong> Confirmed key pages maintained strong internal links after launch.
<ul>
<li>Ahrefs audit is my fav for internal linking stuff</li>
</ul>
</li>
<li><strong>Performance and page speed monitored:</strong> Watched for regressions introduced by new templates, scripts, or plugins.
<ul>
<li>PageSpeed Insights is great for this</li>
</ul>
</li>
<li><strong>Search visibility tracked:</strong> Monitored early ranking and visibility signals for signs of systemic issues.</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-working-with-devs-and-pms-mattered-most"><span class="sec-n" aria-hidden="true">04</span>Why working with devs and PMs mattered most</h2>
<p>The biggest difference came from <strong>getting involved early in the design process</strong> and staying close to developers and product managers.</p>
<h3>Developers</h3>
<p>Instead of flagging SEO issues after launch, requirements were built into templates and components from the start.</p>
<p>That helped avoid:</p>
<ul>
<li>Duplicate or near-duplicate pages</li>
<li>Broken pagination and filtering</li>
<li>Pages that were crawlable but not meant to be indexed</li>
<li>Category and model pages overlapping unintentionally</li>
<li>Location pages differing only by minor text changes</li>
</ul>
<p>Fixing these things in code once is much easier than fixing them across thousands of URLs later.</p>
<h3>Product managers</h3>
<p>PMs helped balance SEO needs with real delivery timelines.</p>
<p>That made it easier to:</p>
<ul>
<li>Help align important business objectives to the SEO system</li>
<li>Decide what had to ship at launch</li>
<li>Avoid late changes that could hurt crawlability</li>
<li>Keep SEO aligned with key business goals</li>
</ul>
<p>SEO worked best when it was part of planning, not a last-minute review.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="a-quick-note-on-the-cms"><span class="sec-n" aria-hidden="true">05</span>A quick note on the CMS</h2>
<p><strong>The CMS was WordPress.</strong> It mattered less than how it was used.</p>
<p>Standard templates and controlled content fields made it easier to keep pages consistent, even with multiple teams publishing content. I LOVE WORDPRESS. Let me repeat, I love wordpress.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="pre-launch-is-where-most-problems-were-solved"><span class="sec-n" aria-hidden="true">06</span>Pre-launch is where most problems were solved</h2>
<p>Most of the real SEO work happened before launch.</p>
<p>That included:</p>
<ul>
<li>Reviewing URL structures and redirects</li>
<li>Fixing broken links, 404 errors, messy structure, etc.</li>
<li>Checking internal linking and crawl depth</li>
<li>Making sure similar pages behaved the same way</li>
</ul>
<p>Catching any issues early and cleaning them up reduced risk and cut down on post-launch cleanup.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="search-intent-remained-high-priority-throughout"><span class="sec-n" aria-hidden="true">07</span>Search intent remained high priority throughout</h2>
<p>Never lost sight of which pages were for <a href="https://haydenschuster.com/writing/search-intent/">what type of search</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="post-launch-watching-for-issues"><span class="sec-n" aria-hidden="true">08</span>Post-launch: watching for issues</h2>
<p>After launch, the focus was on making sure things stayed stable.</p>
<p>That meant:</p>
<ul>
<li>Watching for crawl errors and broken links</li>
<li>Checking index coverage and visibility trends</li>
<li>Keeping an eye on performance and page speed</li>
</ul>
<p>This involved in-depth and consistent SEO audits (Ahrefs, GSC, GA4, Screaming Frog). Because the foundations were consistent, issues were easier to spot and fix. The goal here is to look for early patterns in the <a href="https://haydenschuster.com/writing/measurement/">data and track them</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-approach-changed"><span class="sec-n" aria-hidden="true">09</span>What this approach changed</h2>
<p>Across multiple launches, this approach:</p>
<ul>
<li>Reduced repeated SEO issues</li>
<li>Kept crawl and indexation more stable</li>
<li>Made launches less stressful for everyone involved</li>
</ul>
<p>Teams spent less time reacting and more time improving.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-made-these-launches-predictable"><span class="sec-n" aria-hidden="true">10</span>What made these launches predictable</h2>
<p>Enterprise SEO is about setting up systems that scale.</p>
<p>The biggest wins came from:</p>
<ul>
<li><strong>Working closely with developers and PMs</strong></li>
<li><strong>Focusing on templates and patterns, not one-off fixes</strong></li>
<li><strong>Doing more work before launch and less after</strong></li>
</ul>
<p>That's what made these launches more predictable and easier to support long-term.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Search Console as a visibility dashboard</title>
    <link>https://haydenschuster.com/writing/search-console-visibility-dashboard/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/search-console-visibility-dashboard/</guid>
    <pubDate>Tue, 03 Feb 2026 00:00:00 GMT</pubDate>
    <description>A Search Console setup for reporting visibility: export day-by-day data, find the trends, then read the Performance, Pages and Indexing reports.</description>
    <content:encoded><![CDATA[<p>Google Search Console is usually treated as a problem-fixing tool. Indexing errors. Coverage issues. Manual actions.</p>
<p>That approach misses the bigger opportunity. <strong>For client reporting, Google Search Console is one of the best tools you have for explaining search visibility in plain language.</strong> It shows what Google is showing, how that changes over time, and where performance is improving or slipping. <strong>It's my SEO measurement go-to!</strong></p>
<p>This guide explains how to use <a href="https://search.google.com/search-console/about">Google Search Console</a> as a visibility dashboard for client reports, not just a technical alert system.</p>
<h2 id="what-clients-need-from-an-seo-visibility-report"><span class="sec-n" aria-hidden="true">01</span>What clients need from an SEO visibility report</h2>
<p>A good client-facing SEO report should answer three simple questions:</p>
<ul>
<li>What pages and topics are getting visibility</li>
<li>Whether that visibility is growing or declining</li>
<li>Where Google seems confused or uncertain</li>
</ul>
<p>Search Console already answers all three. <strong>The key is pulling the right views and explaining them clearly.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="my-gsc-productivity-hack-day-by-day-data-over-long-windows"><span class="sec-n" aria-hidden="true">02</span>My GSC productivity hack: day-by-day data over long windows</h2>
<p>Instead of relying only on summary metrics, this approach <strong>pulls day-by-day organic visibility data over longer windows (monthly, quarterly, semi-annual, or yearly) to surface trends, inflection points, and opportunities that are invisible</strong> in rolled-up reports.</p>
<h3>Step 1: Pull GSC data</h3>
<ul>
<li>Go to Google Search Console, open the Performance report</li>
<li>Set the date range to pull day-to-day data from the exact window you need (monthly, quarterly, semi-annual, yearly, custom)</li>
<li>Export the report: use the export button at the top to pull data into Google Sheets or Excel</li>
<li>Organize the data how you'd like, or add more data if you are doing this from multiple tools (GA4, Ahrefs, etc.)</li>
</ul>
<h3>Step 2: Analyze with AI</h3>
<ul>
<li>Paste the day-by-day dataset into an AI tool</li>
<li>Prompt it to analyze organic SEO visibility trends across the full timeframe</li>
<li>Ask it to identify patterns, spikes, drops, and sustained movements</li>
<li>Have it calculate percentage increases and decreases between meaningful periods</li>
<li>Tip: The more you prompt for what you want, and the more you add as far as specific goals, expectations, and things you're looking for, the better the result will be.</li>
</ul>
<h3>Step 3: Control the result</h3>
<p><strong>Specify whether the summary should be client-facing, internal, technical, or strategist-facing</strong>, depending on what you're using it for.</p>
<p>Note: Client-facing will focus on clear progress, wins, and great plain language.</p>
<h3>Why day-by-day data works</h3>
<ul>
<li><strong>Day-by-day data exposes momentum, volatility, and turning points</strong> that averages hide</li>
<li><strong>Longer windows</strong> reveal whether gains are durable or just short-term noise</li>
<li><strong>Percent change adds clarity and defensibility</strong> in conversations</li>
</ul>
<h3>Where day-by-day data helps</h3>
<ul>
<li>QBRs and executive readouts</li>
<li>Live client calls and stakeholder meetings</li>
<li>Compiling wins tied to specific actions or launches</li>
<li>Identifying problem areas early, before they show up in summary reports</li>
<li>Finding growth opportunities worth doubling down on</li>
</ul>
<p>Now, let's talk about each type of GSC report and how to use them.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="performance-report-your-main-visibility-chart"><span class="sec-n" aria-hidden="true">03</span>Performance report: your main visibility chart</h2>
<p><strong>The Performance report should be the foundation of most client reports.</strong></p>
<p>Impressions mean Google is showing your site. Clicks mean users are choosing it. The position shows how competitive that visibility is over time.</p>
<p><strong>For client reporting, focus on trends, not exact numbers.</strong></p>
<p>Pull pages with <strong>high impressions but low clicks</strong>. These pages are being shown in search, but users are not choosing them. This usually points to issues with titles, descriptions, or a mismatch between the page intent and the search intent.</p>
<p>Next, highlight <strong>pages where impressions are increasing.</strong> Even if clicks have not increased yet, this shows growing visibility and early momentum, which clients clearly understand as progress.</p>
<p>Pay close attention to pages where <strong>impressions decline before clicks drop.</strong> This is an early warning signal and helps explain traffic decreases before they happen.</p>
<p>Always <strong>group performance data by page rather than by keyword.</strong> Pages are easier for clients to understand and tell a clearer story, while keyword lists often create confusion.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="pages-report-which-urls-google-cares-about"><span class="sec-n" aria-hidden="true">04</span>Pages report: which URLs Google cares about</h2>
<p>The Pages report helps explain <strong>which URLs Google considers important</strong>.</p>
<p>Use this in reports to show pages that are <strong>gaining visibility unexpectedly</strong>, pages that <strong>lost visibility after a site change</strong>, and similar pages that perform very differently.</p>
<p><strong>When two similar pages behave differently, it is often internal linking, page placement, or structure.</strong> This helps move the client conversation away from &quot;we need more content&quot; and toward smarter site decisions.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="indexing-report-why-some-pages-don-t-show-up"><span class="sec-n" aria-hidden="true">05</span>Indexing report: why some pages don't show up</h2>
<p>Clients often ask <strong>why certain pages are not ranking.</strong> The Indexing report helps answer that.</p>
<p>Pull pages that are <strong>crawled but not indexed.</strong> This usually means Google does not see enough value or sees overlap with other pages.</p>
<p>Pull pages indexed that <strong>were not intentionally submitted.</strong> This can reveal discovery paths the site owner did not expect.</p>
<p>Watch <strong>big changes in indexed page counts.</strong> These often explain visibility shifts before traffic changes show up. You need to explain what Google is choosing not to show and why.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="experience-reports-ruling-out-performance-problems"><span class="sec-n" aria-hidden="true">06</span>Experience reports: ruling out performance problems</h2>
<p>Core Web Vitals and experience metrics are best used as <strong>supporting context in client reports.</strong></p>
<p>Use them to confirm that visibility drops are <strong>not caused by performance issues</strong>, show that new templates <strong>did not introduce instability</strong>, and separate content relevance problems from usability problems. Avoid framing these as pass or fail scores. Clients care more about consistency than perfection.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="time-comparisons-clients-understand"><span class="sec-n" aria-hidden="true">07</span>Time comparisons clients understand</h2>
<p>Time comparison is where many reports fall apart. <strong>Compare before and after major changes.</strong> Use the same pages across both time ranges. Avoid week-over-week views unless explaining short-term testing. Clients understand patterns. They do not need daily fluctuations.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="turning-search-console-into-a-client-ready-dashboard"><span class="sec-n" aria-hidden="true">08</span>Turning Search Console into a client-ready dashboard</h2>
<p>To use Search Console effectively for reporting, <strong>pull data regularly</strong>, not only when traffic drops.</p>
<p><strong>Combine Performance, Pages, and Indexing insights</strong>. Explain changes in visibility before explaining traffic. Use charts and simple language instead of SEO jargon. When framed correctly, <strong>Search Console tells a clear story about progress and priorities.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-gives-a-client-report"><span class="sec-n" aria-hidden="true">09</span>What this gives a client report</h2>
<p>Google Search Console is one of the <strong>clearest ways to explain SEO visibility results to clients.</strong> When you focus on impressions, page-level trends, and indexing signals, you can show how visibility is changing and why. That turns reports into explanations, not excuses, and builds trust over time.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How AI search finds and understands your content</title>
    <link>https://haydenschuster.com/writing/how-ai-search-understands-content/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/how-ai-search-understands-content/</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>What modern search systems need to understand a page, how AI snippets and expanded results pick content, and where most content fails AI discovery.</description>
    <content:encoded><![CDATA[<p>Modern search systems are designed to <strong>interpret, summarize, and <a href="https://haydenschuster.com/writing/content-strategy/">select content</a></strong> before a user ever clicks. AI-driven discovery has changed what it means to be visible, and many sites are still optimizing as if search engines only retrieve pages instead of understanding them.</p>
<h2 id="what-modern-search-systems-try-to-understand"><span class="sec-n" aria-hidden="true">01</span>What modern search systems try to understand</h2>
<p>Modern search systems do more than match keywords to pages. They attempt to understand:</p>
<ul>
<li>What a page is about</li>
<li>Who it is for</li>
<li>What problem it solves</li>
<li>How it relates to other information</li>
</ul>
<p><strong>This understanding is what powers AI-driven features like AI snippets, summaries, and expanded SERP layouts.</strong> If a system cannot confidently interpret your content, it is unlikely to surface it in these discovery surfaces.</p>
<h3>Why AI-driven discovery changes SEO fundamentals</h3>
<p>AI discovery shifts search from <strong>retrieval to interpretation.</strong></p>
<p>Instead of asking, &quot;Which page should rank?&quot; systems increasingly ask:</p>
<ul>
<li>Which content best explains this topic?</li>
<li>Which source can be summarized accurately?</li>
<li>Which page fits this query context right now?</li>
</ul>
<p>This means pages are no longer competing only for clicks. They are competing to be <strong>understood well enough to be reused</strong>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-ai-snippets-and-expanded-serp-layouts-are"><span class="sec-n" aria-hidden="true">02</span>What AI snippets and expanded SERP layouts are</h2>
<h3>AI snippets</h3>
<p><strong>AI snippets summarize information directly in search results.</strong> They pull from multiple sources and often answer the query without a click.</p>
<p>Instead of ranking a single page, search systems pull information from multiple sources and combine it into an answer. In many cases, the user gets what they need without clicking through to a website. These snippets are not simple excerpts. The system is interpreting the query, deciding what information is relevant, and synthesizing a response that fits the context of the search.</p>
<p>For your content to appear in AI snippets, <strong>clarity matters more than completeness.</strong></p>
<p>Pages that perform well here tend to share a few traits. They are <strong>clearly structured</strong>, with headings and sections that make the main idea easy to identify. They answer a <strong>specific question early and directly</strong>, without forcing the system to wade through background or mixed intent. They also <strong>avoid ambiguity</strong>. When a page tries to serve multiple audiences or hedge too much, it becomes harder to summarize cleanly.</p>
<p>Content that rambles or buries its point often gets skipped, even if it is accurate. It does <strong>not resolve intent efficiently</strong> enough for summarization.</p>
<p><strong>AI snippets favor content that is focused, direct, and easy to interpret.</strong> The easier it is for a system to understand what you are saying and why it matters, the more likely that content is to be used.</p>
<h3>What content needs to appear in AI snippets</h3>
<ul>
<li><strong>Be clearly structured</strong></li>
<li><strong>Answer a specific question quickly and cleanly</strong></li>
<li><strong>Avoid ambiguity or buried context</strong></li>
</ul>
<p>Pages that ramble or mix audiences are difficult to summarize and often ignored.</p>
<h3>Expanded SERP layouts</h3>
<p>Modern SERPs (Search Engine Results Pages) now include:</p>
<ul>
<li><strong>AI-generated summaries</strong></li>
<li><strong>Follow-up questions</strong></li>
<li><strong>Comparison blocks</strong></li>
<li><strong>Contextual refinement prompts</strong></li>
</ul>
<p><strong>Expanded SERP layouts refer to search results pages that no longer present information as a simple list of links</strong>. Instead, results are distributed across multiple visual and functional components such as:</p>
<p><em><strong>AI summaries, carousels, product grids, local packs, videos, images, and interactive elements.</strong></em></p>
<p>In these layouts, visibility is not limited to ranking first. Content can be surfaced, summarized, or referenced in several places on the page, each serving a different type of intent. A user might <strong>scan an AI summary</strong>, <strong>glance at a carousel</strong>, <strong>compare options in a grid</strong>, <strong>and only click if something feels relevant or trustworthy.</strong></p>
<p>This changes what it means to &quot;<strong>perform</strong>&quot; in search. Success is no longer just about driving traffic to a single page. It is about being present and legible across the surfaces where decisions are being shaped.</p>
<p>Expanded layouts also force search systems to rely more heavily on interpretation. The system has to decide not only which pages are relevant, but how to break content apart, where it fits visually, and how it relates to other results on the page. Pages that are <strong>clearly structured and tightly scoped are easier to reuse across these layouts.</strong></p>
<p>Content that depends on linear reading or buried context struggles here. <strong>When information cannot stand on its own, it is harder for the system to place it into a card, snippet, or comparison view.</strong> As a result, some pages may rank but remain invisible within the broader layout.</p>
<p>Expanded SERP layouts <strong>reward content that is clear.</strong> The more easily your content can be understood in pieces, the more opportunities it has to appear across modern search results, even when traditional clicks decline.</p>
<h3>What content needs to appear in expanded SERP layouts</h3>
<ul>
<li><strong>Anticipate related questions</strong></li>
<li><strong>Clearly separate concepts</strong></li>
<li><strong>Provide strong topical signals</strong></li>
</ul>
<p>Content that <strong>tries to do everything at once</strong> becomes harder to surface in these environments.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="where-most-content-fails-modern-discovery"><span class="sec-n" aria-hidden="true">03</span>Where most content fails modern discovery</h2>
<h3>Too much information, not enough meaning</h3>
<p>Many pages contain a lot of information but little clarity. AI systems struggle with content that:</p>
<ul>
<li>Mixes multiple intents</li>
<li>Targets multiple audiences</li>
<li>Lacks clear structure</li>
</ul>
<p>This makes summarization risky and selection unlikely.</p>
<h3>Structure that assumes a human reader only</h3>
<p>Content written purely for linear reading often fails in AI-driven discovery. Systems need:</p>
<ul>
<li>Clear sections</li>
<li>Direct answers</li>
<li>Obvious topical boundaries</li>
</ul>
<p>Without these, even high-quality content can be overlooked.</p>
<h3>What modern search systems are looking for instead</h3>
<p>Content that:</p>
<ul>
<li>Clearly states what it is about</li>
<li>Answers questions directly</li>
<li><a href="https://haydenschuster.com/writing/search-behavior/">Maintains consistent intent</a> throughout the page</li>
<li>Connects cleanly to related topics</li>
</ul>
<p>This does not mean oversimplifying. It means <strong>reducing interpretive friction</strong>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-build-content-that-ai-systems-can-understand"><span class="sec-n" aria-hidden="true">04</span>How to build content that AI systems can understand</h2>
<h3>Write with interpretation in mind</h3>
<p>Assume your content may be:</p>
<ul>
<li>Summarized</li>
<li>Quoted</li>
<li>Compared</li>
<li>Shown without context</li>
</ul>
<p>Each section should stand on its own and still make sense.</p>
<h3>Structure content around questions and concepts</h3>
<p>Questions and concepts are key, because they can:</p>
<ul>
<li><a href="https://haydenschuster.com/writing/intent-transitions/">Match clear query intent</a></li>
<li>Group related ideas logically</li>
<li>Avoid unnecessary narrative detours</li>
</ul>
<p>This improves both human comprehension and machine interpretation.</p>
<h3>Support understanding with internal context</h3>
<p>Internal links help systems understand relationships between topics. Link to:</p>
<ul>
<li>Supporting concepts</li>
<li>Deeper explanations</li>
<li>Adjacent systems</li>
</ul>
<h3>Signs that AI discovery is picking up your content</h3>
<p><strong>Look for:</strong></p>
<ul>
<li>Changes in impression patterns</li>
<li>Visibility across multiple query types</li>
<li>Growth in informational and mid-funnel queries</li>
<li>Increased assisted engagement</li>
</ul>
<p>AI-driven discovery often shows up as <strong>broader visibility</strong>, not immediate clicks.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-mistakes-to-avoid"><span class="sec-n" aria-hidden="true">05</span>Common mistakes to avoid</h2>
<ul>
<li>Writing for keywords instead of clarity</li>
<li>Mixing multiple intents on one page</li>
<li>Ignoring structure in favor of prose</li>
<li>Treating AI features as optional</li>
</ul>
<p>These mistakes make content harder to interpret and easier to skip.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-clarity-decides-ai-visibility"><span class="sec-n" aria-hidden="true">06</span>Why clarity decides AI visibility</h2>
<p><strong>If your content cannot be easily understood, summarized, or placed into context, it will struggle in AI-driven discovery environments</strong>, regardless of how well it ranks traditionally. Clarity is now a competitive advantage.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-ai-driven-search-discovery"><span class="sec-n" aria-hidden="true">07</span>Questions people ask about AI-driven search discovery</h2>
<h3>Why is my content not showing up in AI snippets?</h3>
<p><strong><a href="https://haydenschuster.com/writing/content-strategy/">Content</a> often fails to appear in AI snippets when it is overly long, mixes audiences, buries answers, or lacks clear structure.</strong> Even high-quality content can be skipped if the system cannot easily identify what question it answers and where the answer lives.</p>
<h3>Why does search visibility change without ranking changes?</h3>
<p><strong>Visibility can change even when rankings stay the same because AI summaries, carousels, and blended layouts may surface or suppress content independently of traditional positions.</strong> Being understood matters as much as being ranked.</p>
<h3>What is selection bias in AI search systems?</h3>
<p><strong>Selection bias occurs when AI systems consistently favor content that is clearer, simpler, or easier to summarize.</strong> Pages that require heavy interpretation or context are less likely to be selected, even if they are accurate.</p>
<h3>How should SEO measurement change for AI-driven search?</h3>
<p>SEO measurement should focus less on rankings alone and more on visibility patterns, citations, impressions, and <strong>how often content appears across different SERP features and discovery surfaces.</strong></p>
<h3>How do you tell if AI search understands your content?</h3>
<p>Signals include whether content is summarized accurately, referenced in AI features, or surfaced consistently for related queries. <strong>Misinterpretation often shows up as partial summaries or exclusion from AI-driven results.</strong></p>
<h3>Does keyword research still matter for AI search?</h3>
<p>Keyword research still matters, but it is used to understand questions and intent rather than to place exact phrases. <strong>Long-tail queries help identify how people frame problems and what explanations they are seeking.</strong></p>
]]></content:encoded>
  </item>
  <item>
    <title>Why informational content stalls</title>
    <link>https://haydenschuster.com/writing/informational-content-to-decision/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/informational-content-to-decision/</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>Why informational pages earn traffic but leave readers stuck, and what they need to do instead: help people place their problem and see the next question.</description>
    <content:encoded><![CDATA[<p>Informational content is often treated as the beginning of a funnel. <strong>In reality, it's closer to orientation. People arrive unsure, not undecided.</strong> They are trying to figure out what kind of problem they have before they decide how to solve it.</p>
<p>When informational content ignores that role, it creates understanding without direction.</p>
<h2 id="where-informational-searches-come-from"><span class="sec-n" aria-hidden="true">01</span>Where informational searches come from</h2>
<p>Informational searches are not neutral curiosity. <strong>They usually come from friction.</strong></p>
<p>Someone searches because:</p>
<ul>
<li>something feels unclear</li>
<li>a situation changed</li>
<li>a decision is approaching, but not yet formed</li>
</ul>
<p>Queries like:</p>
<ul>
<li>&quot;what does informational content actually do&quot;</li>
<li>&quot;how does google understand website content&quot;</li>
<li>&quot;what causes rankings to fluctuate&quot;</li>
</ul>
<p>These queries are attempts to reduce uncertainty.</p>
<p>The mistake is treating informational intent as a <strong>request for completeness</strong>, instead of a <strong>request for clarity</strong>.</p>
<h3>Quick recap of search intent terms</h3>
<p>Informational, <a href="https://haydenschuster.com/writing/commercial-search-intent/">commercial</a>, <a href="https://haydenschuster.com/writing/navigational-search-intent/">navigational</a>, and <a href="https://haydenschuster.com/writing/transactional-pages-fail/">transactional search intent</a> reflect different stages of how people move toward a decision. <strong>Informational searches are about orientation and understanding, where someone is trying to make sense of a topic or situation.</strong> Commercial investigation searches sit in the middle, where users compare options, evaluate tradeoffs, and reduce risk. Navigational searches signal familiarity and trust, with users trying to reach a specific brand or destination. Transactional searches happen last, when someone is ready to act but still needs confirmation. <strong>Problems arise when content treats these intents as interchangeable, rather than designing pages to support the specific questions and expectations that exist at each stage.</strong> The full map is in <a href="https://haydenschuster.com/writing/search-intent/">the four types of search intent</a>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-informational-content-looks-successful-but-quietly-fails"><span class="sec-n" aria-hidden="true">02</span>Why informational content looks successful but quietly fails</h2>
<p>Informational content is rewarded early.</p>
<p>Yes, it earns <strong>impressions</strong>. Yes, it earns <strong>clicks</strong>. Yes, it earns <strong>rankings</strong>. That feedback loop convinces teams that the content is working, even when it isn't doing anything downstream.</p>
<p>What looks like success at the surface often masks a deeper issue: the content explains <em><strong>what something is</strong></em>, but not <em><strong>why it matters now</strong></em> or <em><strong>what it connects to next</strong></em>.</p>
<p>Understanding increases. Confidence does not.</p>
<p><strong>One important clarification</strong>, though, as I don't want this point to get lost:</p>
<p><strong>Clear, calculated informational content is still absolutely essential. It is how people discover problems, learn vocabulary, and orient themselves</strong> before any decision is possible. Without informational content, users never reach the evaluation or action stages at all. The issue is treating informational pages as finished work instead of the foundation of a larger journey. When informational content is designed to support progression rather than stand alone, it becomes one of the most valuable parts of an SEO system.</p>
<p>However, poor informational content structure can lose influence and hurt visibility.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="where-poorly-done-informational-content-loses-its-influence"><span class="sec-n" aria-hidden="true">03</span>Where poorly done informational content loses its influence</h2>
<h3>It treats the topic as the goal</h3>
<p>Most informational pages are written as if the topic itself is the destination. Once explained, the job is considered done.</p>
<p>But readers don't arrive to master a topic. They arrive to situate themselves.</p>
<p>When content ends at explanation, <strong>it leaves the reader informed but unanchored.</strong></p>
<h3>It avoids making tradeoffs visible</h3>
<p>Informational content often tries to be neutral. It lists options, definitions, or factors without helping the reader understand which ones matter in different situations.</p>
<p><strong>Neutrality feels safe, but it removes usefulness.</strong> Readers need help <strong>narrowing their thinking.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="a-more-realistic-example-of-informational-failure"><span class="sec-n" aria-hidden="true">04</span>A more realistic example of informational failure</h2>
<p>Consider a post titled:</p>
<p><em><strong>How Google Understands Website Content</strong></em></p>
<p>The article explains crawling, indexing, and relevance clearly. It ranks. It gets traffic.</p>
<p>But it never addresses:</p>
<ul>
<li><strong>When</strong> this understanding breaks down</li>
<li><strong>What</strong> site owners should worry about first</li>
<li><strong>How</strong> this affects real-world decisions</li>
</ul>
<p>The reader understands more, but still doesn't know what to <em>pay attention to</em>.</p>
<p>So they search again. Fish off the hook, I repeat, <strong>FISH OFF THE HOOKKKKK.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-this-creates-long-term-seo-blind-spots"><span class="sec-n" aria-hidden="true">05</span>Why this creates long-term SEO blind spots</h2>
<p>When informational content <strong>doesn't guide orientation</strong>:</p>
<ul>
<li>Users don't explore deeper pages</li>
<li>Internal links don't get used</li>
<li>Related topics remain disconnected</li>
</ul>
<p>Over time, the site accumulates knowledge without cohesion. <strong>Search systems see content, but not a clear progression.</strong> Authority stalls, even as volume grows.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-informational-content-needs-to-do-differently"><span class="sec-n" aria-hidden="true">06</span>What informational content needs to do differently</h2>
<h3>Help the reader locate themselves</h3>
<p>Good informational content quietly answers:</p>
<ul>
<li>what kind of problem this is</li>
<li>how urgent it is</li>
<li>what typically comes next</li>
</ul>
<p>This doesn't require selling or pushing. It requires framing.</p>
<h3>Make the next question obvious</h3>
<p>The strongest informational pages don't force a next step. They make it feel natural.</p>
<p>By the end of the page, the reader should know:</p>
<ul>
<li>what they still don't know</li>
<li>which direction to explore</li>
<li>what kind of decision they are moving toward</li>
</ul>
<p>That is momentum.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-tell-if-informational-content-is-actually-working"><span class="sec-n" aria-hidden="true">07</span>How to tell if informational content is actually working</h2>
<p>Traffic is a weak signal.</p>
<p>Better signals include:</p>
<ul>
<li><strong>whether readers click into adjacent topics</strong></li>
<li><strong>whether the same users return later</strong></li>
<li><strong>whether informational pages assist deeper engagement</strong></li>
</ul>
<p>Informational content that never participates in a longer journey is isolated knowledge.</p>
<p>On that note, I hope you continue reading about <a href="https://haydenschuster.com/writing/search-behavior/">search behavior and intent</a> 😉</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-informational-content-traps"><span class="sec-n" aria-hidden="true">08</span>Common informational content traps</h2>
<ul>
<li>Treating explanation as impact</li>
<li>Writing for completeness instead of usefulness</li>
<li>Ending pages without orientation</li>
<li>Measuring success only at the page level</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-understanding-alone-is-not-progress"><span class="sec-n" aria-hidden="true">09</span>Why understanding alone is not progress</h2>
<p>The problem is <strong>mistaking understanding for progress.</strong></p>
<p><strong>Informational content should not close the conversation.</strong> It should open the right one.</p>
<p>When informational pages help readers orient themselves and see what comes next, they become the foundation of decision-making. When they don't, they become dead ends that look productive but go nowhere.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-informational-search-intent"><span class="sec-n" aria-hidden="true">10</span>Questions people ask about informational search intent</h2>
<h3>What is informational search intent?</h3>
<p><strong>Informational search intent describes queries where someone is trying to understand a topic, situation, or problem.</strong> The goal is clarity and orientation, not immediate action or purchase.</p>
<h3>How is informational search intent different from transactional search intent?</h3>
<p><strong>Informational search intent is about orientation and understanding, while transactional search intent is about confirmation and action.</strong> Informational content helps users figure out what kind of problem they have and what concepts matter, whereas transactional content helps users decide whether they are ready to act and with whom. Informational content builds context and confidence early, while transactional content resolves remaining doubt at the end. Problems arise when informational pages are expected to convert, or when transactional pages assume understanding that was never built upstream.</p>
<h3>How is informational search intent different from commercial search intent?</h3>
<p><strong>Informational search intent is about orientation, while commercial search intent is about evaluation.</strong> When someone searches informationally, they are trying to understand a topic, define a problem, or build enough context to know what matters. Commercial search intent comes later, when the user already understands the problem and is actively comparing options, weighing tradeoffs, and reducing risk. Informational content answers &quot;what is this and why does it matter,&quot; while commercial content answers &quot;which option fits my situation best.&quot; Confusion happens when informational pages try to persuade too early, or when commercial pages assume understanding that was never established.</p>
<h3>How is informational search intent different from navigational search intent?</h3>
<p><strong>Informational search intent is about understanding, while navigational search intent is about access.</strong> When someone searches informationally, they are trying to learn, orient themselves, or reduce uncertainty about a topic or situation. Navigational search intent appears when the user already knows where they want to go and is using search as a shortcut to reach a specific brand, site, or page. Informational content helps users make sense of a problem, while navigational content confirms familiarity and trust. Confusion happens when informational pages assume brand awareness, or when navigational pages try to educate instead of getting users where they expect to land quickly.</p>
<h3>How can I tell if my informational content is a dead end?</h3>
<p>Common signs include high impressions with low internal clicks, users leaving the site after one page, or informational pages that never assist conversions or deeper engagement.</p>
<h3>Should informational content include calls to action?</h3>
<p>It should include <em>contextual direction</em>, not aggressive sales CTAs. <strong>Informational pages work best when they point to comparisons, deeper explanations, or applied examples that match the reader's next question.</strong></p>
<h3>Does AI-driven search change how informational content works?</h3>
<p>Yes. <strong>AI summaries and new SERP layouts often surface informational content directly.</strong> Pages that lack clarity, structure, or contextual framing are harder for systems to interpret and reuse.</p>
<h3>Can informational content hurt SEO if done poorly?</h3>
<p><strong>Indirectly.</strong> While it may rank initially, content that consistently fails to engage or guide users can weaken overall site cohesion and stall authority growth.</p>
]]></content:encoded>
  </item>
  <item>
    <title>How misaligned intent stalls decisions</title>
    <link>https://haydenschuster.com/writing/intent-transitions/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/intent-transitions/</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>Why content that ranks still fails to move people toward a decision, and how to build intent transitions: mapping, internal links, CTAs and measurement.</description>
    <content:encoded><![CDATA[<p>We live in a world overflowing with <strong>informational content</strong> like how-to guides, beginner explanations, definitions, and comparisons. But here's the harsh truth: <strong>most of it goes nowhere</strong>. It stops at awareness and never guides the user to the <strong>decision stage</strong>.</p>
<h2 id="what-search-intent-is-and-why-it-matters"><span class="sec-n" aria-hidden="true">01</span>What search intent is and why it matters</h2>
<h3>A quick breakdown of search intent</h3>
<p>Search intent is the reason someone types something into a search engine. Generally, it falls into four types (the full map is in <a href="https://haydenschuster.com/writing/search-intent/">the four types of search intent</a>):</p>
<p><strong><a href="https://haydenschuster.com/writing/transactional-pages-fail/">Transactional</a></strong>: Ready to take action (e.g., &quot;let's buy&quot;)</p>
<p><strong><a href="https://haydenschuster.com/writing/informational-content-to-decision/">Informational</a></strong>: Looking to learn something (e.g., &quot;why should I buy this&quot;)</p>
<p><strong><a href="https://haydenschuster.com/writing/navigational-search-intent/">Navigational</a></strong>: Looking for a specific site (e.g., &quot;where should I buy&quot;)</p>
<p><strong><a href="https://haydenschuster.com/writing/commercial-search-intent/">Commercial</a></strong>: Considering options (e.g., &quot;what is best for my situation&quot;)</p>
<p>Understanding <strong>which stage your content matches</strong> is essential for ranking well and converting users.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-search-intent-is-a-big-deal-for-seo"><span class="sec-n" aria-hidden="true">02</span>Why search intent is a big deal for SEO</h2>
<p><strong>Google is smarter now.</strong> It looks beyond keywords to understand what users really want. If your content doesn't match that intent or help users move from one stage to the next, then your chances of converting traffic drop fast.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-misaligned-intent-is-one-of-the-most-costly-seo-mistakes"><span class="sec-n" aria-hidden="true">03</span>Why misaligned intent is one of the most costly SEO mistakes</h2>
<p>Misaligned search intent is a critical SEO mistake because it <strong>breaks the connection between why someone is searching and what a page actually delivers.</strong> Even when a page ranks and attracts traffic, intent misalignment causes users to hesitate, backtrack, or abandon the journey entirely. <strong>When content answers a different question than the one the searcher is trying to resolve at that moment, trust erodes and progress stops.</strong> Over time, this leads to pages that appear successful on the surface but consistently fail to influence decisions or outcomes.</p>
<p>This is why <strong>intent misalignment shows up most often in informational content.</strong> Many pages successfully explain a topic but fail to recognize what the reader needs next in order to move forward. Information alone rarely resolves uncertainty or builds confidence. Without context, prioritization, or a clear sense of what matters, even accurate content can leave users stuck in research mode. This gap between understanding and action is where informational pages quietly lose their influence, setting the stage for why informational content on its own is rarely enough.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-informational-content-isn-t-enough-on-its-own"><span class="sec-n" aria-hidden="true">04</span>Why informational content isn't enough on its own</h2>
<h3>Lots of views, few results</h3>
<p>It's easy to focus on traffic numbers. Writing informational content brings in visitors, and that feels like success. But if you're not guiding those visitors toward your products, services, or other helpful content, you're just building traffic for traffic's sake.</p>
<h3>People need help taking the next step</h3>
<p>If your blog post explains &quot;What is ______?&quot; but doesn't suggest what to do next (like comparing tools or trying a demo), readers won't stick around. And they definitely won't convert. They'll just go back to Google and click on someone else's content.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="a-real-example-informational-content-that-doesn-t-deliver"><span class="sec-n" aria-hidden="true">05</span>A real example: informational content that doesn't deliver</h2>
<p>Let's say you are an auto dealership focused on <a href="https://haydenschuster.com/writing/local-seo/">local SEO</a> and publish an article titled:</p>
<p><em><strong>Best SUVs for Families</strong></em></p>
<p>It does a great job explaining the concept. Maybe it even ranks on page one. But if it:</p>
<ul>
<li>Doesn't link to related content</li>
<li>Doesn't mention your inventory</li>
<li>Doesn't suggest the next question the reader might have</li>
</ul>
<p>...it stops short. You've created awareness, but not momentum.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-most-informational-content-fails-to-reach-the-decision-stage"><span class="sec-n" aria-hidden="true">06</span>Why most informational content fails to reach the decision stage</h2>
<h3>Users aren't being guided forward</h3>
<p>Someone searching for &quot;what is CRM&quot; will eventually ask, &quot;Do I need one?&quot; or &quot;Which one is best for me?&quot; If your content doesn't point them in that direction, they'll find answers elsewhere.</p>
<h3>Content structure doesn't support progression</h3>
<p>Most content is organized by topic, not by intent. That means someone reading about CRM basics isn't being guided to explore tools, comparisons, or pricing.</p>
<h3>You're missing SEO opportunities too</h3>
<p>When you don't guide users between intent stages, Google doesn't see a clear content journey. That hurts your topical authority, and you miss out on ranking for more valuable, high-converting keywords.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-build-intent-transitions-that-actually-work"><span class="sec-n" aria-hidden="true">07</span>How to build intent transitions that actually work</h2>
<h3>How to map out those transitions</h3>
<ul>
<li><strong>Identify</strong> the intent behind each piece of content (use tools like Ahrefs or Semrush)</li>
<li><strong>Group</strong> your content by intent stage, not just by topic</li>
<li><strong>Link</strong> them together in a way that naturally helps the user take the next steps</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="practical-ways-to-bridge-intent-gaps"><span class="sec-n" aria-hidden="true">08</span>Practical ways to bridge intent gaps</h2>
<h3>Use internal links strategically</h3>
<p>Don't let your top-of-funnel content be a dead end. Add links that make sense for where the reader might want to go next. For example:</p>
<ul>
<li>&quot;See why the CR-V Hybrid is the best choice for families.&quot;</li>
<li>&quot;Want to compare family-friendly SUVs? Here's a full breakdown.&quot;</li>
</ul>
<h3>Add calls to action that fit the moment</h3>
<p><strong>Match your call to action with the reader's mindset.</strong> If they're still learning, don't ask them to buy right away. Try:</p>
<ul>
<li>&quot;Compare the top family SUVs&quot;</li>
<li>&quot;Check our latest SUV specials&quot;</li>
<li>&quot;Explore the best family-friendly SUV features.&quot;</li>
</ul>
<h3>Build content pillars around intent stages</h3>
<p>Instead of one big topic pillar like &quot;Family SUVs,&quot; split it into:</p>
<ul>
<li>Awareness: &quot;Family SUVs for sale near me&quot;</li>
<li>Consideration: &quot;Best Family SUVs for sale near me&quot;</li>
<li>Decision: &quot;Why [CR-V Hybrid] is the best choice for families&quot;</li>
</ul>
<p>This helps you rank across different stages and lead users all the way through.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-measure-if-your-intent-transitions-are-working"><span class="sec-n" aria-hidden="true">09</span>How to measure if your intent transitions are working</h2>
<h3>Key metrics to track</h3>
<ul>
<li>Are people clicking deeper into your site?</li>
<li>Are they moving from blog posts to product pages?</li>
<li>Are assisted conversions going up?</li>
</ul>
<h3>Tools to measure progress</h3>
<ul>
<li><strong>Google Analytics (GA4)</strong>: Check user paths and engagement</li>
<li><strong>Search Console</strong>: See how your pages rank by intent</li>
<li><strong>Hotjar or Microsoft Clarity</strong>: Watch how users navigate your pages</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="examples-of-content-that-transitions-well"><span class="sec-n" aria-hidden="true">10</span>Examples of content that transitions well</h2>
<h3>SaaS funnel example</h3>
<ul>
<li><strong>Blog</strong>: &quot;What is customer churn?&quot;</li>
<li><strong>Link to</strong>: &quot;Top customer retention strategies&quot;</li>
<li><strong>Link to</strong>: &quot;How our platform reduces churn&quot;</li>
<li><strong>CTA</strong>: &quot;Request a demo&quot;</li>
</ul>
<h3>Local service funnel example</h3>
<ul>
<li><strong>Blog</strong>: &quot;How Google decides which local businesses show up in map results&quot;</li>
<li><strong>Link to</strong>: &quot;What relevance, proximity, and prominence actually mean for local rankings&quot;</li>
<li><strong>Link to</strong>: &quot;How to improve visibility for a local service area page&quot;</li>
<li><strong>CTA</strong>: &quot;See our local SEO work&quot;</li>
</ul>
<h3>E-commerce funnel example</h3>
<ul>
<li><strong>Blog</strong>: &quot;How to style white sneakers for each season&quot;</li>
<li><strong>Link to</strong>: &quot;Best white sneakers in 2026&quot;</li>
<li><strong>CTA</strong>: &quot;Shop the collection now&quot;</li>
</ul>
<p>These examples work because they anticipate the user's next need, and offer it before they bounce.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-pitfalls-to-avoid"><span class="sec-n" aria-hidden="true">11</span>Common pitfalls to avoid</h2>
<ul>
<li>Writing tons of informational content <strong>with no clear next step</strong></li>
<li>Using <strong>aggressive sales CTAs</strong> on beginner content</li>
<li><strong>Linking randomly</strong> instead of based on user intent</li>
<li>Ignoring &quot;<strong>People Also Ask</strong>&quot; sections that reveal intent shifts</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="where-to-start"><span class="sec-n" aria-hidden="true">12</span>Where to start</h2>
<p><strong>If your content isn't leading people toward a decision, you're wasting your efforts.</strong></p>
<p>Informational content is important. <strong>But on its own, it won't drive results unless you help users take the next step.</strong> That means building smart intent transitions, linking content with purpose, and thinking about what people actually want to know next.</p>
<p>Start small. Add a few links. Map out your content by intent. Make sure everything connects with meaning.</p>
<p>That's how you turn <strong>content into conversions.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-misaligned-search-intent"><span class="sec-n" aria-hidden="true">13</span>Questions people ask about misaligned search intent</h2>
<h3>What does misaligned search intent actually mean?</h3>
<p><strong>Misaligned search intent happens when a page ranks for a query but answers a different question than the searcher is trying to resolve at that moment.</strong> The content may be accurate, but it does not match the user's underlying goal, which causes hesitation, backtracking, or abandonment.</p>
<h3>Can a page rank well and still have the wrong search intent?</h3>
<p>Yes, very often. Rankings reflect relevance signals, not satisfaction. <strong>A page can rank because it matches keywords or topics, but still fail if it does not meet the user's expectations or help them move forward.</strong></p>
<h3>How do I know if my content has an intent problem?</h3>
<p>Common signs include <strong>high traffic with low engagement, users bouncing back to search results, strong impressions with weak conversions, or pages that attract readers but never influence decisions.</strong> These patterns usually point to intent misalignment rather than a visibility issue.</p>
<h3>Is intent the same as keywords?</h3>
<p><strong>No.</strong> Keywords describe what someone typed. Intent describes why they typed it. Two queries can use similar words but represent very different goals. Optimizing for keywords without understanding intent is one of the most common causes of misalignment.</p>
<h3>Does misaligned intent hurt rankings?</h3>
<p><strong>Indirectly, yes.</strong> While intent misalignment does not always cause immediate ranking drops, it can lead to <strong>poor engagement signals, lower trust, and reduced effectiveness</strong> over time. Search systems increasingly reward pages that satisfy intent, not just match topics.</p>
<h3>How can I fix intent misalignment on existing pages?</h3>
<p><strong>Start by identifying what question the user is actually trying to answer at that stage.</strong> Then adjust the page to acknowledge that need, clarify priorities, and offer a logical next step. Often this means reframing content, not rewriting it entirely.</p>
<h3>Is this more important for blogs or product pages?</h3>
<p><strong>It matters for both, but it shows up differently.</strong> Blogs often fail by stopping at explanation, while product or service pages fail by assuming readiness. In both cases, the issue is a gap between user expectations and page delivery.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Why transactional pages fail ready buyers</title>
    <link>https://haydenschuster.com/writing/transactional-pages-fail/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/transactional-pages-fail/</guid>
    <pubDate>Sat, 31 Jan 2026 00:00:00 GMT</pubDate>
    <description>Why pages that rank for buying searches still lose ready buyers, and how to build them as confirmations: fit, trust, and what happens after the click.</description>
    <content:encoded><![CDATA[<p>We tend to think transactional pages are the easy part of SEO. Someone searches with the intent to buy, lands on a page, and converts. In reality, <strong>transactional intent is where many sites fail hardest.</strong></p>
<h2 id="what-transactional-search-intent-actually-means-in-practice"><span class="sec-n" aria-hidden="true">01</span>What transactional search intent actually means in practice</h2>
<p>Transactional search intent signals readiness to act.</p>
<h3>Quick recap of search intent terms</h3>
<p><strong>Transactional search intent represents the final stage of how people move toward a decision, but it depends heavily on everything that comes before it.</strong> <a href="https://haydenschuster.com/writing/informational-content-to-decision/">Informational searches</a> help users orient themselves and understand a problem, while <a href="https://haydenschuster.com/writing/commercial-search-intent/">commercial investigation</a> searches allow them to compare options, evaluate tradeoffs, and reduce risk. <a href="https://haydenschuster.com/writing/navigational-search-intent/">Navigational searches</a> signal familiarity and trust, when users are trying to reach a specific brand or destination they already recognize. <strong>Transactional searches come last, when someone is ready to act but still needs reassurance that their choice is correct.</strong> Problems arise when transactional pages are built in isolation, without accounting for the understanding, evaluation, and trust that should already exist upstream. The full map is in <a href="https://haydenschuster.com/writing/search-intent/">the four types of search intent</a>.</p>
<h3>Transactional search examples by industry</h3>
<p>In <strong>service-based industries</strong>, transactional searches include phrases like &quot;<strong>schedule dental cleaning</strong>,&quot; &quot;<strong>emergency plumber near me</strong>,&quot; &quot;<strong>IT support services pricing</strong>,&quot; or &quot;<strong>hire cybersecurity consultant.</strong>&quot; These queries often appear when urgency is high and tolerance for friction is low. Users are not exploring options casually; they are selecting a provider who can solve a problem quickly and reliably.</p>
<p>Transactional intent often shows up in <strong>consumer-focused searches</strong> like &quot;<strong>best mortgage rates today,</strong>&quot; &quot;<strong>health insurance plans for families</strong>,&quot; or &quot;<strong>hire a personal injury lawyer near me</strong>.&quot; In everyday purchases, this includes queries such as &quot;<strong>buy noise cancelling headphones</strong>,&quot; &quot;<strong>best king size mattress,</strong>&quot; &quot;<strong>same day flower delivery,</strong>&quot; or &quot;<strong>book flight to New York.</strong>&quot; These searches signal readiness to act, with users looking to confirm price, availability, or provider trust before committing.</p>
<p><strong>Transactional intent in B2B and professional contexts</strong> looks slightly different but follows the same pattern. Examples include &quot;<strong>CRM software pricing,</strong>&quot; &quot;<strong>marketing automation platform demo,</strong>&quot; &quot;<strong>enterprise data warehouse solution,</strong>&quot; or &quot;<strong>accounting software for small businesses.</strong>&quot; In education and career services, users search for things like &quot;<strong>online MBA program cost,</strong>&quot; &quot;<strong>coding bootcamp enrollment,</strong>&quot; or &quot;<strong>resume writing service pricing.</strong>&quot; These queries indicate evaluation is nearly complete and the user is preparing to move forward.</p>
<figure class="post-fig pframe post-fig--inline post-fig--diagram" id="fig-transactional-search-examples" style="--frame: var(--field); --frame-shadow: var(--piece-s)"><div class="pframe-img post-fig-frame"><picture class="post-fig-pic"><source type="image/webp" srcset="https://haydenschuster.com/assets/post-images/transactional-search-examples-by-industry-480.webp 480w, https://haydenschuster.com/assets/post-images/transactional-search-examples-by-industry-960.webp 960w, https://haydenschuster.com/assets/post-images/transactional-search-examples-by-industry-1536.webp 1536w" sizes="(min-width: 1100px) min(960px, 56vw), calc(100vw - 52px)"><img src="https://haydenschuster.com/assets/post-images/transactional-search-examples-by-industry-480.jpg" width="1536" height="1024" alt="Three columns of example searches. Consumer purchases and services: best mortgage rates today, health insurance plans for families, hire a personal injury lawyer near me, buy noise cancelling headphones, same day flower delivery. Professional and on-demand services: schedule dental cleaning, emergency plumber near me, IT support services pricing, hire cybersecurity consultant. B2B, software and education: CRM software pricing, marketing automation platform demo, enterprise data warehouse solution, online MBA program cost, coding bootcamp enrollment." loading="lazy" decoding="async"></picture></div><figcaption><span class="post-fig-n">Figure 1</span> Searches from people close to acting, in three groups: consumer purchases and services, professional and on-demand services, and B2B, software and education. <a class="post-fig-full" href="https://haydenschuster.com/assets/post-images/transactional-search-examples-by-industry-1536.webp">Open it full size</a></figcaption></figure><p>But transactional does <strong>not</strong> mean &quot;convinced.&quot; It means the user is close enough to act <em>if</em> the remaining doubts are resolved. That distinction matters.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-transactional-intent-is-a-big-deal-for-seo"><span class="sec-n" aria-hidden="true">02</span>Why transactional intent is a big deal for SEO</h2>
<p>Transactional queries are high value, but they are also high risk.</p>
<p>When these pages fail:</p>
<ul>
<li>Users do not browse</li>
<li>They do not explore</li>
<li>They leave quickly</li>
</ul>
<p>Search systems notice this.</p>
<p>Google evaluates whether the page satisfies the expectation that query implies.</p>
<p>When transactional pages underperform, there is a mismatch between <strong>what the user expects to confirm</strong> and <strong>what the page actually delivers</strong>.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="transactional-intent-breaks-when-pages-assume-too-much"><span class="sec-n" aria-hidden="true">03</span>Transactional intent breaks when pages assume too much</h2>
<p><strong>Transactional search intent fails most often because pages skip the confirmation step. They jump straight to:</strong></p>
<ul>
<li>&quot;Buy now&quot;</li>
<li>&quot;Schedule today&quot;</li>
<li>&quot;Request a quote&quot;</li>
</ul>
<p><strong>Before answering:</strong></p>
<ul>
<li>Is this the right option for me?</li>
<li>Can I trust this business?</li>
<li>What happens after I click?</li>
</ul>
<p>A transactional page is where <strong>persuasion should already feel complete.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-transactional-pages-look-fine-but-still-don-t-convert"><span class="sec-n" aria-hidden="true">04</span>Why transactional pages look fine but still don't convert</h2>
<h3>Rankings create false confidence</h3>
<p>A page ranking for a transactional keyword feels like success. But rankings do not guarantee readiness.</p>
<p>You can rank for &quot;<strong>used SUVs for families</strong>&quot; and still lose the user if:</p>
<ul>
<li>The inventory context is unclear</li>
<li>Pricing expectations are hidden</li>
<li>Differences between options are not explained</li>
</ul>
<p>The page answers <em>what exists</em>, not <strong><em>why this choice makes sense</em>.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="transactional-pages-skip-the-why-this-one-moment"><span class="sec-n" aria-hidden="true">05</span>Transactional pages skip the &quot;why this one&quot; moment</h2>
<p>Many transactional pages assume the user already decided.</p>
<p><strong>But most users arrive asking:</strong></p>
<ul>
<li>Why this dealership?</li>
<li>Why this service?</li>
<li>Why this option instead of another?</li>
</ul>
<p>If the page does not answer that quietly and clearly, the user returns to Google.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="a-real-example-transactional-content-that-fails-in-local-seo"><span class="sec-n" aria-hidden="true">06</span>A real example: transactional content that fails in local SEO</h2>
<p>Imagine a dealership page titled:</p>
<p><em><strong>Used Family SUVs for Sale Near Me</strong></em></p>
<p>It ranks well. It gets traffic.</p>
<p>But the page:</p>
<ul>
<li>Dumps inventory with no guidance</li>
<li>Lacks family-specific filters or callouts</li>
<li>Does not explain the tradeoffs between similar models</li>
<li>Pushes &quot;Contact Us&quot; immediately</li>
</ul>
<p>The user was ready to buy <em>something</em>, but not ready to choose <em>this</em>.</p>
<p>The intent was transactional. The page treated it as terminal. <strong>That is where conversion dies.</strong></p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="why-transactional-pages-fail-structurally"><span class="sec-n" aria-hidden="true">07</span>Why transactional pages fail structurally</h2>
<h3>Users are not being reassured</h3>
<p>At this stage, users are not learning fundamentals. They are resolving uncertainty.</p>
<p>Transactional pages fail when they do not:</p>
<ul>
<li>Clarify fit</li>
<li>Reduce risk</li>
<li>Reinforce trust</li>
</ul>
<p>Silence creates doubt.</p>
<h3>Content structure ignores decision logic</h3>
<p>Most transactional pages are structured around inventory or offerings.</p>
<p>They should be structured around <strong>decision questions</strong>, such as:</p>
<ul>
<li>Is this right for my situation?</li>
<li>What are my alternatives?</li>
<li>What happens after I act?</li>
</ul>
<p>When those questions are unanswered, the user leaves.</p>
<h3>How failed pages lose rankings too</h3>
<p>When transactional pages fail, Google sees:</p>
<ul>
<li>Short sessions</li>
<li>Rapid backtracking</li>
<li>Weak engagement</li>
</ul>
<p>Over time, those signals erode performance, even if the page technically matches the query.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-transactional-pages-should-be-built-instead"><span class="sec-n" aria-hidden="true">08</span>How transactional pages should be built instead</h2>
<h3>What a transactional intent page is really for</h3>
<p>A transactional page is for confirming someone is making the right choice.</p>
<p><strong>That means the page should:</strong></p>
<ul>
<li>Acknowledge hesitation</li>
<li>Surface reassurance naturally</li>
<li>Make the next step feel safe, not urgent</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="practical-ways-to-fix-transactional-intent-failures"><span class="sec-n" aria-hidden="true">09</span>Practical ways to fix transactional intent failures</h2>
<h3>Use internal links that reinforce confidence</h3>
<p>Transactional pages should not be isolated.</p>
<p><strong>Examples:</strong></p>
<ul>
<li>&quot;Not sure which SUV fits your family? Compare top options here.&quot;</li>
<li>&quot;See how this model compares to similar vehicles.&quot;</li>
<li>&quot;Why this service works best for multi-location dealerships.&quot;</li>
</ul>
<p>These links do not distract. They reduce anxiety.</p>
<h3>Match CTAs to decision readiness</h3>
<p>Avoid aggressive CTAs by default.</p>
<p><strong>Instead of:</strong></p>
<ul>
<li>&quot;Buy Now&quot;</li>
</ul>
<p><strong>Use:</strong></p>
<ul>
<li>&quot;Check availability&quot;</li>
<li>&quot;See pricing options&quot;</li>
<li>&quot;Schedule a test drive&quot;</li>
</ul>
<p><strong>The action should feel like a confirmation, not a leap.</strong></p>
<h3>Build transactional pages as the end of a journey</h3>
<p><strong>If informational and commercial content did its job, the transactional page should feel obvious.</strong></p>
<p>If it feels abrupt, something upstream is broken.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-to-measure-if-transactional-intent-is-working"><span class="sec-n" aria-hidden="true">10</span>How to measure if transactional intent is working</h2>
<h3>Key <a href="https://haydenschuster.com/writing/measurement/">SEO measurement</a> metrics that matter</h3>
<ul>
<li>Assisted conversions</li>
<li>Return visits to transactional pages</li>
<li>Navigation paths leading into them</li>
<li>Time spent before action</li>
</ul>
<h3>Tools that show hesitation</h3>
<ul>
<li>GA4 to trace assisted paths</li>
<li>Search Console to see which queries drive transactional landings</li>
<li>Clarity or Hotjar to observe hesitation patterns</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="examples-of-transactional-pages-that-work"><span class="sec-n" aria-hidden="true">11</span>Examples of transactional pages that work</h2>
<h3>Automotive example</h3>
<p>Page: &quot;<strong>CR-V Hybrid for Families</strong>&quot;</p>
<p><strong>Includes:</strong></p>
<ul>
<li>Why it fits family needs</li>
<li>Comparison to similar SUVs</li>
<li>Inventory visibility</li>
<li>Soft CTA: &quot;See available models&quot;</li>
</ul>
<p>The page confirms, not pressures.</p>
<h3>Local SEO service example</h3>
<p>Page: &quot;Local SEO help for multi-location dealerships&quot;</p>
<p><strong>Includes:</strong></p>
<ul>
<li>Who it is for</li>
<li>What problems it solves</li>
<li>How it differs from generic SEO</li>
<li>CTA: &quot;See how we approach local SEO&quot;</li>
</ul>
<p>This works because the user already wants help. They just need reassurance.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-transactional-mistakes-to-avoid"><span class="sec-n" aria-hidden="true">12</span>Common transactional mistakes to avoid</h2>
<ul>
<li>Treating transactional pages as pure sales pages</li>
<li>Skipping explanation because &quot;they're ready&quot;</li>
<li>Isolating pages from supporting content</li>
<li>Using urgency where clarity is needed</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-a-transactional-page-has-to-do"><span class="sec-n" aria-hidden="true">13</span>What a transactional page has to do</h2>
<p><strong>Transactional intent is fragile.</strong></p>
<p><strong>The goal of a transactional page is to confirm.</strong></p>
<p><strong>When handled well, it converts quietly and consistently. When handled poorly, it looks like traffic with no payoff.</strong> If your transactional pages are not converting, the issue is almost always unresolved intent.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="questions-people-ask-about-transactional-search-intent"><span class="sec-n" aria-hidden="true">14</span>Questions people ask about transactional search intent</h2>
<h3>What is transactional search intent?</h3>
<p><strong>Transactional search intent refers to queries where users are ready to take an action</strong>, such as buying, booking, or contacting a business, but may still need confirmation before doing so.</p>
<h3>How is transactional search intent different from informational search intent?</h3>
<p><strong>Transactional search intent is about action, while informational search intent is about orientation.</strong> Transactional searches happen when a user is ready to buy, book, sign up, or contact someone, but may still need final confirmation. Informational searches happen earlier, when the user is trying to understand a topic, define a problem, or build context. Transactional content should confirm a decision, while informational content should help users make sense of what comes next. Problems arise when transactional pages assume understanding that was never built, or when informational pages are expected to convert.</p>
<h3>How is transactional search intent different from commercial search intent?</h3>
<p><strong>Transactional search intent is about committing to an action, while commercial search intent is about evaluating options.</strong> Commercial searches happen when users are comparing alternatives, weighing tradeoffs, and reducing risk before deciding. Transactional searches come after that evaluation, when the user has narrowed choices and is ready to act. Commercial content should help users choose between options, while transactional content should reassure them that their choice is sound. Confusion happens when transactional pages try to compete instead of confirm, or when commercial pages push users to act too soon.</p>
<h3>How is transactional search intent different from navigational search intent?</h3>
<p><strong>Transactional search intent is about completing an action, while navigational search intent is about reaching a known destination.</strong> Navigational searches occur when users already trust a brand or site and want to get to a specific page quickly. Transactional searches may still involve uncertainty, even if the user is ready to act. Navigational pages should prioritize speed and clarity, while transactional pages should prioritize reassurance and next-step confidence. Issues arise when transactional pages behave like shortcuts, or when navigational pages introduce friction instead of access.</p>
]]></content:encoded>
  </item>
  <item>
    <title>2026 auto SEO trends to take advantage of</title>
    <link>https://haydenschuster.com/writing/auto-seo-trends-2026/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/auto-seo-trends-2026/</guid>
    <pubDate>Wed, 28 Jan 2026 00:00:00 GMT</pubDate>
    <description>Five SEO trends for auto dealerships: AI summaries, voice search, image SEO, local listings and evergreen content.</description>
    <content:encoded><![CDATA[<p>I wrote about dealership SEO at Adpearance in November 2024. This is my take on what matters for auto sites in 2026.</p>
<h2 id="key-strategies-for-auto-dealership-seo"><span class="sec-n" aria-hidden="true">01</span>Key strategies for auto dealership SEO</h2>
<p>In the rapidly evolving digital landscape, staying ahead in search engine optimization (SEO) is crucial for auto dealerships aiming to attract and retain customers. Recent insights highlight <a href="https://haydenschuster.com/writing/content-strategy/">emerging trends and strategies</a> that can enhance your dealership's online presence.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="embracing-ai-generated-summaries"><span class="sec-n" aria-hidden="true">02</span>Embracing AI-generated summaries</h2>
<p>Search engines are increasingly utilizing AI to generate concise summaries at the top of search results. To position your dealership's content within these AI-generated snippets:</p>
<ul>
<li><strong>Craft High-Quality Content:</strong> Develop engaging, accurate, and helpful information that stands out.</li>
<li><strong>Provide Direct Answers:</strong> Anticipate common customer queries and address them clearly on your landing pages.</li>
<li><strong>Organize with Clear Structure:</strong> Use descriptive headings and logical formatting to make your content easily digestible for both readers and AI algorithms.</li>
</ul>
<p>Implementing these practices increases the likelihood of your content being featured prominently, enhancing visibility and credibility.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="optimizing-for-voice-search"><span class="sec-n" aria-hidden="true">03</span>Optimizing for voice search</h2>
<p>With the rise of voice-activated assistants like Siri, Alexa, and Google Assistant, optimizing for voice search is becoming essential:</p>
<ul>
<li><strong>Use Conversational Language:</strong> Incorporate natural, colloquial phrasing that mirrors how customers verbally ask questions.</li>
<li><strong>Focus on Long-Tail Keywords:</strong> Target phrases that reflect spoken language, which are often longer and more specific than typed queries.</li>
</ul>
<p>By aligning your content with the nuances of voice search, you can capture a growing segment of users who prefer hands-free, spoken interactions.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="enhancing-visual-content-with-seo"><span class="sec-n" aria-hidden="true">04</span>Enhancing visual content with SEO</h2>
<p>Visual elements play a significant role in user engagement, but they must be optimized for search engines:</p>
<ul>
<li><strong>Use Descriptive File Names and Alt Text:</strong> Clearly label images with relevant keywords to improve searchability.</li>
<li><strong>Ensure Fast Loading Times:</strong> Optimize image sizes to maintain quick page load speeds, enhancing user experience and SEO rankings.</li>
</ul>
<p>Properly optimized visuals not only attract users but also signal to search engines that your site is relevant and valuable.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="local-seo-for-dealerships"><span class="sec-n" aria-hidden="true">05</span>Local SEO for dealerships</h2>
<p>For dealerships, attracting local, in-market customers is vital:</p>
<ul>
<li><strong><a href="https://haydenschuster.com/writing/local-seo/">Optimize for Local Search</a>:</strong> Ensure your dealership appears in relevant local search results and Google Maps listings by focusing on local SEO tactics.</li>
<li><strong>Maintain Accurate Business Listings:</strong> Keep your Google Business Profile and other local directories up to date to enhance visibility and build trust with potential customers.</li>
</ul>
<p>By prioritizing local SEO, you make it easier for nearby shoppers to find and choose your dealership.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="building-long-term-authority-and-trust"><span class="sec-n" aria-hidden="true">06</span>Building long-term authority and trust</h2>
<p>Establishing your dealership as a credible source of information can lead to sustained success:</p>
<ul>
<li><strong><a href="https://haydenschuster.com/writing/content-strategy/">Create High-Quality, Evergreen Content</a>:</strong> Develop blog posts and resources that provide lasting value, such as car maintenance tips, vehicle comparisons, and financing advice.</li>
<li><strong>Engage with Customer Reviews:</strong> Actively manage and respond to online reviews to build trust and demonstrate your commitment to customer satisfaction.</li>
</ul>
<p>Consistently delivering valuable content and engaging with customers fosters long-term relationships and enhances your dealership's reputation.</p>
<p>By integrating these strategies, auto dealerships can effectively navigate the evolving SEO landscape, attract more qualified leads, and drive sustained growth in an increasingly competitive market.</p>
]]></content:encoded>
  </item>
  <item>
    <title>Why local SEO is underrated</title>
    <link>https://haydenschuster.com/writing/why-local-seo-matters/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/why-local-seo-matters/</guid>
    <pubDate>Mon, 26 Jan 2026 00:00:00 GMT</pubDate>
    <description>What local SEO is, how it helps a business with a physical location, the free tools worth using, and the three pillars a local SEO plan needs to stand on.</description>
    <content:encoded><![CDATA[<h2 id="what-local-seo-is"><span class="sec-n" aria-hidden="true">01</span>What local SEO is</h2>
<p>SEO, or <a href="https://searchengineland.com/guide/what-is-seo">Search Engine Optimization</a>, is the practice of setting up your website and all of your content to appeal to the algorithms that search engines use to rank quality content. While general SEO focuses on ranking highly for niche-specific queries, local SEO accounts for geographic location. This is especially important for brick-and-mortar locations. For example, if you own a local car dealership in Beaverton, Oregon, you want to be the first result when someone in your area searches for a &quot;car dealership near me.&quot;</p>
<p>Here's a <a href="https://blog.hubspot.com/marketing/local-seo">comprehensive guide to local SEO</a> from one of my favorite resources, HubSpot.</p>
<p>Tip: If you're interested in learning more, Semrush Academy has a <a href="https://www.semrush.com/academy/courses/local-seo-essentials-with-semrush/">local SEO course</a> covering Google Business Profile, local keyword research and tracking. It's a useful place to get the basics in order.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-local-seo-works"><span class="sec-n" aria-hidden="true">02</span>How local SEO works</h2>
<p>Search engines use artificial intelligence to crawl, index, and rank all online content and filter out the best results. Your position on the results page relies on your content containing the necessary elements Google is looking for, while not implementing penalizing elements. In short, local SEO works to gain preference from these platforms with a more specific geographical target. Instead of competing with the major companies in your market, you'll be working to stand out in your local community.</p>
<p>Every SEO dreads the almost weekly algorithm changes, but it's important to adjust and be on your toes.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-local-seo-helps-a-business"><span class="sec-n" aria-hidden="true">03</span>How local SEO helps a business</h2>
<p>According to RVS Media, these are <a href="https://www.rvsmedia.co.uk/blog/benefits-of-local-seo/#How-Local-SEO-Helps-Local-Businesses">key benefits of local SEO</a>:</p>
<ul>
<li>Enhanced Traffic</li>
<li>Better Conversion Rates</li>
<li>Less Advertising Costs</li>
<li>Continuous, Long-Term Business Growth</li>
<li>Long-Lasting SERP (Search Engine Results Page) Rankings</li>
<li>More Local Reviews</li>
<li>Google's 3-Pack Enlistment</li>
<li>Mobile Optimization</li>
<li>Community Building</li>
</ul>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="tools-i-use-for-local-seo"><span class="sec-n" aria-hidden="true">04</span>Tools I use for local SEO</h2>
<p>Here are some of my favorites:</p>
<ul>
<li><a href="https://www.semrush.com/blog/definitive-guide-google-search-console/">Google Search Console</a></li>
<li><a href="https://analytics.google.com/analytics/web/">Google Analytics</a></li>
<li><a href="https://www.screamingfrog.co.uk/seo-spider/">Screaming Frog</a></li>
<li><a href="https://moz.com/products/local">Moz Local</a></li>
<li><a href="https://ahrefs.com/">Ahrefs</a></li>
</ul>
<p>Semrush also keeps a <a href="https://www.semrush.com/blog/free-seo-tools/">list of free SEO tools</a>. Pick the tool that answers the question you actually have.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="the-three-pillars-of-a-local-seo-plan"><span class="sec-n" aria-hidden="true">05</span>The three pillars of a local SEO plan</h2>
<p>Try to establish these pillars when building your local SEO plan:</p>
<ul>
<li><a href="https://haydenschuster.com/writing/technical-seo/"><strong>Technical</strong>.</a> This includes tasks like fixing technical errors, using the proper URL structure, setting up the right website hierarchy, managing page speed, etc.</li>
<li><a href="https://haydenschuster.com/writing/content-strategy/"><strong>Content</strong>.</a> While more exciting and creative than technical SEO, content is time-consuming and expensive (if outsourced). Having said that, it's the fuel to any good SEO strategy. Without it, you aren't going anywhere.</li>
<li><strong>Authority</strong>. You need to tap into the authority of other websites to set your brand apart. The more you align with other trustworthy sites, the faster you'll grow.</li>
</ul>
]]></content:encoded>
  </item>
  <item>
    <title>How I think about technical SEO on enterprise websites</title>
    <link>https://haydenschuster.com/writing/technical-seo-complex-sites/</link>
    <guid isPermaLink="true">https://haydenschuster.com/writing/technical-seo-complex-sites/</guid>
    <pubDate>Sun, 25 Jan 2026 00:00:00 GMT</pubDate>
    <description>Why checklist technical SEO stalls on large sites, and how to treat crawl, indexation and performance problems as one system built for long-term stability.</description>
    <content:encoded><![CDATA[<p>That's where technical SEO stops being a checklist and starts becoming a systems problem.</p>
<h2 id="the-problem-with-most-technical-seo-advice"><span class="sec-n" aria-hidden="true">01</span>The problem with most technical SEO advice</h2>
<p>A lot of technical SEO guidance is framed as a list of fixes:</p>
<ul>
<li>Improve Core Web Vitals</li>
<li>Clean up indexation</li>
<li>Reduce errors</li>
<li>Follow best practices</li>
</ul>
<p>None of that is wrong, but it assumes a level of control and simplicity that rarely exists on complex websites.</p>
<p>On larger sites, technical SEO problems are usually <strong>symptoms, not root causes</strong>.</p>
<ul>
<li>Crawl issues often point to architectural decisions</li>
<li>Indexation problems expose internal linking gaps</li>
<li>Performance issues surface tradeoffs made elsewhere in the stack</li>
</ul>
<p>Treating these in isolation often creates more work without meaningfully improving outcomes.</p>
<p>This is why <strong>purely tool-driven technical SEO tends to stall</strong>. You can surface hundreds of issues, but without a system-level view, it's hard to know what actually matters.</p>
<p><strong>Essential takeaway:</strong> <a href="https://haydenschuster.com/writing/technical-seo/">Technical SEO</a> tools are good at showing problems, but poor at telling you which problems are worth solving.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="how-i-actually-think-about-technical-seo"><span class="sec-n" aria-hidden="true">02</span>How I actually think about technical SEO</h2>
<p>I approach technical SEO as an <strong>interconnected system</strong>, not a set of independent optimizations.</p>
<p>The goal is <strong>stability, clarity, and scalability</strong>.</p>
<p>That means starting with questions like:</p>
<ul>
<li>How does this site want search engines to understand it?</li>
<li>Where are we introducing unnecessary complexity?</li>
<li>What decisions will still make sense six months from now?</li>
</ul>
<p>On complex websites, every technical change comes with tradeoffs.</p>
<ul>
<li>Fixing one issue can expose another</li>
<li>Improving crawl efficiency may require structural changes that affect content teams</li>
<li>Performance gains may conflict with design or product priorities</li>
</ul>
<p>Good technical SEO acknowledges those realities instead of pretending they don't exist.</p>
<p>I care less about eliminating every warning and more about <strong>building foundations that support consistent growth over time</strong>.</p>
<p><strong>Essential takeaway:</strong> Strong technical SEO optimizes for long-term behavior, not short-term cleanliness.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-this-looks-like-on-real-websites"><span class="sec-n" aria-hidden="true">03</span>What this looks like on real websites</h2>
<h3>During site launches and migrations</h3>
<p>Technical SEO success here comes from understanding how URLs, templates, internal linking, and indexation work together so changes don't destabilize search visibility.</p>
<h3>On large inventories, multi-location sites, and enterprise CMS setups</h3>
<p>At scale, small structural decisions compound quickly.</p>
<ul>
<li>A single template issue can affect thousands of pages</li>
<li>Internal linking patterns matter more than individual page optimizations</li>
<li>Structural consistency beats page-level perfection</li>
</ul>
<p>Technical SEO becomes about <strong>designing systems that behave predictably under pressure</strong>.</p>
<p>When that foundation is solid, tactical improvements actually stick.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="common-mistakes-i-see-on-complex-sites"><span class="sec-n" aria-hidden="true">04</span>Common mistakes I see on complex sites</h2>
<p>A few patterns show up repeatedly.</p>
<ul>
<li>Over-indexing on tools and reports without translating them into decisions</li>
<li>Trying to fix everything at once instead of sequencing work by impact and risk</li>
<li>Treating technical SEO as something to clean up rather than integrate into the ongoing strategy</li>
</ul>
<p>The most damaging mistake is addressing symptoms while leaving the underlying structure untouched. That's how <strong>technical debt quietly rebuilds itself</strong>.</p>
<p><strong>Essential takeaway:</strong> If the structure stays broken, the same problems will keep returning in different forms.</p>
<div class="clear-line" aria-hidden="true"><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i><i></i></div><h2 id="what-technical-seo-on-complex-sites-comes-down-to"><span class="sec-n" aria-hidden="true">05</span>What technical SEO on complex sites comes down to</h2>
<p>Technical SEO on complex websites is about <strong>designing systems that search engines and humans can both navigate reliably</strong>, even as the site evolves.</p>
<p>This mindset underpins how I approach technical SEO and site architecture, and it's the difference between short-term fixes and long-term performance.</p>
]]></content:encoded>
  </item>
</channel>
</rss>
