Ads script exclusion is code, not a caption

Publisher promises fail in two boring ways. One is a caption that says ads never appear on a page while the page still loads the ads script. The other is a caption that says ads may appear everywhere while the product shells stay clean. Oernoe’s hostnames guide and Cookie Policy pick a harder middle: ads only on selected finished www pages, and a list of surfaces that do not load the ads script at all. Home, About, the journal listing, the guides listing, editorial standards, and legal pages are in that exclusion set. The exclusion is enforced in code, not as a caption. AdSense stays off product subdomains and app shells. Eligible pages are named in Cookies so a reviewer does not have to reverse-engineer intent from a slogan.

That sentence is the claim. The rest of this essay is how to check it, why captions alone fail, and what “selected finished pages” means when the publisher network is watching.

## What the hostnames guide actually draws

www.oernoe.com is the publisher: journal, guides, How-To, About, Team, Contact, and the legal set. It is also where Google AdSense can appear, and only on pages that already work as documents. The guide is explicit that Home, About, the journal listing, the guides listing, editorial standards, and legal pages do not load the ads script. It then adds the enforcement line that matters for trust: that split is enforced in code, not as a caption.

Search, Chat, Health, AI, Docs, Drive, Tracker, and Account are different hosts. Ads are not allowed inside those products. If an ad unit appears there, the hostnames page calls it a bug and points to support. That is a different rule from the www exclusions, but it travels with the same idea: the presence or absence of the script is a product decision, not a footnote on a marketing page.

www is not Search. There is no query box on the publisher host that writes into the search index. Mixing those jobs produces landing pages that say nothing useful and invite reviewers to call the site low value. Keeping AdSense off the shells that are not documents is part of keeping the publisher host honest about what it is.

## What Cookies lists as excluded and eligible

The Cookie Policy’s section on where advertising is not used names the AdSense script exclusion in operational language. The script is excluded from the homepage, About, Team, Contact, short journal posts, the journal index, the guides index, editorial standards, login and signup screens, account and application pages, legal pages, error pages, and Oernoe service subdomains such as Search, Chat, Drive, Docs, Health, Tracker, and Account. Application shells on www that send a noindex header also do not load ads.

Eligible publisher pages sit in a separate subsection. Ads may load on How-To; finished guides including How Search works, Search queries and Google ads, Using an account, What we publish, Which hostname does what, Corrections, and How a privacy request is handled; and journal articles that still pass originality and length checks. ads.txt at the site root names the publisher id. Pages carry a google-adsense-account meta tag so Google can verify the publisher even when a given URL has no unit.

That eligible list is not a promise that every listed URL always shows a unit. It is permission for the script and inventory rules to apply on pages that already work as documents. Thin stubs, promotional leftovers, and short posts stay out. What we publish repeats the same publisher logic: if a page cannot survive as a document without an ad, it should not have an ad.

## Why “enforced in code” is the whole point

A caption is easy to ship and easy to forget. Someone updates a template, a new route inherits the wrong layout, and the caption still says “no ads here” while the browser fetches adsbygoogle. Reviewers who view-source are not fooled by captions. The hostnames guide invites that check: view-source on the guide should include the AdSense client when the page is eligible; view-source on About should not.

Code enforcement means the layout or page flags that decide whether the script tag is emitted are the same flags that define the page type. Legal pages inherit a legal layout that never requests AdSense. Home and About inherit company layouts that never request it. Journal listing and guides listing are indexes, not articles, and they stay out. Editorial standards is a policy document that should not be ad inventory. Those decisions live next to the routes, not in a paragraph that can drift.

When the code and the caption disagree, the page is wrong. The hostnames guide says that out loud. Corrections already lists older copy that talked as if the whole network had no ads while the publisher hostname was applying for AdSense. Both sentences have to be true at once: Search still does not use queries as an advertising file, and selected finished www pages may show Google ads. Captions that erase one of those sentences to flatter the other are how the site got into trouble before.

## Product subdomains are not publisher inventory

AdSense on www does not license AdSense inside Chat or Drive. Privacy says the 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. Cookies repeats the subdomain exclusion. The hostnames page repeats it again for people who only read the map.

This split is easy to mash in conversation. People say “Oernoe has ads” and mean the whole network. People say “Oernoe has no ads” and mean Search. The accurate pair is narrower. Selected finished documents on the publisher host may load the script. Product hosts and account screens do not. If you saw an ad unit inside those products, that is a bug, not a privacy setting you forgot to toggle.

Queries typed at search.oernoe.com are not an input file for AdSense on www. That rule sits in Cookies under advertising and in the hostnames guide under Search. It keeps the publisher arrangement from being misread as Search selling queries. The exclusion of the ads script from Search is part of that wall. Code keeps the script off the search host. Policy keeps the query file from becoming an advertising profile. Different mechanisms, same refusal to mash the products together.

## How to verify without trusting the essay

Look at the hostname first. If you are reading an article, you should be on www.oernoe.com. If you are typing a query, you should be on search.oernoe.com. If you are signing in, you should be on account.oernoe.com. Then look at the page type. Home, About, indexes, legal, editorial standards: expect no ads script. Finished guides and substantial journal articles: the script may be present. View-source is the check the guides themselves recommend. /ads.txt should name the publisher id used on this site. The public document index should list finished documents, not login shells.

None of that requires believing a journal essay. The essay exists so the rule is stated in editorial prose the same way the guides state it in policy prose. If the live page disagrees with the rule, the page is wrong and should be corrected, not defended with a caption.


## Indexes are not articles, and shells are not documents

The journal listing and the guides listing look like content because they contain titles and links. They are still indexes. An index’s job is navigation. Monetizing navigation the same way you monetize a finished argument is how a publisher starts to look like a doorway site. Cookies keeps those indexes out of the ads script path for that reason. Editorial standards is policy text, not inventory. Legal pages are the record a reader needs when something goes wrong. Loading the ads script there would train the wrong habit: treat every route as a surface for a unit.

Application shells on www are the other side of the same coin. They are routes that exist so old links do not 404, or so an app can boot. They send noindex. They are not documents in the public-index sense. They do not load ads. Confusing a shell with a finished guide is how empty pages end up in front of a reviewer who then assumes the whole host is padding. What we publish already called that failure mode by name. Code exclusion is how the ads path refuses to join it.

## What this essay refuses to clone

This is not the short note that Home and About do not carry ads, though it includes that fact inside a larger code-versus-caption frame. It is not the legal-pages-never-carry-AdSense piece alone. It is not the network-scope essay that AdSense is www-not-the-network, though subdomain exclusion appears here as evidence. It is not the Chat-and-Health-stay-off-AdSense-by-rule essay as a product-privacy story. It is not www-is-publisher-not-an-app-shell as a hostname identity piece. It is not the Google display-ads bot-allow publisher-only technical note. Those URLs have their own jobs.

It also stays away from neighboring company essays about short company pages naming the operator, recovery rules that are not press releases, how the company makes money without selling queries, cookie-bar OK not being consent, dismiss flags not being ad ids, and what the cookies banner is for. Consent and notice are Cookies section 4. This essay’s job is narrower: the script either loads or it does not, and that decision is enforced in code on the surfaces the guides name.

## Practical consequence for writers and reviewers

Writers on this hostname should not paste “ads may appear” into a legal page footer and call it honesty. Legal pages do not load the script. Writers should not paste “this site never shows ads” into a finished guide that is on the eligible list. Both mistakes are caption theater. The correct move is to match the page type to the code path, then describe that match in language a reviewer can check with view-source.

Reviewers should treat a missing script on About as expected, not as proof the whole publisher never monetizes documents. They should treat a present script on a finished guide as expected, not as proof Search sells queries. The hostnames map and the Cookies eligible list exist so those two observations can sit in the same head without collapsing into a slogan.

Anoepal operates Oernoe. Angel remains the named person for this publisher. Product claims get checked against live hostnames. Policy claims get checked against Privacy, Cookies, and Terms. If those sources disagree with a journal sentence, the article loses until it is fixed. This article’s sentence is the one already on the hostnames page: Home, About, journal listing, guides listing, editorial standards, and legal pages do not load the ads script, enforced in code, not as a caption; AdSense stays off product subdomains and app shells; eligible pages are the ones Cookies lists. Believe the code path. Update the caption if it drifts. Do not ship the caption alone and hope.