-
I have a website where I’m the sole admin and also the sole author of the content. For convenience, I use the same login for both admin work and authoring content. In the past, when I tried to use a different, non-admin login for authoring content, I would sometimes use the wrong one.
Now I find that all the content pages include a link to an author page in the schema. (Sensitive data below.) The URL for this author page includes the username for the author, which is also the username for the admin.
Should I be concerned that this username is exposed in the schema on all the content pages of the website? Is there a way to avoid this, without maintaining separate logins for admin and authoring? For example, can I change the slug for the author page so it doesn’t include the username? Any other suggestions?
The ticket ‘Username exposed in schema’ is closed to new replies.