I really don't understand the way schema has been implemented in Joomla. Suppose I create a website with recipes and set up articles with custom fields for ingredients, cooking time etc. I fill out the all the info and the instructions as the article text. That will be the visual part for the end user / visitor of my site.
With the new schema's I get an extra tab with at least 20 fields I have to fill out by hand, including items like author and published date, which is already set by Joomla. It seems like I have to do a lot of duplicate work to get the schema data (hidden) in my webpage, so the search engine can identify the content. This is a lot of extra work I have to do for each article. Why not map schema data to the existing fields and allow me to tell what custom field belongs to what schema field?
It feels like schema is more bloatware to the user who wants to write a quick post, with more steps he has to take before the article is ready. My customers are not going to use this, in this way.
Or am I missing something here?
With the new schema's I get an extra tab with at least 20 fields I have to fill out by hand, including items like author and published date, which is already set by Joomla. It seems like I have to do a lot of duplicate work to get the schema data (hidden) in my webpage, so the search engine can identify the content. This is a lot of extra work I have to do for each article. Why not map schema data to the existing fields and allow me to tell what custom field belongs to what schema field?
It feels like schema is more bloatware to the user who wants to write a quick post, with more steps he has to take before the article is ready. My customers are not going to use this, in this way.
Or am I missing something here?
Statistics: Posted by stevent — Fri Mar 22, 2024 11:47 am