by
npc01
1 (0 reviews)
NPC Slug Genius
Automatically generates short English URL slugs from Japanese post titles using AI. BYOK (Bring Your Own Key).
NPC Slug Genius ranks #28,540 among WordPress.org plugins with 20+ active installations, is #1,187 of 4,265 in the SEO & Marketing category, a 1/5 rating from 0 reviews, and was last updated Oct 20, 2026. Data from WordPress.org, refreshed twice daily — see methodology.
Compatible with WP 7.1
v1.1.3
Current Version v1.1.3
Updated 2 weeks ago
Last Update on 20 Oct, 2026
Refreshed 1 week ago
Last Refreshed on
#1,187 of 4,265 in SEO & Marketing
Top 50% by installs
Downloads -33.3% this week
Actively maintained
Rank
#28,540
—
No change
Active Installs
20+
—
No change
KW Avg Position
N/A
—
No change
Downloads
1.4K
+1 today
Support Resolved
0%
—
No change
Rating
20%
Review 1 out of 5
1
(0 reviews)
Next Milestone 30
20+
30+
5,795
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 3 more installs to reach 30+
Rank Changes
Current
#28,540
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.1.3
- Last Updated
- Oct 20, 2026
- Requires WP
- 5.0+
- Tested Up To
- 7.1
- PHP Version
- 7.4 or higher
- Author
- npc01
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,757
Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits
30K+ installs
#1,015
Yoast SEO – Advanced SEO with real-time guidance and built-in AI
10M+ installs
#2
Rank Math SEO – AI SEO Tools to Dominate SEO Rankings
4M+ installs
#13
Redirection
2M+ installs
#21
All in One SEO – AI SEO Plugin to Boost SEO Rankings & Traffic (Schema, Local SEO, Sitemap & SEO Insights)
2M+ installs
#22
MC4WP: Mailchimp for WordPress
1M+ installs
#35
Hostinger Reach – AI-Powered Email Marketing for WordPress
1M+ installs
#41
XML Sitemap Generator for Google
1M+ installs
#56
EWWW Image Optimizer
1M+ installs
#60
Frequently Asked Questions
Common questions about NPC Slug Genius
Yes. You need an API key from one of the supported providers (Anthropic, OpenAI, or Google). You only need one - whichever you prefer.
Each slug generation is one API request: a fixed instruction text included in the plugin (about 3 KB) plus the post title, with a reply limited to 64 tokens. The plugin uses a low-cost model from each provider (Claude Haiku 5.5, GPT-6 Luna, Gemini 3.5 Flash-Lite). The actual cost depends on the provider's current pricing and on how often you save posts that need a new slug, so please check your provider's pricing page.
Yes. You can change the active provider from the settings page anytime. API keys for unused providers are kept in your settings (but never sent anywhere) until you delete them.
The plugin fails silently. Your post saves normally with the default WordPress slug behavior (which keeps the Japanese title as the slug). No errors are shown to the visitor. If the provider does not respond, saving may take up to 30 seconds while the plugin waits for it. When the API call succeeds again, saving such a post replaces its Japanese slug if the post meets the conditions in "Which posts does this plugin process?" below, which changes its URL.
The post type is selected in the settings. An API key is set for the active provider. The post has a title, it is not an auto-draft, a revision, an attachment, or in the trash, and the user saving it has permission to edit it. The current slug is empty, contains non-ASCII characters such as Japanese, or contains a percent sign followed by two hexadecimal digits (the percent-encoded form that WordPress uses for Japanese, such as %e3). The slug is not locked (see the next question). One of these applies: this plugin has generated a slug for the post before; you enabled "Also process posts created before plugin activation"; or the time the plugin was first activated on this site is recorded and the post is dated on or after it (posts that have no date yet, such as most unpublished drafts, count as new). The activation time is normally recorded when the plugin is activated. If the API call fails, the AI's reply is cut off before it is complete (for example, at the reply limit), or WordPress cannot save the new slug, the post saves normally and the slug is not changed.
Yes. A slug that you type yourself using only English letters, numbers and hyphens is never replaced. Once this plugin has generated a slug for a post, saving the post with a different, non-empty slug locks it. After that, the plugin does not generate a slug for that post again, even if you change the slug back to Japanese. On a published post, WordPress fills an empty slug from the title, so clearing the slug field usually results in a locked Japanese slug. One exception to this lock: if the slug is exactly the one that WordPress makes from the generated slug when the post is published under its current parent, it does not count as a change and does not lock the slug. A slug that you type yourself is not locked either if it is exactly that slug. WordPress adds a number such as "-2" in these cases: Another post already uses the slug (for example, "contact-2" when you publish a draft whose slug "contact" is used by another post). The slug is a reserved word such as "feed". The slug is made only of numbers, depending on the post type and permalink settings. The slug can still be locked in these cases: You move a draft or pending page (or a post of another type that can have a parent) to another parent, or out from under its parent, in Quick Edit (WordPress adds the number based on the previous parent). The post got the number while it was saved without this plugin's check (for example, while the plugin was inactive, while its post type was not selected in the settings, by a user or tool without permission to edit it, or while version 1.1.1 or earlier was active), and the slug without the number (for example, "contact") became free before the post was saved again (for example, the other post that used it was deleted, moved to the Trash, or given a different slug). Version 1.1.1 or earlier could not save the generated slug for the post, so the post still has its Japanese slug. Slugs that were locked by an earlier version stay locked after updating.
The post title, together with a fixed instruction text included in the plugin and the API key of the selected provider (for authentication). The post content, author, categories, tags, and other user data are not sent. If the title itself contains personal information (for example, a person's name), that text is sent as part of the title. See "External services" below for details.
Yes. Public post types, including public custom post types, are listed under Settings > NPC Slug Genius. Check the ones you want.
Not by default. Posts dated before the plugin was first activated on this site are skipped, to protect existing URLs. The settings page shows this time as "Plugin was activated on". Deactivating and reactivating the plugin does not change it; deleting the plugin resets it. However, a post dated on or after that time that still has a Japanese slug (for example, because the plugin was inactive, no API key was set, or the API call failed when the post was published) gets an English slug the next time it is saved, if it meets the conditions in "Which posts does this plugin process?" above. This changes its URL. If you want older posts to be processed as well, enable "Also process posts created before plugin activation" in the settings. This does not convert posts in bulk: each post is processed the next time it is saved (warning: this changes existing URLs). Locked slugs are not changed.
