Choosing a new slug for every post, term, or language version is extra URL design work. Slug-Free Permalinks lets you move that work out of the publishing flow by using an item's ID in the permalink instead.<\/p>\n\n
Select the public post types and taxonomies you want to change, choose a URL format, and keep the rest of your site on its existing permalink structure. The plugin is intentionally focused: it changes URL structure without adding content features or front-end UI.<\/p>\n\n
You can choose between:<\/p>\n\n
\/post\/123\/<\/code><\/li>\n\/post-123\/<\/code><\/li>\n<\/ul>\n\nThe plugin only affects the post types and taxonomies you enable in the settings screen.<\/p>\n\n
What you can configure:<\/p>\n\n
\n- Select individual public post types<\/li>\n
- Select individual public taxonomies<\/li>\n
- Use each selected type's registered rewrite slug for the ID-based route<\/li>\n
- Choose slash or hyphen based ID permalink format<\/li>\n
- Optionally redirect legacy slug URLs to the current ID-based permalink when WordPress can resolve the request<\/li>\n
- Preserve prefixed permalink bases such as
\/en\/<\/code> when another plugin adds them<\/li>\n- Flush rewrite rules automatically when settings change<\/li>\n<\/ul>\n\n
A focused, predictable change<\/h3>\n\n
Legacy slug redirects are optional and only run when WordPress can already resolve the request. Slug-Free Permalinks does not guess at every 404, so it avoids turning an ID-based permalink plugin into a site-wide slug lookup system.<\/p>\n\n
The plugin is intended for new sites, structured-content sites, or projects that are still defining a permalink policy.<\/p>\n\n
If your site already has many established slug-based URLs, review existing inbound links, search traffic, social shares, and editorial workflow assumptions before enabling it.<\/p>\n\n
\n- Plugin page (English)<\/a><\/li>\n
- Plugin page (Japanese)<\/a><\/li>\n
- Development repository<\/a><\/li>\n<\/ul>\n\n
Known limitations:<\/p>\n\n
\n- The settings screen rejects selected post types or taxonomies with identical registered rewrite slugs.<\/li>\n
- Prefixed ID routes reserve the matching path shape, so language or path prefixes should not overlap existing page routes.<\/li>\n<\/ul>\n\n\n
\n- In the WordPress admin screen, go to
Plugins > Add New<\/code>.<\/li>\n- Search for
Slug-Free Permalinks<\/code>.<\/li>\n- Click
Install Now<\/code>, then activate the plugin.<\/li>\n- Go to
Settings > Slug-Free Permalinks<\/code>.<\/li>\n- Choose a permalink format.<\/li>\n
- Check the post types and taxonomies you want to convert to ID-based permalinks.<\/li>\n
- Optionally enable legacy permalink redirects.<\/li>\n
- Save changes.<\/li>\n<\/ol>\n\n
If you prefer manual installation, upload the plugin folder to \/wp-content\/plugins\/<\/code> and activate it from the Plugins<\/code> screen.<\/p>\n\n\n\nDoes this change every post type automatically?<\/h3><\/dt>\nNo. Only the post types and taxonomies you check in the settings screen are affected.<\/p><\/dd>\n
Does it redirect every old slug URL?<\/h3><\/dt>\nNo. Slug-Free Permalinks avoids aggressive 404 slug guessing.\nRedirects only run when WordPress can already resolve the request.<\/p>\n\n
This keeps the plugin lightweight and predictable.<\/p><\/dd>\n
Why not attempt slug lookups for every 404?<\/h3><\/dt>\nPerforming slug lookups on every 404 can introduce unnecessary database queries and unpredictable behavior.<\/p>\n\n
The plugin prioritizes performance and compatibility with WordPress routing.<\/p><\/dd>\n
Does it support pages?<\/h3><\/dt>\nNo. Pages are intentionally excluded to avoid conflicts with typical WordPress page permalink structures.<\/p><\/dd>\n
Does it support taxonomies too?<\/h3><\/dt>\nYes. Public taxonomies with UI support can be switched to the same ID-based format.<\/p><\/dd>\n