A service page can make sense from top to bottom while one extracted sentence needs more context.
Before asking a developer to suppress that sentence, identify the boundary you need. Should it remain public? Should the whole page remain discoverable? Is the concern about an excerpt or about unauthorized access?
Those decisions lead to different work. Write the requirement first. Choose a search directive after the owner has confirmed what may be public.
Google primarily creates snippets from page content and may use a meta description instead. The excerpt can differ by query. A description is a candidate summary, not a fixed search-result script. Google explains snippet generation.
This article proposes a decision worksheet for public B2B pages. The worked service page is fictional. The examples concern Google's documented behavior checked on 2026.10.28; they do not establish how another search provider behaves.
Decide Whether the Material Belongs on a Public Page
Imagine a fictional consultancy publishing a supplier-onboarding service page. It contains a service overview, an illustrative process, and an invented scheduling example.
The scheduling paragraph describes a sample sequence that depends on several assumptions. The editor wants readers to understand those assumptions before interpreting the sequence. They ask whether the paragraph can be excluded from search excerpts.
First, ask the service owner whether the paragraph is approved for public reading. If the answer is yes, an excerpt restriction may fit the editorial objective.
Now change the scenario. Suppose the paragraph contains an actual customer's private schedule. That introduces an access requirement. Stop treating it as a snippet problem.
Google recommends password protection for confidential content. Its guidance also explains that noindex leaves direct access possible. Read Google's content-sharing guidance.
For the fictional page, keep the example synthetic and explicitly labeled. Give the access owner any separate requirement to protect real business records. An editor's search preference should never become the approval for publishing private material.
Use this decision before inspecting markup. A technically correct excerpt setting can still implement the wrong requirement.
Separate Four Control Questions
Put four questions at the top of the change request. Answer each in ordinary language before discussing tags.
| Question | Decision to record | Evidence to request |
|---|---|---|
| Who may read the material? | Public, approved users only, or unresolved | Access owner's requirement and an unauthorized-access check |
| Should the page appear in search? | Desired indexing treatment | Page-level indexing configuration and inspection evidence |
| May the crawler fetch the page? | Intended crawl policy | Applicable crawler rules and fetch evidence |
| What excerpt boundary is wanted? | Whole page, length ceiling, or selected passage | Delivered markup and the approved passage boundary |
This table is an editorial handoff, not a security design. Have the person responsible for each system supply the evidence for that row.
A robots.txt block controls crawling; it does not reliably exclude a known page from search. Google explains this indexing limitation.
Google needs crawl access to read page-level directives. Google's robots guidance explains the interaction.
Do not combine a crawl block and a page directive without asking the maintainer how the directive will be read. Keep an access decision separate from both.
The technical SEO checklist offers a place to organize a broader crawl and indexing review. Keep the excerpt request specific enough that its owner can approve one boundary.
Choose the Smallest Suitable Excerpt Restriction
Google documents these three text-preview controls. Check the current specification before implementation.
| Control | Documented scope |
|---|---|
nosnippet |
Suppresses text snippets and video previews; image thumbnails may remain |
max-snippet:N |
With positive N, caps text snippets at N characters without limiting image or video previews; 0 equals nosnippet |
data-nosnippet |
Excludes designated text on span, div, or section elements |
For the fictional service page, the editor wants the overview available for excerpts. Only the scheduling illustration needs the narrower boundary. Select the passage-level option for review.
If the owner instead requests no text preview for the page, discuss the page-level option. Ask them to approve that wider boundary explicitly. Do not silently suppress the entire page because one paragraph was inconvenient to wrap.
Use a length ceiling only when the requirement concerns length. It does not express which particular passage the editor considers unsuitable. Write down why the selected number fits the requirement. Avoid borrowing a number from an unrelated page.
These decisions concern presentation. This worksheet does not attempt featured-snippet acquisition or predict visibility gains. Keep any broader search strategy review in a separate assignment.
Use Scoped HTML Examples
The following fragments are alternative examples for review, not instructions to apply all three. A maintainer should place the chosen meta tag in the page's HTML head.
For a page-wide restriction aimed at Google:
<meta name="googlebot" content="nosnippet">
For a proposed text-preview ceiling of 120 characters:
<meta name="googlebot" content="max-snippet:120">
Google treats 0 as equivalent to nosnippet, including its video-preview restriction. A value of -1 leaves Google to choose the snippet length. With conflicting rules, the stricter rule wins. Separately permitted uses, including some structured data, have exceptions. See the max-snippet specification.
The number in this example is illustrative. It is not a recommended default for every service page. Have the editor state the need before the maintainer installs a page-wide setting.
For the fictional scheduling paragraph, use a supported wrapper around only the approved passage:
<p>We review the steps in your supplier onboarding process.</p>
<section data-nosnippet>
<h2>Fictional scheduling illustration</h2>
<p>This sample sequence assumes the buyer has assigned a reviewer.</p>
</section>
<p>The engagement scope defines the agreed deliverables.</p>
The attribute is boolean: data-nosnippet="false" still excludes text. Close wrappers correctly. Avoid adding or removing the attribute on existing nodes through JavaScript. Structured data remains independently usable. Google documents these element constraints.
Ask the maintainer to point to the opening and closing wrapper in the delivered page. Compare that boundary with the approved paragraph. A screenshot of the visible text cannot show whether the attribute is present.
Keep the code example separate from production instructions. Record the exact page, component, and environment where the approved change belongs.
Give the Editor a Decision Worksheet
Complete this worksheet before assigning the implementation. Leave unknown fields unresolved instead of supplying a convenient guess.
| Field | Fictional service-page decision |
|---|---|
| Page under review | Supplier-onboarding service page |
| Material status | Public, synthetic example approved by the service editor |
| Reader problem | Scheduling illustration needs its surrounding assumptions |
| Required excerpt boundary | Exclude the illustration heading and paragraph |
| Content outside the boundary | Overview and deliverable description |
| Selected control | data-nosnippet on the illustration section |
| Implementation owner | Website maintainer |
| Editorial approver | Service editor |
| Shared-component scope | Unconfirmed; inspect before editing |
| Verification evidence | Delivered HTML, wrapper boundary, response headers, rendered page |
| Follow-up owner | Search editor |
| Review trigger | Publication of the approved change and a later recorded search observation |
Add a short rationale below the table. In this example: the paragraph may be read publicly, but the editor prefers it interpreted with its assumptions.
That rationale matters when another editor reviews the setting later. Without it, a restriction can survive after the original paragraph has been removed or replaced.
Name a real implementation owner in the working record. A role is sufficient in a fictional worksheet, but an unassigned role does not complete a production handoff.
If the requirement changes to private access, return the worksheet to the access owner. Do not attempt to stretch the selected excerpt control into a new purpose.
Verify the Page in Layers
Start with implementation evidence. Ask the maintainer for the delivered HTML and applicable response headers. Identify the intended directive and any other preview restrictions already present.
Read the exact wrapper boundary. Confirm that the overview stays outside it and the entire scheduling illustration stays inside it. Ask the editor to approve that boundary against the final prose.
Then inspect the rendered page. Confirm that the public example remains understandable and that the page still distinguishes illustration from commitment. A snippet setting should not become a reason to leave misleading prose on the page itself.
Review the shared component separately if one is involved. Identify every page the component change would affect before approving wider installation. A one-page requirement deserves a one-page implementation unless the owner approves more.
Keep the release record distinct from later search evidence. Record when the approved page became available. Record any subsequent search query, date, device, and observed excerpt separately.
If the selected paragraph does not appear in a result, do not treat that absence alone as proof of enforcement. The observation shows what appeared. Your markup inspection records what was implemented.
If the excerpt still contains the passage, preserve the observation. Ask the maintainer to check the delivered boundary, existing rules, page version, and implementation history. Leave the explanation unresolved until the evidence supports one.
Make a Meta Description Useful Without Treating It as a Lock
Write a short description that represents the public service accurately. For the fictional consultancy, an editorial draft might read: “Review supplier onboarding steps, responsibilities, and handoffs before defining a process improvement project.”
Have the service owner check each noun. Does the page cover responsibilities? Does it discuss handoffs? Is a process review the actual offer?
Remove details the page does not support. A description should not introduce a service promise that the visible copy carefully avoids.
For this review, compare the description with the approved excerpt boundary. If the description repeats the scheduling illustration, give that inconsistency to the editor. Do the same for other descriptive fields the maintainer identifies.
Use the existing zero-click search strategy discussion to frame a separate visibility conversation. The decision here remains narrower: which public text does the publisher want eligible for an excerpt?
No search observation in this worksheet establishes a revenue effect or a change in buyer behavior. Keep those claims out of the implementation receipt.
Keep the Restriction Attached to Its Reason
Revisit the worksheet when the service page changes. A new example, revised scope, or different component can require a fresh boundary review.
Ask the editor whether the original reason still applies. Ask the maintainer whether the implementation still covers the intended passage. Record both answers with the current page revision.
Close the implementation task after the approved boundary is verified. Keep any unresolved search observation with its evidence and assigned follow-up owner.
A useful receipt states the page, selected control, covered text, verifier, and remaining uncertainty. It should let a later editor decide whether to retain, revise, or remove the restriction.
Define the boundary before the tag.
Sources
- Google Search Central: Control your snippets in search results. Query-dependent snippets and meta descriptions. Checked 2026.10.28.
- Google Search Central: Robots meta tag, data-nosnippet, and X-Robots-Tag specifications. Preview settings, element constraints, and rule interactions. Checked 2026.10.28.
- Google Search Central: Introduction to robots.txt. Crawl controls and discoverable blocked URLs. Checked 2026.10.28.
- Google Search Central: Control what you share with Google Search. Public access, password protection, and indexing distinctions. Checked 2026.10.28.