Identify the market and the customer
State which market you want to reach and who you want enquiries from. End users, distributors and procurement teams may need different information. Identify the product group, languages and the first action you want the customer to take. That might be requesting a price, downloading a catalogue or describing a project. Choosing a language is more than adding an option to a menu.
List pages and files together
Menus, form labels, error messages and email replies affect the experience alongside the homepage and product copy. Include downloadable catalogues, technical data sheets and instructions in the scope. Record the current version and owner of each item. Identify material that should stay untranslated, brand names and statements that need approval before work begins.
- Priority product and service pages
- Menus, forms and transaction messages
- Catalogues and technical files
- Owners for updates and approvals
Write for the target customer’s questions
Customers should quickly understand what the product does, what information to provide and how to contact you. Clarify ambiguity in the source at the start rather than carrying it into another language. Your company must verify product features, delivery terms and warranty statements. We can use approved terminology and brand-language preferences in translation; we do not create new product promises.
Connect real language versions to the right pages
Google recommends clearly organising multilingual content and identifying related language versions. In the project, consider each language’s actual page address, title, description and internal links together. The language switch should take users to the appropriate version of the same content. Select search wording naturally for each language and avoid creating numerous pages that merely repeat keyword variations.
Test the enquiry form for the target market
Plan how customers will describe a product, quantity or project requirement. Do not make unnecessary fields compulsory. Explain what happens after submission, how you will respond and the file-sharing arrangements. Checking mobile layouts, different alphabets and right-to-left languages such as Arabic on the published page can be a separate task from delivering the translated text itself.
Define translation, design and SEO separately
Design, technical setup, translation, published-page checks and SEO review may belong to one project, but they have different scopes. Share the existing platform, access conditions and expected deliverables. At quotation stage, identify who is responsible for each task and how it will be accepted. After publication, assess the pages that generate enquiries and the quality of the requests. Search rankings and sales outcomes cannot be guaranteed.
Checklist before requesting a quote
- Target markets, languages and customer groups
- Website address and existing platform
- Priority product pages and downloadable files
- Verified product information and terminology preferences
- Enquiry form and communication needs
- Expected design, translation and SEO deliverables
Preparation templates
Complete these blank templates for your files. Use them to explain the scope before uploading any documents.
Frequently asked questions
01Do I need a new website to translate the existing one?+
Not always. We can review the current platform and requirements, then identify translation, editing or new-build tasks separately.
02Can catalogues and manuals be part of the project?+
Yes. Add their files and versions to the scope list. We can assess website and document translation, checking and delivery requirements together.
03Is SEO automatically included in translation?+
Translation, linguistic adaptation and technical SEO are different tasks. Specify any title, description, language-alternative or technical review requirements so they can be stated in the quote.
04Does adding a language guarantee more sales or a top search position?+
No. Products, markets, competition and other factors affect results. Use genuine enquiries and suitable project requests to guide later improvements.
Official sources and further information
Google Search Central — Multilingual and multi-regional websites ↗Design, translation and SEO scopes are defined separately in the quote. Search rankings, traffic and sales outcomes are not guaranteed.