Login does not live on the publisher hostname. The hostnames guide states the live addresses without decoration: login is account.oernoe.com/auth/login, and signup is account.oernoe.com/auth/sign-up. Older www paths such as /login and /signup still resolve so old links do not 404. They are application shells. They send X-Robots-Tag: noindex. They are not in the public listing of finished writing. They do not carry ads. If you arrived there from a bookmark, use the account hostnames instead. That paragraph is the whole product map. This essay exists because people still treat a www path that paints a login form as if it were Account.
www.oernoe.com is the publisher: journal, guides, How-To, About, Team, Contact, and the legal set. account.oernoe.com is where authentication and security settings live. Mash those into one sentence about the Oernoe app and you get the wrong bookmark, the wrong expectation about ads, and the wrong assumption about what a crawler should index. The logo is shared. The host is not.
## What still resolves on www, and why
Old links are sticky. Browser bookmarks, chat pastes, and third-party pages keep pointing at www paths long after the product host moved. Returning 404 on /login and /signup would punish readers for our migration. Keeping a shell that resolves is kinder. Kindness is not the same as inventing a second Account product on the publisher host.
A shell in this sense is a thin application surface that may look like a form and may even hand you toward the real login flow, but it is not the durable Account hostname. It is not where password reset and security settings are supposed to live as the canonical story. Using an Oernoe account points creation at account.oernoe.com/auth/sign-up, or at an account screen opened from a service hostname. Forgot password lives on the account login host. The www leftovers exist so history does not break. They do not redefine where Account is.
Because they are shells, they carry the same indexing discipline as other application chrome on the publisher host. X-Robots-Tag: noindex. Out of the finished-document listing. No ads script beside a password field. That last point is both a product choice and a publisher-policy choice. Putting ads next to credentials would be a defect. If it ever happens, screenshot it and send it to support@oernoe.com.
Resolving without ranking is a deliberate compromise. We accept that a person with an old link still reaches a page. We refuse to treat that page as a document we want Search to promote. We refuse to monetize it. We refuse to let it teach the wrong host as the long-term home of Account. Those refusals only work if the public copy keeps saying them.
## Account is a product host, not a brochure path
One account opens Search, Health, Chat, AI, Docs, Drive, and Tracker. Account screens do not load ads. That split is on the hostnames page because reviewers and readers both collapse Oernoe into a single surface. Search is search.oernoe.com. The publisher is www.oernoe.com. Login is account.oernoe.com. If you are signing in, look at the hostname in the address bar, not the logo.
Using an account also clarifies what the login is for. You do not need an account to read this website. You need one to use the products. Creation is free. There is no credit card on the signup form. Basic access does not wait on a verification ritual. A verification message, when it arrives, is for recovering the inbox later, not a gate that pretends the products are locked until a ceremony completes. How-To used to point people at the wrong signup story on www. Corrections already named that mistake. The durable addresses are the account host paths above.
None of that turns /login on www into Account. A resolving shell can still confuse a hurried reader. The editorial job is to keep saying the host out loud until bookmarks move. Journal essays that talk as if www were the login product are out of date the moment they ship.
Password length guidance and age rules still sit on Using an account and How-To. Twelve characters with mixed case and numbers is the floor we tell people. Longer is better. You must be at least 13. If you are under 18, use the services with a parent or guardian. The site is not directed at children under 13. Terms and Privacy say that because ordinary law and the ads program both care. None of those sentences relocate Account onto www.
## Shells, noindex, and what not Account means for Search
Noindex on a shell is not a claim that the URL is secret. It is a claim that the URL is not a publisher document we want ranked next to guides and journal essays. Crawlers may still fetch it. They should honour the header. That pairing matters for the same reason the robots correction matters elsewhere: if you Disallow a shell so hard that the crawler never sees noindex, you can end up with accidental indexing. For www login paths, the published rule is already header-based refusal of ranking, plus absence from the finished listing, plus no ads.
Not Account also means the shell is not the place we describe as the home of security settings, session review, or two-factor controls. Those live on the account host when the settings exist. Using an account tells people who still have access to look at active sessions and sign out anything they do not recognize. It tells people who forgot the password to use Forgot Password on account.oernoe.com/auth/login. It does not tell them to trust a www leftover as the long-term control panel.
If a future sign-in method is added, Using an account and How-To have to name it. Until then, address and password is the path. Shortcuts that invent sign-in with the publisher homepage are not the live product. Hostnames beat slogans.
Thin shells also fail the What we publish test. That guide says www is for original writing, help pages, and the legal and company record. A leftover /signup path is none of those jobs. Keeping it alive for old links is maintenance. Promoting it as Account would be a product lie.
## Ads stay off login even when the publisher shows them elsewhere
Selected finished pages on www may load Google AdSense. That is a publisher arrangement on public writing. Login, signup, password reset, and the product apps do not load that script. The hostnames guide and the privacy-requests guide both repeat the split because people keep hearing that Oernoe applied for ads as if ads appear beside every Oernoe screen. Those are different claims. A guide on www may show ads because it is public documentation. Signing in is not a commercial page.
www /login and /signup inherit the no-ads rule because they are application shells, not finished articles. They also inherit noindex. That combination is deliberate. We are not monetizing thin chrome. We are not ranking thin chrome. We are keeping old links from breaking while the canonical Account host does the real work.
What we publish draws the same line from the other direction: do not monetize login, legal pages, thin stubs, or the journal listing. Product claims get checked against live hostnames. If a journal draft talks as if /signup on www were the product, the draft loses until it matches the hostnames page.
The cookie notice on the publisher host does not rewrite Account either. Dismissing the bar with OK only hides the bar. It is not consent. Ads on eligible pages are requested as non-personalized. None of that belongs next to a password field on a shell, and none of it moves login off account.oernoe.com.
## Bookmarks, support notes, and how to stop teaching the wrong host
If you landed on a www login path from a bookmark, change the bookmark to account.oernoe.com/auth/login. If you are creating an account, use account.oernoe.com/auth/sign-up. If signup fails, write support@oernoe.com with the browser, the time, and which host you were on. Do not send the password. If you think someone else has the password, change it on the account host first, then write support with the time you noticed the problem.
A support note that says I signed in on www is still actionable, because the shells may still hand people into a flow. It is also a signal that our public writing has not finished moving the mental model. This essay is part of that move. It is not a promise that every old link on the open web will rewrite itself. It is a promise that our own guides and journal copy will keep naming the account host as Account.
People also confuse Account with the publisher Contact page. Contact is how you reach the company about the site. Account is how you authenticate into products. Mixing those jobs produces tickets that ask support to reset a password from a www URL that was never the control plane. The hostnames guide exists so that mix stops sounding reasonable.
## What this essay refuses to blur
This is not an essay about robots.txt Disallow lines that used to hide noindex on other shells. That batch neighbor stays on the robots mismatch for /auth, /console, and /dashboard style routes and on the fetch-then-header repair. This piece stays on www /login and /signup as leftover shells, and on account.oernoe.com as the live Account host.
It is also not the essay that says the account host holds login rather than journal ads, not the forgot-password-only-on-account note, not the signup-is-not-a-verification-gate piece, not the using-an-account-guide-is-not-signup-chrome piece, and not the broader shells-should-not-rank argument. Those documents have their own jobs. Overlap in facts is allowed. Overlap in thesis is not.
Finally, this is not a claim that every resolving www path is harmless. Shells that still resolve must keep noindex, stay out of the finished listing, and stay free of ads. If any of those checks fail, the page is wrong. Write support@oernoe.com for product defects and hello@oernoe.com for public copy that still teaches the wrong host.
Look at the address bar. If you are reading an article, you should be on www.oernoe.com. If you are signing in, you should be on account.oernoe.com. A www path that still paints a login form is a shell keeping old links alive. It is not Account. Bookmarks should follow the host that actually owns the login.
The durable test is simple enough to run without a committee. Open account.oernoe.com/auth/login and account.oernoe.com/auth/sign-up. Those are Account. Open www /login and /signup only if you must follow an old link, then move your bookmark. Treat any public sentence that collapses those hosts as unfinished copy. That is how shells stay shells, and how Account stays on the account host.
www.oernoe.com is the publisher: journal, guides, How-To, About, Team, Contact, and the legal set. account.oernoe.com is where authentication and security settings live. Mash those into one sentence about the Oernoe app and you get the wrong bookmark, the wrong expectation about ads, and the wrong assumption about what a crawler should index. The logo is shared. The host is not.
## What still resolves on www, and why
Old links are sticky. Browser bookmarks, chat pastes, and third-party pages keep pointing at www paths long after the product host moved. Returning 404 on /login and /signup would punish readers for our migration. Keeping a shell that resolves is kinder. Kindness is not the same as inventing a second Account product on the publisher host.
A shell in this sense is a thin application surface that may look like a form and may even hand you toward the real login flow, but it is not the durable Account hostname. It is not where password reset and security settings are supposed to live as the canonical story. Using an Oernoe account points creation at account.oernoe.com/auth/sign-up, or at an account screen opened from a service hostname. Forgot password lives on the account login host. The www leftovers exist so history does not break. They do not redefine where Account is.
Because they are shells, they carry the same indexing discipline as other application chrome on the publisher host. X-Robots-Tag: noindex. Out of the finished-document listing. No ads script beside a password field. That last point is both a product choice and a publisher-policy choice. Putting ads next to credentials would be a defect. If it ever happens, screenshot it and send it to support@oernoe.com.
Resolving without ranking is a deliberate compromise. We accept that a person with an old link still reaches a page. We refuse to treat that page as a document we want Search to promote. We refuse to monetize it. We refuse to let it teach the wrong host as the long-term home of Account. Those refusals only work if the public copy keeps saying them.
## Account is a product host, not a brochure path
One account opens Search, Health, Chat, AI, Docs, Drive, and Tracker. Account screens do not load ads. That split is on the hostnames page because reviewers and readers both collapse Oernoe into a single surface. Search is search.oernoe.com. The publisher is www.oernoe.com. Login is account.oernoe.com. If you are signing in, look at the hostname in the address bar, not the logo.
Using an account also clarifies what the login is for. You do not need an account to read this website. You need one to use the products. Creation is free. There is no credit card on the signup form. Basic access does not wait on a verification ritual. A verification message, when it arrives, is for recovering the inbox later, not a gate that pretends the products are locked until a ceremony completes. How-To used to point people at the wrong signup story on www. Corrections already named that mistake. The durable addresses are the account host paths above.
None of that turns /login on www into Account. A resolving shell can still confuse a hurried reader. The editorial job is to keep saying the host out loud until bookmarks move. Journal essays that talk as if www were the login product are out of date the moment they ship.
Password length guidance and age rules still sit on Using an account and How-To. Twelve characters with mixed case and numbers is the floor we tell people. Longer is better. You must be at least 13. If you are under 18, use the services with a parent or guardian. The site is not directed at children under 13. Terms and Privacy say that because ordinary law and the ads program both care. None of those sentences relocate Account onto www.
## Shells, noindex, and what not Account means for Search
Noindex on a shell is not a claim that the URL is secret. It is a claim that the URL is not a publisher document we want ranked next to guides and journal essays. Crawlers may still fetch it. They should honour the header. That pairing matters for the same reason the robots correction matters elsewhere: if you Disallow a shell so hard that the crawler never sees noindex, you can end up with accidental indexing. For www login paths, the published rule is already header-based refusal of ranking, plus absence from the finished listing, plus no ads.
Not Account also means the shell is not the place we describe as the home of security settings, session review, or two-factor controls. Those live on the account host when the settings exist. Using an account tells people who still have access to look at active sessions and sign out anything they do not recognize. It tells people who forgot the password to use Forgot Password on account.oernoe.com/auth/login. It does not tell them to trust a www leftover as the long-term control panel.
If a future sign-in method is added, Using an account and How-To have to name it. Until then, address and password is the path. Shortcuts that invent sign-in with the publisher homepage are not the live product. Hostnames beat slogans.
Thin shells also fail the What we publish test. That guide says www is for original writing, help pages, and the legal and company record. A leftover /signup path is none of those jobs. Keeping it alive for old links is maintenance. Promoting it as Account would be a product lie.
## Ads stay off login even when the publisher shows them elsewhere
Selected finished pages on www may load Google AdSense. That is a publisher arrangement on public writing. Login, signup, password reset, and the product apps do not load that script. The hostnames guide and the privacy-requests guide both repeat the split because people keep hearing that Oernoe applied for ads as if ads appear beside every Oernoe screen. Those are different claims. A guide on www may show ads because it is public documentation. Signing in is not a commercial page.
www /login and /signup inherit the no-ads rule because they are application shells, not finished articles. They also inherit noindex. That combination is deliberate. We are not monetizing thin chrome. We are not ranking thin chrome. We are keeping old links from breaking while the canonical Account host does the real work.
What we publish draws the same line from the other direction: do not monetize login, legal pages, thin stubs, or the journal listing. Product claims get checked against live hostnames. If a journal draft talks as if /signup on www were the product, the draft loses until it matches the hostnames page.
The cookie notice on the publisher host does not rewrite Account either. Dismissing the bar with OK only hides the bar. It is not consent. Ads on eligible pages are requested as non-personalized. None of that belongs next to a password field on a shell, and none of it moves login off account.oernoe.com.
## Bookmarks, support notes, and how to stop teaching the wrong host
If you landed on a www login path from a bookmark, change the bookmark to account.oernoe.com/auth/login. If you are creating an account, use account.oernoe.com/auth/sign-up. If signup fails, write support@oernoe.com with the browser, the time, and which host you were on. Do not send the password. If you think someone else has the password, change it on the account host first, then write support with the time you noticed the problem.
A support note that says I signed in on www is still actionable, because the shells may still hand people into a flow. It is also a signal that our public writing has not finished moving the mental model. This essay is part of that move. It is not a promise that every old link on the open web will rewrite itself. It is a promise that our own guides and journal copy will keep naming the account host as Account.
People also confuse Account with the publisher Contact page. Contact is how you reach the company about the site. Account is how you authenticate into products. Mixing those jobs produces tickets that ask support to reset a password from a www URL that was never the control plane. The hostnames guide exists so that mix stops sounding reasonable.
## What this essay refuses to blur
This is not an essay about robots.txt Disallow lines that used to hide noindex on other shells. That batch neighbor stays on the robots mismatch for /auth, /console, and /dashboard style routes and on the fetch-then-header repair. This piece stays on www /login and /signup as leftover shells, and on account.oernoe.com as the live Account host.
It is also not the essay that says the account host holds login rather than journal ads, not the forgot-password-only-on-account note, not the signup-is-not-a-verification-gate piece, not the using-an-account-guide-is-not-signup-chrome piece, and not the broader shells-should-not-rank argument. Those documents have their own jobs. Overlap in facts is allowed. Overlap in thesis is not.
Finally, this is not a claim that every resolving www path is harmless. Shells that still resolve must keep noindex, stay out of the finished listing, and stay free of ads. If any of those checks fail, the page is wrong. Write support@oernoe.com for product defects and hello@oernoe.com for public copy that still teaches the wrong host.
Look at the address bar. If you are reading an article, you should be on www.oernoe.com. If you are signing in, you should be on account.oernoe.com. A www path that still paints a login form is a shell keeping old links alive. It is not Account. Bookmarks should follow the host that actually owns the login.
The durable test is simple enough to run without a committee. Open account.oernoe.com/auth/login and account.oernoe.com/auth/sign-up. Those are Account. Open www /login and /signup only if you must follow an old link, then move your bookmark. Treat any public sentence that collapses those hosts as unfinished copy. That is how shells stay shells, and how Account stays on the account host.
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