by
Slug Sync
1 (0 reviews)
SlugSync
Preview and safely regenerate content slugs, with transliteration, WooCommerce SKU cleanup, redirects, reports and undo.
SlugSync ranks #58,200 among WordPress.org plugins with 1+ active installations, is #6,313 of 12,226 in the E-commerce category, a 1/5 rating from 0 reviews, and was last updated Aug 31, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.0.0
Current Version v1.0.0
Updated 2 weeks ago
Last Update on 31 Aug, 2026
Refreshed 9 hours ago
Last Refreshed on
#6,313 of 12,226 in E-commerce
Actively maintained
Rank
#58,200
—
No change
Active Installs
1+
—
No change
KW Avg Position
28
—
No change
Downloads
75
+6 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 10
0+
10+
57,487
Ranks to Climb
-
Growth Needed
8,000,000
Active Installs
Pro
Unlock Exact Install Count
See the precise estimated active installs for this plugin, calculated from real-time ranking data.
- Exact install estimates within tiers
- Track install growth over time
- Milestone progress predictions
Need 8 more installs to reach 10+
Rank Changes
Current
#58,200
Change
Best
#
Downloads Growth
Downloads
Growth
Peak
Upgrade to Pro
Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.
Upgrade NowReviews & Ratings
1.0
0 reviews
Overall
20%
5
0
(0%)
4
0
(0%)
3
0
(0%)
2
0
(0%)
1
0
(0%)
Track This Plugin
Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.
Start Tracking FreePlugin Details
- Version
- 1.0.0
- Last Updated
- Aug 31, 2026
- Requires WP
- 5.6+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- Slug Sync
Support & Rating
- Rating
- ★ ☆ ☆ ☆ ☆ 1
- Reviews
- 0
- Support Threads
- 0
- Resolved
- 0%
Keywords
Upgrade to Pro
Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.
Upgrade NowSimilar Plugins
Adminify – White Label, Admin Menu Editor, Login Customizer
6K+ installs
#2,752
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,007
WooCommerce
7M+ installs
#6
MonsterInsights - Google Analytics Dashboard for WordPress (Website Stats Made Easy)
2M+ installs
#25
ManageWP Worker
1M+ installs
#54
Google for WooCommerce
800K+ installs
#75
WooPayments: Integrated WooCommerce Payments
800K+ installs
#76
WooCommerce PayPal Payments
800K+ installs
#81
WooCommerce Stripe Payment Gateway
700K+ installs
#85
WooCommerce Tax (formerly WooCommerce Shipping & Tax)
500K+ installs
#115
Frequently Asked Questions
Common questions about SlugSync
For posts, products and other content that does not nest inside a parent, old URLs keep redirecting, because the plugin records each previous slug the way WordPress does. The exported redirect map is there as a second layer, and for anything you would rather handle in a dedicated redirect plugin. Pages are the exception and have their own answer below. Purge your page cache and CDN after a run; sitemaps need no resubmission, since Google retired its ping endpoint in 2023.
For posts in the same WordPress slug namespace, the lower post ID is processed first and keeps the clean available slug; the other takes the next numeric suffix. Pages under different parents may both keep the same final segment because WordPress treats those as different namespaces. Every suffix added by WordPress is flagged in the report.
Yes, but read this first, because pages behave differently from posts and products. WordPress only records a previous slug for content that does not nest inside a parent, so it will not redirect an old page URL by itself. Import the redirect report into a redirect plugin instead. There is a second consequence. A page's URL contains its parents' slugs, so renaming a parent also changes the URL of every page beneath it. Those child URLs are not in the reports, which list only the items whose own slug changed, and for the same reason a preview of a child shows the parent's current slug rather than its new one. Check what sits under anything you rename. Posts, products and other non-nesting types are unaffected by either point, and the plugin says all of this on screen when you select a nesting type.
No. Variations are a separate post type and are never listed.
No. It writes the same sounds with readable Latin characters, such as Кофеварка to kofevarka. It does not change the visible title, infer another language, or contact an external translation service. Cyrillic and Greek come from a map bundled with the plugin; additional scripts are available when the server provides PHP's international transliterator. Always review the preview for the language used on your site.
For Cyrillic and Greek, yes. Those two scripts are resolved by the bundled map before PHP's international transliterator is consulted, so a site moved between hosts does not regenerate different URLs for the same titles. Greek follows ELOT 743 and reads vowel pairs as pairs, so Φίλτρου becomes filtrou rather than filtroy, and Λευκάδα becomes lefkada. Scripts outside the bundled map, such as Chinese, are handled only where the server provides the international transliterator, so those do depend on the host.
Free can leave out the exact WooCommerce SKU saved on that product when the same value appears as a separate part of its title, or add the assigned SKU from Product data → Inventory when it is absent. Other model numbers and codes remain, and the same SKU is never added twice. If removing it would leave fewer than two useful name words, SlugSync keeps the original title source instead. Pro adds broader configurable code, filler-word and replacement rules.
Yes. Previous runs provide an Undo changes button for each applied run. Any item whose slug changed again after that run is skipped instead of being overwritten, as is any item whose old slug has since been claimed elsewhere.
It processes in batches and continues automatically, and there is an option to stop after the first batch so you can inspect the result before committing to a full run. Take a database backup first regardless.
