On custom page templates such as Properties List or Directory List, the text shown after the listings is usually taken from the theme’s after list text field.
In these page templates, that field is often saved as plain or escaped text, not as full HTML content. Because of this, tags such as <h2> or <h3> may be stored as text and displayed exactly as written, instead of being rendered as headings.
Why does this happen?
This happens because the after listings content is not always processed through a full editor content format.
If the field is saved through a text-only control or with escaped HTML, WordPress will show the tags literally instead of interpreting them as HTML markup.
Can I use the after list text field for heading tags?
Not reliably.
If you add heading tags manually in that field, they may appear as plain text on the front end instead of showing as real headings.
What is the best solution?
If you want reliable heading structure and full layout control, the best solution is to build this page with Elementor instead of relying on the theme’s after list text field.
Recommended Elementor setup
The recommended setup is:
- Remove the current theme page template used for that page
- Build the page with an Elementor Full Width Page layout
- Add a Heading or Text Editor widget before the listings
- Add the Properties List with Filters widget
- Add another Heading or Text Editor widget after the listings
This approach preserves proper semantic H2 and H3 tags and gives you more control over the page structure and content.
Why is Elementor the better option?
Elementor is the better option because it lets you manage headings and text content through normal content widgets, instead of relying on a theme meta field that may not render HTML as expected.
It is also easier to maintain long-term if you want more flexibility in the page design.
Helpful guide
You can use this guide for the Elementor filtered listings widget:
How to manage the WpResidence Properties List with Filters widget for Elementor