Email Tag Guard
Check Liquid, Mailchimp, and HubSpot merge tags after a translation, or lock them before one. The HTML stays in this tab.
100% client-side: Your email HTML never leaves your browser.
How it works
Email Tag Guard checks merge tags after you translate an HTML email, and it can lock those tags before a translator rewrites the file. A renamed variable, a smart quote inside a filter, or a deleted unsubscribe tag can still look fine in a browser and then fail at send time. It sits next to HTML Translate. For the full workflow, read how to translate an HTML email template without breaking merge tags.
Audit & Diff compares the original template with the translated one. Paste both, or drop a .html, .htm, .mjml, or .txt file. Auto-Detect All reads Liquid (Klaviyo, Shopify, Braze), Mailchimp, Handlebars, HubSpot HubL, and Salesforce AMPscript together. Outlook conditional comments are a checkbox and start turned on.
Tags are counted, not lined up. German, Japanese, and Arabic often move a variable inside the sentence. That move is not an error when the tag text is unchanged and the number of copies matches. A missing tag, a lower count, a translated name, or a changed bracket is a critical error. Smart quotes and HTML entities inside a tag are listed as a mutation, and an unclosed block is listed with its line number.
Protect & Restore is the step before translation. Protect replaces every matched tag with a numbered token. The default token is a bracket pair that most translators leave alone. The other is a span marked translate="no". Download the protected HTML and the JSON map. This page does not store the map. Translate the protected file, paste the result into Restore, and upload the map if you closed the tab. Restore writes each original tag back only when every token is still present once. A missing or duplicated token is listed, and the restore is marked incomplete.
Supported ESP syntax
These are the syntaxes the auditor reads. Custom delimiters are two literal strings, not a regular expression, so a delimiter cannot stall the page.
| Syntax | Example | Blocks |
|---|---|---|
| Liquid | {{ first_name }}, {% if %} | if / endif, for / endfor, unless / endunless, case / endcase |
| Mailchimp | *|FNAME|*, *|UNSUB|* | *|IF:|* and *|IFNOT:|* close with *|END:IF|* |
| Handlebars / HubL | {{#if}}, {{{ name }}} | #if /if, #each /each, #unless /unless |
| AMPscript | %%=v(@name)=%%, %%FirstName%% | No block pairs |
| ActiveCampaign | %UNSUB% | Off in auto-detect, so CSS such as 100% is ignored |
| Outlook MSO | <!--[if mso]> | <![endif]--> |
FAQ
Does Email Tag Guard upload or store my email HTML?
No. The template stays in this browser tab. Audit, protect, and restore do not upload it. The mapping file is created on your machine for you to download. Closing the tab clears the boxes and the map.
Why do translators break Liquid filters and merge tags?
A merge tag looks like a word with odd punctuation, and a Liquid filter looks like copy. A translator may rename the variable, swap in typographic quotes, or encode an apostrophe as an HTML entity. The send then fails while the HTML still opens in a browser.
Does changing word order during translation trigger false errors?
No. Tags are compared by how many times each exact string appears, not by position. Moving a variable to the front of a German sentence is not an error. An error is a tag that was dropped, duplicated, or rewritten.
How can I automate merge-tag checks in CI/CD?
Keep the untranslated template beside each locale file and fail the review when a tag is missing, the count changed, or a block is unclosed. There is no CI plugin here. Use this page on the finished HTML, or copy the same comparison into the script that builds your locale files.