Example:
The token &mvt:store:name; will not render it's value in Edit Page: Storefront > SEO > Title field.
This forces individuals to modify "hard code" template page.
Here is why I think it's a good idea to to be able to render tokens in Template SEO fields from both an SEO and retailer/owner perspective.
From an SEO perspective, some websites need the ability to list category name breadcrumb on PROD page title and meta description.
From a retailer/owner's perspective, do you really want someone who is not accustom with templates to mess with that? These are fields that require occasional tweaking to improve SERPs, the least people touch templates the better IMO.
Finally, I don't see any cons to enabling the use of tokens in this field, only pros. After all, its not like one is forced to use it. ;)
The token &mvt:store:name; will not render it's value in Edit Page: Storefront > SEO > Title field.
This forces individuals to modify "hard code" template page.
Here is why I think it's a good idea to to be able to render tokens in Template SEO fields from both an SEO and retailer/owner perspective.
From an SEO perspective, some websites need the ability to list category name breadcrumb on PROD page title and meta description.
From a retailer/owner's perspective, do you really want someone who is not accustom with templates to mess with that? These are fields that require occasional tweaking to improve SERPs, the least people touch templates the better IMO.
Finally, I don't see any cons to enabling the use of tokens in this field, only pros. After all, its not like one is forced to use it. ;)
Comment