Paid media / Practical guide

Google Ads language targeting: a multilingual checklist

Prepare for Google Ads language changes with clear English and Afrikaans ad journeys, matching landing pages and a practical account checklist.

Two differently coloured conversation paths connect ad panels to matching website panels. Conceptual editorial illustration.
Two differently coloured conversation paths connect ad panels to matching website panels. Conceptual editorial illustration.

Google plans to remove campaign-level language targeting from Search and AI Max for Search in late September 2026. For multilingual businesses, the practical response is to make the language of each ad, landing page and customer handover clear. Do not assume a campaign-language selection will remain a hard delivery filter.

For South African businesses working in English, Afrikaans or other languages, this is about the complete customer journey. Reaching someone in a language your sales team cannot support can create an enquiry without creating a useful opportunity.

Reviewed 20 September 2026. The change is forthcoming in Google's published timetable, not treated here as a completed global rollout. The underlying announcement was published on 13 August.

What is changing, and what is not?

Google's official developer announcement separates Search from other Performance Max inventory:

Campaign or inventory Documented change
Search and AI Max for Search Campaign-level language targeting is removed; matching uses ad language and other relevant signals.
Performance Max on Google Search The campaign-level language setting is no longer used for that inventory.
Performance Max on channels such as YouTube, Display, Discover and Gmail The selected campaign-level languages continue to guide delivery.

Google advises advertisers to structure ads and landing pages clearly in the intended languages. It also identifies user language preferences as a matching signal. Where multiple eligible campaigns exist, AI-based ad-group prioritisation selects the most relevant ad language.

That does not mean location targeting disappears, every user receives the same language or every Performance Max surface behaves identically. Keep those separate settings and behaviours separate in your account notes.

Start with the languages you can genuinely support

List the language options your business can support through the whole enquiry journey. Include the website, telephone response, appointment reminders, quotations and any ongoing customer support. A translated headline alone is not a complete service experience.

For each option, record who maintains the copy and who handles the enquiry. If an Afrikaans ad reaches an Afrikaans-speaking prospect but the only available follow-up is an automated English sequence, decide whether that experience is acceptable before advertising it.

Do not infer a person's preferred language from their name, suburb or background. Use the language they choose or communicate in, and collect only information that is genuinely needed for the interaction.

Build a simple ad-to-page language map

Use one row per advertised journey:

  • Campaign and ad-group identifiers.
  • Intended ad language and the actual active assets.
  • Landing-page URL and the language of its substantive content.
  • Primary action: call, enquiry, booking or purchase.
  • Language of the acknowledgement and follow-up.
  • Person responsible for reviewing the journey.

This map exposes mixed assets, inherited English headlines in another-language ad group and destinations that redirect to an unrelated language. Check mobile navigation and form validation messages as well as the hero paragraph.

For example, a service business might advertise the same repair in English and Afrikaans. The two paths may share an internal pipeline while presenting different copy and acknowledgements. That is an illustrative design choice, not a claim that separate pipelines or duplicate websites are required.

If website changes are needed, scope them around usable content and handover rather than creating thin translated pages solely for keywords. Our website-design approach starts with those requirements.

Should you split every language into its own campaign?

Not automatically. Separate campaigns can be useful where budgets, offers, reporting ownership or service capacity differ. They can also fragment a small account and make administration harder.

First ask what decision the separation would support. If one language needs a different budget or a different offer, the distinction may be operationally valuable. If the only reason is to recreate a targeting filter Google is removing, the account structure will not guarantee the old behaviour.

Keep ad-group messaging coherent and match each destination to the promise made in the ad. Where automated text or destination features are enabled, inspect what they can use and what they produce. Avoid combining a language restructuring with unrelated bidding changes unless necessary.

How should you evaluate performance after the change?

Record when the account's settings or delivery behaviour changes, then compare equivalent periods. Segment the evidence that the account actually exposes, and combine it with appropriately collected enquiry feedback. Do not claim to know every visitor's language from a campaign label.

Review whether callers understood the offer, whether the team could respond and whether enquiries progressed. Distinguish a language mismatch from a pricing objection, an unsupported service request or a slow response. Those problems need different remedies.

A lower cost per form submission does not establish that the language journey improved. Use your qualification criteria and allow for the sales cycle. The enquiry-measurement guide provides a starting point for that review.

What should integration owners check?

Google says existing Search language criteria can still be returned by the API even though they will no longer control targeting. Reading an old criterion is therefore not proof that it remains effective.

The announcement says attempts to add or update Search campaign language criteria will return ContextError.OPERATION_NOT_PERMITTED_FOR_CONTEXT. Performance Max language criteria remain relevant to its other channels, so they must not be removed indiscriminately from every campaign-creation workflow.

Ask your integration owner to identify where language criteria are created, distinguish campaign types and test the intended behaviour safely. They should check current rollout documentation before deploying a change. No account-wide deletion is required simply for tidiness.

The useful next step

Audit one important language journey end to end, then expand the method to the rest of the account. Keep the change small enough to understand and assign an owner to each mismatch.

Our Google Ads service can help frame the account review; Google Ads training is relevant when your own team will maintain the campaigns. Use the existing Discuss project form with the languages, campaign types and follow-up constraints that matter to your business.

Sources & review boundaries

Source links checked 20 September 2026. Platform settings and policies can change. Verify the current documentation before implementation.

Examples and checklists are practical guidance, not guarantees, legal advice or a replacement for account-specific testing. Linked D4J case studies carry their own evidence cut-offs and limitations.

Worth passing on?

Send the guide to the person making the decision.

Email

A useful conversation

Have a question or a correction?

We keep discussion focused and reviewed. Send us the article link and what you would like to clarify.

Talk to Digital 4 Jesus