1. Identify which text is misleading before changing the page

For a Singapore SME service page, begin with one concrete question: is the search description explaining this service, or quoting an unrelated promotion? Create a working record containing the page URL, exact search query, observation date, displayed description and matching passage on the website. Treat this as an editorial investigation rather than an instruction to rewrite every page.

Google calls the description beneath a search result a snippet. It primarily creates snippets from page content, sometimes uses the meta description, and can show different snippets for different searches. A mismatch therefore does not automatically mean your website editor saved the wrong meta description. Source: Google Search Central, snippets.

Hypothetical example: an office maintenance page has a shared footer advertising a seasonal household service. A search description quotes that promotion. Compare the displayed words with the footer, service introduction and meta description before deciding what to change. This is an illustrative scenario, not a reported business result.

Repeat the check for a small, predefined set of relevant questions. Keep each observation separate. Your immediate objective is to identify the passage needing attention, not to infer a sitewide problem from one result.

2. Repair the service explanation and description first

Read the opening paragraph without the menu, banner or footer. Our recommended test is whether a prospective customer could identify the service, intended customer and next action from that paragraph alone. Replace vague introductory language with an accurate explanation approved by the person responsible for delivering the service. Do not add unsupported availability, credentials or delivery promises.

Then write a page-specific meta description that summarises the same offer. Google recommends accurate, distinct descriptions for individual pages and warns that strings of keywords do not clearly explain their content. Google also states that meta descriptions have no fixed length limit, although displayed snippets may be truncated to fit the device. A short editorial limit is therefore a publishing choice, not a Google requirement. Source: Google Search Central, snippets.

Hypothetical example: replace a generic introduction such as “Your trusted solutions partner” with an approved explanation of the maintenance work offered and how to request an assessment. Leave any unconfirmed service details out.

If the footer promotion has expired, correct or remove the promotion itself. Our recommendation is to resolve inaccurate customer-facing wording before considering a technical control that only changes its eligibility for search previews.

3. Assess data-nosnippet for a narrowly defined block

If a promotion remains useful to website visitors but is inappropriate as a description of this service, discuss a targeted exclusion with your website editor. Google documents data-nosnippet as a way to prevent particular parts of a page from appearing in snippets. Its separate nosnippet control prevents a page snippet, while max-snippet specifies a maximum snippet length. These controls address different scopes. Source: Google Search Central, snippets.

Prepare a precise editing brief: identify the unwanted block, explain why it misrepresents the service in isolation, and list the neighbouring content that must remain outside the exclusion. Request a preview before publication. Avoid a vague instruction such as “hide the footer”, especially when the footer also contains information you want customers to find.

Hypothetical example: isolate the seasonal promotion rather than including the service summary and enquiry instructions in the same excluded block. The example describes an editing decision, not a guaranteed search outcome.

Also consider your Google AI visibility objective before widening exclusions. Google says these preview controls limit information shown in Search, including its AI features; supporting links in AI Overviews and AI Mode require pages to be indexed and eligible for a snippet. Source: Google Search Central, AI features.

4. Verify the implementation and judge the wording

Before publishing, ask the editor to show the exact exclusion boundary and confirm that the intended service explanation remains readable. Record the previous wording, revised wording, affected URLs, publication date and responsible editor. For a shared footer, request a list of pages affected by the template change so your comparison has a defined scope.

If preview controls appear ineffective, Google recommends checking that the control is correct and visible to Googlebot, using URL Inspection to examine the HTML received during crawling, and allowing time for recrawling and processing. Its guidance notes that crawling can take several days to several months, depending on how often its systems determine that a page needs refreshing. Source: Google Search Central, AI features.

Compare the original searches again and record whether the unrelated promotion remains. Assess accuracy rather than whether Google reproduces your preferred sentence verbatim: Google generates snippets automatically and may choose different wording for different queries. Source: Google Search Central, snippets.

For your internal decision, separate implementation from observation. “The correct block has the control” is one check; “this query now shows an accurate description” is another. Keep unresolved observations open instead of repeatedly rewriting the page without a specific diagnosis.

It does not give you that control. Google primarily creates snippets from page content and only sometimes uses the meta description. Improve both, then assess a targeted data-nosnippet exclusion if a particular block should not appear in snippets. Source: Google snippet guidance.

Should I use nosnippet for the whole service page?

For one irrelevant promotion, our recommendation is to assess a narrower exclusion first. Google distinguishes blocking a page snippet with nosnippet from excluding particular content with data-nosnippet. Source: Google snippet guidance. Google also requires snippet eligibility for supporting links in AI Overviews and AI Mode. Source: Google AI guidance.

What should I send my website editor?

Send the affected URL, exact query, observed snippet, matching source passage and proposed exclusion boundary. Ask for a preview and a record of affected template pages. This is our recommended handover checklist. For troubleshooting preview controls, Google recommends verifying correctness and inspecting the HTML received by Googlebot. Source: Google AI guidance.