🧭 Overview
There is no one-click migration for an entire multilingual Vite project into Website Studio. You can, however, migrate the website by importing its built pages or recreating them in Website Studio, then configuring each language version and its SEO settings.
⚙️ Prepare Your Vite Project
- Make a backup of your Vite project and confirm that all pages build successfully.
- Run your production build and identify the generated static files, usually in the dist folder.
- List every route, including language-specific routes such as /en/, /es/, or localized paths.
- Record page titles, meta descriptions, canonical URLs, hreflang relationships, images, fonts, and downloadable files.
- Check whether any content depends on server-side code, APIs, authentication, or client-side routing. These features may need to be rebuilt or connected separately.
📥 Open Website Studio
In Search Atlas, open Website Studio from the left sidebar, or go to /website-studio. Create or open the project where you want to rebuild the site.
🛠️ Move Your Pages
Choose the approach that best fits your project:
- Rebuild pages: Create each page in Website Studio and copy over the content, layout, images, and links. This is the most reliable option for projects that use dynamic React components or custom routing.
- Import a built site: If your Vite build produces self-contained static HTML, CSS, JavaScript, and asset files, use the available import workflow and test the result carefully. Remove unsupported build-only elements and verify that the imported preview loads correctly.
- Use an existing deployment as a reference: Keep the Vite site available while rebuilding pages in Website Studio. Compare each language version, then switch traffic only after testing the new site.
Importing a project does not automatically recreate every Vite route, component, dependency, or project setting. Review the generated pages and replace unsupported functionality with Website Studio elements or supported integrations.
🌍 Configure Languages and URLs
- Create a separate page for each language and keep the URL structure consistent.
- Use clear language paths, such as /en/about and /fr/about, or the structure already used by your site.
- Add links between equivalent language pages so visitors can switch languages without losing their location.
- Set the correct language for each page and review navigation, buttons, forms, images, and alt text in every translation.
- Make sure URLs use the correct slugs and do not create duplicate pages with different language content.
🔍 Preserve Multilingual SEO
For every translated page, verify the title, meta description, canonical URL, and language alternates. Each language version should reference the equivalent versions, including a correctly configured default or fallback language when applicable.
Also review XML sitemaps, robots directives, internal links, structured data, redirects, and any language selector links. Do not leave the old Vite URLs pointing to missing pages; create redirects when a URL changes.
✅ Test Before Launching
- Open every language homepage and key page on desktop and mobile.
- Test direct access to localized URLs, browser refreshes, navigation, forms, menus, and language switching.
- Check that images, fonts, scripts, and downloads load from the correct paths.
- Inspect page source or SEO settings to confirm canonical and hreflang values.
- Test the site on a staging or preview URL before changing your primary domain.
- Monitor indexing, redirects, and broken links after launch.
💬 Get Help
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.