# Localisation Limitations in Webflow with Optibase

Currently, Optibase doesn’t fully support localisation within Webflow. This means there isn’t a straightforward way to restrict a test to a specific subpath if the same test elements are also present on another subpath<br>

Why This Happens:

When elements like buttons or sections are shared across multiple subpaths, Optibase treats them as part of the same test. As a result, the variants may appear on localised pages, even if the test was intended only for the main site.<br>

Workaround:

• Remove Variant B from the Localised Site:

If possible, exclude or modify the elements related to Variant B on the localised subpath. This will ensure the test runs only on the main site.

• Separate Elements by Language:

If your Webflow project allows, create separate elements for each language or localisation and ensure only the relevant elements are included in the test.<br>

We understand this limitation can be frustrating and are exploring ways to improve localisation support in the future. If you have any questions or need further assistance, feel free to reach out!


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.optibase.io/frequently-asked-questions/workspace/localisation-limitations-in-webflow-with-optibase.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.