Which pages should you consider for noindex?

Consider pages that support an existing visit but that you do not want to offer as starting points from search. Make a short list and explain each choice. Avoid a blanket rule based only on a page name or its current traffic.

Hypothetical example: a small workshop business

Imagine a pottery studio with a class description, a booking form and a generic booking confirmation. The owner wants new customers to find the class description. The confirmation is intended for someone who has already booked.

I would consider noindex for that generic confirmation. I would review the booking form separately: perhaps the owner wants people searching for an immediate booking to land there. This is a decision exercise, not a claim about results from a real studio.

Do not treat every quiet page as disposable. Ask whether you would improve it, combine it with something else, or stop presenting it in search. Use a practical SEO audit to organize that review before changing a whole section.

For several versions of the same content, also read the canonical tag guide. Tell your specialist whether the problem is choosing a preferred version or excluding a page from search altogether. Keep those decisions explicit in the brief.

What does the noindex instruction actually do?

Noindex tells Google not to show a page or resource in search results. A robots meta tag is a piece of page code containing instructions for search crawlers, the programs that visit websites. Google describes these page rules in its robots meta specification.

Use those definitions to ask a clearer question of your supplier: “Which exact page will receive this instruction?” Request a sample before approving a change across many pages.

Keep privacy separate

A noindexed page can still be opened directly by someone with its link. Google recommends password protection for confidential content. Its content sharing guide separates that protection from noindex.

If a page contains a customer's details, begin with who should have permission to see them. Do not put a visibility setting in the place of an access decision. Ask the person responsible for the website to document how unauthorized visitors are kept out.

Why is noindex different from robots.txt?

Robots.txt controls which URLs a crawler can access. It does not reliably keep a web page out of search: Google can discover its address through links and display that address without visiting the page. This limitation is explained in Google's robots.txt guide.

A crawler must be able to access the page to read its noindex instruction. Blocking that access can prevent the instruction from being seen. Google states this requirement in the robots meta documentation.

Write the desired outcome, not “block Google”

For a public utility page, write: “Keep this available to visitors, exclude it from search, and allow Google to read the exclusion instruction.” That wording gives your developer something concrete to implement.

If an existing robots.txt rule covers the page, include it in the review. Avoid deleting broad rules without understanding what else they cover. The robots.txt setup guide can help you prepare that conversation.

How do you add noindex to a page or PDF?

For an ordinary HTML page, place this robots meta tag in its head section, the part containing page information. This is the implementation shown in Google's setup example.

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

Give this example to the person maintaining your website. Specify the exact page address and ask them to show the resulting instruction. Do not paste the code into a paragraph in your page editor.

Using WordPress, Wix or another website editor

Your content management system, meaning the software used to edit your site, may provide a search visibility setting instead of direct code editing. Google discusses this approach for systems including WordPress, Wix and Blogger in its CMS guidance.

1. Open the specific page you intend to change.
2. Find that platform's instructions for search visibility.
3. Check whether the setting affects one page or a wider group.
4. Save the change and inspect the published page.

Ask for help if the setting's scope is unclear. “Hide this page” and “change the website's search settings” are not precise enough as work instructions. Put the affected addresses in writing.

Using an X-Robots-Tag header

An HTTP response header is information the server sends along with a file. The X-Robots-Tag header can carry noindex for resources such as PDFs, as described in Google's header documentation.

X-Robots-Tag: noindex

For a public PDF that should stay outside search, give your developer the PDF address itself. Ask for confirmation that its response contains the instruction. Separately decide whether the page linking to that file should remain discoverable.

What should you check before calling the job complete?

Ask for evidence from the published page, not just a screenshot of a saved setting. I recommend accepting the work against a short checklist that includes the target page and a few important pages outside the change.

• The exact intended address was changed.
• The published page or file carries the intended instruction.
• Crawler access was reviewed so the instruction can be read.
• The homepage and main sales pages were checked separately.
• The reason, responsible person and review date are recorded.

If the proposed work expands from one page to an entire template, pause and review the list of affected pages. Ask your supplier to explain why that larger scope is necessary. Approve the list rather than relying on a broad label such as “utility pages.”

Do not add nofollow automatically

Noindex concerns whether the page appears in search. Nofollow instructs crawlers not to follow links on that page. Google lists them as separate rules in its indexing and serving specification.

Keep the first task focused on your stated visibility goal. If someone proposes additional link rules, ask for the reason separately. Review your internal linking plan as a distinct piece of work.

How can you organize the work this week?

Start with one page whose purpose is clear. Prepare the brief, request the change, and check what was delivered before considering a larger group. Keep uncertain pages on a review list.

A brief you can send to your website manager

Target page: [address]. Visitors should still be able to open this public page, but we do not want it displayed in Google Search. Apply noindex only to this address, review crawler access, and show the instruction on the published page or response.

Add your business reason underneath. In a hypothetical online shop, that might be: “This page gives general next steps after an order. We do not want someone arriving from search to mistake it for confirmation that they placed an order.”

Also write who can approve expanding or reversing the change. For a team updating several pages, use a simple register with address, purpose, decision, owner and verification result. Keep that register with your website redesign checklist if a redesign is underway.

At the next review, ask whether each page still serves the same purpose. A business decision made for an old campaign may need reconsideration when the page is reused. Require a fresh explanation rather than copying the old instruction into a new brief.