This translation has not been editorially reviewed yet. The German version is authoritative. Deutsche Fassung →
Indexing
Why doesn't my finished website appear on Google?
The most common cause is a forgotten "noindex" — a single technical instruction that tells search engines not to add the page to the index. During development, it's set deliberately, so unfinished pages don't show up on Google. If the switch is forgotten at launch, the finished website stays unfindable, even though it works perfectly. The "Indexing" audit area reads both spots where a noindex can hide.
One instruction, total effect
"noindex" is a single word in a web page's technical section. It tells every search engine: don't add this page. There's no partial version of it — a single noindex excludes the page entirely from search results. The tricky part: nothing changes for visitors. The page loads normally, every link works, the design is right. That's why the error often goes unnoticed for months, until someone asks why the website can't be found on Google. In our assessment, this rule carries 25 of the audit area's 100 points — more than any other, because its effect is total.
Two hiding spots: meta tag and header
A noindex can sit in two places. First, in the page's own source code, as a so-called meta tag — anyone who opens the source code and searches for it finds it there. Second, in the HTTP header, an invisible cover note the server attaches to every response; the technical term is X-Robots-Tag. This second spot isn't visible in the browser, and it's exactly there that it gets overlooked most often. Our check reads both spots on every run and states, word for word, what instruction was found in the finding — so it can be removed specifically.
The forgotten test-mode switch
For a new website build, the agency works on a preview address. To stop this work-in-progress showing up on Google too early, it's protected with noindex — that's correct. When moving to the real domain, this protection has to be removed. This exact step keeps getting lost in the rush of a launch date. The result: the new website is live, looks great, and still disappears step by step from search results. So explicitly ask about this switch at every relaunch — and have the answer confirmed with a look at the source code.
- Open your homepage's source code (right-click, "View page source") and search for the word "noindex".
- Search Google for "site:your-domain.at" — if not a single page appears, your website is probably excluded.
- Explicitly ask after every relaunch whether the noindex from testing was removed.
- Ask your agency to check the HTTP headers too — a noindex can sit there without being visible in the source code.
FAQ
What does noindex mean?
noindex is a technical instruction to search engines not to add a page to the search index. It sits either as a meta tag in the source code, or as an X-Robots-Tag in the HTTP header of the server response. For visitors, the page stays normally usable — it just can't be found via search engines any more.
Why is my new website invisible on Google?
The most common cause is a noindex from the development phase that wasn't removed at launch. Other possible reasons are a blocking robots.txt, or simply time: Google has to visit a new website first. A forgotten noindex keeps the page away permanently, though — check that first.
Can noindex also apply to just individual pages?
Yes. The instruction applies per page, not per website. Some pages are deliberately excluded — internal search results or confirmation pages, say. It becomes critical when important pages, like the homepage or service pages, are affected. The check assesses whichever specific page was measured.
How quickly does my page reappear after removing noindex?
That can't be predicted to the day. Google has to visit the page again and read the changed instruction — only then can it return to the index. You can help the process along by making sure the page is in the sitemap and well linked internally.