[MGNLSTK-408] Adding customized meta tag's and its values - Google Webmaster Tool Created: 30/Jun/09  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Standard Templating Kit (closed)
Component/s: base system
Affects Version/s: 1.1
Fix Version/s: 1.x

Type: New Feature Priority: Major
Reporter: Christian Ringele Assignee: Ondrej Chytil
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

Right now ins STK there is only the possibility do fill the value of two predefined meta-tags ("keywords" and "description").
These meta-tag values are page wise.

Boris mentioned (long ago) the need in STK to be able to define customized meta-tags in a dynamic way, as it was possible with site designer.
Now I came across a use-case for it, so the topic got back in my mind (and for not forgetting again into Jira):

If you want to use the 'Google Webmaster Tools' you need to add to your page the meta-tag <meta name="verify-v1 content="someUIDfromGoogle" > for verification.
This should be a meta-tag counting site wise and not only page wise.

So this would be needed, if I see it right:

  • Possibility to add dynamically meta-tags in STK
  • It should be possible to define on each of these meta-tags if it counts site or page wise.


 Comments   
Comment by Christian Ringele [ 25/Mar/13 ]

Very old idea from Boris.
Eventually either maintenance, or the issue can be dropped as 'won't fix' of 'obsolete'.
Makes no sense this issue is assigned to me for ages -> maintenance.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 07:26:44 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.