Skip to content
English - United States
Nous Contacter
  • There are no suggestions because the search field is empty.

Some pages are not translating on your Webflow site with Localize: is this a bug?

Identify and correct the causes of non-translation

Key points:

  • This isn't necessarily a bug: several reasons can prevent text detection.
  • Content that is not published or is dynamically loaded is not always translated.
  • An incomplete configuration or a missing scan may prevent Localize from displaying translations.

Sometimes, certain pages on a hotel website may remain in their original language, while others are correctly translated using Localize. This doesn't necessarily mean the script is broken; in most cases, it's a detection or publishing issue. Here's how to identify and resolve the specific cause.

Step 1: Verify that the page is correctly published on Webflow

Localize can only translate publicly accessible content.

  1. Log in to Webflow Editor or Designer.
  2. Open the relevant page.
  3. Check that it is published (green "Published" icon).
  4. If it's a CMS page (blog, offer, news), make sure the article is visible online and not just a draft.

💡 Tip: Localize never detects content that has remained in draft or unpublished form.

Step 2: Rerun a site scan in Localize

When a page is added or modified, it is not automatically translated until a new scan is performed.

  1. Log in to your Localize account.
  2. Open the project associated with your Webflow site.
  3. Go to Settings → Languages.
  4. Click on “Rescan Website” (or “Scan for new content”).
  5. Please wait while Localize analyzes your public pages.

💡 Tip: Run a rescan after each major update (new page, CMS content, seasonal offer, etc.).

Step 3: Verify that the Localize script is correctly loaded on the page

If your site contains multiple layouts or page templates (CMS, landing pages, etc.), it is possible that the Localize script may not be present everywhere.

  1. Open Webflow → Project Settings → Custom Code.

  2. The script must be inserted in the `<body>` section to be active on all pages.

If some pages have custom code, check that it doesn't override the Localize script. <script src="https://global.localizecdn.com/localize.js"></script>

<script>

Localize.initialize({

key: 'YOUR_PROJECT_KEY',

rememberLanguage: true,

detectLanguage: true

});

</script>

  2. Republish the site once the verification is complete.

💡 Tip: If you have manually added Localize to a specific page, move the script globally to avoid forgetting.

Step 4: Check dynamic content and third-party scripts

Localize translates the text content rendered in the initial HTML, but not the text loaded afterwards via JavaScript.

  • External integrations (forms, booking widgets, Google Maps, etc.) are not automatically translated.
  • CMS content that is too dynamic (loaded via an AJAX script) can be ignored.

💡 Solution: Use the “Dynamic Content” mode in Localize → “Translations” tab. You can manually add missing text there to force its translation.

Step 5: Verify that the page language is enabled

  1. In Localize → Settings → Languages, ensure that the target language is enabled.
  2. If you have recently removed or added a language, the system may have disabled some translations.
  3. Reactivate the relevant language, then republish your site.

💡 Tip: Without an active secondary language, Localize automatically ignores translation on these pages.

Step 6: Clear the cache and test in private browsing mode

Sometimes the browser displays an older, untranslated version.

  • Clear your browser's cache.
  • Open your website in an "Incognito" window.
  • Reload the page and test the language change again.

💡 Tip: For a complete test, try it on another device or via a VPN to simulate a foreign visitor.

Step 7: Check the Localize plan limits (free accounts)

Free or entry-level Localize plans translate a limited number of pages.

  • If you exceed this quota, some pages will not be translated.
  • Log in to your account → Billing → Usage to check the number of channels or pages covered.

💡 Tip: If you manage a complete hotel website (rooms, restaurant, offers, blog…), a higher-level plan is often necessary to cover everything.

Best practices for hotels

  • Run a full scan every week if you frequently update your content.
  • Centralize the Localize code globally to avoid oversights.
  • Test each translated page on desktop and mobile.
  • If you are using an external booking engine, translate it separately or via a multilingual iframe.

Conclusion

If some pages of your Webflow hotel website aren't translating with Localize, it's usually not a bug. The problem most often stems from unpublished content, a missing script, or a page that hasn't been scanned. By checking your settings and running a full scan, you can restore translation to all your pages in minutes.