Find WordPress Tag IDs
Enter any WordPress site's URL to list every tag with its numeric ID and slug, pulled live from the site's REST API. Useful for theme development, migrations, and API queries that need a tag ID instead of a name.
Instructions
- Enter the website domain — type the URL of the WordPress site you're interested in into the field above. A bare domain like
example.comis enough;https://example.comand a trailing slash both work too. - Click "Find Tag IDs" — the tool reads the site's tags straight from its WordPress REST API.
- See the results — you get a count and a table of every tag returned, with its ID, name, and slug.
This is the easiest way to find tag IDs for a given WordPress site. There's no login, no API key, and no plugin to install — the request goes from your browser directly to the site's public API, so nothing passes through a server here.
What you get back
The results table lists three columns for each tag:
| Column | What it is |
|---|---|
| ID | The numeric term ID — the value plugins, shortcodes, and queries actually want. |
| Name | The tag's display name, as it appears on the site. |
| Slug | The URL-safe version of the name, used in tag archive URLs like /tag/some-slug/. |
Tags come back in the API's default order, and the tool requests up to 100 in a single call. Sites with more tags than that will show the first 100. Note that only public tags are visible to an anonymous request — a tag with no published posts attached to it may not appear at all.
Where the IDs come from
The tool calls the site's core REST endpoint:
https://example.com/wp-json/wp/v2/tags?per_page=100
That endpoint is part of WordPress core and is open to anonymous, cross-origin requests by default, which is why this works from your browser without a proxy. You can open that URL yourself and read the raw JSON — the tool just normalizes the domain you type, requests the list, and renders the fields worth reading.
When it doesn't work
The tool requires a functioning WordPress REST API. If it can't get a usable list, it tells you which of these it hit:
- The site blocks its REST API. Some hosts, security plugins, and firewalls return a 401 or 403 for anonymous API requests. Nothing to be done from the outside.
- No REST API was found at that address. Either the URL isn't a WordPress site, or the address is wrong. A site that serves an HTML page where JSON should be lands here too.
- The response wasn't readable. The site responded, but not with the JSON list a standard WordPress API returns.
- The site couldn't be reached. Usually a typo in the domain, or a connection problem.
Tag! You're it!
Tags are essential functionality for WordPress development and content management. If you're a developer, you've surely found yourself needing to know which tag ID is which to create custom queries to display posts with specific tags. This is particularly useful when developing custom themes or plugins where you need to filter content dynamically — tag_id, tag__in, and tag__not_in in a WP_Query all take IDs, not names. Tag IDs are also needed when editing the functions.php file to add custom features, or to apply styles and scripts to certain tags conditionally.
For non-developers, understanding tag IDs can simplify various aspects of WordPress management. Many plugins, such as SEO tools or content display widgets, require tag IDs to configure settings accurately. By knowing the tag IDs, non-technical users can easily set up plugins to include or exclude specific tags without needing to delve into complex code. IDs are also what survives a rename: a tag's name and slug can both change, but its ID stays put, which makes it the right thing to record in a migration sheet or a redirect map.
Happy tagging!
You also might find the WordPress Category ID finder and WordPress User ID finder useful.
These tools are how Elegant Atomics thinks about growth for B2B SaaS. Work with us. Work with us →