Google-Display-Ads-Bot Allow is publisher-only

A robots.txt Allow line for Google-Display-Ads-Bot on www.oernoe.com is easy to misread as a Search license. A reader sees the string, notices Google in the name, and decides that Oernoe Search must be feeding queries into display advertising. That leap skips the documents that already refuse it. Privacy keeps search history out of advertising profiles. How Search works keeps queries with Search. About and the homepage keep the publisher host separate from search.oernoe.com. This essay is privacy writing about one bot name. It grounds the live robots.txt, Privacy, Cookies, and How Search works. It names only the ads-bot strings the live file shows. It is not a remake of the Mediapartners-Google Allow essay. That hinge already refused the Mediapartners leap. The hinge here is narrower: Google-Display-Ads-Bot Allow is a publisher-only fetch permission, and it does not travel into Search as profiling.

## What the live file actually says

A guest fetch of https://oernoe.com/robots.txt on 8 September 2026 returned a short file. Mediapartners-Google is Allowed across the site. Google-Display-Ads-Bot is Allowed across the site. The ordinary wildcard user-agent is Allowed across the site, with Disallow only for /api/ and /debug/. Host is declared as https://www.oernoe.com. Discovery points at the public listing of URLs the company claims to publish. Those are the only ads-bot names used below, because those are the only ads-bot names the live file shows. Inventing extra bot strings would make the essay stop being checkable.

What we publish closes with a mechanical check that matches the file: robots.txt should allow Google’s ads crawlers. Eligible inventory lives on finished How-To, finished guides, and substantial journal articles that still pass originality and length checks. Ads crawlers need to fetch those documents to evaluate them. Blocking Google-Display-Ads-Bot while asking a display network to understand publisher pages would be theater: ask for review, then refuse the fetch that review requires. Allowing the bot on www is therefore part of publisher honesty. It is not a side door that quietly turns search.oernoe.com into an ad-profile machine.

The Host line matters for the same reason. The file declares www.oernoe.com as the publisher host for this robots contract. Search is a different hostname. Chat, Health, Docs, Drive, Tracker, AI, and Account are different hostnames. An Allow line in the www robots file does not rewrite Privacy on those hosts. It does not install AdSense on their shells. It does not create a query file.

## A display-ads fetch is still not a Search profile

Robots.txt is a fetch contract. An Allow line tells a named crawler it may retrieve URLs on this host under ordinary politeness rules. It does not hand Google a copy of anyone’s Search history. It does not rewrite section 3 of the Privacy Policy. It does not move advertising onto Chat. It does not create an advertising profile from a query typed at search.oernoe.com.

Privacy Policy section 3 states the Search limit in hallway language. Oernoe does not sell account information or search history. Oernoe does not use search history to create advertising profiles. Oernoe does not provide account or search data to advertisers for their own direct marketing. Those sentences are not optional color. They are the privacy map that a robots Allow cannot override.

How Oernoe Search works repeats the same limit from the product side. Ranking uses signals that do not require a search-history advertising profile. Queries are not sold or used to build advertising profiles. The guide’s funding FAQ answers how the company makes money if Search does not profile users: optional premium features and contextual Google ads on selected publisher pages such as that guide. Search queries stay with Search. The publisher page that explains Search may still load AdSense. That is a different system. Treating Google-Display-Ads-Bot Allow as proof that Search sells the query collapses those systems on purpose.

Cookie Policy section 2 makes the same split for advertising technology. Selected substantial publisher pages on www.oernoe.com may use Google AdSense. Google and its partners may use cookies or similar identifiers, IP address, browser and device information, page context, and ad interaction data to serve, secure, limit, and measure contextual or non-personalized ads. Search queries typed at search.oernoe.com are not an input to those units. The bot Allow that lets Google fetch the publisher page is about page context on www. It is not a pipe from the Search box.

## Why Display-Ads-Bot is a publisher sentence

Mediapartners-Google and Google-Display-Ads-Bot both appear in the same short file. They are both ads-related crawlers Allowed on the publisher. They are not interchangeable slogans. This essay’s job is the Display-Ads-Bot line as a publisher-bound sentence: the bot may fetch www documents so display advertising systems can evaluate publisher inventory. That evaluation lives on the publisher hostname where AdSense is allowed to appear. It does not live inside Search ranking. It does not live inside Health notes. It does not live inside Chat messages.

Privacy Policy section 1 draws the host fence before any bot name is interesting. Advertising disclosures apply to selected publisher pages on www.oernoe.com. They do not mean advertising is enabled on Chat, Drive, Docs, Health, Tracker, Account, login screens, or other application surfaces. Cookie Policy section 3 lists the exclusions in operational language: homepage, About, Team, Contact, short journal posts, the journal index, the guides index, editorial standards, login and signup, account and application pages, legal pages, error pages, and service subdomains. Google-Display-Ads-Bot being Allowed to fetch www does not erase those exclusions. An Allow is not an enablement of every product surface.

Privacy Policy section 4 names where AdSense may load on www: selected substantial publisher pages, including How-To, finished guides such as How Search works and Corrections, and substantial journal articles. It also names where AdSense is not loaded: homepage, About, login or signup, protected application pages, legal pages, error pages, the journal index, short or promotional journal posts, the guides index, editorial standards, or service subdomains. Ads are requested as non-personalized by default. Google may still process page context, cookies or similar identifiers, IP address, browser and device information, and ad interaction data to serve, secure, limit, and measure advertisements. That processing is publisher-side advertising work. It is not Search building a profile from queries.

## The zero-tracking failure that makes the leap tempting

Corrections, updated 26 August 2026, already named the older homepage failure that still tempts the leap. Older homepage and product copy talked as if the whole Oernoe network had no ads, no cookies, and no third parties. That was false once this publisher site applied for Google AdSense. Search still does not use queries as an advertising file. Selected finished pages on www.oernoe.com may show Google ads, and Google may process page context, cookies, IP address, and device data on those pages. Both sentences have to be true at once.

A reader who still wants a single slogan will treat Google-Display-Ads-Bot Allow as proof that the “no tracking” promise never meant anything, or as proof that Search must be the ad file. Both readings are lazy. The correction is the split, not a new slogan. Publisher Allow for ads crawlers belongs with publisher AdSense disclosures. Search’s refusal to keep a query file for ads belongs with How Search works and Privacy section 3. Collapsing them is how a robots line becomes a false business model.

About’s funding section prints the same split without needing a bot name. Account creation is free. Some products have optional paid tiers, and those are labeled in the product. Selected finished pages on this hostname may show Google ads. Oernoe does not sell account or search data, and does not sell journal articles, links, or reviews. Sponsored-post pitches are declined. Ads do not appear on Search, Health, Chat, AI, Docs, Drive, Tracker, or Account. They do not appear on Home, About, legal pages, or the journal listing. Google-Display-Ads-Bot Allow sits inside that publisher inventory story. It does not rewrite the Search half.

## Three systems that share a brand and refuse to share a file

First system: Search at search.oernoe.com. Ranking without a search-history advertising profile. Continuous crawl that respects robots.txt and rate limits. Queries not sold. Personalization that is explicit and under the user’s control when an account saves preferences. How Search works is the public guide for that system.

Second system: the publisher at www.oernoe.com. Journal, guides, How-To, company pages, legal. Selected finished pages may load AdSense. Privacy and Cookies disclose what Google may process on those pages. robots.txt Allows Google-Display-Ads-Bot and Mediapartners-Google so ads crawlers can fetch eligible documents. What we publish says which pages belong in the index and which stay up but leave it.

Third system: product and account hosts. Health, Chat, AI, Docs, Drive, Tracker, and Account. Privacy section 1 says advertising disclosures for www do not enable ads on those surfaces. About’s ship gate names why Chat and Health do not carry AdSense. Application shells that still exist for old links send noindex rather than pretending to be inventory.

Google-Display-Ads-Bot Allow belongs to the second system. Stretching it across the first is the error this essay exists to refuse. Stretching it across the third is the same error with a different hostname.

## What the Allow is allowed to mean

It is allowed to mean that Google’s display-ads crawler may fetch public URLs on www under the robots contract. It is allowed to mean that publisher inventory can be evaluated as publisher inventory. It is allowed to sit next to the mechanical check in What we publish that ads crawlers should be Allowed. It is allowed to coexist with non-personalized default requests and with the cookie notice that is a notice, not a consent management platform.

It is not allowed to mean that Search builds advertising profiles from queries. It is not allowed to mean that account data is sold. It is not allowed to mean that Chat or Health load AdSense. It is not allowed to mean that dismissing the cookie bar is consent. It is not allowed to mean that every Google string on the network is one relationship. Privacy, Cookies, How Search works, About, and the homepage already refuse those meanings. A robots line does not get to invent them.

## Checks that keep the leap from returning

Open the live robots.txt and confirm the ads-bot names yourself. Do not trust a screenshot from an older essay. Open Privacy sections 1, 3, and 4 and read the host fence, the no-sale and no-search-history-profile lines, and the AdSense scope. Open Cookies for the exclusion list and the sentence that Search queries are not ad-unit input. Open How Search works for ranking without a search-history advertising profile and for the funding FAQ that separates optional premium and publisher ads from query sale. Open About for the funding split and the product hosts that do not carry ads. Open Corrections if you still want the zero-tracking failure in public language.

If those sources disagree with a journal claim, the article loses until it is fixed. That rule is in Corrections and in What we publish. This essay is written to survive that rule. Google-Display-Ads-Bot Allow is publisher-only. It is not Search profiling. The live file, Privacy, and How Search works already say so. The job is to keep reading them as separate documents instead of one Google-shaped rumor.