Pre-sale questions

Ask us any question about Linguise service and get an instant reply!

Notifications
Clear all

Custom canonical/hreflang base URL for a reverse-proxy setup

2 Posts
2 Users
0 Reactions
4,381 Views
 Max
(@Max)
Posts: 1
Topic starter
 
[#614]

Hi team,

We're planning to run Linguise behind our own reverse proxy (a Cloudflare Worker), so visitors and Google only ever see translated pages at streamlocator.com/fr/... — a subdirectory on our main domain — rather than at Linguise's own hosting subdomain. The proxy fetches content from the Linguise subdomain and re-serves it under our main domain's path.

Before committing, we need to confirm:

  1. Can Linguise be configured to emit canonical tags, hreflang tags, and sitemap URLs pointing at a different domain/path (streamlocator.com/fr/...) than the subdomain it's actually hosted on? If so, where is that setting?
  2. If not directly supported, is there another supported way to achieve the same effect — e.g. a "public URL" setting separate from the hosting subdomain?
  3. Does Linguise's translation crawler ever get blocked by a destination site's firewall (e.g. Cloudflare) when it needs to re-crawl for updates? Asking because we've seen this reported as a recurring problem with a competing tool.

Thanks you


 
Posted : 12/08/2026 9:23 am
(@ilham)
Posts: 145
Admin
 
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

Leave a reply

Author Name

Author Email

Title *

Preview 0 Revisions Saved