Build a single post layout in Elementor and you hit the problem immediately. You type the title, and now that layout works for exactly one post. Type the date, the author, the featured image, and you have built a page, not a template.
Dynamic tags are the fix. Instead of typing a value into a field, you attach a source to it. The field then reads whatever the current post, term, user or site holds, so one design serves every post you will ever publish.
Sky Addons registers 55 of them on a standard WordPress install, and another 22 appear when WooCommerce is active. They cover post data, site data, archive data, terms, users, custom fields and ACF.
| Typing the value | Dynamic tags | |
|---|---|---|
| Works for | One post | Every post |
| Updating a title | Edit the template | Edit the post |
| New posts | Need a new layout | Use the existing template |
| Custom fields | Not possible | Text, image, URL and gallery |
| Archive headings | Hardcoded | Read from the term |
| Risk of going stale | High | None |
A template with typed values is just a page with extra steps. The tag is what turns a design into something that keeps working after you stop looking at it.
They fall into groups, and knowing the groups is faster than scrolling the list.
Post data, the largest group. Title, content, excerpt, ID, slug, status, type, date, time, author, comments count, terms and the featured image. This is what a single post template runs on.
Archive data. Archive title, description and meta, so one archive template labels itself correctly whether someone is browsing a category, a tag, an author or a date.
Site and search data. Site title, tagline, logo, icon and URL, plus the search query and the result count.
Term and user data. Term title, slug, ID, description and post count. User info, user meta and the author avatar.
Custom fields and ACF. A generic custom field tag for post meta, plus dedicated ACF tags for text, image, URL, date and gallery fields.
WooCommerce, when it is installed. Price, SKU, stock, rating, sale state, shipping, attributes, description, product images and a set of URLs including add to cart and checkout. These stay dormant on a site without WooCommerce rather than cluttering the list.
Each tag declares what kind of value it produces, so a field only offers the tags that fit. An image control offers image tags. A link control offers URL tags. You cannot put a gallery into a heading, and the interface will not let you try.
The obvious benefit is that one template replaces hundreds of pages. The real benefit is that content and design stop being the same job. An editor updates a post and the layout follows, with nobody opening Elementor.
It also removes a whole class of slow decay. Typed values go stale silently: a year in a footer, an author name on a template, a price in a heading. A field bound to its source cannot drift, because there is nothing to forget to update.
Custom fields are where it gets genuinely powerful. Once ACF fields are available as tags, a custom post type stops needing a developer for every layout change. WordPress post metadata becomes something a designer can lay out directly, and ACF’s own field types map onto tags that respect what each field holds.
Dynamic tags answer one question: what value goes in this field, for the thing currently being viewed. They are deliberately narrow, and knowing the edge saves a lot of wasted searching.
They do not choose which posts appear. A tag reads the current post. Deciding that a grid should show the six most recent posts in one category, excluding the one already on screen, is a query, and that belongs to the widget’s own query settings or the query builder. People often go hunting for a dynamic tag that filters a list, and there is not one, because filtering is not what a tag does.
They do not do arithmetic or formatting beyond what each tag offers. A price tag returns the price as WooCommerce formats it. A date tag offers date formats. If you need a value calculated from two other values, that is a custom field holding the result, not a tag.
They also do not reach across posts. A tag on a single post template reads that post. It cannot read the previous post, or the parent, or an unrelated page, with the exception of the navigation URL tags that exist precisely because that case comes up so often.
Inside those limits, dynamic tags are close to unlimited, and the limits themselves are useful information. If you find yourself trying to make a tag do selection, formatting or cross referencing, the answer is a query, a field or a template condition, and you will find it much faster once you stop looking in the tag list.
field_1 tells you nothing at the moment you are choosing.Yes, the tag set ships in the free Sky Addons plugin and is switched on by default in the Advanced tab. The free versus Pro page covers what Pro adds elsewhere.
No. Free Elementor is enough.
No. ACF tags appear only if ACF is installed, and the generic custom field tag reads ordinary post meta without it.
Yes. Site level tags like the logo and site title are the normal way to build a header in the theme builder.
The fallback renders. If you did not set one, the field renders nothing, which is why the first rule above is the first rule.
Dynamic tags bind a widget field to a real source instead of a typed value, so one template serves every post, product, term or user. Sky Addons ships 55 on a standard install covering post, archive, site, term, user and custom field data, with 22 more for WooCommerce, and they are free.
If you are still typing content into a template, you are maintaining copies of a page that should have been one design.
Start with the dynamic tags documentation and the guide to inserting a dynamic tag. For the templates they feed, read Elementor Theme Builder. Queries are covered in the query builder reference, and licences are on the pricing page.
Comments are closed.