Google supports noindex instructions in a page’s HTML or HTTP response header. It must be able to crawl the page to see the instruction. Blocking the page in robots.txt can prevent Google from reading noindex, so the two settings do different jobs. Source: Google Search Central: Block indexing with noindex

Agree which pages should appear

List the public pages intended for search and any pages deliberately excluded. Ask the website team to check the actual settings against that list. This gives a clear basis for spotting an accidental exclusion on an important guide or booking page.

Check the result after changes

Use the search platform’s inspection tools to review a changed page and retain the finding with the change record. For private material, ask the developer to review access controls separately. This keeps the search visibility decision and the privacy requirements explicit.

Written and updated by Travelgenix. Sources checked on 19 October 2026. Practical advice and examples are Travelgenix editorial guidance.