Search queries and Google ads on Oernoe ends with a section titled “How to check us.” It is not a branding exercise. It is a short checklist for anyone who landed from an ads review, a privacy question, or a Search result and does not want to trust a slogan. This Company essay walks that checklist in the order a careful stranger would: view-source on eligible pages versus Home and About, open ads.txt, open Privacy section 4, open the journal listing, ignore old promotional URLs that still resolve, notice the verification meta even when the homepage has no units, and read robots.txt for the ads crawlers the publisher allows.
## Start with view-source, not with a press sentence
Open view-source on a How-To or guide URL and look for the AdSense client `ca-pub-9477175344230263`. Open Home or About and confirm the AdSense client script is missing. That is the first check the guide names, and it is the one that survives marketing language. Live checks on 8 September 2026 show the client script on How-To and on How Oernoe Search works. About and the homepage do not load `adsbygoogle.js`. They do carry a `google-adsense-account` meta tag with the same publisher id so Google can verify the site even when those pages have no ad units. Meta for verification is allowed. A unit script on About is not.
That distinction is easy to miss if you only search the page source for the publisher number. The number can appear in a meta tag on pages that correctly refuse units. The check the guide wants is whether the AdSense client loads. Eligible finished pages may load it. Home, About, legal pages, login, signup, the journal index, error pages, and the apps are supposed to refuse it. If after a deploy the client appears on About, the guide is wrong that day and should be corrected the same day — the guide’s own closing standard.
View-source also beats a screenshot of a rendered page when Auto ads misbehave. A leftover unit after you navigate from an eligible article to Home can be a client-side guard failure. The source of Home should still lack the client. If the source is clean and the rendered page is not, you have a transient injection problem to report. If the source includes the client on a forbidden page, you have a configuration problem. Both belong at support@oernoe.com with URL, time, browser, and screenshot. Neither is fixed by arguing about privacy in the abstract.
Name the files you opened. Comparative checks beat a single page in isolation.
## Open /ads.txt and Privacy section 4
The second mechanical check is `/ads.txt` at the site root. On 8 September 2026 it reads as a single authorization line for Google with publisher id `pub-9477175344230263`, marked DIRECT, with Google’s certification identifier. That file tells buyers who is authorized to sell inventory on the domain. It is not itself an ad unit. It does not prove a particular article is monetized. It does prove the publisher is not pretending there is no advertising relationship on www.
Privacy Policy section 4 is titled “Google AdSense on www.oernoe.com.” It lists the kinds of substantial publisher pages that may use AdSense and the surfaces that do not: homepage, About, login or signup screens, protected application pages, legal pages, error pages, the journal index, short or promotional journal posts, the guides index, editorial standards, and Oernoe service subdomains. It includes the Google-required language about advertising cookies, Ads Settings, aboutads.info, non-personalized requests by default, and the fact that Google may still process page context and related signals. It also repeats that the cookie bar is a notice, not a consent management platform.
A reviewer who only opens the homepage hero will miss section 4. A reviewer who only opens ads.txt will miss which pages are in scope. How to check us insists on both, plus view-source, because the three together describe authorization, legal scope, and actual script presence. If those three disagree after a deploy, the public record is broken. Fix the page or the implementation; do not leave the contradiction for a stranger. Section 4 also keeps Search out of the wrong sentence: ads on www are a publisher fact, not proof that Search sells queries. Verify the publisher side with tools you already have in the browser.
## The journal listing should be finished writing
Open `/blog` and confirm it is a list of finished articles, not a wall of “coming soon.” What we publish explains why that check exists. The site took an AdSense rejection for low value content. The recovery rule is a smaller, stricter public index: original writing about search, privacy, and products that actually run; help pages; legal and company record. Generic outlines and launch stubs are rewritten or kept out of the index. Indexable journal articles need enough original text to be a document, and they still fail if the title is hype or the body is an unfinished launch note.
Ads, when they appear on journal URLs, are supposed to sit on those finished documents. The journal listing itself stays off units. That split keeps the index from becoming a gallery of empty shells whose only job is to hold inventory. If `/blog` ever returns to a wall of stubs, view-source on a random card will not save the review. The listing itself is the quality signal the checklist names.
About says public-index writing has to be original to Oernoe. The `/blog` step is that sentence made operational: look at the list instead of trusting a memo.
## Old promotional URLs can resolve and still be the wrong site
How to check us is explicit about reviewers who chase leftovers. Do not treat an old promotional URL as the site. Those URLs can still resolve for old links. They are noindexed, they are not offered as the current public set of documents, and they do not load ads. The homepage makes the same point in different clothes: a reviewer who only opens the hero and a leftover console-style path is seeing the old site. The current one is the documents that survive What we publish.
That is why “it still loads” is not the same as “it represents Oernoe to a reviewer.” Resolution without index inclusion is a migration scar. The checklist tells you to ignore that scar on purpose. Start with Search queries and Google ads, How Search works, What we publish, Using an account, How-To, and the journal pieces that are actually listed. Those are the pages the company is willing to defend as the public record on a given day.
Noindex without deletion can look odd if you expect every old path to vanish. The published rule prefers honesty about leftovers: they may answer, but they are not the review corpus and not where ads should live.
## Verification meta and ads crawlers are publisher facts
Pages carry a `google-adsense-account` meta tag even when the homepage has no ad units. That is verification plumbing for Google, not a hidden unit. Confusing the meta with a loaded client is how a careless check false-positives Home and About. The live homepage and About pages show the meta and omit the client. Eligible guides show both. Keep those two facts in separate buckets when you write a review note.
robots.txt on www allows Mediapartners-Google and Google-Display-Ads-Bot with `Allow: /`, then allows other user agents with ordinary Disallow rules for `/api/` and `/debug/`. The ads guide states the reason: so an ads crawler can see the same writing a person sees. Allowing those bots is a publisher-hostname fact. It is not a claim that Search profiles queries for ads. It is not a claim that product subdomains are in the ads program. Scope stays on www’s public documents.
Ads-bot allows let a reviewer bot fetch the same HTML a person fetches. That does not require units on About, and it is not Search query profiling.
## What the checklist refuses to become
The checklist is not a request to click ads. It is not a request to pay for clicks. It is not a claim that non-personalized ads are “not tracking.” It is not a claim that the whole network is free of third parties. Search queries and Google ads lists those refusals in “What we will not claim.” How to check us is the positive form: here is how you can see the current truth without asking the company for a private tour.
It is also not a substitute for reading the article. View-source without reading Privacy section 4 will miss the Europe-facing notice language. Reading Privacy without opening ads.txt will miss the buyer authorization line. Opening ads.txt without opening `/blog` will miss whether the journal still looks like a publisher. The strength of the checklist is that each step catches a different failure mode.
A lone ads.txt screenshot without view-source comparison is theater. Used as a sequence, the checklist stays boring in the useful way.
## Company discipline, not theater
Oernoe is operated by Anoepal and founded by Angel Mejia Rodriguez. www.oernoe.com is the publisher site. Search lives on its own hostname and is not supposed to feed an advertising file of queries into the units on www. The company already had to walk back overclaiming on the homepage. Corrections and What we publish exist because the public index and the public claims had to get smaller and stricter. How to check us is part of that stricter culture: give strangers a way to verify without a sales call.
If the checks fail, the guide says the guide is wrong and should be corrected the same day. That sentence is the Company point. A checklist that is allowed to rot is worse than no checklist, because it teaches reviewers that the disclosures are decorative. Keeping view-source, ads.txt, Privacy section 4, `/blog`, the noindex stance on old promotional paths, the verification meta, and the ads-bot allows in agreement is operational work. It is how a small publisher stays reviewable.
Run the checks when the question is “where are the ads, really?” Do not run them as a substitute for product privacy on Search, Health, Chat, or the other apps — those surfaces are supposed to stay off AdSense by rule. Do not treat a verification meta as a unit. Do not treat a resolving old URL as the current site. Do not treat an ads crawler allow as query profiling. The guide’s checklist is narrow on purpose. Used narrowly, it is enough to see whether today’s www matches what the company published about advertising.
Date your check. Privacy and Cookies both showed 31 August 2026 on the fetches for this draft. A note that lists view-source, ads.txt, Privacy §4, /blog, and robots ads-bot allows on 8 September 2026 beats “seems fine.” How to check us is written for that stronger note; this essay is where the Company shelf points when someone asks how to produce it.
## Start with view-source, not with a press sentence
Open view-source on a How-To or guide URL and look for the AdSense client `ca-pub-9477175344230263`. Open Home or About and confirm the AdSense client script is missing. That is the first check the guide names, and it is the one that survives marketing language. Live checks on 8 September 2026 show the client script on How-To and on How Oernoe Search works. About and the homepage do not load `adsbygoogle.js`. They do carry a `google-adsense-account` meta tag with the same publisher id so Google can verify the site even when those pages have no ad units. Meta for verification is allowed. A unit script on About is not.
That distinction is easy to miss if you only search the page source for the publisher number. The number can appear in a meta tag on pages that correctly refuse units. The check the guide wants is whether the AdSense client loads. Eligible finished pages may load it. Home, About, legal pages, login, signup, the journal index, error pages, and the apps are supposed to refuse it. If after a deploy the client appears on About, the guide is wrong that day and should be corrected the same day — the guide’s own closing standard.
View-source also beats a screenshot of a rendered page when Auto ads misbehave. A leftover unit after you navigate from an eligible article to Home can be a client-side guard failure. The source of Home should still lack the client. If the source is clean and the rendered page is not, you have a transient injection problem to report. If the source includes the client on a forbidden page, you have a configuration problem. Both belong at support@oernoe.com with URL, time, browser, and screenshot. Neither is fixed by arguing about privacy in the abstract.
Name the files you opened. Comparative checks beat a single page in isolation.
## Open /ads.txt and Privacy section 4
The second mechanical check is `/ads.txt` at the site root. On 8 September 2026 it reads as a single authorization line for Google with publisher id `pub-9477175344230263`, marked DIRECT, with Google’s certification identifier. That file tells buyers who is authorized to sell inventory on the domain. It is not itself an ad unit. It does not prove a particular article is monetized. It does prove the publisher is not pretending there is no advertising relationship on www.
Privacy Policy section 4 is titled “Google AdSense on www.oernoe.com.” It lists the kinds of substantial publisher pages that may use AdSense and the surfaces that do not: homepage, About, login or signup screens, protected application pages, legal pages, error pages, the journal index, short or promotional journal posts, the guides index, editorial standards, and Oernoe service subdomains. It includes the Google-required language about advertising cookies, Ads Settings, aboutads.info, non-personalized requests by default, and the fact that Google may still process page context and related signals. It also repeats that the cookie bar is a notice, not a consent management platform.
A reviewer who only opens the homepage hero will miss section 4. A reviewer who only opens ads.txt will miss which pages are in scope. How to check us insists on both, plus view-source, because the three together describe authorization, legal scope, and actual script presence. If those three disagree after a deploy, the public record is broken. Fix the page or the implementation; do not leave the contradiction for a stranger. Section 4 also keeps Search out of the wrong sentence: ads on www are a publisher fact, not proof that Search sells queries. Verify the publisher side with tools you already have in the browser.
## The journal listing should be finished writing
Open `/blog` and confirm it is a list of finished articles, not a wall of “coming soon.” What we publish explains why that check exists. The site took an AdSense rejection for low value content. The recovery rule is a smaller, stricter public index: original writing about search, privacy, and products that actually run; help pages; legal and company record. Generic outlines and launch stubs are rewritten or kept out of the index. Indexable journal articles need enough original text to be a document, and they still fail if the title is hype or the body is an unfinished launch note.
Ads, when they appear on journal URLs, are supposed to sit on those finished documents. The journal listing itself stays off units. That split keeps the index from becoming a gallery of empty shells whose only job is to hold inventory. If `/blog` ever returns to a wall of stubs, view-source on a random card will not save the review. The listing itself is the quality signal the checklist names.
About says public-index writing has to be original to Oernoe. The `/blog` step is that sentence made operational: look at the list instead of trusting a memo.
## Old promotional URLs can resolve and still be the wrong site
How to check us is explicit about reviewers who chase leftovers. Do not treat an old promotional URL as the site. Those URLs can still resolve for old links. They are noindexed, they are not offered as the current public set of documents, and they do not load ads. The homepage makes the same point in different clothes: a reviewer who only opens the hero and a leftover console-style path is seeing the old site. The current one is the documents that survive What we publish.
That is why “it still loads” is not the same as “it represents Oernoe to a reviewer.” Resolution without index inclusion is a migration scar. The checklist tells you to ignore that scar on purpose. Start with Search queries and Google ads, How Search works, What we publish, Using an account, How-To, and the journal pieces that are actually listed. Those are the pages the company is willing to defend as the public record on a given day.
Noindex without deletion can look odd if you expect every old path to vanish. The published rule prefers honesty about leftovers: they may answer, but they are not the review corpus and not where ads should live.
## Verification meta and ads crawlers are publisher facts
Pages carry a `google-adsense-account` meta tag even when the homepage has no ad units. That is verification plumbing for Google, not a hidden unit. Confusing the meta with a loaded client is how a careless check false-positives Home and About. The live homepage and About pages show the meta and omit the client. Eligible guides show both. Keep those two facts in separate buckets when you write a review note.
robots.txt on www allows Mediapartners-Google and Google-Display-Ads-Bot with `Allow: /`, then allows other user agents with ordinary Disallow rules for `/api/` and `/debug/`. The ads guide states the reason: so an ads crawler can see the same writing a person sees. Allowing those bots is a publisher-hostname fact. It is not a claim that Search profiles queries for ads. It is not a claim that product subdomains are in the ads program. Scope stays on www’s public documents.
Ads-bot allows let a reviewer bot fetch the same HTML a person fetches. That does not require units on About, and it is not Search query profiling.
## What the checklist refuses to become
The checklist is not a request to click ads. It is not a request to pay for clicks. It is not a claim that non-personalized ads are “not tracking.” It is not a claim that the whole network is free of third parties. Search queries and Google ads lists those refusals in “What we will not claim.” How to check us is the positive form: here is how you can see the current truth without asking the company for a private tour.
It is also not a substitute for reading the article. View-source without reading Privacy section 4 will miss the Europe-facing notice language. Reading Privacy without opening ads.txt will miss the buyer authorization line. Opening ads.txt without opening `/blog` will miss whether the journal still looks like a publisher. The strength of the checklist is that each step catches a different failure mode.
A lone ads.txt screenshot without view-source comparison is theater. Used as a sequence, the checklist stays boring in the useful way.
## Company discipline, not theater
Oernoe is operated by Anoepal and founded by Angel Mejia Rodriguez. www.oernoe.com is the publisher site. Search lives on its own hostname and is not supposed to feed an advertising file of queries into the units on www. The company already had to walk back overclaiming on the homepage. Corrections and What we publish exist because the public index and the public claims had to get smaller and stricter. How to check us is part of that stricter culture: give strangers a way to verify without a sales call.
If the checks fail, the guide says the guide is wrong and should be corrected the same day. That sentence is the Company point. A checklist that is allowed to rot is worse than no checklist, because it teaches reviewers that the disclosures are decorative. Keeping view-source, ads.txt, Privacy section 4, `/blog`, the noindex stance on old promotional paths, the verification meta, and the ads-bot allows in agreement is operational work. It is how a small publisher stays reviewable.
Run the checks when the question is “where are the ads, really?” Do not run them as a substitute for product privacy on Search, Health, Chat, or the other apps — those surfaces are supposed to stay off AdSense by rule. Do not treat a verification meta as a unit. Do not treat a resolving old URL as the current site. Do not treat an ads crawler allow as query profiling. The guide’s checklist is narrow on purpose. Used narrowly, it is enough to see whether today’s www matches what the company published about advertising.
Date your check. Privacy and Cookies both showed 31 August 2026 on the fetches for this draft. A note that lists view-source, ads.txt, Privacy §4, /blog, and robots ads-bot allows on 8 September 2026 beats “seems fine.” How to check us is written for that stronger note; this essay is where the Company shelf points when someone asks how to produce it.
O
Oernoe Editorial Team
Writes for the Oernoe Journal. Questions about this article can go to the contact page.
Get in touchRelated Articles
Want to Learn More?
Explore our complete guides and knowledge base for more insights on privacy, technology, and best practices.
Browse Our Guides