<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Alessandro Verri</title>
    <description>The latest articles on DEV Community by Alessandro Verri (@alessandro_verri_7ced6d8d).</description>
    <link>https://dev.to/alessandro_verri_7ced6d8d</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4244893%2F2f8c9b67-3222-43e3-8a91-a94ee58cefad.jpg</url>
      <title>DEV Community: Alessandro Verri</title>
      <link>https://dev.to/alessandro_verri_7ced6d8d</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/alessandro_verri_7ced6d8d"/>
    <language>en</language>
    <item>
      <title>Model a trading brand and founder without losing the service provider in WordPress</title>
      <dc:creator>Alessandro Verri</dc:creator>
      <pubDate>Tue, 17 Nov 2026 10:35:50 +0000</pubDate>
      <link>https://dev.to/alessandro_verri_7ced6d8d/model-a-trading-brand-and-founder-without-losing-the-service-provider-in-wordpress-4gg9</link>
      <guid>https://dev.to/alessandro_verri_7ced6d8d/model-a-trading-brand-and-founder-without-losing-the-service-provider-in-wordpress-4gg9</guid>
      <description>&lt;p&gt;A WordPress redesign page calls the business “Alder Studio”. The company profile says “Alder Digital Ltd”. The founder has a personal profile under “Maya Chen”. A customer needs to know who actually provides the redesign. In this fictional example, it is Alder Digital Ltd.&lt;/p&gt;

&lt;h2&gt;
  
  
  Give the subjects stable IDs
&lt;/h2&gt;

&lt;p&gt;The organisation and the person each get an ID that can be reused across pages. The organisation's public name and legal name can coexist in one record when they describe the same entity. If the site manages the brand as an independent subject, Schema.org also lets you represent it as a Brand with its own ID and link it via the organisation's brand property.&lt;/p&gt;

&lt;h2&gt;
  
  
  What Neuralis actually publishes
&lt;/h2&gt;

&lt;p&gt;I checked an existing configuration on a WordPress test site. The service page emits a &lt;code&gt;Service&lt;/code&gt; for Web Design and a separate &lt;code&gt;Person&lt;/code&gt; for Alex Rivera. The same organisation ID appears in &lt;code&gt;Service.provider&lt;/code&gt; and &lt;code&gt;Person.worksFor&lt;/code&gt;. I resolved it against the &lt;code&gt;Corporation&lt;/code&gt; node on another page of the same site.&lt;/p&gt;

&lt;p&gt;Here are the relevant fields from those pages, combined for readability. The test hostname is replaced with &lt;code&gt;example.com&lt;/code&gt;.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;[&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Service"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/aim-kg/service/12"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Web Design"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"provider"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/aim-kg/organization/1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Organization"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Person"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/aim-kg/person/17"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Alex Rivera"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"worksFor"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/aim-kg/organization/1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Organization"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="p"&gt;{&lt;/span&gt;
    &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Corporation"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://example.com/aim-kg/organization/1"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Acme Studio"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"legalName"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Acme Studio"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="nl"&gt;"brand"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Acme Studio"&lt;/span&gt;
  &lt;span class="p"&gt;}&lt;/span&gt;
&lt;span class="p"&gt;]&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;The sample organisation uses “Acme Studio” in all three name fields. In the Alder example above, the legal company name and trading brand would be different. In the test output, Alex’s founder role appears in &lt;code&gt;jobTitle&lt;/code&gt;, and the link to the company is &lt;code&gt;worksFor&lt;/code&gt;. A formal Schema.org &lt;code&gt;founder&lt;/code&gt; relationship would be a separate statement.&lt;/p&gt;

&lt;h2&gt;
  
  
  Apply the provider relationship in Neuralis
&lt;/h2&gt;

&lt;p&gt;I developed Neuralis AI Identity Manager for WordPress. Define the Organization and Person separately. Add the company profile to the Organization and Maya’s personal profile to the Person. Define Shop redesign as a Service, select the Organization as its provider and assign the Service to the redesign page.&lt;/p&gt;

&lt;p&gt;Visit the public page and inspect every JSON-LD block. Find the Service node and resolve its provider ID to the intended organisation. If a theme or another plugin emits a separate organisation, check its identifier and reported data before deciding how to handle the overlap. Check that the visible service page names the same provider as the structured output.&lt;/p&gt;

&lt;p&gt;Use the &lt;a href="https://aim.verri.pro/docs/how-to-connect-a-service-page-to-its-provider-in-wordpress/" rel="noopener noreferrer"&gt;Neuralis provider setup guide&lt;/a&gt; for the Service-to-provider configuration.&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
    <item>
      <title>One provider, two WordPress service pages: link them with JSON-LD</title>
      <dc:creator>Alessandro Verri</dc:creator>
      <pubDate>Sun, 15 Nov 2026 11:25:23 +0000</pubDate>
      <link>https://dev.to/alessandro_verri_7ced6d8d/one-provider-two-wordpress-service-pages-link-them-with-json-ld-4l7j</link>
      <guid>https://dev.to/alessandro_verri_7ced6d8d/one-provider-two-wordpress-service-pages-link-them-with-json-ld-4l7j</guid>
      <description>&lt;p&gt;A WordPress site can have one page for tracking audits and another for monthly reporting, both offered by the same studio. If the structured data describes each service on its own, it leaves that relationship unstated. You can fix it on one page first, then reuse the same organization on the next.&lt;/p&gt;

&lt;h2&gt;
  
  
  Before: the service stands on its own
&lt;/h2&gt;



&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Service"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Tracking audit"&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h2&gt;
  
  
  After: the service points to the studio
&lt;/h2&gt;

&lt;p&gt;Here is a minimal, illustrative JSON-LD graph for the audit page. The URLs use a fictional domain.&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight json"&gt;&lt;code&gt;&lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="nl"&gt;"@context"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://schema.org"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
  &lt;span class="nl"&gt;"@graph"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;[&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Organization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://studio.example/#organization"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Example Studio"&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
    &lt;span class="p"&gt;{&lt;/span&gt;
      &lt;span class="nl"&gt;"@type"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Service"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://studio.example/services/tracking-audit/#service"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"name"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"Tracking audit"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt;
      &lt;span class="nl"&gt;"provider"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
        &lt;span class="nl"&gt;"@id"&lt;/span&gt;&lt;span class="p"&gt;:&lt;/span&gt; &lt;span class="s2"&gt;"https://studio.example/#organization"&lt;/span&gt;
      &lt;span class="p"&gt;}&lt;/span&gt;
    &lt;span class="p"&gt;}&lt;/span&gt;
  &lt;span class="p"&gt;]&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On the monthly reporting page, give that service its own ID and reuse &lt;code&gt;https://studio.example/#organization&lt;/code&gt; as its provider. The two services have distinct identities and point to the same provider. If your site already publishes an Organization for that studio, inspect its ID and the existing markup before adding a separate definition.&lt;/p&gt;

&lt;h2&gt;
  
  
  Apply it on an existing WordPress page
&lt;/h2&gt;

&lt;p&gt;I built Neuralis AI Identity Manager. With Neuralis Free, you can define the studio as an Organization, create the Service with that studio as its provider, and assign the Service to the existing audit page. The plugin publishes the relationship in structured data. The snippet above illustrates the relationship; the plugin's generated IDs and graph can differ.&lt;/p&gt;

&lt;p&gt;To verify the change, open the published page and inspect its JSON-LD. Find the tracking audit Service, read its &lt;code&gt;provider.@id&lt;/code&gt;, and check that the ID refers to the studio. When you add the second service, compare its provider ID with the first one. That is the part you can verify directly on your site.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://schema.org/provider" rel="noopener noreferrer"&gt;Schema.org definition of provider&lt;/a&gt; · &lt;a href="https://aim.verri.pro/docs/how-to-connect-a-service-page-to-its-provider-in-wordpress/" rel="noopener noreferrer"&gt;WordPress walkthrough with Neuralis&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: this article was generated with AI under the author’s direction.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>wordpress</category>
    </item>
  </channel>
</rss>
