This would turn this component from 'great' to 'absolutely brilliant' .

Again, I stress that accommodation is a highly competitive field so not being able to modify the SEO title and description tags is a real roadblock to us using this for many clients.

I would also like the ability to identify meta keywords for individual properties in SP Property.

Also, the SP Property -> Properties pages have no ability to identify a meta description or keywords.

Seems odd that the ability to specify meta description & keywords wouldn't have been built in from day one since SP Page Builder has it. Essentially the SP Property module removes parent functionality.

Is it possible to point me to the file where I could customize the code to add meta keywords for individual properties? At a minimum I would just take the title & add a static string.

I just found that SP Property -> Properties pages do have the ability to set a meta description through the metadata tab on the menu configuration, but it doesn't work.

Yes, there is an issue here. I have added it to our feature list.

You have two options for now:

1. Create an override at /templates/shaper_helixultimate/html/com_spproperty/property and then customize this file: /templates/shaper_helixultimate/html/com_spproperty/property/default.php so it can pull the meta descriptions and inject them into the header when the page loads. However, the downside is that it will inject the same description for all properties.
2. Create a plugin for SP Property, which can dynamically fetch each property’s title and other necessary data, provide options to add them, and render them properly when the page loads.

Thanks.

I was able to add meta keywords for a property by adding the following to the file components/com_spproperty/views/property/view.html.php: $itemMeta['keywords'] = $this->item->title . ", " . "space for lease"; since 'keywords' was already defined in the helper function.

What I really need to fix is the meta description for SP Property -> Properties pages because they just use the global configuration and SEO doesn't like duplicated meta descriptions across pages. Could you point me to the file where this is being set so I can modify the meta description?

Thanks.

I am not referring to an individual property listing, which is the file you pointed me towards. I am referring to when you create a menu page and make the menu item type: SP Property -> Properties it creates a page of properties (of similar type) with an ordering (e.g. office). What file controls this where meta data could be inserted?

You can override the properties listing page at:

/templates/shaper_helixultimate/html/com_spproperty/properties

This functionality has been noted as a feature request for a future update.

Thank you for your understanding.

I found an easier way to correct this deficiency. Instead of making a menu item point directly to the SP Property -> Properties module, have the menu item point to SP Page Builder -> Page and have the page builder page point to the SP Properties module. This then allows you to update the meta description & keywords within Page Builder.

Doing this creates another issue, longer url's (which could approach 100 characters) because "component/spproperty/" is added to the path and "?Itemid=101" is added at the end. Is there a way to remove "?Itemid=101"? Every property listing has it and the property listing can be reached without it.

Hi Scott,

Thanks for sharing your findings and workaround. You’re correct that using a Page Builder page to embed SP Property allows you to edit meta titles, descriptions, and keywords.

Regarding the longer URLs and the ?Itemid=101 issue, this happens because Joomla adds query strings when there isn’t a dedicated menu item for each property. While it’s technically possible to remove this by creating hidden menu items or implementing a custom router override, we do not recommend this approach as it requires deep customizations and development knowledge.

If you want to pursue this, you could either explore these options carefully yourself or consider hiring a developer to implement a proper solution.

Thank you for your understanding.

Best regards,