Content Localization Keyword Audit: What to Translate, Rewrite, Merge, or Hold

A content localization keyword audit should happen before pages enter translation. Review each source URL against one target country and language, then assign a decision: translate, update, rewrite, merge, or hold. Translation proceeds only when the target market supports the same user task, the local keyword evidence is sufficient, the language is approved, and the business can support the page's promise.

This guide is for a content strategist working through an existing source-language inventory. It does not decide which country the business should enter, approve legal claims, or certify target-language copy. Its job is to prevent a translation queue from becoming an accidental page-creation plan.

1. Set the audit unit: one source page, one target market

Do not audit a page against a language in the abstract. Audit it against a country-language pair. Google distinguishes multilingual and multi-regional sites: a site may serve several languages, several countries, or both. A source page that deserves a French version for France is not automatically approved for French-speaking Canada.

• Record the source URL and the user task it serves, such as compare accounting software, buy replacement filters, or understand a filing requirement.
• Name one target country and language. Create another row when the same source page is being considered for another country.
• Record the existing target URL when one already exists. An empty field means the audit may propose a new page, not that a new page is automatically justified.
• Assign an owner and evidence date so the decision can be reviewed when the market, offer, or result page changes.

2. Describe the source page by its task, not its title

A source title and keyword can hide the page's real job. Two pages may both mention the same product category while one helps readers compare options and the other enables a purchase. Write a short source-page task before collecting target-market keywords. This becomes the comparison point for the local SERP.

Keep the description concrete: who is searching, what they need to decide or do, and which page type delivers the answer. If the team cannot agree on the source task, the row is not ready for localization. Fix the source strategy or mark it Hold rather than asking a translator to resolve the ambiguity.

3. Build target-market keyword evidence

Treat the source keyword as an input, not a translation instruction. Generate several local candidates, record the exact target country, and keep the provider and research date beside any volume, difficulty, CPC, or intent estimate. A translated phrase remains a hypothesis until country evidence, a result-page check, and the required language review support it.

Global Keyword Finder can assist with this discovery step. The current product accepts a source-language seed and selected target country, then returns up to 30 relevance-ranked candidates with country-scoped estimated volume, keyword difficulty, CPC, intent, and CSV export. Those fields help create a shortlist; they do not approve customer-facing wording or decide which URL should own the task.

• Verified: dated country-scoped metrics, a documented target-country SERP review, and an accountable language decision support the candidate.
• Directional: useful evidence exists, but the SERP location method, sample, metric coverage, or language review is incomplete.
• Missing: no defensible local query or result-page evidence exists. The workbook returns Hold.

Use the country-level volume guide when metrics from several markets have been mixed together. Use the SERP validation procedure when the local phrase exists but its task or page type is unclear.

4. Compare the target SERP task with the source page

The key audit question is not whether the local phrase translates back to the source keyword. It is whether the target-country results reward the same task and page type as the source page. Record the dominant type across a documented sample: product, category, service, comparison, guide, support, tool, mixed, or unknown.

• Same: the target results and source page serve substantially the same user task and compatible page type.
• Different: the local query is relevant, but the results require a different task or page type. The source may inform the new brief, but it should not control it.
• Duplicate: an existing target page already owns the task. Creating another localized URL would split ownership without adding a distinct user job.
• Unknown: the sample, location method, or evidence is insufficient. Hold the row instead of guessing.

Record how the SERP was observed and its limitations. A browser's language setting or incognito mode alone does not prove a target-country result set. If the method cannot reliably represent the target location, label the observation directional and keep the uncertainty visible.

5. Check the target inventory before proposing a new URL

Search the current target-language section for pages that already serve the task. Check live URLs, canonicals, redirects, and retired pages. The absence of a translated source counterpart does not prove a content gap, and the presence of a local page does not prove it is the right owner.

Google recommends separate URLs for language versions and uses visible page content to determine language. That technical separation makes localized pages discoverable, but it does not justify creating every source page in every locale. Create or retain a target URL because it has a supported market task and accountable owner.

Use hreflang only after page purpose is settled. Google's localized-version documentation explains how annotations connect language or regional variations. The editorial inference is important: annotations communicate a relationship between pages; they do not validate the keyword, task, offer, or language on those pages.

6. Apply the five decisions consistently

• Translate: the target market supports the same task, no target owner exists, and search, language, and business evidence are complete. Localize around the approved market language rather than translating sentences mechanically.
• Update: the same task is valid and an existing target page already owns it. Improve that page instead of creating another URL.
• Rewrite: the target keyword is relevant, but the SERP requires a different page task or format. Build a target-market brief; preserve source material only where it helps the new task.
• Merge: another target page already owns the same task. Consolidate the plan around one owner and handle redirects and internal links through a separately reviewed migration plan.
• Hold: evidence, task fit, language approval, business clearance, or ownership is unresolved. State the missing prerequisite and assign a next action.

7. Separate keyword approval from language and business approval

A plausible keyword does not authorize customer-facing copy. Record language review separately and require an accountable reviewer for the final phrase, title, metadata, calls to action, and market-specific claims. Not required should be rare and documented, such as a row that contains no target-language recommendation and will not be published.

Business clearance is another independent gate. The target page must describe an offer the company can fulfil and support. Pricing, delivery, returns, availability, regulated claims, and policy obligations belong to accountable business, legal, or compliance owners. This audit records their status; it does not replace their judgment or provide legal advice.

8. Turn approved rows into production briefs

Send only approved Translate, Update, or Rewrite rows into production. Each handoff should include the source task, target country and language, approved primary candidate, supporting variants, intent, dominant SERP page type, target owner URL, evidence date, reviewer, source links, and any claim or offer constraints.

Then use the SEO localization workflow to sequence metadata, URL, brief, translation, review, implementation, and launch. The audit chooses what should enter that workflow; the workflow controls how an approved row becomes a page.

9. Feed launch evidence back into the audit

After publication, compare the intended owner and keyword task with observed performance. Google Search Console's Performance documentation explains how data is grouped by query, page, and country. It also notes that anonymized queries are omitted and that query rows can be truncated, so use the report as evidence with limits rather than a complete record of all searches.

• Filter to the target country and relevant page before reviewing queries.
• Check whether unexpected queries reveal a different task or whether several pages appear for the same query family.
• Investigate page quality, indexing, canonicals, and internal links before blaming keyword selection alone.
• Update the decision and evidence date when the page task, target owner, offer, or result set materially changes.

Final audit rule

Translate only when the target market supports the same task and every approval gate is complete. Update when the correct local owner already exists. Rewrite when local intent changes the page job. Merge when ownership is duplicated. Hold whenever the evidence or accountable review is incomplete. The result is a smaller localization queue, but every remaining page has a reason to exist.