Home/HighLevel/Features/Marketing/How to fix HTML tags in HighLevel RSS email body

Marketing

How to fix HTML tags in HighLevel RSS email body

In short

When an RSS email shows raw <p> or <br> tags, the feed’s HTML is being escaped. By switching the RSS content placeholder from double braces to triple braces inside a Custom RSS Items layout, HighLevel can render trusted HTML as formatted text, improving readability for recipients.

AreaMarketing · Section
Used forDigital marketing agency, Online magazine, Small ecommerce store
Setup steps11 steps in 2 tasks
Last updatedNovember 17, 2026

01Who this is for

  • Email marketers can ensure their newsletter content appears formatted, not as code.
  • Agency owners can deliver clean RSS driven campaigns to client inboxes.
  • Content publishers can maintain brand consistency when using RSS feeds.

02RSS email bodies, explained

The feature lets you control how RSS feed descriptions are inserted into an email. By default the platform escapes HTML markup, so tags appear as plain text. Changing the placeholder to triple braces tells HighLevel to output the HTML without escaping it.

This setting lives inside the Design Editor. Open the email template, select an RSS Items block, and pick the Custom option under RSS Editing Options. The custom layout contains the variable that you edit.

When the variable uses triple braces, supported HTML such as paragraphs and links renders in the recipient’s inbox, while unsupported tags may still be altered by the email client.

03How businesses use RSS email body

  • Digital marketing agency. The agency opens a client’s RSS email template, selects the RSS Items block, and switches {{rss_item.content}} to {{{rss_item.content}}}. This lets the client’s blog excerpts appear with proper formatting in the campaign.
  • Online magazine. The magazine updates its weekly newsletter template, editing the description variable to triple braces so article snippets retain paragraph breaks and anchor tags when sent to subscribers.
  • Small ecommerce store. The store modifies the RSS product feed email, changing the content placeholder to triple braces so product descriptions with bold or link tags display correctly in promotional blasts.

04How to set up and use RSS email body in HighLevel

Fix HTML tags in RSS email body

  1. Navigate to Marketing > Emails > Templates and open the targeted email in the Design Editor.
  2. Click the RSS Items block and select Custom under RSS Editing Options.
  3. Locate the description variable and replace {{rss_item.content}} with {{{rss_item.content}}}.
  4. Leave the opening and closing loop tags of the RSS Items block untouched.
  5. Save the template.
  6. Important: Triple braces insert HTML without escaping it; use them only with RSS feeds you trust. Unsupported HTML or styling may still render differently across email clients.

Test the RSS HTML fix

  1. In the Email Builder, select Preview.
  2. Open the three dot menu beside Preview and choose Test Email.
  3. Enter the test email details and provide a valid RSS Feed URL.
  4. Send the test email.
  5. Open the received email and verify that paragraphs, links, and other supported formatting display correctly.

05What it looks like in HighLevel

06Settings that matter

  • Custom. Enables a custom layout for the RSS Items block, allowing you to edit the variables that render feed content.
  • RSS Editing Options. Provides the choice between default and custom rendering modes for RSS content within an email template.

07Things to know before you rely on it

  • Triple braces output HTML without escaping it; use only with RSS feeds you trust.
  • Unsupported HTML or styling may still appear differently across email clients.
  • The fix applies only to the description variable; other RSS variables remain unchanged.

08If something goes wrong

  • HTML tags still appear. Verify the RSS Items block is set to Custom and that you edited the correct description variable. Review how the source feed includes its HTML.
  • RSS content is blank. Make sure the test uses a valid RSS Feed URL. For live campaigns, schedule the RSS send rather than using a regular email send.
  • Formatting looks different. Simplify the feed’s markup to use only supported tags and resend a test email.

09How it connects to the rest of HighLevel

Michael's take

Michael Reimer
Michael ReimerFounder of CRM Pros, HighLevel Commander and Certified Admin

Beware that triple braces bypass HTML escaping entirely.

Get More InformationOpens on HighLevelPublished November 3, 2026 · Updated November 17, 2026

Common questions

Common questions about RSS email body.

Why are HTML tags showing in my RSS email?

The feed’s description contains HTML but the default variable {{rss_item.content}} escapes that markup, so tags appear as text.

How do I change the variable to render HTML?

Edit the RSS Items block in Custom mode and replace {{rss_item.content}} with {{{rss_item.content}}}, which outputs the HTML without escaping.

Should I change every RSS variable to triple braces?

No. Only modify fields that need to render trusted HTML. Leave title, URL and other variables in their standard formats.

Does this change edit my website or RSS feed?

No. It only changes how the selected RSS field is displayed inside the email; the source feed remains unchanged.

What if my RSS descriptions are plain text?

Keep the double brace variable. Triple braces are only needed when the description includes HTML.

Will the fix apply to every post in the RSS Items block?

Yes. The Custom RSS Items layout repeats for each post, so the updated variable is used for all items in the block.

Next step

Pick the features that matter. Then get the plan that unlocks them.

Explore the features you want, start with the five at the top, and upgrade through my link when you are ready. The bonuses and the team come with it.

The features directory explains every HighLevel feature in plain English. Browse it to see what the platform can do.

Back to the FeaturesSee the full details
⌃

Site preview

Explore the next page

This destination is reserved in the page inventory and is not built yet.