Website Context Viewer displays the actual website page directly in the Crowdin Editor while translators work. It reads URLs from string context and renders the live website in a side panel, showing translators exactly where and how their content appears.

What you get

• Live website preview displayed right in the Crowdin Editor
• Automatic text highlighting - selected strings are highlighted on the page
• Non-interactive mode - translators can see but not click or interact with the site
• Works with any context source - WPML, headless CMS, or custom integrations

How to add URLs to context

For WPML WordPress users: Install WPML Companion app alongside this one. WPML Companion automatically extracts URLs from WPML XLIFF files and adds them to string context. Zero configuration needed.

For headless CMS and other integrations: You need to add URLs to the string context field in format: URL: https://your-site.com/page

Use apps like Custom Post-Import Processor to automatically add URLs during file import with custom JavaScript code.

How it works

1. Install the app in your Crowdin project
2. Ensure strings have URL: https://... in their context field
3. Open the Editor and select a string
4. The website appears in the right panel
5. Selected text is automatically highlighted on the page

Features

• Proxy technology bypasses X-Frame-Options restrictions
• Smart text matching handles HTML entities and Unicode characters
• Handles complex strings with tags and special formatting
• Visual feedback with loading states and error messages

Perfect for anyone translating website content who wants translators to see the full visual context, not just isolated strings.

Important notes

The app displays the source language website to provide visual context. It does not show a preview of your translation.

Text highlighting uses smart matching to locate content on the page. In most cases, the selected text will be highlighted automatically. However, for some complex strings, dynamically generated content or very short texts, highlighting may not always be possible, or wrong part of the page can be highlighted!

Very short texts (such as "Name") that appear multiple times in different contexts may be highlighted in the wrong order. This is because the app can only find matching text on the page, rather than reliably mapping specific segments from the Crowdin resource file to their exact usage on the website. Even when automatic highlighting isn't available, the website preview will still be displayed to provide visual context.