Skip to content
regensbot
DEV-INT-11Should11 of 12 in INT

Write pages in the words, spellings and script the audience searches with, and never add synonym or variant lists

Level
Should

Recommended: skip it only for a reason you can name.

Documentation

Documented

At least one cited Google document states or supports it.

Covered

Assisted

Proposed with the evidence. A person confirms it.

Why it matters

Google expands almost every query with synonyms, treats spellings with and without diacritics as the same behind the scenes, and recognises an English term and its local-language equivalent as one thing, so a page needs neither every synonym nor both spellings. Blocks of keyword variants read as keyword stuffing, which Google's spam policies prohibit. Said at Search Central Live: users expect text written the way they search, which differs by language and script; Hindi users, for example, search both in Devanagari and in Latin letters.

How to meet it

Keep editors' wording as written in the CMS: do not strip diacritics from titles, headings or body text, and do not auto-append synonym, misspelling or transliteration blocks, hidden keyword fields or tag clouds. Where an audience searches in two scripts or spellings, choose the form per market from real query data instead of duplicating the page. Use another name for a term only where readers might not understand otherwise.

How to test it

Search Console's Performance report shows which spellings and scripts users type for key terms; searching each variant on Google shows whether Google treats them as the same thing; a template audit finds no generated synonym or variant lists.

How Regensbot covers it

AssistedNeedsYour verified site

Regensbot proposes a verdict with the evidence; a person on your team confirms it.

The evidence comes from your verified site: its pages, its profile and the files you upload.

You verify the site by a DNS TXT record, a meta tag or a file. Regensbot then keeps a checklist item for this requirement, with a state, a guide, an evidence upload and reminders.

How verdicts workWhat you connect

Sources

Google documents03

  1. 01Search Engine Optimization (SEO) Starter GuideGoogle Search Central (opens in a new tab)
  2. 02How search results may differ based on accented characters and interface languagesSearch Central blog (1 September 2006) (opens in a new tab)
  3. 03Spam policies for Google web searchGoogle Search Central (opens in a new tab)

Claims in the knowledge base10

  1. D3-C023ConfirmedMaking sense of users' queriesSaid on stage
  2. D3-C042ConsistentMaking sense of users' queriesSaid on stage
  3. D3-C044ConsistentMaking sense of users' queriesSaid on stage
  4. D3-C048ConfirmedMaking sense of users' queriesSaid on stage
  5. D3-C050ConsistentMaking sense of users' queriesSaid on stage
  6. D3-C051UndocumentedMaking sense of users' queriesSaid on stage
  7. D3-C024n/aMaking sense of users' queriesThe author's interpretation
  8. D3-C055n/aMaking sense of users' queriesThe author's interpretation
  9. D2-C965ConsistentLightning session G: InternationalisationSaid on stage
  10. D2-C981SourceLightning session G: InternationalisationGoogle's documentation

Claim IDs refer to the Search Central Live 2026 knowledge base. The knowledge base (opens in a new tab)

Confirmed
Google's documentation states the same thing.
Consistent
Google's documentation supports it without stating it.
Undocumented
Said or shown at the event, not in the documentation.
Source
The claim is the cited document itself.
n/a
Nothing to verify: a quotation, framing, opinion or analysis.

Audit

Check it on your site.

One audit checks a URL against all 138 requirements and returns one finding for each, with its source. One URL decides 66; for each of the others, the finding says which source to connect.