Some of my source content isn’t being detected, why?

There are several reasons that Localize may not detect content on specific pages or specific content on specific pages. Here are some things to look for.

• Some Localize features available in your dashboard that can block content include:
  • Disable Localize by Page
  • Disable Phrase Detection by Page
  • Exclude Phrases by CSS Classes and IDs
  • Block New Phrases by Pattern
  • Phrase Detection by Domain
  • Misuse of Define Variables, creating a variable-based phrase that eliminates other phrases.
• Localize.initialize()Settings:
  • Exclude Phrases by CSS Classes and IDs
  • Do you have saveNewPhrases set to false?
  • Do you have saveNewPhrasesFromSource set to true and you are visiting pages in a target language?
  • Do you have any of the translateXYZ set to false, and that is what they are looking for?
    • e.g. translateAlt, translateBody, translateMetaTags, etc.
  • Do you have translateBodyset to false?
    • If yes, do you see any use of class="localizejs" or id="localizejs"?
  • Are you using translateClasses?
    • If yes, what CSS class(es) did you assign, and do you see those in the source of your page?
• Other conditions:
  • Your content is in an iframe.
  • Are you over the 100,000 active phrases limit for a single project?
    • If yes, Localize will stop ingesting new content into your dashboard.
    • Speak with your Customer Success Manager or submit a support ticket.