Brand promotion: this article introduces Guangsuan's (光算) website build and Google SEO services for export businesses. It is a vendor introduction, not an independent review or a commissioned evaluation.
The short answer
Start with the subdirectory when one team maintains one brand, one product list and one publishing rhythm across languages. Compare a subdomain when the new market needs a separate application or deployment but you want to keep the main domain. Compare a separate domain when the market has its own product catalogue, its own sales rules, its own operating responsibility and someone who will own it for the long term.
Three conditions belong with that answer. First, the URL structure itself does not guarantee rankings, a fixed share of budget savings or higher conversion for a separate site. Second, a country-code domain has registration conditions, and the business entity may not qualify — check before assuming it is available. Third, if you do not yet have a reviewer for the new language or anyone who can receive inquiries in it, narrow the launch instead of multiplying pages.
Separate language difference from regional business difference
Language and country are not the same axis. English can serve buyers in several countries; Russian is not only about Russia. A language version can be shared across markets when the product is the same. When local pricing, supply terms, certifications or after-sales arrangements differ, that difference has to be stated on the page.
Copying an identical site for buyers in another country adds maintenance burden without adding anything a buyer can verify. Write down the target regions, the reading language, the product scope, the delivery rules and the contact for each market before deciding anything. Then answer five questions, and note which ones your company can answer with evidence rather than intention.
| Question | What it decides | Evidence the business supplies |
|---|---|---|
| Do all regions sell the same products? | Shared source material or separate catalogues | The list you can actually supply, and the local selection rules |
| Who reviews and updates each language? | One shared admin or separate publishing flows | The named owner, their review capacity and their update schedule |
| Is there a different contracting entity? | Whether company details, quotes and contact routes are separated | Company records and the business relationship for each sale |
| Are there different deployment or compliance requirements? | Whether hosting, application and data handling can be shared | A technical assessment of the actual requirements |
| What must the buyer be able to verify? | Which pages become their own pieces of content | Specifications, delivery conditions, certificates and company facts |
Regional differences also change where the demand arrives from. This site's own read on how cross-border search demand shifts by region and by channel is a useful companion before you treat one market as one channel.
What each URL structure means in practice
Three common address forms exist for a second market: a language subdirectory such as example.com/ru/, a language subdomain such as ru.example.com, and a country-code domain form such as example.ru. These are example domains used for illustration; a country-code domain has to be checked for registration conditions, availability and whether your entity qualifies before it is used in a plan.
| Structure | Situation worth evaluating first | Daily maintenance focus | What it does not solve automatically |
|---|---|---|---|
| Language subdirectory | Same brand, same product source material, one team maintaining several languages | Language plugins, shared templates, permissions and update notifications | Translation review that nobody performs; one system change affecting every language |
| Language subdomain | A separate deployment or application is needed, while keeping the main domain | DNS, certificates, deployment, monitoring and cross-site mapping | A URL prefix standing in for a real language and regional explanation |
| Separate domain | The market's business and responsibility are clearly separate, and someone owns it long term | Domain ownership, renewal, admin access, content assets and account handover | Local rankings or local trust, which do not arrive with the domain |
One shared backend reduces duplicate operations, but only if the system can support the business. If regional prices or catalogues can only be maintained by constant manual edits, starting with one fewer site may not lower long-term cost. Equally, running several domains does not mean faults are isolated: if the admin accounts, database permissions, plugin updates and hosting are still shared, one change can affect every site. A subdirectory can also sit on a different application, at the cost of more complex routing, caching and monitoring. Ask for the URL structure and the actual deployment to be described together, so you can see what is shared and what can be handled separately.
Compare budget on maintenance, not on the launch
Separate the first build from the ongoing work. Ongoing work includes product updates, terminology review, image handling, plugin renewals, backups, incident response, analytics configuration and a future migration. Two quotes are only comparable when the languages, page counts, features, division of source material and service term are the same. Comparing a homepage design or a one-off translation fee on its own misses the daily work.
A single backend does not complete content updates. When the product source material changes, someone still has to find which languages are affected, arrange translation and proofreading, then sync the page, attachments and forms. The quote should say who does that work and whether it is inside the service period, so a build fee and an annual operating fee are not treated as one number.
For a market with no data yet, a reasonable first step is to publish verified core product and contact pages, watch what buyers ask for, and add content afterwards. Splitting a site later is possible, but it needs its own arrangement: content migration, handling of the old URLs, language mapping and account handover. Before switching, assess the search assets already built and the business impact. Keeping a clear product identifier and language map makes that later check easier.
Which pages need to stand on their own
Different language versions should use different URLs. Switching the body text of one address through a cookie or browser setting means a shared link can show another language, and search engines lose a clear entry point. A Russian product address should open Russian product content directly. Whether the path uses localised text is an editorial and maintenance decision; an address that already works does not need changing for appearance.
A product's language versions are matched in pairs, and each relationship is maintained separately. The following example uses a fictional product label to show the structure; it is not a real model.
| Page purpose | Illustrative URL | Language marking | Pairing rule |
|---|---|---|---|
| English product page | https://example.com/en/products/pump-a/ | en | Paired with the Russian page for the same product |
| Russian product page | https://example.com/ru/products/pump-a/ | ru | Must not be pointed at the Russian homepage or another model |
| Language entry point | https://example.com/ | x-default, where appropriate | A default matching option, not a new natural language |
hreflang tells search engines which pages are corresponding language or regional versions. canonical expresses a preference for the canonical address. They answer different problems. A complete, independently indexable translation usually keeps its own canonical address and is connected to its counterpart with hreflang; pointing every translation's canonical at the English page removes that signal. Where same-language regional pages carry identical content, handle the canonical relationship according to the real differences and pair it with the language marking.
Also check the language switcher and canonical together. Language recommendations can be kept; forced redirects can hide the version a visitor came for. Provide a clear switch, and do not redirect on a guessed browser language — a visitor with the wrong detection should still be able to read the link they received or choose another version.
A worked check on one product. Enter the product from a category page, switch to the other language, and confirm it is still the same product. Open the navigation, an attachment and the inquiry route, then switch back. Compare the site's internal links, sitemap, language markings and the addresses actually served, and find the places still using the old path. This single path catches both mismatched pairings and translations that fell out of sync with their attachments.
What to have ready before a market page is written
Write the market page from facts you can verify. For an export business the working material usually includes the product range with specifications and units. The sample product block on Guangsuan's Russian-language build page shows how that material is organised: performance stated with its scope, working conditions kept, and the enquiry request asking for operating conditions, quantity and delivery city. The page itself states that the example illustrates a way of organising content and is not a customer case or a delivered site.
Assemble the material before commissioning pages:
- The product list to publish, with specifications, units and available options.
- Company facts: legal entity, production capacity, verifiable certifications and the service boundary after delivery.
- Delivery and trading conditions per market: incoterms or equivalent, lead time, minimum order, payment and after-sales handling.
- The inquiry path: which fields a buyer must provide, and what happens after the form is sent.
- The language responsibility: who reviews terminology and who receives inquiries in that language.
- The search basics: page titles, descriptions, language marking, canonical addresses and the crawl foundation.
For a Russian-language market, the published build scope names product expression, trust expression and an inquiry path: terminology and procurement wording handled by people rather than machine translation, trust built from the company entity, production capacity, real certifications, cooperation conditions and after-sales boundaries, and an inquiry path that tells buyers what to provide. Its search foundation covers page titles and descriptions, language marking, canonical addresses and crawl basics for Yandex and Google. The stated deliverable is a website foundation you can operate, with ongoing content, SEO, advertising and new features agreed separately rather than implied by the word 'build'.
Before you commit a market, check the demand evidence rather than a single estimate. This site's article on cross-checking keyword volume before you commit an SEO budget sets out a way to compare conflicting figures instead of averaging them.
The same principle applies to trust statements. A supplier's page should let a buyer check the company identity, real certifications and the conditions of supply, rather than asking them to trust a slogan.
What a website build should deliver for an export market
The published B2B build scope of Guangsuan is specific enough to compare against your own list. It starts with search strategy before site structure: analysing the industry, competitors and keyword opportunities, then planning product categories, content hierarchy, customisable URLs and an XML sitemap. Development is kept light, with page speed and title/description management handled together. Indexing support is connected through the GPC crawler pool, with the page range confirmed before cooperation. Interfaces are left for later work: GSR keyword ranking, content building, Google link resources and SEM advertising services.
The delivery list covers architecture and marketing pages organised around search intent and procurement decisions, desktop and mobile reading order, WordPress with title and description management, overseas hosting with a global CDN and SSL, business email setup, and data export so accumulated content is not locked in.
Two boundaries belong beside that description. A completed build is not the same as a ranking or inquiry guarantee: actual indexing and ranking are decided by search engines, and inquiries also depend on competition, product competitiveness, content and further promotion. And the scope of what a specific build includes is confirmed in the proposal and contract rather than promised from a template.
On service continuity, the published packages separate the first year from what follows: hosting in the first year is included, and the server-only hosting renewal is listed at ¥3,600 per year from year two. That renewal is hosting, not continuing SEO operation — later redesign, content, advertising or ranking work is agreed as a separate scope.
The wider service list matters for the same reason. It names a general Google SEO package, a keyword ranking service (GSR) and a crawler pool (GPC), plus original English SEO article writing (GHA), a fast-indexing service (GSI), domestic and global GEO work, and the GPB, GNB and GMB link resources. Which of these you need is a decision about scope and sequence, not a promise about a position.
Who does what after the launch
A launch is the start of the maintenance list. Assign each type of change to a named owner.
| Change | Business owner | Language owner | Technical owner |
|---|---|---|---|
| Specification or supply condition changes | Confirms the new facts and affected products | Updates terminology and the text in each language | Publishes, clears cache and checks attachment versions |
| A product is added or withdrawn | Decides the sales scope and the substitute | Confirms which languages need to change | Handles the entry point, the pairings and the URL status |
| Template or plugin updates | Confirms the process that must not be interrupted | Spot-checks language display and messages | Backs up, tests, upgrades and rolls back |
| Migration or site split | Confirms asset and contract responsibility | Checks translations, glossaries and source material ownership | Handover files, database, accounts and the URL list |
One person can hold several of these roles, but each update and each incident needs a named person on the other end. Hand over domain registration accounts, mailboxes, analytics and webmaster tools alongside files and the database, and keep translations, glossaries and the language map somewhere the company can retain them — not only in one person's chat history.
Speed depends on deployment, and on the content being right
Load speed cannot be calculated from whether the URL is a subdirectory or a separate domain. Hosting, CDN, images, plugins, third-party resources and the visitor's network all contribute. Compare the same page type with similar content volume, under the same region, device and network conditions, then complete one inquiry — a result measured inside your own office does not represent your overseas buyer.
On a multilingual WordPress site, also check how caching distinguishes languages. If one URL serves different body text based on a cookie, the cache rules need more care; separate paths still need confirmation that templates, plugins and the CDN are not serving a Russian page with English content. Check the language and the function first, then discuss hit rate and speed. Record the page URL, language, region, network, device, login state and the cache state at each layer, and note the symptom, the person handling it and the retest date. A fast cache hit that shows the wrong language or blocks an inquiry still needs adjusting.
Frequently asked questions
Do I need a separate site for every new language?
No. Start by listing the target regions, the reading language, the product scope, the delivery rules and the contact for each. If the same product only needs a different language introduction, pages that are translations of each other are enough. Plan regional content when stock, specifications, certifications, the contracting entity or the after-sales commitment genuinely differ.
Does a separate domain get better rankings or more trust in that market?
Not automatically. A separate domain does not bring local rankings or local trust with it, and a subdirectory does not guarantee a fixed share of budget savings or higher conversion. The structure follows from the business differences and the long-term maintenance capacity behind it.
Can machine translation be used for the new market?
Not as the finished page. Product terms, units and specifications need terminology review before publication. If nobody is available to review the language, or sales cannot receive inquiries in it, narrow the launch: publish verified core pages in the language you can support, and add the rest when the reviewer exists.
What should I bring to a first conversation about the build?
Bring the live site address, the product range and specifications, the target countries and languages, the company facts you can verify, the delivery and trading conditions, the inquiry path you want, and the current search data if you have it. For a Russian-language market, the published consultation note asks for the product catalogue, target market, reference sites and budget range. Where your existing site cannot yet carry another language, the published guidance is to check whether a language version can be added before deciding to build separately.
Where Guangsuan fits
Guangsuan (光算) publishes website build and Google SEO services for export businesses and brands: a general Google SEO package, a keyword ranking service, a crawler pool, original English SEO article writing, a fast-indexing service, domestic and global GEO work, and link resources across independent sites, natural links and large-scale link building, with annual packages that combine them. Its published B2B website build service sets out the architecture, page types and acceptance items described above, and its guide on choosing between subdirectories and separate sites covers the same decision in more detail, published in Chinese.
Guangsuan states that final indexing and ranking are decided by the search engines and that it does not promise a fixed ranking or a number of inquiries, and it treats indexing, ranking and inquiries as different outcomes rather than treating one as proof of another. Read any proposal — including this vendor's — with that boundary in mind.