Overview
This article helps you set up and manage multiple languages on your Access Volcanic website. Language support allows you to create multilingual recruitment sites. Visitors can switch between different language versions using an automatic selector. You can configure which languages are available, set your default language, and manage content independently for each language through the Admin Area.
Key benefits
Create multilingual recruitment experiences for international candidates.
Switch between languages using an automatic language selector in your site header.
Manage content and pages independently for each language version.
Support over 30 languages including major European, Asian, and regional variants.
Improve local SEO and candidate engagement with localised content.
Maintain consistent branding while delivering culturally appropriate messaging.
Before you start
Before setting up multiple languages, make sure you have:
Admin access to your Access Volcanic platform.
A clear understanding of which languages you want to support.
Content translation plans and resources for each target language.
Knowledge of any ATS integration requirements that may affect language setup.
📌 Note: Your website must have a default language configured to ensure features like candidate registration function correctly.
Supported languages
Access Volcanic supports the following languages and region codes:
Code | Language | Code | Language |
bg | Bulgarian | ko | Korean |
cs | Czech | ky | Kyrgyz |
da | Danish | mk | Macedonian |
de | German | ne | Nepali |
en | English (UK) | nl | Dutch |
en-US | English (US) | no | Norwegian |
es | Spanish | pl | Polish |
fi | Finnish | pt | Portuguese |
fr | French | ro | Romanian |
ga | Gaelic | ru | Russian |
hu | Hungarian | sk | Slovenian |
it | Italian | sv | Swedish |
ja | Japanese | tg | Tajik |
th | Thai | tr | Turkish |
uk | Ukrainian | uz | Uzbek |
vi | Vietnamese | zh | Simplified Chinese |
zh-TW | Traditional Chinese (Taiwan) | zh-HK | Traditional Chinese (Hong Kong) |
📌 Note: If you need a language not listed here, contact your Account Manager to confirm whether it can be added to your website.
Setting your default language
Every Access Volcanic website requires a default language. Without one, core features like candidate registration may not work properly.
Log in to your Admin Area.
Click Settings in the top navigation.
Select Languages (under Global heading).
Select Global, then click Languages.
If no language appears, click New to add one.
Choose your preferred language from the dropdown list.
Tick the Default checkbox.
Click Submit to save your changes.
📌 Note: If you cannot see Languages in your settings, contact Support via the Digital Assistant to review.
Adding additional languages
You can add extra languages either during your initial website build or after your site goes live.
During implementation
Multiple languages can be included as part of your initial website build, depending on your website package and implementation scope.
After launch
Contact your Account Manager or Customer Success Manager to discuss your language requirements.
Confirm project scope, costs, and timelines with the Professional Services team.
The Access team will enable the new language, set up language-specific page structures, and add the language selector to your website.
🤓 Tip: Discuss localisation strategy, content translation timelines, and implementation approach before proceeding with additional languages.
Managing multilingual content
Once multiple languages are enabled, you can manage content separately for each language version across different areas of your Admin Area.
Language-specific tabs appear throughout the platform wherever content can be localised, including:
Custom pages: Create unique landing pages for each language.
Blogs: Write blog posts tailored to different markets.
Navigations: Configure menu items and labels per language.
Events: Set up region-specific events and announcements.
Each language tab represents that language's complete content structure. You can add or edit content independently within each language section using language-specific templates and content blocks (reusable page elements).
Front-end experience
Once languages are enabled, visitors to your website will see several changes that allow them to navigate between different language versions.
A language selector appears in your site header, allowing visitors to switch between enabled languages.
Selecting a language displays the content and pages for that specific language version.
Each language operates as a parallel site structure with its own navigation and content.
URLs automatically update to reflect the selected language, allowing visitors to bookmark and share language-specific pages.
All visible text, navigation menus, and content blocks display in the chosen language.
📌 Note: The exact appearance and placement of the language selector may vary depending on your website design and implementation.
Best practices
Set and verify your default language before launching additional language versions.
Treat each language as its own complete site structure to ensure high-quality localisation.
Plan content translation and localisation before enabling new languages.
Test all forms, navigation, and key user journeys in each language version.
Review consultant and job visibility settings to ensure appropriate content appears in each language.
Consider cultural differences when localising content beyond simple translation.
Coordinate with your ATS provider if you use external applicant tracking systems.
📌 Note: Language setup affects multiple platform areas, so thorough testing ensures a smooth user experience across all language versions.
FAQs
Q1: Do I need to translate every page on my website?
Answer: No, but fully localised content provides the best user experience. While automated translation tools can assist, manually written content is recommended for key marketing and legal pages.
Q2: Can I add languages after my website goes live?
Answer: Yes, additional languages can be added post-launch through the Professional Services team using either direct payment or Access FlexPoints (a flexible service currency that lets you book Access services as needed).
Q3: Where does the language selector appear on my website?
Answer: The language selector typically appears in your site header, though exact placement may vary depending on your website implementation and design.
Q4: What happens if I don't set a default language?
Answer: Without a default language, core features like candidate registration may not function correctly. Every website must have a default language configured.
Q5: Can I hide certain jobs or consultants from specific language versions?
Answer: Yes, but this requires specific configuration during implementation. Discuss language-aware visibility rules with your Account Manager or Professional Services team.
Q6: How do multilingual sites affect SEO?
Answer: Properly configured multilingual sites can improve local SEO by providing language-specific content for different markets. Each language version can be optimised for regional search terms.
Q7: Do I need different domain names for each language?
Answer: No, multiple languages operate within the same domain structure with language-specific URLs automatically generated by the platform.
Q8: Can visitors bookmark pages in specific languages?
Answer: Yes, each language version has its own URL structure, allowing visitors to bookmark and share pages in their preferred language.
Q9: What if my ATS integration doesn't support multiple languages?
Answer: Review language compatibility with your ATS provider before enabling multiple languages, as some integrations may need specific configuration to handle multilingual job data correctly.
Q10: How long does it take to add a new language to an existing website?
Answer: Timeline depends on project complexity and Professional Services team availability. Custom projects can take several weeks to start, so plan ahead if you have specific deadlines.
Q11: Can I control which jobs appear on specific language versions?
Answer: Yes, job visibility can be configured per language, but this requires specific setup during implementation. Discuss your requirements with your Account Manager or Professional Services team.
Q12: How do consultant profiles work across different languages?
Answer: Consultant profiles may need grouping or localisation rules to filter appropriately by language. This configuration depends on your specific implementation and should be discussed during setup.
Q13: Do I need special ATS configuration for multilingual sites?
Answer: Yes, ensure your applicant tracking system can handle multilingual job data correctly. Some ATS integrations may need specific configuration to work properly with multiple languages.