Checking the logs

When a translation isn't showing up, isn't correct, or a translated URL doesn't resolve, Umbraco's own log is usually the fastest way to find out why. The package logs through the same pipeline as the rest of Umbraco.

Jump straight to the relevant entries

Search in the Umbraco logs for Weglot or click the View Weglot logs quicklink button from within Settings → Advanced → Umbraco Translator - Weglot.

Failed translations

A failed translation call is logged as an Error, at the default log level, with the page URL and Weglot's raw response:

Unable to translate page "https://example.com/fr/blog/conferences". Weglot response is:
"\"You have reached your words limit, you need to upgrade. (NMC)\""

The response tells you whether the problem is your Weglot word allowance (as above), an invalid or revoked API key, or a language pair Weglot doesn't support (e.g. "Not valid languages pair: en to xx.").

The visitor still gets a page: the original, untranslated content. That untranslated result is cached, so the error is logged once per cache period, not on every request.

Turning on debug logging

Successful translations are logged at Debug level, which Umbraco hides by default. To see them, lower the minimum level for the package in appsettings.json (or wherever you configure Serilog):

{
  "Serilog": {
    "MinimumLevel": {
      "Override": {
        "Arjo.Umbraco.Weglot": "Debug"
      }
    }
  }
}

Each translated request then logs a pair of lines:

Translation started for page https://example.com/fr/about-us : en -> fr. Total number of words requested: 214
Translation returned for page https://example.com/fr/about-us : en -> fr. Total number of words responded: 214

• Both lines appear: the call to Weglot worked.
• Neither appears for a page you expected to be translated: either the request wasn't recognised as a translated request (wrong URL prefix, unlicensed hostname, or a real page at that path), or the page was served from the cache without calling Weglot.

Remove the override once you're done; debug logging on a busy site is noisy.

Checking Weglot's status

The badge in the Weglot API Key panel shows whether Weglot's service is reachable, checked live from your browser. If it's red ("Weglot may be unavailable"), the problem is most likely on Weglot's side rather than in your configuration; try again shortly.

Because the check runs in your browser, a browser extension or network policy that blocks requests to api.weglot.com can also turn it red, even though your server can reach Weglot fine. If the badge is red but the logs show successful translations, it's the browser check that's blocked.

Checking your API key and word allowance

Login to your Weglot account, on the same settings page, opens your Weglot dashboard. There you can check your remaining word allowance and whether your API key's project is active. Most "translations have silently stopped" reports come down to one of these two.