Introduction

This article is documentation-based research, not a live API test. It is written for one specific reader task: setting up a Surfer Content Editor that writes in one language while targeting a country whose official language is different, using the documented country-plus-suffix location format. This article may contain affiliate links.

Surfer’s help center states that its core tools support all languages, and that its analysis depends on your keyword and target location reflecting the language and region you are aiming for (https://docs.surferseo.com/en/articles/8052688-surfer-language-and-location-support). The same page gives the concrete mechanic for the mismatch case: if you want to write in Spanish and target the United States, you use a Spanish keyword when creating your query and select “United States – ES” as your targeted location. The trailing “-ES”, “-EN”, “-FR” and similar suffixes are language indicators that let you target different language versions of a location-specific SERP.

The Content Editor overview describes the setup flow itself: navigate to Content Editor, select New Content, enter the keyword, then choose a location and a corresponding language, a crawler type, and optionally a folder (https://docs.surferseo.com/en/articles/5700347-content-editor-overview). The overview also notes that each successfully created Content Editor counts as a single usage against your limit depending on your subscription, so a misconfigured editor is not free to discard. That is the practical reason this guide treats the language decision and the location-suffix selection as one joint step rather than two independent dropdowns.

For related background on the broader tool, see /surfer-seo-review/.

Documented Workflow

The vendor documentation supports a short, ordered sequence. Our suggestions about how to prepare for it are separated below, because the contract and the working method are not the same thing.

Documented mechanics, per the two help center pages cited above:

Content Editor is created around a main keyword, and the wizard asks you to enter the keywords you want to rank for.
The wizard then asks you to select a location and a corresponding language.
In the location selector, a country name can carry a language indicator suffix such as -ES, -EN, or -FR.
That suffix determines which language version of the location’s SERP is analyzed.
The keyword you enter should be in the language you are writing in, not necessarily the official language of the country you select.

Our suggested preparation, which is editorial process rather than vendor contract:

Write down the writing language before you open the wizard. This is the language your draft will be in.
Write down the target country separately. This is the market whose SERP you want to be compared against.
If the two do not match, plan to use the country-plus-suffix form rather than the bare country name.
Draft your main keyword in the writing language, not in the country’s official language.
Only after those three notes exist should you open the Content Editor wizard.

That ordering matters because the wizard presents keyword entry and location selection in sequence. If you decide the language at the location dropdown, you are already past the keyword field and may have entered a keyword in the wrong language.

Practical Walkthrough

This section walks through the setup as a sequence of decisions. It is a hypothetical illustration of the documented format, not a report of a test performed against a live account.

Hypothetically, an editor is preparing content for a United States audience but the article will be written in Spanish. The editor’s notes look like this before opening Surfer:

Writing language: Spanish.
Target country: United States.
Main keyword: a Spanish-language phrase relevant to the topic.

With those notes in hand, the editor opens the Content Editor section, selects New Content, and enters the Spanish keyword. Because the keyword field and the location field are separate, the editor does not need to translate the keyword into English to match the country. The documentation’s own example follows the same logic: a Spanish keyword paired with the United States – ES location.

At the location step, the editor looks for the country name followed by the language indicator that matches the writing language. United States alone would point the analysis at the default language version of that country’s SERP. United States – ES points it at the Spanish-language version. The suffix is the part that keeps keyword language and location aligned.

Two small decisions are worth recording at this point, because they are easy to lose later:

Crawler type: desktop or mobile. The overview lists this as part of creation, and it is a separate choice from language and location.
Folder: optional. The overview notes folders can group editors by topic, client, or stage of work.

After creation, the overview says a deep analysis runs and may take a couple of minutes, and that the editor opens immediately while guidelines populate in the background. That means the absence of guidelines for a short period is expected behavior, not a signal that the language or location choice failed.

A reusable output from this walkthrough is a short setup note, kept alongside the draft or in the folder description:

Writing language: Spanish
Main keyword entered: (the Spanish keyword)
Location selected: United States – ES
Crawler type: (desktop or mobile)
Created: (date)

That note is the deliverable. It answers the question “why is this editor pointed at United States – ES?” months later, when the original reasoning is no longer obvious.

Completion Checks

These checks are observable from the created editor and the setup note. They do not require running a test or measuring rankings.

The created Content Editor shows the chosen country together with its language suffix, not the bare country name.
The keyword shown for the editor is in the writing language you chose, not the country’s official language.
The setup note records writing language, keyword, and country-plus-suffix location as a single matched set.
The crawler type in the editor matches the one in your note.
If you used a folder, the editor appears in the folder you intended.
If guidelines have not appeared yet, you have waited past the couple-of-minutes deep analysis window the overview describes before treating it as a problem.

A failed check is easy to describe: if the editor shows the country without the suffix, the location decision was not applied and the editor is analyzing a different language version of the SERP than the one you intended. The fix is a new editor with the corrected location, which consumes another usage against your limit.

Limits

The following limits come from the documentation or from the boundaries of this article. They are stated so you can decide whether the documented format is enough for your case.

The language and location page does not state how many language variants exist per country.
It does not describe what happens if no matching suffix is offered for your country.
It does describe a support path: you can ask the team to add a language variant to an existing location, and newly added locations will not appear in Keyword Research and Topic Research because those tools are database-dependent.
Content Audit and Topical Map locations are based on your site’s traffic from connected Google Search Console, so a location you want may not appear if the page is not getting enough traffic there.
The Surfer app interface language is a separate setting from content language and location; the interface is currently available in English, Polish, and French.
AI article generation supports a specific list of languages, and RTL languages and Maltese are not available with AI generation. AI-generated outlines in the Content Editor work in all languages, and the AI Assistant works for all languages and locations, while the Humanizer fully supports English only.
Optimization scores and AI visibility reports are vendor signals. They are not Google ranking factors and they are not indexing guarantees.
This article is documentation-based research, not a live API test. No editor was created, no SERP was analyzed, and no ranking outcome was measured for this guide.
The absence of a detection signal in any tool is not proof of human authorship, and this guide makes no such claim.

Final Verdict

The documented mechanic is small but decisive: when your writing language differs from your target country’s official language, enter the keyword in your writing language and select the country name with the matching language indicator. The documentation gives the Spanish-keyword and United States – ES pairing as the worked example, and it explains the suffix as the part that selects a language version of a location-specific SERP.

What the documentation does not do is tell you whether your particular country and language combination has a suffix available. That is the main open question you should resolve before committing an editor, because each created editor counts against your subscription limit. If your combination is not listed, the documented path is to contact support and request the language variant rather than guessing at a suffix.

For a reader whose writing language and target country match, the bare country name is the simpler choice and this guide’s suffix step does not apply. The suffix format is for the mismatch case, and it should be recorded in a setup note so the reasoning survives past the day the editor is created.

Official Sources

Surfer Language & Location Support: https://docs.surferseo.com/en/articles/8052688-surfer-language-and-location-support
Content Editor Overview: https://docs.surferseo.com/en/articles/5700347-content-editor-overview