<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Janak Pokharel: SEO and Search Notes]]></title><description><![CDATA[Janak Pokharel: SEO and Search Notes]]></description><link>https://janakpokharel.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Tue, 20 Oct 2026 15:42:16 GMT</lastBuildDate><atom:link href="https://janakpokharel.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Generative Engine Optimization: What the Research Shows and What Developers Can Do]]></title><description><![CDATA[Generative engine optimization explained: what the KDD 2024 GEO study found, what Google says, and how Next.js developers can apply it.]]></description><link>https://janakpokharel.hashnode.dev/generative-engine-optimization-what-the-research-shows-and-what-developers-can-do</link><guid isPermaLink="true">https://janakpokharel.hashnode.dev/generative-engine-optimization-what-the-research-shows-and-what-developers-can-do</guid><category><![CDATA[SEO]]></category><category><![CDATA[Next.js]]></category><category><![CDATA[Artificial Intelligence]]></category><dc:creator><![CDATA[Janak Pokharel]]></dc:creator><pubDate>Fri, 16 Oct 2026 07:29:27 GMT</pubDate><content:encoded><![CDATA[<p><strong>Last Reviewed:</strong> October 16, 2026 | <strong>Fact-Checked:</strong> October 16, 2026</p>
<p>Generative engine optimization (GEO) is the practice of structuring content so AI answer engines are more likely to use and cite it. The main study, presented at KDD 2024, found that adding quotations, statistics and cited sources raised visibility in a simulated engine, while keyword stuffing lowered it. The tests used a research setup, and Google says its AI features need no special optimization.</p>
<p>Generative engine optimization has plenty of confident advice and very little checked evidence. Most guides stack statistics without naming where they came from, then promise citations that nobody can guarantee. This post sticks to what a published study measured and what official documentation says.</p>
<p>I'm Janak Pokharel, an SEO and paid ads consultant. I have not run controlled GEO experiments, so I am not presenting test results of my own. I am reporting a peer-reviewed paper and documentation from Google, OpenAI and Anthropic, and I label my own analysis as analysis. You will see what the paper tested, which methods scored highest, where the study stops being useful, what Google tells site owners, and how a Next.js developer can apply the findings without overclaiming. The aim is to help you make better content decisions, not to chase a formula that the evidence does not support. Nothing here is a guarantee. Everything below was checked on October 16, 2026.</p>
<h2>What did the GEO paper test?</h2>
<p>The GEO paper, by Pranjal Aggarwal and five co-authors, tested nine ways of rewriting web content to increase its visibility in AI-generated answers. It used GEO-bench, a set of 10,000 queries, and a simulated generative engine. It was presented at the 30th ACM SIGKDD Conference in August 2024.</p>
<p>The paper, titled <a href="https://arxiv.org/abs/2311.09735">GEO: Generative Engine Optimization</a>, lists Vishvak Murahari, Tanmay Rajpurohit, Ashwin Kalyan, Karthik Narasimhan and Ameet Deshpande as the other authors. The version I read is v3, dated June 28, 2024.</p>
<p>The setup works in two steps. Each query was paired with the cleaned text of the top five Google results. A model, gpt-3.5-turbo at temperature 0.7, then wrote an answer from those sources. The authors measured two things: a position-adjusted word count, which scores how much of the answer is attributed to your source and how early it appears, and a subjective impression score.</p>
<h2>Which methods scored highest and lowest?</h2>
<p>In the paper's main table, Quotation Addition scored highest at 27.2 against a 19.3 baseline, followed by Statistics Addition at 25.2, Fluency Optimization at 24.7 and Cite Sources at 24.6. Keyword Stuffing scored 17.7, below the baseline. The scores measure visibility inside a simulated AI answer, not Google rankings.</p>
<table>
<thead>
<tr>
<th>Method</th>
<th>What it changes</th>
<th>Overall score</th>
<th>Change vs baseline</th>
</tr>
</thead>
<tbody><tr>
<td>Quotation Addition</td>
<td>Adds quotations from relevant sources</td>
<td>27.2</td>
<td>+40.9%</td>
</tr>
<tr>
<td>Statistics Addition</td>
<td>Adds statistics</td>
<td>25.2</td>
<td>+30.6%</td>
</tr>
<tr>
<td>Fluency Optimization</td>
<td>Improves how smoothly the text reads</td>
<td>24.7</td>
<td>+28.0%</td>
</tr>
<tr>
<td>Cite Sources</td>
<td>Adds citations to sources</td>
<td>24.6</td>
<td>+27.5%</td>
</tr>
<tr>
<td>Technical Terms</td>
<td>Adds technical vocabulary</td>
<td>22.7</td>
<td>+17.6%</td>
</tr>
<tr>
<td>Easy-to-Understand</td>
<td>Simplifies the language</td>
<td>22.0</td>
<td>+14.0%</td>
</tr>
<tr>
<td>Authoritative</td>
<td>Uses a more authoritative style</td>
<td>21.3</td>
<td>+10.4%</td>
</tr>
<tr>
<td>Unique Words</td>
<td>Adds unusual vocabulary</td>
<td>20.5</td>
<td>+6.2%</td>
</tr>
<tr>
<td>Keyword Stuffing</td>
<td>Adds more query keywords</td>
<td>17.7</td>
<td>-8.3%</td>
</tr>
<tr>
<td>No optimization (baseline)</td>
<td>Nothing</td>
<td>19.3</td>
<td>0%</td>
</tr>
</tbody></table>
<p>I calculated the last column from the paper's printed scores. The scores themselves come from the paper's Table 1.</p>
<p>The pattern is useful for writers. The best methods add substance a reader can check: a quote, a number, a named source. The only method that made things worse is the one SEO has used for years.</p>
<h2>What are the limits of the study?</h2>
<p>The study used a simulated engine built on gpt-3.5-turbo, tested single-turn questions only, and found that effectiveness varies by domain. Its authors also note that methods may need to adapt as generative engines evolve. A Perplexity.ai test on a 200-query subset reported Quotation Addition improving position-adjusted word count by 22%, which is promising but still one test.</p>
<p>Here is how I read those limits. The paper does not measure how often ChatGPT, Gemini, Claude or Google's AI Overviews cite a page, because it did not test those products directly. The engine in the main experiment is a research setup, not a commercial one. The data also predates today's products. Treat the results as a reason to improve content quality, not as a ranking formula.</p>
<h2>What does Google tell site owners to do?</h2>
<p>Google's AI features documentation, updated December 10, 2025, says a page must be indexed and eligible to show in Search with a snippet to appear as a supporting link in AI Overviews or AI Mode. Google lists no extra technical requirements and says no special schema.org markup, AI text files or other optimization is needed.</p>
<p><a href="https://developers.google.com/search/docs/appearance/ai-features">Google's AI features guidance</a> lists ordinary best practices instead:</p>
<ul>
<li><p>Allow crawling in robots.txt and in any CDN or host settings.</p>
</li>
<li><p>Make content easy to find through internal links.</p>
</li>
<li><p>Provide a good page experience.</p>
</li>
<li><p>Keep important content in text form.</p>
</li>
<li><p>Support text with relevant images and videos.</p>
</li>
<li><p>Make sure structured data matches the visible page text.</p>
</li>
<li><p>Keep Business Profile and Merchant Center information current.</p>
</li>
<li><p>Verify your site in Search Console.</p>
</li>
</ul>
<p>Google also says traffic from AI Overviews and AI Mode is counted in the Web search type in Search Console's performance report. There is no separate AI report.</p>
<h2>How do you build citable pages in Next.js?</h2>
<p>Build citable pages by putting the direct answer in server-rendered text near the top of each section, supporting it with a named source or a verified quotation, and keeping structured data consistent with the visible text. These steps follow Google's guidance and the paper's findings, but neither guarantees citations from any AI engine.</p>
<p>In Next.js, a component without <code>'use client'</code> is a Server Component, so its text is in the initial HTML. A small wrapper keeps every section consistent:</p>
<pre><code class="language-tsx">// components/AnswerSection.tsx (a Server Component: no 'use client')
type Props = {
  id: string
  question: string
  answer: string
  children: React.ReactNode
}

export function AnswerSection({ id, question, answer, children }: Props) {
  return (
    &lt;section id={id}&gt;
      &lt;h2&gt;{question}&lt;/h2&gt;
      &lt;p&gt;&lt;strong&gt;{answer}&lt;/strong&gt;&lt;/p&gt;
      {children}
    &lt;/section&gt;
  )
}
</code></pre>
<p>Use it with a short checklist, which is my own analysis and not a proven method:</p>
<ol>
<li><p>Write the answer in 30 to 60 words that still make sense if copied alone.</p>
</li>
<li><p>Name the subject instead of writing "it" or "this".</p>
</li>
<li><p>Add one statistic or one verified quotation only where it supports the claim, and name the source in the sentence.</p>
</li>
<li><p>Show a visible review date for topics that change.</p>
</li>
<li><p>If you add JSON-LD, make it match the text on the page. The <a href="https://nextjs.org/docs/app/guides/json-ld">Next.js JSON-LD guide</a> shows how to render it safely.</p>
</li>
</ol>
<h2>Which crawlers does robots.txt control?</h2>
<p>OpenAI and Anthropic each document separate crawlers for search, model training and user-initiated visits. Blocking a search crawler can keep a site out of that product's answers, while blocking a training crawler signals that content should not be used for training. Robots.txt changes can take about 24 hours to apply.</p>
<table>
<thead>
<tr>
<th>Bot</th>
<th>Operator</th>
<th>Purpose, as documented</th>
<th>What blocking it means</th>
</tr>
</thead>
<tbody><tr>
<td>OAI-SearchBot</td>
<td>OpenAI</td>
<td>Surfaces sites in ChatGPT's search features</td>
<td>The site will not be shown in ChatGPT search answers</td>
</tr>
<tr>
<td>GPTBot</td>
<td>OpenAI</td>
<td>Crawls content that may be used for model training</td>
<td>Signals that content should not be used for training</td>
</tr>
<tr>
<td>ChatGPT-User</td>
<td>OpenAI</td>
<td>Visits pages when a user asks</td>
<td>OpenAI says robots.txt rules may not apply</td>
</tr>
<tr>
<td>ClaudeBot</td>
<td>Anthropic</td>
<td>Collects web content for model development</td>
<td>Signals exclusion from training datasets</td>
</tr>
<tr>
<td>Claude-SearchBot</td>
<td>Anthropic</td>
<td>Improves the quality of search results</td>
<td>May reduce visibility in user search results</td>
</tr>
<tr>
<td>Claude-User</td>
<td>Anthropic</td>
<td>Fetches pages when a user asks Claude a question</td>
<td>Prevents retrieval for that user query</td>
</tr>
</tbody></table>
<p>This table follows <a href="https://developers.openai.com/api/docs/bots">OpenAI's crawler documentation</a> and <a href="https://support.claude.com/en/articles/8896518-does-anthropic-crawl-data-from-the-web-and-how-can-site-owners-block-the-crawler">Anthropic's crawler article</a>. Bots and policies change, so re-check both pages before you edit your file. Whether to allow training crawlers is a business choice.</p>
<h2>Conclusion</h2>
<p>The research supports a modest conclusion: content with checkable quotations, statistics and named sources was more visible in a simulated AI answer, and keyword stuffing was not. Google says pages need to be indexed and snippet-eligible, with no special markup. So do the basics well, state answers clearly, and avoid promising citations. Pick one page this week, rewrite its main answer in plain, source-backed language, and confirm that the page is indexed in Search Console. Revisit the paper's findings as engines change, since its authors expect methods to need updating. If you want help applying this to a site, you can <a href="https://janakpokharel.com.np/contact">request an SEO proposal</a> or read about <a href="https://janakpokharel.com.np/services/advanced-seo">advanced SEO services</a>.</p>
<h2>Frequently asked questions</h2>
<h3>What is generative engine optimization?</h3>
<p>Generative engine optimization is the practice of structuring and improving content so AI answer engines can understand, retrieve and potentially cite it. The term comes from a 2023 research paper. It overlaps heavily with SEO, because Google requires pages to be indexed before they can appear as supporting links.</p>
<h3>Does GEO replace SEO?</h3>
<p>No. Google says a page must be indexed and eligible to show with a snippet to appear in AI Overviews and AI Mode, so crawlability and indexing still come first. GEO is better treated as an extra layer of clear, well-sourced writing on top of sound SEO.</p>
<h3>Does keyword stuffing help in AI answers?</h3>
<p>In the paper's simulated tests, no. Keyword Stuffing scored 17.7 against a 19.3 baseline, about 8.3% lower. That result comes from a research setup, so treat it as evidence against the tactic, not a measurement of any commercial engine.</p>
<h3>Should I block GPTBot or ClaudeBot?</h3>
<p>That is a business decision. GPTBot and ClaudeBot relate to model training, while OAI-SearchBot and Claude-SearchBot relate to search features. Blocking training bots signals that content should not be used for training. Blocking search bots can reduce your visibility in those products.</p>
<h3>Can anyone guarantee citations in ChatGPT, Gemini or Claude?</h3>
<p>No. The paper reports relative visibility gains in tests, and Google documents no special optimization. No study I reviewed shows a method that guarantees a citation. Be cautious of any provider that promises one.</p>
<hr />
<p><em>Janak Pokharel is an SEO and paid ads consultant based in Kathmandu and a co-founder of Limi Creatives. He publishes guides at</em> <a href="https://janakpokharel.com.np"><em>Janak Pokharel's website</em></a><em>.</em></p>
]]></content:encoded></item></channel></rss>