Open WP Visibility → Settings and scroll to the Schema section. Set This site represents to An organization for a business or A person for a personal site, fill in the fields for that choice, add your official account links under Social profile URLs, then click Save changes. WP Visibility then names that entity as the publisher in every page’s structured data.
Before you start
The Schema module is on by default. If the section is missing, turn it on under Modules, click Save changes and reload the page. Have the facts ready: the legal or trading name you want shown, a logo file in the media library, and the URLs of accounts you actually control.
For an organization
| Field | What to enter |
|---|---|
| This site represents | An organization |
| Organization name | The name as you want it published. Leave it empty and the site title is used. |
| Organization logo | Click Select image, pick the logo from the media library and click Use this image. The full-size file is used. |
| Social profile URLs | One official profile per row; Add profile URL adds a row. |
The result is an Organization node with @id https://your-site.com/#organization, its name and URL, the logo as an ImageObject, and your profiles as sameAs.
For a person
| Field | What to enter |
|---|---|
| This site represents | A person |
| Person (user ID) | The WordPress user ID of the person. It is a number; when you edit another user under Users, it appears after user_id= in the address bar. Your own account opens the profile screen, which does not show it (get_edit_user_link); wp user list shows every ID (WP-CLI). Checked September 27, 2026. |
| Social profile URLs | The person’s official profiles. |
The result is a Person node (typed as both Person and Organization) with @id https://your-site.com/#person, the user’s display name, their author archive as the URL, their avatar as the image, and the profiles as sameAs. The organization name and logo are ignored in this mode. If the user ID does not match a user with a display name, WP Visibility falls back to the organization node.
What the rest of the graph does with it
Every page carries one JSON-LD graph. The publisher node comes first, then WebSite (#website, with the site title, tagline and language), then the page itself (WebPage, CollectionPage on archives, or ProfilePage on an author archive), a BreadcrumbList, and on blog posts a BlogPosting node whose publisher points at your organization or person, followed by a Person node for the post’s author. Search results and the 404 page print no structured data.
Check the output
- Open the homepage, view the page source and find the
application/ld+jsonscript. The first node should be your organization or person. - Paste the URL into Google’s Rich Results Test or the Schema Markup Validator. Checked September 27, 2026.
- With Aggregate schema endpoint on (the default), the section shows a View schema graph link. It opens
/wp-json/wpvis/v1/schema-map, which publishes the publisher andWebSitenodes on their own. It is cached for up to 12 hours, so a change to the person’s display name or avatar, or to the logo file itself, can take that long to appear there. The pages update at once.
Things to know
- Profiles are not verified. WP Visibility publishes the links you enter; it does not confirm you own the accounts. Add only accounts you control.
- The site audit reports “The site’s represented entity is not configured” when organization mode has an empty Organization name, or when person mode has no user ID. With an empty name the organization node still prints using the site title; fill in the name to clear the warning.
- Ratings and reviews are never added to the organization. The plugin does not generate self-authored review markup.
- Developers can change a node with the
wpvis_schema_piece_organizationorwpvis_schema_piece_personfilter (the person filter also runs on article author nodes), or the whole graph withwpvis_schema_graph, which does not run on the schema-map endpoint.
Behavior checked against WP Visibility 2.10.3.