Hi,
Thanks for the detailed question.
Linguise doesn't have a dedicated "public URL" setting separate from the domain it's installed on, canonical tags, hreflang tags, and sitemap URLs are generated based on the domain configured in your Linguise dashboard. Routing translated content through a separate reverse proxy (like a Cloudflare Worker) so it appears under a different domain/path than the one Linguise is configured for is not a setup we test or maintain, so we can't guarantee canonical, hreflang, or sitemap output will behave correctly in that configuration, and we're not able to provide support if issues come up specifically from that proxy layer.
The good news is you likely don't need the proxy at all. Linguise natively supports subdirectory installations (e.g. streamlocator.com/fr/) on your main domain without any extra routing layer, and it handles canonical tags, hreflang, and translated sitemaps automatically for that structure. You can find setup details here:
https://www.linguise.com/documentation/
Regarding the crawler and firewalls, our translation crawler can occasionally be blocked by a destination site's firewall (e.g. Cloudflare) if that firewall's bot protection rules aren't set to allow it. If that happens, whitelisting our crawler's IP/user agent on your end usually resolves it.
If you'd like help setting up the native subdirectory configuration, let us know and we can guide you through it.
Best regards,
Linguise Support
Posted : 14/08/2026 2:40 am