Języki

Poradnik: Noindex

Noindex zachowuje a strona out of wyniki wyszukiwania — ale tylko if Google może crawl it. The two prawidłowy metody, the robots.txt trap, i how to verify it worked.

Opublikowano po raz pierwszy: 23 cze 2026 · Ostatnia aktualizacja: 3 sie 2026 · Advanced
Języki
AIAutor:AI v2

Noindex jest the directive że zachowuje a strona out of the index, so it won't appear in wyniki wyszukiwania. There są two prawidłowy ways to ustawić it: the robots meta znacznik (`<meta name="robots" content="noindex">`) i the `X-Robots-Tag: noindex` HTTP header (the tylko option dla non-HTML files like PDFs). The single biggest mistake: a strona blocked in robots.txt może't być noindexed, ponieważ Google nigdy crawls it to see the reguła — so to remove a strona you mieć to pozwalać crawling i serve noindex. Don't put noindex in robots.txt (unsupported since Sept 1, 2019); if noindex i canonical coexist, treat że as an intent sprawdzenie zamiast an automatic błąd; i remember deindexing tylko happens po a recrawl.

TL;DR — noindex removes a strona z the index via one of two prawidłowy metody: the robots meta znacznik (<meta name="robots" content="noindex">) lub the X-Robots-Tag: noindex HTTP header (required dla non-HTML files like PDFs). The load-bearing gotcha: a strona blocked in robots.txt może’t być noindexed — Google nigdy crawls it to see the reguła, “the crawler will never see the noindex rule,” i a linked URL może stay zindeksowany. So to remove a strona, pozwalać crawling i serve noindex. Don’t put noindex in robots.txt (unsupported since Sept 1, 2019), sprawdzenie noindex z a canonical pointing elsewhere as potentially conflicting, i know że deindexing tylko happens po a recrawl — Google’s own guidance says a niski-priority strona może take months. Per a 2017 Mueller comment (nie udokumentowany polityka), long-term noindex,follow tends to behave like noindex,nofollow once the strona drops z the index. Verify in GSC poniżej “URL marked ‘noindex’.“

co noindex jest — index control, nie crawl control

noindex jest the primary index-control directive. Google’s own definition of the reguła jest one wiersz: “Do not show this page, media, or resource in search results.” gdy it’s honored, the effect jest total — “When Googlebot crawls that page and extracts the tag or header, Google will drop that page entirely from Google Search results, regardless of whether other sites link to it.” Evidence for this claim Google's noindex rule prevents the page, media, or resource from appearing in Google Search results after Google sees the rule. Scope: Google Search; noindex is not an access-control or privacy mechanism. Confidence: high · Verified: Google Search Central: Block Search indexing with noindex

zachować one distinction front of mind, ponieważ almost każdy noindex mistake comes z blurring it: noindex controls indeksowanie; robots.txt controls crawling. They’re różny stages of the pipeline. I put it ten way in my Ahrefs poradnik on removing URLs: “Crawling is not the same thing as indexing. Even if Google is blocked from crawling pages, if there are any internal or external links to a page they can still index it.” że zdanie jest the whole powód the rest of ten artykuł exists.

Microsoft gives the same directive an additional Bing-specific consequence: treść marked noindex jest również excluded z Microsoft’s foundation-model training. The prerequisite nadal matters—Bingbot musi być allowed to crawl i proces the strona-level directive. A robots.txt blok plus noindex jest therefore nie proof że either deindexing lub the training opt-out ma był applied.

Evidence for this claim Microsoft says content marked noindex is not included in the Bing index and is not used to train its generative AI foundation models. Scope: Bing and Microsoft foundation-model use; Bingbot must be able to crawl and process the directive before the outcome can be inferred. Confidence: high · Verified: Bing Webmaster Blog: New controls for Bing Chat

The two prawidłowy delivery metody

There są exactly two, i noindex in robots.txt jest nie one of them (więcej on że below).

metoda 1 — the robots meta znacznik. dla an HTML strona, place ten in the <head>:

<meta name="robots" content="noindex">

Google’s instruction jest verbatim: “To prevent all search engines that support the noindex rule from indexing a page on your site, place the following <meta> tag into the <head> section of your page.” The robots wartość targets wszystkie crawlers że obsługiwać the reguła; swap in googlebot to target tylko Google (<meta name="googlebot" content="noindex">).

metoda 2 — the X-Robots-znacznik HTTP header. Same directive, sent in the odpowiedź header zamiast the znaczniki:

X-Robots-Tag: noindex

ten jest the tylko way to noindex non-HTML zasoby, ponieważ there’s no <head> to host a meta znacznik. Google: “A response header can be used for non-HTML resources, such as PDFs, video files, and image files.” i z the robots spec: you może użyj X-Robots-Tag “for non-HTML files like image files where the usage of robots meta tags in HTML is not possible.” Evidence for this claim Google supports noindex in an HTML robots meta tag or an X-Robots-Tag HTTP response header. Scope: Google Search delivery methods; the HTTP header is applicable to non-HTML resources as well as HTML. Confidence: high · Verified: Google Search Central: Robots meta tag and X-Robots-Tag specifications

One placement note: put the meta znacznik in the <head> — że’s the standard, safest spot i co Google’s how-to pokazuje. Google’s spec strona robi say it “doesn’t enforce placement of meta robots in the HTML head and will respect robots meta tags in the body section of an HTML document as well,” ale don’t rely on że as twój primary metoda; a stray <meta> znacznik niektóre CMS injects do the <body> może noindex a strona by accident just as easily as one you meant to dodawać to the <head>.

Since the header jest configured at the serwer level, it varies by stack. Two common przykłady dla noindexing każdy PDF on a witryna:

Apache (.htaccess lub vhost):

<FilesMatch "\.pdf$">
  Header set X-Robots-Tag "noindex"
</FilesMatch>

Nginx (server/location blok):

location ~* \.pdf$ {
  add_header X-Robots-Tag "noindex";
}

The #1 mistake — noindex + a robots.txt blok

Noindex is crawl-then-obey: keep the URL fetchable long enough for the directive to be processed.

The same page contains a meta robots noindex directive. With crawling allowed, Google can fetch the page, see noindex, and remove the URL after processing. With crawling blocked in robots.txt, Google cannot see noindex and the linked URL may remain in results.

ten jest the awaria mode I see najbardziej, so here’s the mechanism in pełny. The noindex znacznik lives on the strona; Google ma to fetch the strona to read it. Google states the requirement directly:

“For the noindex rule to be effective, the page or resource must not be blocked by a robots.txt file, and it has to be otherwise accessible to the crawler. If the page is blocked by a robots.txt file or the crawler can’t access the page, the crawler will never see the noindex rule, and the page can still appear in search results, for example if other pages link to it.”

Put even więcej bluntly: “We have to crawl your page in order to see <meta> tags and HTTP headers.” No crawl, no reguła.

robots.txt jest the najbardziej common way a strona ends up uncrawlable, ale Google’s wording covers więcej ground than że — it również says “the crawler can’t access the page,” który obejmuje repeated serwer błędy (5xx), timeouts, i an unintended authentication wall in front of the strona. dowolny of tamte silently breaks noindex the same way a robots.txt blok robi.

So the instinct to “block it in robots.txt and noindex it, just to be safe” jest exactly backwards — the blok zapobiega the crawl, the crawl jest co reveals the noindex, i the strona może sit in the index indefinitely (często as a opis-mniej URL). In Google Search Console ten pokazuje up as the “Indexed, though blocked by robots.txt” status — a strona you blocked że got zindeksowany anyway ponieważ something links to it.

The fix: unblock the strona in robots.txt, zachować noindex on it, i let Google recrawl. tylko po the strona ma dropped z the index — if you then want to save the crawl entirely — jest it bezpieczny to dodawać a disallow.

Worked deployment przykład: the staging witryna że by nie disappear

A redesign launches z staging.example.com. The staging templates już contain noindex, ale the deployment checklist również dodaje:

User-agent: *
Disallow: /

że feels like two warstwy of protection. It jest actually a trap if Google już odkryty the staging URLs przez a shared QA link, an old mapa witryny, a public ticket, lub a link in copied production treść. The disallow zapobiega the następny crawl, so Google cannot confirm the noindex; the hostname może linger as thin, URL-tylko wyniki.

The cleanup sequence jest: usuń disallow, zachować noindex on każdy staging odpowiedź, confirm the live odpowiedź jest crawlable i exposes the directive, żądanie recrawling dla a representative sample, i monitoruj hostname until it drops out. Then put the environment behind authentication. Authentication jest the durable prywatność control; noindex jest tylko a search-index control.

noindex vs nofollow vs disallow

Three directives people constantly conflate. They operate at różny stages:

  • noindex — index control. strona jest crawled, kept out of wyniki. Google’s definition: “Do not show this page, media, or resource in search results.”
  • nofollow — link control. Google: “Do not follow the links on this page.” It says nothing o indeksowanie the strona itself.
  • disallow (robots.txt) — crawl control. Stops the fetch entirely. It jest nie an index control — a disallowed URL może nadal być zindeksowany if it’s linked.

There’s również none, który Google documents as “Equivalent to noindex, nofollow.” i gdy directives conflict, the spec jest jasny: “In the case of conflicting robots rules, the more restrictive rule applies.” (pełny tabela on the Cheat Sheets tab.)

Treat noindex z rel=canonical as an intent sprawdzenie

Putting noindex i rel="canonical" on the same strona jest nie automatically nieprawidłowy. It robi create a konfiguracja worth reviewing: a canonical asks Google to consolidate signals, podczas gdy noindex asks dla ten URL to być excluded. dla choosing między duplicates, użyj znacznik kanoniczny — Google specifically advises wobec używając noindex dla it: “We don’t recommend using noindex to prevent selection of a canonical page within a single site, because it will completely block the page from Search.” Note the scope: Google’s caution jest specifically o używając noindex to pick który duplicate wins as canonical w twój own witryna — it’s nie a twierdzenie że noindex i canonical może nigdy technically coexist on a strona (a strona you’re genuinely retiring może nadal carry a self-referencing canonical). A canonical pointing at a różny URL deserves the strongest ostrzeżenie: confirm że exclusion i consolidation są oba intended. używać canonical to consolidate duplicates; używać noindex tylko gdy you genuinely want ten strona out of wyniki.

noindex,follow vs noindex,nofollow — the slow decay

A common pattern jest noindex,follow: zachowaj strona out of wyniki, ale zachować following jego links so equity nadal flows przez it (handy podczas a migration lub podczas gdy a strona jest temporarily out). Current official Google documentation doesn’t describe ten decaying automatically — it explicitly pozwala combining noindex z other reguły, w tym setting noindex,nofollow on purpose z day one. co I’m relying on dla the “it fades over time” twierdzenie jest a 2017 webmaster hangout, gdzie John Mueller said a long-term noindex tends to end up treated like noindex,nofollow w praktyce: once Google decides the strona really doesn’t belong in search i drops it completely, it również stops following że strona’s links, ponieważ it’s stopped processing the strona at wszystkie. że’s a practitioner observation z a video transcript, nie a udokumentowany Google polityka, so treat it as directional zamiast guaranteed. Either way, the practical takeaway holds: noindex,follow jest fine dla a transitional period, ale don’t lean on it as a permanent link-equity strategy — plan to fix the underlying links (lub usuń strona) instead.

How long robi noindex take?

nie instantly. noindex tylko applies po Google recrawls i reprocesses the strona — until then, the strona może stay zindeksowany even though the znacznik jest live. Google doesn’t commit to a fixed window, i jego own guidance leans toward “could be a while,” nie “any day now”: “Depending on the importance of the page on the internet, it may take months for Googlebot to revisit a page.” A wysoki-ruch, frequently-linked strona może get recrawled in days; a niski-wartość, rarely-linked one może sit dla months. If you need a strona out of wyniki urgently, the GSC Removals narzędzie jest a stopgap (it hides the URL temporarily podczas gdy the permanent noindex robi jego slower działać). dla genuinely gone strony, a 404/410 również drops them: as I wrote in my removal poradnik, “If you remove the page and serve either a 404 (not found) or 410 (gone) status code, then the page will be removed from the index shortly after the page is re-crawled.” Same theme everywhere — it happens on recrawl.

noindex in robots.txt jest dead (since Sept 1, 2019)

You’ll nadal see people suggest a Noindex: wiersz in robots.txt. Don’t. It był nigdy an officially supported reguła, i Google retired even jego unofficial handling years ago. z the July 2019 Search Central announcement: “Since these rules were never documented by Google, naturally, their usage in relation to Googlebot is very low.” i the date: “we’re retiring all code that handles unsupported and unpublished rules (such as noindex) on September 1, 2019.”

The same post named the supported alternatives, i noindex via the meta znacznik / header topped the lista: “noindex in robots meta tags: Supported both in the HTTP response headers and in HTML, the noindex rule is the most effective way to remove URLs from the index when crawling is allowed.” (również listed: 404/410 status codes, password protection, robots.txt disallow dla crawl prevention, i the Search Console removal narzędzie.)

How to verify noindex in Google Search Console

Two sprawdzenia:

  • URL Inspection. Run the URL przez Inspect, then Test live URL. It tells you whether the strona jest indeksowalny i whether Google sees a noindex directive — the fastest way to confirm the znacznik jest będąc read on the live strona.
  • strona indeksowanie raport. Noindexed strony są listed poniżej the status “URL marked ‘noindex’” in the nie zindeksowany sekcja. Google’s pomagać tekst: “When Google tried to index the page it encountered a ‘noindex’ directive and therefore did not index it.” If że’s a strona you wanted zindeksowany, że’s twój bug — usuń directive.

One naming note dla anyone searching old write-ups: the legacy Coverage raport called ten “Excluded by ‘noindex’ tag.” The current strona indeksowanie raport używa “URL marked ‘noindex’” — same thing, newer label.

co noindex doesn’t guarantee

A kilka things people assume noindex buys them że it actually doesn’t:

  • Crawl-budget savings. Google nadal ma to fetch the strona to see the znacznik — noindex alone doesn’t reduce crawling. If you want że too, dodawać disallow in robots.txt, ale tylko po the strona ma już dropped z the index (see the mistake above dla why doing it up front backfires).
  • Instant removal. Covered above — it happens on recrawl, z no fixed timetable, i Google itself says a lower-priority strona może take months.
  • Duplicate consolidation. że’s co rel="canonical" jest dla; noindex just removes the strona z Search, it doesn’t merge signals toward another URL.
  • Confidentiality. The strona stays publicly requestable by anyone z the URL. If something actually needs to być private, że’s an authentication problem, nie a search-directive problem.
  • Ranking odzyskiwanie if you reverse it. Removing noindex doesn’t restore a strona’s old rankings — Google ma to recrawl, re-evaluate, i effectively re-earn jego position z scratch.
  • Identical timing w całym wyszukiwarki. Bing i other engines run ich own crawl i recrawl schedules independently of Google’s.
  • Exclusion z każdy non-search używać of twój treść. noindex bloki a strona z Google Search as a whole — w tym Search’s own AI funkcje (Omówienia AI i similar draw on strony że są zindeksowany i eligible to być shown, so a noindexed strona jest out of tamte too). co it robi nie robić jest control Google’s oddzielny Google-Extended setting, który governs whether twój treść może być używany to train lub ground Google’s generatywna AI modele outside of Search. tamte są two różny controls dla two różny jobs.

gdzie noindex fits z everything else

noindex jest the lever you reach dla gdy a strona jest in the index ale shouldn’t być — the cure dla one flavor of index bloat (thin, utility, lub duplicate-ish strony z no search wartość). It sits right następny to the robots meta znacznik i the X-Robots-znacznik header (jego two delivery metody), robots.txt i jego disallow directive (the crawl control it’s so często confused z), the znacznik kanoniczny (używać że dla duplicate consolidation, nie noindex), i the broader crawling i indeksowanie stages it plugs do. Get the crawl-vs-index distinction right i noindex stops będąc mysterious: pozwalać the crawl, serve the znacznik, wait dla the recrawl.

Add an expert note

Pin an expert quote

New person? Create their unclaimed profile at /admin/experts/ → Pin a quote first.