Jul 04, 2026

Tip 4 of 31: Do Not Accidentally Block Useful Extracts

Even when a page can be found and indexed, specific settings can prevent Google Search from displaying extracts from it. This is less visible than a blocked page, but it can make useful content less prominent in search results and AI features in Search.

 

The Problem

When a search engine recommends a page, it may display a sentence or passage to explain why the page is relevant.

Instructions such as nosnippet tell supported search engines not to display a text snippet from the page. Another instruction, data-nosnippet, can exclude specific sections of text from those snippets.

Both have legitimate uses. Neither should be applied accidentally to content you want to remain eligible for useful search extracts.

 

What These Instructions Do

Nosnippet tells supported search systems not to display a descriptive text extract for the page in their results.

In Google Search, it also limits text from the page being shown in AI features. It does not, by itself, prevent the page from being indexed.

Data-nosnippet applies to a specific div, span or section element. It prevents the text inside that marked section from being used in eligible snippets while allowing the rest of the page to remain available.

This does not mean you need to expose every passage on every page. It means reviewing whether these instructions have been applied where they are genuinely needed, rather than across content you want to remain visible in search extracts.

Other AI-assisted systems may use different sources, crawlers and controls, so these settings should not be treated as universal instructions for every AI tool.

 

The Invisible Barrier

One of our clients generated £45,000 in placement fees from their website in a single month.

Results like this depend on people and search engines being able to find and understand useful pages. Accidentally suppressing the clearest description or answer from search snippets can make those pages less informative when they appear in results.

Nosnippet and data-nosnippet are valuable controls when used deliberately. The problem is applying them unintentionally to content that would benefit from an informative extract.

 

What to Do

Ask your developer to check which pages carry nosnippet or data-nosnippet instructions and whether those instructions are deliberate or default.

They should check:

  • Robots meta tags in the page HTML
  • X-Robots-Tag HTTP response headers
  • data-nosnippet attributes in the page content
  • CMS and SEO plugin defaults
  • Template-level settings that affect multiple pages

Pay particular attention to pages with strong definitions or explanations, pages answering direct customer questions and service pages describing what you offer.

Remove or amend these instructions where the content should remain eligible for search snippets.

Where only one passage needs to be excluded, apply data-nosnippet to the smallest relevant supported element rather than suppressing snippets for the whole page.

Do not remove a restriction where it is protecting sensitive information or preventing a potentially misleading partial quotation.

 

Up Next

Tip 5 of 31 covers helping search engines find your content in the first place, before they even reach a specific page.

 

Frequently Asked Questions

What does the nosnippet instruction actually do?

It tells supported search engines not to display a text snippet for the page in their results. In Google Search, the control also limits text from that page being shown in AI features. It does not prevent the page from being indexed unless a separate noindex instruction is present.

When should I legitimately use nosnippet?

Nosnippet can be appropriate when no text from a page should appear in search snippets, for example where partial extracts could be misleading or where the page contains material you do not want reproduced in Search. It should be applied deliberately rather than broadly across useful service, article or educational content.

What is data-nosnippet and how is it different?

Data-nosnippet is applied to a specific div, span or section element rather than the whole page. It prevents text within that marked section from appearing in supported search snippets while leaving the rest of the page eligible. It can be useful for excluding a particular disclaimer or sensitive passage without suppressing snippets for the entire page.

How do I find out if my pages are affected?

Check the page HTML for nosnippet in robots meta tags and data-nosnippet attributes. Your developer should also check the HTTP response headers for an X-Robots-Tag containing nosnippet. Website crawling tools can help identify these controls across multiple pages.

Could these instructions be added automatically by a plugin or platform?

Yes. A CMS, SEO plugin, website template or server configuration may add snippet controls automatically. Review the platform defaults and any changes made during a migration, redesign or SEO update to confirm that the controls are intentional.

 

 

 

Darren Revell, Co-Founder, RecruiterWEB

Co-Founder, RecruiterWEB

Darren Revell began working in recruitment technology in 2004 when he founded Recruitwise Technology. He later became a founder of RecruiterWEB, which acquired the Recruitwise Technology brand, platform and customer base in 2016. Darren remains Co-Founder and Co-Owner of RecruiterWEB.

Darren came to Rectech after eleven years working in recruitment. He started as a trainee recruiter in 1993 and progressed through the ranks to recruiter, billing manager, billing director, and eventually recruitment company owner. During that career, he delivered permanent hires, contract hires, client campaign advertising, team moves, retained search, master vendor services, and RPO.

In 2004, he switched focus to recruitment technology and began building websites and job boards specifically for recruitment agencies. RecruiterWEB has since built websites for 667+ agencies and executive search firms in the UK and internationally. The platform runs on custom code built explicitly for recruitment, with built-in job board functionality, ATS and job poster integration, Google for Jobs structured data, and GDPR-compliant candidate registration included as standard on every plan.

Darren writes on recruitment website design, SEO and AI visibility for recruitment agencies, candidate data protection, and the commercial impact of digital investment on recruitment businesses.

Specialist Areas

  • Recruitment website design and technology
  • SEO and AI visibility for recruitment agencies
  • ATS and job poster integration (Bullhorn, Vincere, idibu, and others)
  • GDPR and candidate data protection
  • Branding for recruitment agencies and executive search firms

Connect

LinkedIn: linkedin.com/in/recruitmentwebsitedesign

Phone: 01223 655278

Darren has also appeared as a guest on the RecTalk podcast, covering his background in recruitment and the founding of RecruiterWEB.

 

 

SCROLL