Website-Pflichtencheckby Jurono
WebsiteTechnicalMaintenancePerformance

Is Your Website Accidentally Hiding from Google?

How noindex, robots.txt, incorrect canonicals, and broken sitemaps can make entire sections disappear after deployment.

By Jurono
Updated: July 19, 2026

A website can be fully available, fast, and almost invisible to search engines at the same time.

No dramatic outage is required. A leftover noindex, an overly broad robots.txt rule, a canonical pointing to the wrong domain, or a sitemap containing staging URLs can be enough. Visitors with a direct link notice nothing. The problem appears later as declining impressions, missing landing pages, and one uncomfortable question: “Why can Google not find the new pages?”

Available is not the same as discoverable

An HTTP 200 only proves that a URL returns content. Search visibility requires several signals to agree:

  • Crawlers must be allowed to access the page.
  • The page must not be excluded with noindex.
  • Canonicals and redirects must point to the intended destination.
  • The URL should be linked internally and represented appropriately in the sitemap.
  • Language and environment variants must not contradict each other.

Google notes that noindex can only be detected when the crawler is allowed to fetch the page. Blocking a URL in robots.txt while also expecting Google to see a noindex directive creates an unreliable and harder-to-debug setup.

Five common causes of invisible pages

1. Staging settings reach production

Test environments are often intentionally protected with noindex. During deployment, the page template moves to production while the robots metadata remains.

2. robots.txt blocks too much

Disallow: / makes sense on staging and is disastrous in production. Less obvious path rules can also block products, categories, or resource sections.

3. Canonicals point to an old or wrong domain

After domain changes, multilingual restructuring, or preview deployments, a production page may still declare another URL as canonical.

4. The sitemap sends bad signals

A sitemap containing redirects, 404 pages, noindex URLs, or staging hosts does not provide clarity. It documents inconsistency.

5. Headers and HTML disagree

An X-Robots-Tag may be set by the server or CDN while the HTML appears indexable. Reviewing only page source misses the response-header directive.

A useful visibility check after every release

Do not test only the homepage. Select representative URLs from each important page type:

  • homepage
  • service or product page
  • category
  • article or insight
  • contact or conversion page
  • language variant
  • newly published page

For each URL, check:

  1. final status and redirect target
  2. access under robots.txt
  3. meta robots and X-Robots-Tag
  4. canonical
  5. hreflang where applicable
  6. inclusion in the correct sitemap
  7. internal links
  8. hostname and protocol

Parts of this can be automated. The important step is defining the expected indexation state for each page type. Without an expectation, a crawler produces data but not a reliable verdict.

Quick check for website owners

  • Is it clear which sections should and should not be indexed?
  • Are production and staging rules separated?
  • Is robots.txt tested after deployments?
  • Are both noindex and X-Robots-Tag checked?
  • Does the sitemap contain only canonical, reachable URLs?
  • Do canonicals use the current production domain?
  • Are there alerts for sharp drops in indexable pages or impressions?
  • Is every new page template tested before release?

Several “no” answers mean visibility currently depends more on luck than on a controlled process.

What Website-Pflichtencheck would review

A technical visibility audit combines crawl data, response headers, robots rules, canonicals, sitemaps, internal linking, and language signals. It checks not only whether individual pages appear indexable, but whether rules remain consistent across page types, environments, and domains.

This is especially useful after relaunches, domain moves, CMS migrations, new language versions, or changes to hosting and CDN configuration.

A website nobody can find is not reliably live. When indexation is only checked after traffic has already fallen, the control arrives too late. A brief post-deployment visibility review costs less than weeks of lost organic reach.

Jurono logo

Jurono

Technical website audits, website fixes, and AI code rescue for small businesses, practices, law firms, and founders in Germany.

Get our free security checklist before you go.

Download free PDF

Want a first signal in 30 seconds? Run the free website quick test.

Get website notes by email

One short technical note every two weeks. No spam, no sales pitch.

Matching offers

Move forward directly

Based on the topics in this article — without a long search.

Manual Website Check

When nobody is sure which scripts, cookie signals, or technical risks are currently running on the site.

249

Manual technical first assessment and clear priorities within two business days.

  • Quickly see whether tracking, cookies, external services, or HTTPS look suspicious
  • Mobile, load time, and technical issues explained in plain language
  • The most important points in a short priority list
Start Manual Website Check

Technical Website Audit

When the website matters, but nobody knows which visible required areas, technical risks, and fixes actually have priority.

549

Audit, assessment, and concrete action plan within 3-5 business days.

  • Everything from the manual website check, assessed and documented in more depth
  • Concrete findings for cookie, tracking, and external service signals
  • Visible required areas checked technically, without legal advice
Get clarity with Technical Website Audit

Website Protection & Maintenance

For small businesses without an internal web team that need ongoing technical calm instead of occasional emergencies.

279/month

Monthly technical support after a short onboarding check.

  • Updates and backups supported in a controlled way depending on system access
  • Monthly short check for new technical findings
  • Up to 90 minutes of small changes or fixes per month
Secure Website Protection & Maintenance

Get clarity before you commit to fixes.

Start with a technical check. If the findings are minor, you can stop there, hand the report to your existing team, or book targeted fixes later.

Technical audit and implementation, not legal advice. I check visible signals, integrations, and delivery issues; legal texts and binding legal assessments remain the work of lawyers or privacy consultants.

Is Your Website Accidentally Hiding from Google?