Blogo Team
100 B2B Questions: 94% of Cited Pages Were Inner Pages
Our 2026 study of 325 recorded API citations: page types cited for B2B content and SEO-tool questions, homepage vs inner page, and the evidence limits.
We sent 100 questions written for B2B marketers and export manufacturers through an API configured for web search, then examined its recorded citation annotations. After tracking cleanup and deduplication within each question, 305 of 325 citations (94%) pointed to an inner page and 20 (6%) to a homepage. Official guidance from Google, OpenAI and others made up 42% of the recorded citations. The records contain no citation annotations for 28 questions; they do not establish whether those requests used search.
This post shares the data, the method and its limits, and what we think it means for a manufacturer or exporter deciding what to publish next. For the record: Blogo was cited zero times.
The study at a glance
| Measure | Result |
|---|---|
| Questions asked | 100 (50 English, 50 Chinese) |
| Questions that produced at least one citation | 72 |
| Questions without recorded citation annotations | 28, including 16 of the 20 how-to questions |
| Citations after per-question normalization | 325 |
| Inner pages vs homepages | 305 inner (94%), 20 homepages (6%) |
| Citations to official guidance | 137 (42%) |
| Citations to vendor product, feature, docs and help pages | 90 (28%) |
| Citations to wordpress.org plugin-directory pages | 17 (5%) |
| Citations to third-party "best tools" listicles | 3 (1%) |
| Citations to Blogo | 0 |
Who we asked about, and what we asked
We wrote the 100 questions by hand for two groups of people: 50 in English for overseas B2B marketers and 50 in Chinese for teams at export factories. Each language set covers five buying stages with 10 questions each:
- Problem, for example "Why is our B2B blog getting no traffic from Google?"
- How-to, for example "How to build a content calendar for a B2B manufacturer website"
- Solution or tool, for example "What is the best AI blog writing tool for B2B manufacturers?"
- Comparison, for example "Jasper vs Surfer SEO vs Frase for B2B blog content"
- Trust or risk, for example "Does Google penalize AI-generated content in 2026?"
None of the questions names Blogo. We wrote them to represent decisions a buyer might make before knowing which vendors exist; they are not measured search demand or a sample of customer queries.
Finding 1: inner pages, not homepages, get cited
Out of 325 citations, 305 went to an inner page: a help article, a documentation page, a feature page, a plugin listing or a guide. Only 20 went to a homepage, and all 20 came from tool and comparison questions (11 and 9 respectively). Problem, how-to and trust questions never produced a homepage citation in this run.
The 8 retained ChatGPT browser spot-check records, labelled temporary and unpersonalized at capture, report 21 cited links, one of them a homepage. That is a small, separate observation; the API run was not 100 native ChatGPT browser chats.
Our editorial reading is to give a specific buyer task a useful answer, rather than rely on a homepage summary. The observed page types do not establish why a model selected a source or predict which page it will cite next.
Finding 2: official guidance dominates problem and trust questions
137 of the 325 citations (42%) went to what we classed as official guidance: Google Search Central and Search Console help pages, OpenAI help and developer docs, Bing, WordPress documentation, and government sites such as nist.gov and copyright.gov.
The share depends heavily on the type of question:
| Stage | Citations | Official guidance | Questions without recorded citations |
|---|---|---|---|
| Problem | 66 | 60 | 1 of 20 |
| How-to | 19 | 16 | 16 of 20 |
| Solution or tool | 100 | 16 | 0 of 20 |
| Comparison | 102 | 12 | 3 of 20 |
| Trust or risk | 38 | 33 | 8 of 20 |
When a marketer asks why traffic is flat or whether Google penalises AI-written content, the answer leans on Google's own pages. The single most-cited URL in the whole run was Google's guide to creating helpful, reliable, people-first content (17 citations), followed by Google's guidance on using generative AI content (10 citations).
Vendors and agencies were almost never cited at these stages. If your plan is to win "is AI content risky?" questions with your own blog post, you are competing with the primary source.
Finding 3: most how-to questions had no recorded citations
28 of the 100 questions had no recorded citation annotations. 16 of those were how-to questions, out of 20 how-to questions in total. Examples include "How to write a buyer's guide for a custom manufactured product" and "How to plan internal links between blog posts and product pages on WordPress". The runner did not retain a search or tool-call trace, so these records cannot tell us why citations were absent.
The retained browser notes separately describe 3 of the 8 chats (one English and two Chinese questions) as showing no search. Those historical observations do not establish the API requests' search activity or prove that an answer came only from the model's prior knowledge.
This result does not measure the usefulness of a how-to guide or its likelihood of earning future citations. A guide can still help a buyer complete a task; evaluate that purpose separately from the annotation counts in this run.
Finding 4: tool questions cite vendor help and feature pages
Solution and comparison questions produced the most citations (100 and 102). Here the cited pages were mostly vendors' own inner pages: product and feature pages (49 citations overall), docs and help articles (41), and plugin listings.
The most-cited domains across the whole run were:
| Domain | Citations | Questions citing it |
|---|---|---|
| google.com (incl. developers. and support.) | 100 | 37 |
| openai.com | 25 | 13 |
| wordpress.org | 24 | 8 |
| jasper.ai | 11 | 10 |
| surferseo.com | 10 | 9 |
| writesonic.com | 9 | 7 |
| semrush.com | 9 | 9 |
| frase.io | 7 | 6 |
| clearscope.io | 7 | 5 |
| ahrefs.com | 6 | 5 |
| marketmuse.com | 6 | 3 |
Two patterns stood out:
- Help-center articles appeared for capability questions. The API answer to the question about a tool that tells you what to write next based on your site and search data recorded a Surfer documentation page about adding Google Search Console, a Semrush features page, an Ahrefs help article and a Clearscope support page. Each page stated a capability in plain words.
- wordpress.org listings appeared for WordPress questions. For "AI writer that sends drafts to WordPress for review", the API record cited three wordpress.org plugin pages, a help article from another vendor and one homepage. The plugins it named were small and little known, not the biggest SEO brands.
Third-party "best tools" listicles were rare in the API run (3 citations), but they did appear in the ChatGPT web spot-checks, including dupple.com and aiunpacking.com.
Finding 5: Chinese tool questions are where homepages still win
Chinese questions produced 13 of the 20 homepage citations, against 7 for English. The biggest cluster came from one question asking which Chinese AI writing tools exist for export websites: 5 of its 8 citations were homepages of small Chinese tools. A question about how to choose a foreign-trade SEO company also cited an agency homepage. That is the one place in our data where homepages were a common answer, and the cited sites were small.
A second detail: when we asked a Chinese question about AI tools for writing English export blogs in ChatGPT itself, it cited English vendor blog posts and the same English listicle it had cited for the equivalent English question. It did not name a China-specific tool.
Finding 6: the picks change from run to run
The same question does not always produce the same answer. For the "what to write next" question, the API run cited dango.sh, the MarketMuse homepage, a Semrush solutions page and a Google Search Console help article, while the ChatGPT web spot-check cited a different set of vendor docs. For "best AI blog writing tool for B2B manufacturers", one ChatGPT chat recommended Jasper; an earlier personalized chat, which we discarded, had recommended Writesonic.
So treat patterns (page type, inner vs homepage, official vs vendor) as the signal, and treat any single "winner" as noise.
What this means for a manufacturer's website
The study was about questions for marketers, not about industrial products, so apply it with care. Still, the patterns line up with what Google says publicly. Google's AI optimization guide advises against recycling what others have already said and in favour of non-commodity content with a unique point of view. It also says special files, chunking content or rewriting just for AI search are not needed. Google's AI features documentation says there are no additional requirements to appear in AI Overviews or AI Mode beyond being indexed and eligible for a snippet.
A practical checklist:
- Give every important question its own URL. One page per product family, material, process or capability, each opening with a plain one-sentence answer.
- Write help-style pages, not only marketing pages. Tolerances, MOQ logic, lead-time factors, certifications, inspection steps and how to send a drawing for a quote. Vendors in our data won tool questions with exactly this kind of page.
- Publish something only you can publish. Test results, process data, failure cases, real photos of your line. Google's helpful content guidance asks: "Does the content provide original information, reporting, research, or analysis?"
- Do not try to out-rank Google on Google topics. For SEO and AI-policy questions, link to the official page and add your own experience instead.
- Be listed where models already look. In our data that meant directories such as wordpress.org. For a manufacturer it may mean industry associations, trade-show exhibitor lists and recognised supplier directories.
- Check that you are not blocking the crawlers. OpenAI's crawler documentation says sites that opt out of OAI-SearchBot will not be shown in ChatGPT search answers.
- Measure what you can. Google has added generative AI performance reports to Search Console, which show impressions, pages, countries, devices and dates for AI features in Search and Discover.
Example: a maker of stainless-steel fasteners could replace one long "Products" page with separate pages for "A2 vs A4 stainless bolts for marine use", "How we test salt-spray resistance" and "Minimum order and lead time for custom fasteners". Each answers one buyer question, and each is an inner page.
Method and limitations
- Requested model and search configuration. We sent each question once through OpenRouter, requesting the alias
openai/gpt-5.6-lunawith a web-search plugin and medium search context. The alias was copied from the request; the runner did not retain a confirmed response model/provider identity or search trace. Each payload contained one user question, no system prompt, conversation history or conversation ID. That describes the sent payload, not the provider's internal memory or search behaviour. A recorded citation is a URL returned as a url_citation annotation. All 100 capture rows contain answers and no recorded errors, with $1.52 in reported API usage cost. - ChatGPT browser spot-checks. The retained records cover 8 questions (en01, en08, en21, en22, en23, zh01, zh08, zh21), labelled temporary and unpersonalized on chatgpt.com's default model. An earlier memory-on conversation was described in a note; a personalized record was discarded as biased. These historical labels and observations were not independently reverified, and they do not identify the exact browser backend model.
- Classification. A script stripped tracking parameters, grouped URLs by registrable domain, marked homepage vs inner page, and labelled page types by URL pattern. URL-pattern labels are approximate. The "google.com" figure groups developers.google.com, support.google.com and other Google subdomains.
- Limits. This is one run on one date (5 October 2026). Citation annotations are recorded source references, not independent verification of the answer or source content. The requested API alias does not establish the model behind chatgpt.com's default. The 100 authored questions are not a representative demand survey, and these counts do not establish current indexing, rankings or model recommendations.
Blogo lets you start with a buyer question, review its writing plan and selected references, then read and edit the draft. Checks surface selected factual statements and source problems; remaining issues still need your review. Copy or download Markdown for your editorial workflow. WordPress handoff creates a new unpublished draft only with an enabled sending feature, a configured connection for your site, a real author, cleared review checks and confirmation of the current article. An unchanged version can reuse its saved receipt; changed content can create another draft.
FAQ
Were homepages or inner pages cited more often in this study? In the API records, inner pages by a wide margin: 305 of 325 citations (94%) were inner pages and 20 (6%) were homepages, all from tool and comparison questions. The requested API alias and the separate browser spot-checks are described above.
Which sites were cited most in the recorded B2B content and SEO answers? In the API records, google.com led with 100 citations across 37 questions, mostly Google Search Central and Search Console help pages, followed by openai.com (25) and wordpress.org (24). Among tool vendors, jasper.ai, surferseo.com, writesonic.com and semrush.com were cited most often.
Why did some questions get no citations? The records do not tell us why. They contain no citation annotations for 28 of the 100 questions, including 16 of the 20 how-to questions, but no search trace was retained. Absence of citations does not prove absence of search.
Was Blogo cited? No. Blogo was cited zero times in these historical records. The study does not establish why, or measure Blogo's current citation visibility.
Will the same questions give the same citations next week? The retained API and browser records show different picks for some repeated questions. They do not measure future stability. Use the dated page-type observations as context, then verify the sources and the reader task you want your own page to answer.
Want Blogo to draft your next article?
Start with your buyer’s question. Review the plan, edit the draft and export Markdown.