MULTILINGUAL KEYWORD RESEARCH — BUYER RFP WORKSHEET Fillable editorial template, 2026-11-20. Not a legal contract or a universal requirement. 1. THE DECISION WE NEED Business offer and customer problem: [fill] Primary buyer/customer: [fill] Decision this research must support: [existing page update / new page brief / market discovery; describe] Conversion or information task: [fill] Business claims, features or markets that must not be implied: [fill] Internal product owner for questions: [name / role] 2. SCOPE, ONE ROW PER COUNTRY-LANGUAGE PAIR Pair ID: [e.g., M1] Country: [fill] Language and script, if relevant: [fill] Search platform and device scope: [fill] Offer available in this market? [yes / no / pending, with evidence] Buyer and page families in scope: [fill] Existing site URLs or section: [fill] Known source concepts/customer language: [fill] Explicit exclusions: [fill] Local-language reviewer supplied by: [buyer / provider / jointly; named role] Repeat this block for every pair. Do not combine two countries under a language-only total. 3. WORK REQUESTED OF THE PROVIDER Discovery method and seed expansion per pair: [ask provider to describe] Sources, database/country settings, language, date range and export dates: [ask provider to identify] Meaning and offer-fit checks: [ask provider to identify reviewer and method] Local SERP checks: [which candidate types, sample size, location method, device, date and limitations] Existing URL check and recommended page action: [define expected level] Resolution of ambiguous and rejected candidates: [define expected record] Any optional copywriting, technical SEO, ads or rank tracking: [separate scope, or explicitly exclude] 4. DELIVERABLES AND REQUIRED FIELDS [ ] Editable approved-task sheet, filterable by country and language. [ ] Editable hold/rejection sheet with reason and next evidence needed. [ ] Method and assumptions note with source/provider name, settings, collection dates and limitations. [ ] Reproducible evidence references or permitted source exports; identify license restrictions. [ ] Concise per-market decision summary and content handoff owners. Minimum row fields: exact local query; country; language; source concept; source/discovery method; collection date; buyer task; proposed page type; existing URL candidate; decision; reason; local-language reviewer/status; SERP evidence reference/status; next action and owner. For every metric used in priority: metric name, source, unit, country/database, time period, collection date and missing-value convention. Inclusion rules for any requested row count or sample size: [fill; never equate raw count with acceptance]. 5. PROPOSAL RESPONSE REQUEST Ask each bidder to state: pair-by-pair scope, research method, named roles and language qualifications, review stages, examples of evidence they can share, timeline, assumptions, exclusions, and correction process. Give each bidder the same inputs and ask them to identify any missing buyer information. 6. PREAGREED ACCEPTANCE RULE Buyer owner and language reviewer: [names / roles] Sample selection: [number or proportion, mixed approved / held / rejected, all markets and high-impact ambiguity] Pass condition: [complete scoped files, traceable settings and reasons, reviewed sample and usable page actions] Hold condition: [missing evidence with an identified next check] Return-for-rework condition: [wrong market/offer, unsupported metric, failed language meaning, unexplained page decision] Exception path and versioning: [fill] Decision date and sign-off record: [fill] This worksheet is a blank planning aid. Its example pair ID is a placeholder, not evidence from a real market. Adapt it to the actual offer, procurement agreement and reviewer capacity before sending.