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, which is exactly where the audit problem starts.

SleekView reads the same wpas_author_slug usermeta key and joins it with role, post count and slug last modified. Display name, custom slug, slug pattern, role, post count and slug modified become first-class columns with sort, filter and inline edit. An admin can pull every user without a custom slug, an SEO lead can scope to a single slug pattern, and an editorial manager can sort by post count to see which active authors still expose the default /author/<username>/ URL.

The plugin stays exactly as it is. Per-user slug edits still happen on the user profile screen and the archive base still lives in the plugin's settings page. SleekView adds the cross-user audit surface that the workflow has always needed.

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 reads the wpas_author_slug usermeta key and renders coverage, pattern mix and per-role gaps as sortable columns. The plugin stays as small and focused as ever, and the team finally has a way to confirm the configuration actually covers everyone it should.