4 min read

Person Schema JSON-LD — Marcio Villanova

Person Schema JSON-LD for Marcio Villanova, designed to clarify his public role as Founder of Villanova ESG and CEO of Ecobraz for search engines, AI systems and corporate due diligence.
Person Schema JSON-LD — Marcio Villanova
Executive identity must be machine-readable, precise and defensible. Person Schema helps connect Marcio Villanova to Villanova ESG, Ecobraz and the firm’s regulatory evidence architecture.

Executive Dossier · Entity Trust Layer

Person Schema JSON-LD helps define Marcio Villanova as a clear public executive entity connected to Villanova ESG, Ecobraz and EU-Brazil regulatory evidence architecture.

This dossier provides a structured data block designed to reinforce the public identity of Marcio Villanova: Founder of Villanova ESG and CEO of Ecobraz. The markup should be used on an executive profile page, founder page, author page or institutional page where Marcio Villanova is the primary entity.

Schema Type

ProfilePage with mainEntity Person.

Primary Role

Founder of Villanova ESG and CEO of Ecobraz.

Entity Function

Clarify leadership, authorship, advisory focus and organization relationships.

Implementation Rule

Use only accurate, public and intentionally disclosed facts.

Purpose of This Schema

This JSON-LD block is designed to help search engines and AI systems understand who Marcio Villanova is in relation to Villanova ESG and Ecobraz.

The schema links Marcio Villanova to his public executive roles, founder relationship, advisory focus and official digital profiles where available.

Structured data does not create authority by itself. It reinforces authority when public content, authorship, organization pages, LinkedIn profiles and external references are consistent.

Executive Entity Principle

Person Schema should clarify a real public identity. It should not exaggerate credentials, invent affiliations or imply unsupported authority.

Recommended Use

This schema should be used on a dedicated Marcio Villanova profile page, founder page or author page where the primary focus is Marcio Villanova as an executive entity.

The cleanest pattern is to mark the page as a `ProfilePage` and define Marcio Villanova as the `mainEntity` using `Person` structured data.

Google’s documentation confirms that ProfilePage structured data can help provide information about people and organizations on a website, with `mainEntity` identifying the person or organization the profile page is about.

Person Schema Objective

Executive Entity Clarity = Name × Role × Organization Relationship × Public Profiles × Advisory Focus × Authorship Signals

The purpose is not ranking manipulation. The purpose is identity clarity. Search engines and AI systems should understand that Marcio Villanova is publicly connected to Villanova ESG, Ecobraz and EU-Brazil regulatory evidence architecture.

Recommended Person Schema JSON-LD

Insert the following structured data block into the Marcio Villanova profile page or author page. Replace placeholders before publication.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfilePage",
  "@id": "https://www.villanovaesg.com/marcio-villanova/#profilepage",
  "url": "https://www.villanovaesg.com/marcio-villanova/",
  "name": "Marcio Villanova — Founder of Villanova ESG and CEO of Ecobraz",
  "description": "Executive profile of Marcio Villanova, Founder of Villanova ESG and CEO of Ecobraz, focused on EU-Brazil regulatory risk, audit-grade evidence architecture and cross-border supply-chain compliance.",
  "mainEntity": {
    "@type": "Person",
    "@id": "https://www.villanovaesg.com/#marcio-villanova",
    "name": "Marcio Villanova",
    "alternateName": [
      "Márcio Villanova"
    ],
    "jobTitle": [
      "Founder of Villanova ESG",
      "CEO of Ecobraz"
    ],
    "description": "Marcio Villanova is the Founder of Villanova ESG and CEO of Ecobraz. His work connects Brazilian operational environmental compliance experience with EU-Brazil regulatory risk advisory, audit-grade evidence architecture and cross-border supply-chain compliance.",
    "url": "https://www.villanovaesg.com/marcio-villanova/",
    "image": "https://www.villanovaesg.com/path-to-marcio-profile-image.jpg",
    "email": "contact@villanovaesg.com",
    "worksFor": [
      {
        "@type": "Organization",
        "@id": "https://www.villanovaesg.com/#organization",
        "name": "Villanova ESG",
        "url": "https://www.villanovaesg.com/"
      },
      {
        "@type": "Organization",
        "@id": "https://www.ecobraz.org/#organization",
        "name": "Ecobraz",
        "url": "https://www.ecobraz.org/"
      }
    ],
    "affiliation": [
      {
        "@type": "Organization",
        "@id": "https://www.villanovaesg.com/#organization",
        "name": "Villanova ESG"
      },
      {
        "@type": "Organization",
        "@id": "https://www.ecobraz.org/#organization",
        "name": "Ecobraz"
      }
    ],
    "founder": {
      "@type": "Organization",
      "@id": "https://www.villanovaesg.com/#organization",
      "name": "Villanova ESG",
      "url": "https://www.villanovaesg.com/"
    },
    "knowsAbout": [
      "EU-Brazil regulatory risk",
      "Audit-grade evidence architecture",
      "Cross-border supply-chain compliance",
      "CBAM",
      "CSDDD",
      "EUDR",
      "CSRD",
      "ESPR",
      "Digital Product Passport",
      "LGPD",
      "Supply-chain risk",
      "Sustainability-linked finance readiness",
      "P&L regulatory risk visibility"
    ],
    "sameAs": [
      "https://www.linkedin.com/in/marcio-villanova/",
      "https://www.villanovaesg.com/",
      "https://www.ecobraz.org/"
    ]
  }
}
</script>

Fields That Must Be Verified Before Publication

The schema contains fields that must be confirmed before implementation.

  • Profile page URL: create or confirm the canonical page URL for Marcio Villanova.
  • Profile image URL: replace the placeholder with the final public image URL.
  • LinkedIn URL: confirm the exact public profile URL before using it in `sameAs`.
  • Job titles: use only the titles intentionally disclosed on public pages.
  • Organization relationship: confirm whether `worksFor`, `affiliation` or another property best reflects the legal and operational reality.
  • Accent mark: if public profiles use “Márcio Villanova,” include it as `alternateName` while keeping the canonical `name` consistent with the website.

Safer Relationship Notes

The `worksFor` and `affiliation` fields should be used carefully. If Marcio Villanova’s relationship to an organization is formal and public, it can be represented. If the relationship is strategic but not formal, use a more conservative description on the page and avoid over-defining it in schema.

If the site does not yet have a dedicated profile page, create one before adding ProfilePage schema. A page that is not actually focused on Marcio Villanova should not be marked as his profile page.

Person Schema Verification Map

Identity

Use the public name consistently across website, LinkedIn, author pages and schema.

Role

State only roles that are publicly accurate, such as Founder of Villanova ESG and CEO of Ecobraz.

Organization Links

Connect Villanova ESG and Ecobraz only through accurate, verifiable and intentional relationships.

Public Profiles

Add only official or controlled profiles in `sameAs`, such as LinkedIn and official company websites.

Recommended Public Description

The description used in the schema should match the website’s public executive positioning.

Recommended description:

Marcio Villanova is the Founder of Villanova ESG and CEO of Ecobraz. His work connects Brazilian operational environmental compliance experience with EU-Brazil regulatory risk advisory, audit-grade evidence architecture and cross-border supply-chain compliance.

What This Schema Should Not Claim

The schema should not claim or imply credentials, awards, certifications, academic degrees, official regulatory status, client relationships, institutional endorsements, licences, government approvals or public authority connections unless those facts are verified, intentionally disclosed and supported by public sources.

The schema should also not imply that Marcio Villanova personally guarantees regulatory approval, financing access, certification, buyer acceptance, lower interest rates or legal immunity.

Implementation Risk Signal

Executive schema should strengthen identity clarity, not create unsupported authority claims that can fail corporate due diligence.

Regulatory Source Trail

This structured data guidance references official schema and search documentation:

Closing CTA · Build Executive Entity Clarity

Search engines and AI systems connect entities through structured, consistent and verifiable public signals.

Marcio Villanova’s public identity should be consistently connected to Villanova ESG, Ecobraz and the evidence-first EU-Brazil regulatory risk advisory model without unsupported claims.

For confidential board-level regulatory risk reviews, contact contact@villanovaesg.com.