Edit Author Slug is the standard solution for changing the /author/<username>/ URL on a WordPress site. It lets an admin pick a custom slug per user (first name, full name, nickname, or a manual value) and rename the /author/ archive base itself (to /writers/, /team/, or anything else). On any multi-author site that takes SEO seriously, it gets installed once and then nobody thinks about it again.

SleekView Charts reads the wpas_author_slug usermeta key the plugin writes and joins it with the user role, post count and last login. A Number card shows how many users have a custom slug set. A Pie shows the split of slug patterns (first name, nickname, manual) across the user base. A Bar shows users by role with and without a custom slug, exposing roles that got missed. An Area trends slug edits over time, useful right after a site-wide migration.

The plugin itself stays exactly as is. Per-user slug edits still happen in the user profile screen and the archive base still lives in the plugin's settings page. SleekView just turns the resulting configuration into a real audit surface, so admins can see slug coverage at a glance and catch the user accounts that never had a custom slug applied.

WordPress exposes /author/<username>/ by default, which is the kind of decision sites quickly want to change. Edit Author Slug is the small, focused plugin that solves it: per-user slug overrides and an archive base rename, with no other behaviour changes. The catch is that it solves the configuration but not the audit, and on a multi-author site the configuration drifts.

New writers get added without a custom slug, a contributor role gets overlooked, a post-migration slug rename gets applied to half the team. SleekView Charts reads the wpas_author_slug usermeta key and renders coverage, pattern mix and per-role gaps as Number, Pie and Bar cards. The plugin stays as small and focused as ever.

The team finally has a way to confirm that the configuration actually covers everyone it should.