Tags in Joomla

2. Creating and Managing Tags

2.1 Creating a Tag

To create a tag on its own, go to:

Components → Tags → New

Two fields matter most:

• Title: the human-readable label shown on the site and in lists.
• Alias: the short, URL-safe name. Joomla generates it from the title if you leave it empty.

2.2 Creating Tags On the Fly

You rarely need the New screen. When you edit an article, the Tags field lets you type a new word and press Enter. Joomla creates the tag immediately and links it to the item. This is fast, but it is also where most messy tag lists begin (see Common Mistakes).

2.3 The Tag Edit Screen

The edit screen is split into tabs, much like a category:

2.4 Key Fields Explained

• Parent: leave at the default root for a flat tag, or pick another tag to nest inside.
• Status: Published, Unpublished, Archived, or Trashed. Only published tags appear on the site.
• Access: Public, Registered, Special, or a custom level. A tag the visitor cannot access is hidden from them.
• Language: bind the tag to one site language, or leave it as "All".
• Description: shown at the top of the tag page on the frontend.

4. Tagging Your Content

4.1 The Tags Field

You tag an item from the item's own edit screen. For an article, open it and find the Tags field on the right-hand column:

Content → Articles → (open an article) → Tags

Start typing. Joomla suggests existing tags as you type. Pick one, or type a new word and press Enter to create and attach it in one step. You can add as many tags as you like to a single item.

4.2 The Same Field Everywhere

The Tags field looks and behaves the same on articles, contacts, newsfeeds, and categories. Any extension that opts in to tagging shows the identical control. This consistency is one of the quiet strengths of the system.

4.3 Batch Tagging

In the Articles list you can tag many items at once. Select several articles, open the Batch tool at the bottom of the list, choose a tag, and apply. This is the fastest way to add a topic tag to existing content without editing each item.

4.4 What Happens When You Save

When you save a tagged item, Joomla does not store the tags inside the article row. Instead it writes one row per tag into a separate mapping table that links the item to each tag. We look at that table in the developer section.

6. Tags versus Categories

Tags and categories look similar in the backend but solve different problems. Choosing the wrong one is the single most common tagging mistake.

A short way to remember the difference:

Categories define what content is.
Tags describe what content is about.

Most content needs exactly one category and a small handful of tags. If you reach for many categories per item, you probably wanted tags. If you create a brand new tag for almost every article, you probably wanted a category.

8. Under the Hood (Developer View)

8.1 Two Core Tables

Tagging uses two tables. The first stores the tags themselves:

#__tags
 id, parent_id, lft, rgt, level, path
 title, alias, note, description
 published, access, language
 params, metadesc, metakey, metadata
 images, urls, hits, version
 publish_up, publish_down

You will notice it is almost identical to #__categories: same nested set columns, same publishing and metadata fields. Tags are, in effect, a second taxonomy tree.

8.2 The Mapping Table

The link between an item and its tags lives in a separate table:

#__contentitem_tag_map
 type_alias        e.g. com_content.article
 core_content_id   PK from #__ucm_content
 content_item_id   PK from the real content table (e.g. #__content)
 tag_id            PK from #__tags
 tag_date          when the link was saved
 type_id           PK from #__content_types

Each tagged item produces one row per tag. This is a classic many-to-many design: one item links to many tags, and one tag links to many items.

8.3 Querying Tags with SQL

Once you know the two tables, direct queries are short. List every published tag:

SELECT id, title
  FROM #__tags
 WHERE published = 1
 ORDER BY title;

Find the tags attached to one article (id 101) by joining the map to the tags table:

SELECT t.id, t.title
  FROM #__tags AS t
  INNER JOIN #__contentitem_tag_map AS m
     ON m.tag_id = t.id
 WHERE m.type_alias = 'com_content.article'
   AND m.content_item_id = 101;

Count how many items carry each tag, most-used first:

SELECT m.tag_id, COUNT(*) AS total
  FROM #__contentitem_tag_map AS m
 GROUP BY m.tag_id
 ORDER BY total DESC;

Always filter on type_alias as well as content_item_id. The id 101 is only unique within a content type, so an article and a contact can share the same numeric id.

8.4 The UCM Layer

Tags rely on Joomla's Unified Content Model (UCM). This is the abstraction that lets one tagging system work for articles, contacts, and custom items alike. Three tables support it:

This is why the map table has both a core_content_id (UCM) and a content_item_id (the real row). UCM gives Joomla a single, consistent way to talk about "an item" no matter which component owns it.

8.5 The Tags API in PHP

You rarely touch the tables directly. The TagsHelper class does the work:

use Joomla\CMS\Helper\TagsHelper;

$tagsHelper = new TagsHelper();

// All tag ids on a given article:
$tagIds = $tagsHelper->getTagIds(42, 'com_content.article');

// Full tag objects (title, alias, etc.) for an item:
$itemTags = $tagsHelper->getItemTags('com_content.article', 42);

// All items that carry a set of tags:
$items = $tagsHelper->getTagItemsQuery([5, 9]);

8.6 Making a Custom Component Taggable

To add tagging to your own component, you do not rebuild anything. You opt in:

1. Register your type in #__content_types (alias, table mapping, route helper).
2. Have your Table class implement TaggableTableInterface and use TaggableTableTrait.
3. Add a tags field of type="tag" to your edit form.

The trait wires in an observer that writes the map rows automatically whenever you store or delete an item. Your component then gets the Tags field, frontend tag pages, and the modules for free.

8.7 Events and Observers

Tagging happens through a table observer rather than a single dedicated event. When a taggable item is saved, the observer fires alongside the normal content events. Plugins can react with the standard content events using a tag context:

10. SEO and Metadata

10.1 Tag Pages Are Real Pages

Every published tag has its own frontend page that lists the items carrying it. Search engines can index these pages, which makes tags a real SEO asset, or a real SEO liability if you neglect them.

10.2 Give Important Tags Metadata

On the tag's Options and Metadata tab you can set a meta description and a page heading. A tag page with a clear title and description, plus a written description at the top, can rank as a topic hub. An empty tag page with just a list of links rarely does.

10.3 Avoid Thin and Duplicate Tag Pages

Hundreds of tags that each point to one or two items create many thin pages. These can dilute your site in search results. Keep the number of tags small and make sure each tag groups a meaningful amount of content.

10.4 Control Indexing

If you do not want tag pages indexed, set the metadata robots value to noindex, follow on the tag, or handle it globally in your template. This keeps the discovery benefit for visitors while keeping thin pages out of the index.

12. Best Practices

If you only remember a few things from this article, remember these:

• Use categories for structure and tags for topics. They are not interchangeable.
• Define a small, fixed tag vocabulary up front, and reuse it.
• Keep tags flat, lowercase, and consistently spelled.
• Give important tags a real menu item, a description, and metadata.
• Use the Similar Tags module for instant "related content" with no manual linking.
• Prune one-off tags so you do not create thin, low-value pages.
• In custom extensions, opt in with TaggableTableInterface rather than reinventing tagging.

14. Summary

Tags are far more than a text box. They are a second taxonomy that links content across the whole site:

• Discovery: visitors follow topics across categories.
• Relationships: the Similar Tags module builds related-content blocks automatically.
• Flexibility: one item can carry many topics at once.
• Reach: the same system works for articles, contacts, newsfeeds, and custom extensions.
• SEO: well-managed tag pages become topic hubs; neglected ones become thin pages.
• Developer integration: a shared API and a simple opt-in interface.

Used with discipline, tags make a Joomla site easier to explore and easier to grow. Used carelessly, they create sprawl, thin pages, and confusion. The difference is almost always a small, consistent vocabulary and a few clear menu items.

If you are planning a new Joomla site, cleaning up a tag list that has grown out of control, or adding tagging to a custom extension, it pays to get the taxonomy right early. Tags are the quiet web of connections that ties your content together.