Schema.org Structured Data - Feature Suggestions for upcoming JReviews v6

[n00bster]

First of all, congratulations on the massive improvement the new Structured Data UI brings in v6 beta - mapping custom fields directly to Schema.org properties per Listing Type is exactly the right direction.

However, there is a bottleneck in the variation of outdoor places or activities to list within the structured data for good results.
I'm running a climbing platform built on Joomla + JReviews, and I've been testing on optimizing the structured data on my test site. This gave me a few concrete ideas that I think would make the Schema.org more powerful - especially for niche content types that don't fit neatly into the predefined types.
It would be interesting to know what other JReviews users think about, too.

1. Multiple @type support (additionalType combinations)

Currently the Schema Type selector allows a single combined type like "SportsActivityLocation + LocalBusiness". For many real-world use cases, a listing is better described by combining types that aren't in the current picker - for example:

@type: ["SportsActivityLocation", "TouristAttraction"]

TouristAttraction is specifically designed for places of tourist interest and unlocks properties like touristType, publicAccess, and isAccessibleForFree - all highly relevant for outdoor sports locations. Being able to freely combine 2–3 Schema types (from a curated list or free input) per Listing Type would dramatically improve semantic accuracy.

Proposed UI: A multi-select field input for Schema Types, similar to how tags work - with a curated list of compatible combinations and a warning if types are semantically incompatible.

 

2. additionalProperty mapping for custom fields**

The current Settings Map covers standard Schema.org properties (name, url, geo, address etc.). But for specialized listing types, the most valuable data lives in custom fields that don't map to any standard Schema.org property - for example:

•   Difficulty grade (UIAA): "7+"
•   Number of pitches: 6
•   Wall height: 220m
•   Climbing time: PT3H30M
•   First ascensionist: "G. Rosenberger, 2005" // array or string

The current UI has no way to map custom fields into additionalProperty arrays.
 

Proposed UI: An "Additional Properties" section in the Settings Map where admins can:

•   Add rows with: [Custom Field selector] → [PropertyValue name] + optional [unitCode]
•   Reorder via drag & drop
•   Mark rows as conditional (only output if field is not empty)

This could make JReviews the only Joomla/WordPress review platform capable of generating fully rich Schema.org output for specialized verticals like outdoor sports, real estate, restaurants etc.

 

3. Raw PHP / JSON-LD override per Listing Type

For developers, a "Custom Schema Override" option per Listing Type would be the ultimate escape hatch - similar to how JReviews already handles PHP Output Format for custom fields.

Concretely: a PHP editor (or template file name input, like the fields_phpformat system) where the full $listing array and $CustomFields helper are available, and the developer can return a complete JSON-LD array that JReviews then renders as a <script type="application/ld+json"> block — replacing or merging with the auto-generated schema.

This approach:

•   Requires zero changes to the core schema generation logic
•   Is fully backward compatible
•   Gives developers complete control for edge cases
•   Follows the same pattern already established in JReviews for field output formatting

 

4. Minor: Boolean and free-text default values

For properties like isAccessibleForFree, publicAccess, or touristType that are the same for all listings of a given type, a simple "Default Value" field in the Settings Map (below the field-mapping section, which already exists in part) would avoid needing a dedicated custom field just to carry a constant value.

 

[Alejandro]

This section is only visible with a valid subscription. If you have a valid subscription, please login.