01Fifteen Languages From One Source
On 18 September 2026 Sentiention’s site went from English alone to English and fourteen translations between 08:36 and 16:49, Poland time. This paper follows what that took, the voice the checks missed, and what Google did with the new pages.
- The whole build took one working day, from a question in the morning to fourteen new languages that were live in the afternoon, each of them with 11 pages, 5 cases, a page for missing addresses and 194 interface lines, which made 238 translated addresses in all.
- Every translation is an ordinary WordPress page, which is rebuilt from 552 keyed segments of the English pages, and all of the theme’s work on languages sits in one file of 382 lines.
- Three scripts passed the first translations whole, and a minute after the last of them a native reader found that the Polish home page sounded machine-made, so the voice was rewritten section by section in all fourteen languages within about an hour and a half.
- One layout carries texts that run from 38 % to 116 % of the English length, with Chinese the shortest and French the longest, and Arabic runs right to left inside it on rules that were measured on 11 of its pages.
- Google showed 118 of the root’s addresses in the 17 days after the launch, against 8 in the five days before it, and 910 of the 1,382 impressions that they drew went to the fourteen new languages, all of which were shown.
- The root’s daily reach fell from about 132 impressions to 81, while its home pages gained with the translations, and almost all of that fall sits in the case pages, which went from about 75 a day to 24.
- Every search that Google names for what the firm does reached a translated page; there were 12 such impressions in 17 days, while 90 of the 109 named ones came on the names of the firm’s clients.
Our Research Question
On the morning of 18 September Sentiention asked us whether its site could carry ten to fifteen languages “without overcomplications”, and we built them that same day. We have kept the record of it ever since, and it holds each script and each file the translators wrote, each chat of the day, and each reading of Search Console that has followed it.
Sentiention’s site went from 1 language to 15 in 8 hours and 13 minutes, from a single source.
So this paper asks how one firm’s site can carry fifteen languages from a single source without any of them turning into a second site to run, and what Google did with those languages in their first weeks. A firm that sells in several markets meets that question on the day it decides to be read in its buyers’ languages, and it usually meets it with very little to go on. Each figure below comes from Sentiention’s records, with its window and its source.
The last part, Method and Sources, says how each one was read and checked, so that another firm could repeat the work on its own site.
The Firm and Its Site
Sentiention runs sourcing, market entry and venture building between Europe and China. A buyer meets it at sentiention.com before sending a brief, and on 18 September there were 11 pages in English at that address, six that carry the voice of the firm and five that are legal. Beside them there were 5 cases and the page of a confidentiality agreement, which stays in English because it is the one binding text.
Underneath is a standalone WordPress block theme. It has no translation plugin, and its pages use the fonts that each operating system already carries.
Google’s record of the site begins on 13 September 2026, the first day its domain property in Search Console holds, five days before the launch. That is why each comparison here is made per day.

How Languages Usually Arrive
Three arrangements are common, and each of them makes a translation into a second system to keep. With a plugin, the translations lie over the pages in tables of their own, and somebody has to keep them in step with every edit. If a firm opens a site for each country, it doubles the work with every market it adds, and each new site starts in search from nothing.
A translate button hands the job to the visitor’s browser, and it hands the firm’s words to a machine that the firm never sees. In all three, by our reading, a translation can drift a little further from its original with each change, unless something in the arrangement records which version of the English it followed.
A translation that cannot name the version of its source has already started to drift.
02One Source, Fourteen Followers
English stays at the root of sentiention.com, and every other language is a tree of ordinary WordPress pages under a two-letter home of its own.
Addresses Under a Prefix
At /de/ the German home is a page, and the German services page is its child at /de/services/, so the English path carries on after the two letters. Each page keeps its English name, which means that whatever the site did by name went on working in all fifteen: its forms, its templates, its sitemap and its search tags.
Cases come to their addresses by a second route. A case in German is a post named after its English original with the language added, and it is tagged in a private list of languages and served at /de/cases/ under its English name. That takes two rewrite rules, because WordPress will not put a post type under a prefix by itself.
It is the first part of the address that sets the language of the interface as well. WordPress reads it through a filter on its locale, so no language pack is ever downloaded, and the lines of the theme itself come from one plain file a language, built from a numbered catalogue of 197 entries. In each language 194 of them are translated, and the names of the firm’s three services stay in English on purpose.
Norwegian is served as Bokmål, Portuguese as the Portuguese of Portugal, and Chinese is declared to search engines as zh-Hans, the simplified script.
Sixteen Links in Every Head
Search engines learn which versions belong together from tags in the code of each version, and all fifteen versions of a sentiention.com page carry the same set. It holds sixteen links, one for each of the fifteen languages, itself included, and one called x-default, which points at the original for a reader whose language is not on the list.
The build’s search check fails any page whose set differs from its siblings’, and any page whose alternates do not answer. And if a language has not got the page yet, it is simply left out of the set; the switcher then leaves it out too, and its links fall back to English.

Four Hundred Lines
Six new parts went into the theme, and we wrote all of them.
- A registry of the languages, which gives each one its prefix, its locale, its search code, its name in its own language and a one-line offer written in it.
- The language of a request, which is read from the first part of its address; the interface follows it, from the plain file of that language.
- One helper for every internal link, which falls back to the English original wherever a translation does not exist yet, so that a half-translated language never leads a reader into an error.
- The alternates search engines read, which tell them which pages are the same page in another language, and which one to show when none of them fits.
- A language switcher that offers the same page in the other languages, only where it exists, by each one’s two letters, with no flags and no redirect.
- The cases, which WordPress will not put under a prefix by itself; two small rules let a reader reach them at /de/cases/ and the rest.
All six of them sit in one file, and it runs to 382 lines in the theme as it stands on 7 October 2026, after a second round of work on its menu on 22 and 23 September. On the day itself the header and the footer were also moved out of the template parts of the theme and into small PHP patterns, because any text that sits inside a block template part cannot pass through WordPress’s translation functions.
With that one file a reader meets a whole site in each language, and the firm looks after all fifteen as one installation.
Edits Made Once
Since every internal link goes through that one helper, a page added in English can be reached from every translation straight away, through the original, until its own translation exists. Then the links move to it, and nobody touches a menu by hand. Each translation stores which English page it came from and a fingerprint of that page as it stood when the translation was built.
When the English changes, the fingerprint no longer matches, so the translations that followed the old version are the ones to rewrite, whole and a section at a time. A language can also be staged by keeping its pages private until all of them are written, and every edit in any language keeps its history, as it would on any other page.
That way of working was put to use again on 6 October, when the firm’s English cases were rebuilt as seven longer case studies. Their translations come by the same road: new segments for the cases alone, a new brief for the writers, and a build that touches the case posts and leaves every page alone. The spoken labels of the drawings got keys of their own, l001 and onward, while the older numbering stayed as it was, so the September files still line up; the September translations of the cases are kept beside them, whole.
Before any change goes to the live site, a script compares the two sides. It reads the theme by each file’s fingerprint, each page, case and menu by what it says, and each image by its name and its size, and it never reads the intakes or the signed agreements. On 2 October 2026 it found the local copy and the live site identical, with 102 of 102 theme files, 244 of 244 pages, cases, styles and menus, and 657 of 657 images.
| A translation plugin | A site per country | One source | |
|---|---|---|---|
| Where the languages live | over the pages, in its own tables | in separate installations | in ordinary pages under each language’s home |
| A change to the English | must be found and carried into each overlay | must be made again on every site | is made once, each language follows it, and links fall back to English until it does |
| What search engines read | what the plugin chooses to print | separate sites, each starting from nothing | one site, its languages declared to each other |
| What the firm maintains | the site and the plugin | as many sites as markets | one site |
03Eight Hours on 18 September
A question came at 08:36 Poland time, the work ran on a copy of the site so that its visitors saw none of it, and the fourteen translations went live together in the afternoon.
Why the Answer Was Yes
Sentiention’s site was already using the fonts that each operating system carries, so Chinese, Japanese, Hindi and Arabic would all show on it without a typeface to load. No style in it set text in capitals, and its search tags were already taking their language from WordPress.
Our first answer, at about nine, put the mechanism and two languages, German and Simplified Chinese, at about a week of work. Arabic was left for a later wave, as a separate piece of styling. Eight hours after the question was asked, all fourteen of them were live, and Arabic was among them.
There was very little to undo.
So the decisions of the firm came quickly, nearly all of them in the first three hours, and each one of them took a question off the table for good.
The intake and its agreement would stay in English while the fields of the form were translated. In the switcher there would be two letters and no flags, and Arabic would run right to left inside the same layout. Every page would be translated, the legal pages included.
It was the firm that named the languages, and there were fourteen of them: German, Simplified Chinese, French, Italian, Spanish, Polish, Swedish, Danish, Norwegian, Finnish, Arabic, Hindi, Japanese and Portuguese.
Each of them was to have all that the English site has, and by the end of the day each one did.
Text in Keyed Segments
A WordPress page is a tree of blocks, and the build took the words out of that tree and left the markup where it stood. Its first script treats all that lies between two block-level tags as one unit, and it keeps the inline tags of a link or an emphasis inside the sentence they belong to. Each unit gets a key, t001 and onward for text and a001 for the alt text of an image.
The units of one page go into a plain text file, with a key on its own line and then its words. Before a single word was translated, the script rebuilt every English page from its own file and compared the result with the original, byte for byte, and each page came back identical.
There are 373 keys on the six pages that carry its voice and 179 on the five legal pages, so a translator in each language wrote 552 units for the pages alone. Inline tags are copied character for character, because the checks compare them, and a key that is left out takes the source text; and ten of the languages left out 33 to 42 keys of the six main pages on purpose, each of them a sentence that had already been translated elsewhere, and the build fills those in.
Then the build sets each translation into the blocks of the English page itself and saves it as an ordinary page under its language’s home. All that is not text comes from the original page, such as the template, the featured image, the order and a case’s facts. It has to run as an administrator, because WordPress strips the form inputs from a page that anyone else saves.

Translators and a Limit
For every language, the brief asked for the meaning, the rhythm and the register of the English, and never its word order. It wanted the formal address that a senior person in the trade would use with a client, which meant Sie, vous, Lei and usted, impersonal turns in Polish, and です and ます in Japanese.
One word for the firm was fixed in each language, die Firma in German, le cabinet in French, firma in Polish and 当社 in Japanese, and where that word fitted, the cases became mandates, as Mandate in German and Mandats in French. The brief also listed all that is never translated, which was Sentiention’s own name, its three services, the three words that its name is built from, and the names of people, platforms and companies. Trade terms were to keep the form the trade uses, as with RFQ, landed cost and HS code, and each number was to keep its value in the local format.
The legal pages had their own brief. They were to be faithful and plain, with the legal terms of each language, such as RGPD, DSGVO and RODO for the data law, and every statute reference, address and tax number exactly as it stands. Impressum, the German name for the page that names the owner of a site, stayed Impressum in every language, with a plain gloss under it wherever the page had room.
Small marks travelled with rules of their own. The firm’s separator, a tilde with a space on each side, stayed in every language and was never turned into a middle dot. French got its no-break space before colons and question marks from the build itself, labels took each language’s own habit with capitals, and where a script is not Latin, the three words that the firm’s name is built from are glossed once in running prose.
All of it was written by AI. Our main session wrote German, French, Italian, Spanish and Chinese and the home pages of Japanese, Hindi and Arabic, and a run of five translation agents took the rest from a written brief. When that run came back at 12:34, one of its five agents had finished and reported; the other four had stopped at the usage limit of the account, partway through their languages.
A second run of five, which was to write the legal pages that were still missing, came back an hour later without a single page. So the main session wrote all of those pages itself.
A plan that rests on parallel writers needs a second way to finish when they stop.
Hour by Hour
By 14:21 the copy was complete. In each language it had 11 pages, 5 cases, a page for missing addresses and 194 interface lines, and there were 238 translated addresses that answered and 255 pages that passed the search check. The ninety minutes that came after it went to the voice.
We had proposed a slower launch, with German, Polish and Chinese going first and the rest kept private for a week or two, until someone who reads each language had read it. Either way would have worked, because a language that is held private appears in no switcher and in no alternate link.
Shortly after four the firm agreed to publish all fourteen at once.
The live site holds real enquiries and signed agreements, so its database was never overwritten. We backed up its database and theme on the host first. Then we ran the same build on the live server and let it create the pages there, and nothing on the live side was taken away.
A dry run came back clean, and two minutes later all sixteen sources stood built on the live site in every language. There was one slip of ours. The new code hides any case without a language tag, so the first tagging step could not see the English cases either, and for about two minutes the live list of cases stood empty until we tagged them directly.
At 16:49 the fourteen languages were live, and 251 addresses answered. When the search check was run against the live domain, it passed all 255 pages. Then a last round of tests read the text back in Polish, Chinese and Arabic, to make sure that none of it had been garbled on the way.
The form answered in German, Polish, Japanese and Arabic, though no one ever sent it. Each address that did not exist gave a real 404 in the visitor’s own language, and the sitemap listed 165 pages and 75 cases.
That push turned up an older fault too. When the English home page had first been moved to the live host, WordPress had stripped six hidden inputs from it, and so its buttons for each stage in detail had never opened; the build put them back.

04Checks That Cannot Read
By 14:21 every translation had passed three scripts that compare it with the original, and only a minute later a native speaker of Polish found that the home page sounded machine-made.
Scripts That Compare
A reviewer with no Finnish at all can still prove a good deal about a Finnish page, and the first check was written for that reviewer. It compares every segment with its English and fails a key that is missing, empty or invented. Numbers are set side by side as sorted lists, so 763,623 and 763.623 count as one number while a changed figure fails.
An English month becomes a number too. A date may be written 2026 年 9 月 13 日.
That script also wants the same inline tags, every link untouched, every separator and shortcode kept, and the brand name never dropped. And it fails a segment that was left in English by accident. The second script called every address there was in every language, 238 of them in all.
It looked at the head of each page, at the legal note, at the sitemap and at the language of the form on the server, and it never sent the form.
A third does what a search engine does with a page. It wants one title and one main heading, a description, a canonical, social tags, structured data and alt text on every image, and for each page in all its languages it wants the same set of sixteen alternates, each one answering. At 14:21 the three of them reported no problem in any of the fourteen languages.

Caught in Polish
One minute after the checks came the note, from a native speaker who had read the home page. It said that the Polish read as an automatic translation, and that every other language probably did too, because the cadence of the English, its sentence structure and even its choice of words had come across with it.
In the Polish the firm stood as the subject of nearly every sentence, a habit of English that Polish drops after the first mention. Nouns were chained where Polish would use a verb, and English images came across word for word, so that the firm “held the European front”.
The same note had opened on Arabic. Once the direction flipped, a heading with its padding on one side only no longer lined up with the text under it, and that slip ran through the whole site.
The unit caused it. We had written each English sentence as a unit with its own key, so that an edit to one sentence could be carried into fourteen languages without touching the rest. That kept the English sentence as the frame of every translation.
When the English sentence is the unit, its structure comes through into every language.
But the scripts guarded figures, names, addresses and markup, and the voice went through all of them unread. One reader with one page found what they had all missed.
A second note, half an hour after the first, set the rule for the full pass. Each language was to be written as a site in that language would be written, so that if the order of the sentences moved, or their length, or the words themselves, they moved because the meaning travels that way there.
Section by Section
We changed the method within the hour. The Polish home page was the pilot, with 51 of its segments rewritten, and by 15:57 the method had reached all fourteen languages.
- Read the whole section in English, then put it away.
- Write the section as the firm would say it in that language, with the language’s own means: the subject dropped after its first mention where the language drops it, its own impersonal turns, and the trade’s living words beside the English abbreviation that a buyer also uses.
- Map it back to the keys afterwards, where sentences inside a key may be joined or split, and a headline written as a pair is translated as a pair, for its rhythm.
- Keep the firm’s named terms as names, so that where the firm has named its own method in three words, those three words stay as they are in display, in each language, and the word a native speaker would use may appear in running prose.
The rewrite reached the home page, the services, the method, the team, the intake page and the contact page. After that it took in the story passages of the five cases. Then came the fourteen interface lines in each language that speak for the firm, from the footer and the line that opens the list of cases to the text of the 404 page, the three doors of the form, the message after a brief is sent and the descriptions that search engines show.
We left the legal pages and the functional labels faithful on purpose, because there accuracy is the voice. One rule in the checks moved with the rewrite; a language may now name the firm where the English says “the firm”, and only a dropped brand name fails.
Headline pairs stayed pairs for their rhythm, as they do in Drei Zugänge. Dieselbe Disziplin. And it was now the trade’s living word that stood beside the English abbreviation, as with zapytania ofertowe in Polish, appels d’offres in French and 询价 in Chinese.
When the intake page’s opening invitation became Nennen Sie Ihr Ziel. in German and Wystarczy cel. in Polish, those same words were made to read the same way on the page, in the footer and in the form.

Said at the Foot
At the end of each translated page, a line says that its text was translated with AI support from the English original, which prevails, and that its abstract images are AI-generated and marked so in their metadata.
On a translated legal page a note above the footer adds that the page is a translation for orientation and that the English version prevails, with a link to it. So the binding text of each legal page always stays the English one, and the reader of any language is told so in their own. The theme prints that note itself, as one line in each language’s file, so no translator ever wrote a disclaimer of their own.
Two more pieces of the frame were settled on the day. In the footer the links to Sentiention’s satellites keep their names and are marked as English, so a reader knows what language waits behind them before the click. And the consent banner was cut to three sentences in every language, which still name the tools and say how to change a choice.

05Every Length, Both Directions
In English the six pages that speak for Sentiention run to 30,153 characters, while in Chinese they come to 11,357 and in French to 34,827, and it is one layout that holds all of them.
Lengths Against the Source
Counted from the build’s own files with the markup taken out, Chinese comes to 38 % of the original and Japanese to 52 %. Arabic comes to 89 %. The European languages run from 104 % in Swedish and Norwegian to 116 % in French, with German at 110 %.
Hindi, at 102 %, sits among the European languages.
Each script had its own rules as well. Hindi was written in Devanagari, with the English loanwords that business Hindi really uses, and Japanese was written with です and ます in running text and with short noun phrases for its labels; Arabic and Hindi both kept Western digits.
Before the launch we measured the layout in all fourteen languages at desktop and at phone width, and it measured clean. Sentiention’s names hold steady across all these lengths. Its three services, its own name and the three words of its method read the same in every script, so a buyer who moves between two languages finds the same marks in both.

The numbers
| Language | Characters | Against the English |
|---|---|---|
| Chinese | 11,357 | 38 % |
| Japanese | 14,361 | 52 % |
| Arabic | 24,768 | 89 % |
| Hindi | 28,485 | 102 % |
| Swedish | 28,801 | 104 % |
| Norwegian | 28,999 | 104 % |
| Polish | 29,227 | 106 % |
| Danish | 29,390 | 106 % |
| Finnish | 30,460 | 110 % |
| German | 33,105 | 110 % |
| Italian | 33,653 | 112 % |
| Portuguese | 31,061 | 112 % |
| Spanish | 31,663 | 114 % |
| French | 34,827 | 116 % |
| English | 30,153 | 100 % |
Arabic Without a Mirror
In this one language the lines run the other way, and the page keeps the order of columns that the other fourteen use. It was the firm that chose this. So the site stays one design in all fifteen.
Its first Arabic pages showed a fault that an English page never could. Each block of text has its own maximum width, and a column keeps its gutter on the right only; in English all of it starts on one shared left edge, and in Arabic the right edge stepped.
We set each block that is narrower than its column on the right edge, moved the gutters to the left in the footer and the service rows, and started the chips from the right, and afterwards the right edges of 11 Arabic pages measured as one line, both at desktop and at phone width. Inside Arabic sentences an arrow points left, the way the reader reads, while a run of Latin words keeps its own direction.

A Switcher Without Flags
Each page carries a small button with its language’s two letters, and it opens a grid of the fifteen codes. A code appears there only where the page exists in that language, so a reader who changes language never lands on an error.
It was the firm that asked for two letters and no flags. A second line, which the theme writes, compares the browser’s languages with those that the page exists in and offers the page in the reader’s own, in one line. It never redirects.
A choice or a dismissal is kept on that one device alone.
At first the footer carried a row of languages as well, and the firm had it removed that afternoon as redundant. But the header and the phone menu both kept theirs.

An Intake Kept in English
Before sending a brief, a visitor signs a confidentiality agreement on the site. Its fields are translated, so a German visitor reads the labels and the messages in German. All that lies behind them stays in English, from the agreement and its signed document to the mails and the brief that reaches the firm.
The German intake page says so, and tells the visitor that the reply will come in English.
It was Sentiention that decided this, in the first hour, because the people who send it briefs work in English. A test that morning pointed the same way, since any name that was typed in Chinese, Cyrillic, Vietnamese or Arabic letters came out empty in the signed document.
Every brief records the language of the page it was sent from.
Which language has sent a brief so far is a question for the intake’s own record, and this paper does not read it.
06What Google Showed the Root
On 7 October we read Search Console’s whole record of sentiention.com by day, by page, by country and by search, from its first day to the last one filled in.
Before and After 18 September
Google’s record from the days before the launch is thin, a mere five days with almost nothing on the first of them, so any comparison here has to be made per day. An earlier version of this paper set two fortnights side by side, 4 to 17 September against 19 September to 2 October, and found twice the impressions after the launch. But that first fortnight held only five days of data, and per day the root’s reach fell.
With the satellites left out and the root taken alone, Google showed 8 of its addresses in those five days and 118 of them in the 17 that followed, and 108 of those were translated. Impressions came to 529 before and 1,382 after; that is about 132 a day over the four full days before, and 81 a day after. Clicks went up from 3 to 14.
Almost all of the fall sits in the case pages. They are found mostly by the names of the firm’s clients, and across all fifteen languages they drew about 75 impressions a day before and 24 after. Over the same days the home pages rose from about 24 a day to 29, and the services, team and method pages of the new languages added about 8 a day, while the English ones stayed at about 1.
| sentiention.com, its own pages | 13 to 17 September, before | 19 September to 5 October, after |
|---|---|---|
| Addresses Google showed | 8 | 118, of them 108 translated |
| Impressions | 529 | 1,382 |
| Impressions a day | about 132 | 81 |
| Home pages, a day | about 24 | 29 |
| Case pages, a day | about 75 | 24 |
| Legal pages, a day | about 33 | 19 |
| Clicks | 3 | 14 |
Reach Moved Between Languages
A searcher in Germany who types the firm’s name now meets the German home, since every page names its siblings and Google uses those links to show each reader the version in their own language. So the English pages lost readers on the very day the translations arrived, and the translated pages took about two thirds of all that the root drew in those weeks. In the first four days after the launch the root drew 147 impressions a day, which was above its rate before, and then it slid; by October its days ranged from 18 to 102.
We cannot fully separate the launch from the first days of the property itself, since Search Console began to record the site only five days before the languages went up.
This reading rests on 23 days of the record of a small site, and two things could move it. A month on each side would show whether the case pages’ early days were a burst that might fade anyway, and the last two or three days of every reading still fill in. If a firm reads its own languages this early, it can judge them on where the reach went, and it should wait a while before it judges the totals.

The numbers
| Day | English pages | The 14 new languages | All of the root |
|---|---|---|---|
| 13 Sep 2026 | 2 | 0 | 2 |
| 14 Sep 2026 | 103 | 0 | 103 |
| 15 Sep 2026 | 172 | 0 | 172 |
| 16 Sep 2026 | 136 | 0 | 136 |
| 17 Sep 2026 | 116 | 0 | 116 |
| 18 Sep 2026 | 136 | 0 | 136 |
| 19 Sep 2026 | 115 | 115 | 230 |
| 20 Sep 2026 | 46 | 101 | 147 |
| 21 Sep 2026 | 35 | 49 | 84 |
| 22 Sep 2026 | 43 | 84 | 127 |
| 23 Sep 2026 | 24 | 44 | 68 |
| 24 Sep 2026 | 25 | 24 | 49 |
| 25 Sep 2026 | 19 | 117 | 136 |
| 26 Sep 2026 | 15 | 21 | 36 |
| 27 Sep 2026 | 15 | 38 | 53 |
| 28 Sep 2026 | 19 | 27 | 46 |
| 29 Sep 2026 | 29 | 94 | 123 |
| 30 Sep 2026 | 12 | 28 | 40 |
| 1 Oct 2026 | 6 | 12 | 18 |
| 2 Oct 2026 | 17 | 20 | 37 |
| 3 Oct 2026 | 30 | 34 | 64 |
| 4 Oct 2026 | 4 | 18 | 22 |
| 5 Oct 2026 | 18 | 84 | 102 |
Which Pages Google Showed
All fourteen translations appeared at least once in the 17 days. German led them all. It had 198 impressions on 11 of its addresses, and after it came Norwegian with 85, Finnish with 80 and Japanese with 76.
Hindi drew only 2.
Of the 910 impressions on translated pages, it was the homes that took 398, while the case pages had 190 and the legal pages 172, which were spread over 39 addresses. Some of those legal pages came up for searches of their own.
Google showed the privacy notices and terms of 14 languages beside the pages that sell.
When a translated home was shown, it was usually near the top, with /pt/ at an average position of 3.0, /fi/ at 4.0, /de/ at 4.6 and /no/ at 5.9, which probably means a search for the firm’s own name. The legal pages sat much lower, and some of them near position 50. Clicks stayed fairly small throughout, 9 on translated pages and 5 on the English ones, 14 in all.

The numbers
| Language | Addresses shown | Impressions | Clicks |
|---|---|---|---|
| German | 11 | 198 | 4 |
| Norwegian | 7 | 85 | 1 |
| Finnish | 9 | 80 | 1 |
| Japanese | 6 | 76 | 0 |
| Chinese | 10 | 69 | 1 |
| Swedish | 12 | 67 | 0 |
| Italian | 8 | 66 | 0 |
| Portuguese | 6 | 61 | 1 |
| Spanish | 10 | 52 | 0 |
| Arabic | 6 | 46 | 0 |
| Polish | 8 | 46 | 0 |
| French | 6 | 37 | 1 |
| Danish | 7 | 25 | 0 |
| Hindi | 2 | 2 | 0 |
| English | 10 | 472 | 5 |
Searches That Found the Languages
Rare queries behind a page are withheld by Google, and for sentiention.com’s own pages it named those behind 109 of the 1,382 impressions, 8 %. Of these, 90 came on the names of the firm’s clients, which the case pages carry, 4 on misspellings of the firm’s own name and 3 on others. The remaining 12 asked for what the firm does, and all of them landed on a translated page.
One was zapytania ofertowe, the Polish term for requests for quotation, and it brought up the Polish home page at an average position of 7.5. It is the living Polish word that the voice pass set beside the English abbreviation on 18 September.
A German search for sourcing plastic packaging in Asia found the German home at position 25, and a Polish one for joint venture found the Polish method page. In Swedish, a search for customs advice found a Swedish page as well, though only at position 80. Twelve impressions are a thin base, and all they can say is where such searches went.
Countries are thinner still, since Google gives a country for only 66 of the 910 impressions on translated pages.
Of those, 51 came from a country where the language of the page is spoken, and the German pages were among them, seen in Germany, Austria and Switzerland.

The numbers
| Pages | A client’s name | What the firm does | The firm’s name, misspelt | Other |
|---|---|---|---|---|
| Translated pages | 47 | 12 | 4 | 3 |
| English pages | 43 | 0 | 0 | 0 |
07Three Weeks, the Whole Domain
Read without a filter, the same property counts the root and Sentiention’s satellites together, over the same days.
Root and Satellites Together
When we read it on 4 October, three weeks in, it showed 113,630 impressions and 536 clicks. Those two figures stand on the studio’s Work page and on the case, and they are the ones Sentiention can check against its own account. Read again on 7 October, those same days held 118,083 impressions and 554 clicks, because Google fills in the last days of a reading after it has been taken.
And through 5 October it counted 122,652 of them, with 569 clicks.
Its curve has the form a new property shows when nothing is pushed. It starts at two impressions on the first day and reaches a few thousand a day by the end of the first week. Its best day was 29 September, when it had 10,219.
The clicks follow at under one in a hundred.

The numbers
| Day | Clicks | Impressions |
|---|---|---|
| 13 Sep 2026 | 0 | 2 |
| 14 Sep 2026 | 5 | 171 |
| 15 Sep 2026 | 25 | 2,384 |
| 16 Sep 2026 | 36 | 6,958 |
| 17 Sep 2026 | 38 | 8,192 |
| 18 Sep 2026 | 31 | 4,282 |
| 19 Sep 2026 | 10 | 2,404 |
| 20 Sep 2026 | 22 | 3,880 |
| 21 Sep 2026 | 47 | 6,192 |
| 22 Sep 2026 | 39 | 6,183 |
| 23 Sep 2026 | 35 | 8,428 |
| 24 Sep 2026 | 27 | 6,827 |
| 25 Sep 2026 | 14 | 6,565 |
| 26 Sep 2026 | 5 | 4,661 |
| 27 Sep 2026 | 10 | 6,276 |
| 28 Sep 2026 | 39 | 8,448 |
| 29 Sep 2026 | 59 | 10,219 |
| 30 Sep 2026 | 39 | 7,890 |
| 1 Oct 2026 | 34 | 5,335 |
| 2 Oct 2026 | 16 | 4,428 |
| 3 Oct 2026 | 7 | 3,836 |
| 4 Oct 2026 | 1 | 866 |
Under One in Two Hundred
In the 23 days to 5 October, 0.46 % of the times the domain was shown turned into a visit. Each reading we make of it returns a rate that low, and by our reading a company’s own site, whose demand is mostly its own name, is probably chosen less often than a catalogue or a reference.
Across 23 days, under 1 impression in 200 became a click.
The root is small. From 19 September to 5 October it drew 1,382 of the 100,663 impressions of the domain, which is 1.4 % of them, and all the rest went to the satellites. We keep the property’s record day by day, so that the next change, whatever it is, will be measured against this one.
Where the Clicks Came From
From 66 countries, Google sent visitors to the domain between 13 September and 5 October, and there were 569 of them in all, with at least one from each country. The United States gave 149 of those, which is 26 %, India gave 48, the United Kingdom 28 and Germany 27.
An earlier version of this paper set the 65 countries it had counted on 4 October beside the languages. But the satellites are in English and they carry almost all of the reach of the property, while the translated pages drew 9 clicks in 17 days, so those countries belong to the whole domain and for the most part to its English sites.
Which languages the clicks came from, page by page, is the next column of the record.

The numbers
| Country | Clicks | Impressions |
|---|---|---|
| United States | 149 | 34,049 |
| India | 48 | 9,291 |
| United Kingdom | 28 | 5,708 |
| Germany | 27 | 2,777 |
| France | 18 | 1,634 |
| Netherlands | 16 | 1,628 |
| Italy | 14 | 1,367 |
| Japan | 14 | 1,191 |
| Taiwan | 14 | 1,084 |
| Canada | 13 | 2,980 |
| 56 other countries | 228 | 49,773 |
08For a Firm Selling Abroad
Noo–Studio’s Planet tier puts a client’s presence into the languages of its markets, usually three to five of them, by the method Sentiention’s fifteen were built with.
Made From the English
Every piece of a firm’s record can have one living place, and then anything that appears twice is either a frozen original or a copy that a script makes, never edited by hand, so that the two cannot drift apart. Sentiention’s fifteen languages keep that rule. None of them drifts from the English, because none of them is the English.
Each one is made from it, carries the version it was made from, and is made again, section by section, when that version changes.
In our reading, knowledge that passes from hand to hand inside a firm loses a part at every hand-off, and a translation of a translation is the same loss in a second language. A site whose fourteen versions are each made from the one English keeps a single voice because it keeps a single source. That is what presence by architecture means in language: the structure decides what every version of a site gets, so the number of languages changes nothing in how the site is kept.
Seven Steps
- Languages are chosen from the record, from where the firm’s visitors and its enquiries already come, and from where its buyers search in their own language.
- Every language sits in one source, as pages of WordPress under a home of its own, which keep the original’s addresses after the prefix, so everything the site does by name works in all of them.
- Each language is declared to the others, so that search engines show every reader the page in their own language and read all of the versions as one page.
- Voice is translated section by section, from what it means and in the cadence that the language has of its own, with the firm’s named terms kept as they are and the legal pages kept faithful.
- Some things stay in one language, so that a process which the firm runs in English can stay in English, as long as this is said plainly on every page that leads to it.
- At the foot of each page, the site says what is translated and how, and each legal page names the version that prevails.
- Results are read language by language and per day, with the reach first and then the enquiries, from the pages of each one.
Figures That Could Still Move
Two readings in this paper rest on very little. One is the fall in the daily reach of the root, which part six sets out with what would move it. The other is the share of searches for what the firm does, which rests on 12 impressions while Google withholds the searches behind 92 % of all the root’s impressions, so a handful more or fewer would change it.
One number we cannot give at all is what the languages have brought in briefs. The intake records the language of every brief, and we have not read it; no brief in the records we did read is traced to a language. A buyer in the same doubt can set a date, read that line in its own intake on the day, and count.
Until a language sends a brief, what it has given the firm is reach, and the record says so.
09Method and Sources
All the figures here come from Sentiention’s build records, the chats of the day it was built, its Search Console and its live pages, each read on the date given with it.
Records of the Build
On a copy of the site, in a separate folder, the languages were made. That folder kept every script, brief and segment file, together with the grid of languages and pages that the checker wrote on 18 September. Both chats of the build are archived beside them, with every message stamped in UTC, and we give their times two hours later, in Poland time.
We read the scripts for what they do, from the extraction and the build to the three checks, and we counted the segment files on 7 October 2026. That copy was retired on 2 October. The local copy of the live site, checked identical to live that day, carries the same build.
On 7 October 2026 we also captured the live site, in a browser window that was 1,440 px wide; the consent banner was set aside and never answered, and no form was sent. In every capture we left out the row of the footer that carries the firm’s address.

Search Console, Three Readings
We pulled Google’s record of the domain through its API, with access to view and nothing more, on 4, 5 and 7 October 2026. The root’s own pages are those whose address begins with sentiention.com and no subdomain, and any address with a jump mark (#) is left out, since it repeats its page’s impressions.
English is counted by leaving out the fourteen two-letter prefixes, and the languages as the root less the English. Grouped by date and grouped by page, both ways give 472 impressions for English and 1,382 for the root from 19 September to 5 October. Because Google withholds rare searches and gives a country for only part of the impressions, the figures by search and by country are lower bounds.
| Reading | Grouped by | Window | Read on |
|---|---|---|---|
| The root, either side of the launch | page | 4 to 17 September and 19 September to 2 October | 4 October |
| The whole domain, a day at a time | date | 13 September to 4 October | 5 October |
| The root, English and the languages | date | 13 September to 6 October | 7 October |
| The root, address by address | page | 13 to 17 September; 19 September to 5 October | 7 October |
| The root, by search | search and page | 19 September to 5 October | 7 October |
| The root, by country | page and country | 19 September to 5 October | 7 October |
| The whole domain, by day and by country | date; country | 13 September to 6 October; to 5 October | 7 October |
Corrections to Our Earlier Figures
This pass changed four lines of the version that went live on 6 October. Two of them, on the windows either side of the launch and on the 65 countries, are set out where they arise, in the parts on Google’s record. That version also had the languages going live at night, while the chats put it at 16:49 Poland time.
And it said that the intake asks for names in Latin letters. What the record holds is a test that found names in other scripts coming out empty in the signed document, with no such rule in the code, so that line has gone.
Left Unclaimed
Nothing in the records we read shows that the new languages have brought a brief yet. Nor do they show that a native speaker read every language before it went live. Only one did, and that was in Polish.
The method changed for all fourteen from that reading.
A reading of German and Chinese by the firm’s own people was proposed on 18 September, and the records do not say it happened.
Nooné, Noo–Studio’s AI writer, wrote this paper from the studio’s own records, and every figure was checked against its source before it was published. Noo–Studio publishes it and answers for it. How the studio uses AI.

