Set schema_metatag defaults for az_person using the az_seo module.

[trackleft]

Motivation

Schema.org recommends adding structured data to person profile pages to improve their discoverability and accurate representation in search engines.

The relevant schema type is Person, which can be used to describe individual profiles, such as those featured on person pages.

Example JSON-LD output:

Person
Can be used on a page where a person is featured, such as a profile page.
https://schema.org/Person

<script type="application/ld+json">
{
	"@context": "http://schema.org/",
	"@type": "Person",
	"name": "{{node:title}}",
	"hasOccupation": {
		"@type": "Occupation",
		"name": "{{Title/Position}}"
	},
	"worksFor": {
		"@type": "CollegeOrUniversity",
		"name": "University of Arizona {{Department/College}}",
		"url": "{{Department/College url}}",
		"parentOrganization": {
			"@type": "EducationalOrganization",
			"name": "University of Arizona",
			"url": "https://www.arizona.edu/",
			"address": {
				"@type": "PostalAddress",
				"streetAddress": "1401 E University Blvd",
				"addressLocality": "Tucson",
				"addressRegion": "AZ",
				"postalCode": "85721",
				"addressCountry": "US"
			}
		}
	}
}
</script>

Is your feature request related to a problem? Please describe.

Person profile pages currently lack schema.org Person metatags. This means they are not optimized for bots and search engines, potentially affecting how they are consumed and displayed.

---

Proposed Resolution

Describe the Solution You’d Like

• Add schema.org Person metatag defaults to az_person using the az_seo module.
• Populate schema.org fields dynamically with data from az_person nodes.
  • Example mappings:
    • name: Map to node:title fields.
    • hasOccupation.name: Map to appropriate field.
    • worksFor.name: Map to appropriate field.
    • worksFor.url: Map to appropriate field.
    • Add static values for parentOrganization based on University of Arizona defaults.

Describe Alternatives You’ve Considered

• Using custom templates for JSON-LD output directly within person page templates. However, this approach would reduce flexibility and reuse compared to using the schema_metatag module.

---

Roles and Permissions Considerations

Anonymous User

• No impact: Schema metatags are not user-editable and only impact site metadata.

Authenticated User

• No impact.

Content Editor

• Gains the ability to review and modify the fields populating schema.org metatags for az_person nodes through the UI.

Content Administrator

• Gains the ability to manage and configure schema.org defaults for az_person nodes through the az_seo module settings.

Administrator

• Gains full control over enabling/disabling schema.org metatag functionality for az_person nodes site-wide.

---

Additional Context

• This issue is blocked by Add schema_metatag Module to Quickstart's Composer File and as a Dependency for az_seo #3903, which integrates the schema_metatag module into Quickstart and the az_seo module.

---

Conditions of Satisfaction

• Schema.org Person metatag defaults are added to az_person via the az_seo module.
• Metatag fields map dynamically to data in az_person nodes (e.g., name, title, department).
• The generated JSON-LD matches the schema.org Person specification.
• Permissions are configured to allow appropriate roles to manage schema metatags.

---

Next Steps

1. Implement schema defaults in az_seo.
2. Test schema output on az_person nodes.
3. Document any configuration or editing instructions for site administrators and content editors.