Search-intent phrase candidates: multilingual SEO / international SEO / website translation SEO / multilingual website traffic
The 5-second answer
Publishing the same article in many languages does not automatically create search traffic.
That is because translating what an article means and matching how people in another market actually search are different jobs.
The real funnel is:
discovered → shown in search → clicked → read → continued to another page
If one stage is blocked, your article count can rise while traffic stays asleep.
You may have built a 12-language publishing factory without building 12 market entrances.
The conveyor belt is humming. The parking lot is empty. Congratulations: you have created an extremely efficient warehouse.
1. Split “no traffic” into five different problems
Do not label every traffic problem “bad SEO.”
Separate at least five stages:
- Discovery: does Google know the URL?
- Impressions: does it appear in search?
- Selection: do searchers click it?
- Satisfaction: does the page answer the question?
- Navigation: does the reader continue to useful related content?
If a page already receives impressions but almost no clicks, fixing crawlability alone is unlikely to solve the problem. The result is already being shown.
Search Console exposes clicks, impressions, CTR, average position, and dimensions such as query, page, country, and device.
The distinction matters:
not shown is different from shown but ignored.
One shop is missing from the map. The other has 100 people walking past the door without entering.
2. A correct translation can still be a weak search result
Literal translation preserves meaning. Search localization preserves intent.
Suppose the source title means “How to make work easier with ChatGPT.”
A grammatically perfect translation may still be weaker than the wording people naturally type into search.
The better pipeline is:
source intent → native search phrasing → content that naturally answers that phrasing
This is not keyword stuffing.
It means adapting the title, H1, meta description, introduction, headings, and natural terminology so they sound like the market’s query language.
Google’s Search Console guidance explicitly recommends examining low-CTR pages and considering changes to titles, descriptions, or content so they better match the queries that trigger the page.
Search Console is therefore not just a report card. It can become a purchase order from the market written in actual queries.
3. Twelve languages are not necessarily twelve markets
A language is not the same thing as a market.
Portuguese makes the problem obvious:
- pt-BR targets Brazilian Portuguese
- pt-PT targets European Portuguese
They share a language, but vocabulary, phrasing, and search habits can differ.
Spanish is also broader than Spain. The same es content may reach users in Spain, Latin America, and Spanish-speaking communities elsewhere, yet the best phrasing is not always identical.
French has multiple regional markets as well.
Indonesian search behavior may favor natural question structures such as “cara,” “kenapa,” or “apa” in contexts where a formal literal translation sounds perfectly correct but less search-native.
The useful model is:
language × region × intent
Google recommends explicitly identifying localized or regional versions with hreflang when relevant.
hreflang is not a ranking spell. It is routing information.
4. Research search phrasing before translation
A stronger multilingual workflow is:
- Freeze the source article’s core meaning.
- Research natural query phrasing in each target language.
- Check SERPs, suggestions, related searches, and existing first-party data.
- Write a market-specific title and H1.
- Align the introduction and headings with the same intent.
- Localize the body without changing the core meaning.
- After publication, validate the hypothesis with real Search Console queries.
Pre-publication keywords are hypotheses.
Do not invent search volumes. If you did not measure a keyword volume, do not claim one.
Before publishing, find natural intent-aligned phrasing.
After publishing, real query data wins.
5. Prioritize pages with impressions but weak CTR
At scale, not every page deserves equal attention.
One of the most useful groups is:
pages that already receive impressions but underperform on clicks
This is not a desert.
People are already outside the shop.
Check:
- Is the title too abstract?
- Does it use the wording the market uses?
- Is the user’s question visible early in the title?
- Does the description explain what the reader will get?
- Does the introduction answer quickly?
- Is the real issue simply low ranking rather than CTR?
For pages with almost no impressions, investigate discovery, indexing, internal links, demand, competition, regional targeting, and topic choice first.
Do not hit every SEO problem with the same wrench.
6. International traffic also dies when every visit ends at one page
One search visitor can create one pageview and leave.
Or that visitor can naturally continue to a second and third useful article.
That makes post-click localization as important as search-entry localization.
Related content should be:
- available in the same language;
- closely related to the current topic;
- relevant in that market;
- a natural answer to the reader’s next question.
A beautiful multilingual homepage cannot compensate for an article page that ends in a cliff.
7. Rename the translation step
If your pipeline calls the stage “Translation,” the system will optimize for linguistic transfer.
A better name is:
Search-intent localization
For each locale, independently generate and QA:
- SEO title
- H1
- meta description
- primary search phrase
- supporting phrases
- opening answer
- section headings
- regional examples
- CTA
- related-content candidates
Then feed back:
query × page × country × impressions × clicks × CTR × position
Now localization becomes a learning loop rather than a one-time export.
8. Multilingual SEO mistakes to avoid
Keyword stuffing
Using the searcher’s language does not mean repeating the same phrase until the article sounds like a malfunctioning robot.
Copying the exact same title pattern into every language
Keep the meaning consistent, not the syntax.
Measuring success by article count
More inventory does not fix a weak storefront.
Overreacting to tiny samples
Changing titles every day because of a handful of impressions creates noise, not learning.
Treating pt-BR as Portugal
Brazilian Portuguese and European Portuguese can require different market design.
Writing for search engines instead of readers
Google continues to emphasize helpful, reliable, people-first content. Search phrasing is the entrance; solving the reader’s problem is the job.
9. The multilingual improvement loop
Use one loop:
DISCOVER → LOCALIZE → PUBLISH → OBSERVE → DIAGNOSE → REVISE → REMEASURE
Check, in order:
- indexed?
- impressions?
- which queries?
- which countries?
- position?
- CTR?
- engagement after landing?
- related-page navigation?
- improvement after revision?
Prioritize:
- broken pages;
- pages already visible but not winning clicks;
- pages beginning to grow;
- pages with too little data.
You do not need to pet every article every day.
Water the shoots that are actually emerging.
Apparently SEO becomes gardening at scale.
Summary: translation carries meaning; localization builds the entrance
When multilingual traffic is weak, do not blame translation quality alone.
Ask whether the page is discovered, shown, phrased in the market’s search language, attractive enough to click, satisfying after the click, and connected to useful next content.
The upgrade is from:
translate into 12 languages
to:
be searchable, selectable, and useful in 12 markets.
The next evolution of a content factory is not merely faster translation.
It is feeding the market’s own language back into the factory.
References (4)
- Google Search Central, Localized Versions: https://developers.google.com/search/docs/specialty/international/localized-versions
- Google Search Console Help, Performance Report: https://support.google.com/webmasters/answer/7576553
- Google Search Console Help, Common Tasks and Use Cases: https://support.google.com/webmasters/answer/17010961
- Google Search Central, Creating Helpful, Reliable, People-First Content: https://developers.google.com/search/docs/fundamentals/creating-helpful-content
