W'd like to add some custom meta-tags, f.e. Google Prey or Verify-v1 (Google verification meta tag) but I can't find such option. This should be possible in such great module. Thanks.
W'd like to add some custom meta-tags, f.e. Google Prey or Verify-v1 (Google verification meta tag) but I can't find such option. This should be possible in such great module. Thanks.
Comments
Comment #1
avpadernoSite verification meta tags are handled by site_verification.module, which already support the meta tag Verify-v1.
Do you have more information about the meta tag Google Prey?
Comment #2
avpadernoComment #3
spookypld commentedGoogle Prey is joke used by SEO specialists.
I've found that XMLSitemap module supports verify-v1 so it may be not neccesary to add it.
Comment #4
avpadernoXML sitemap is dropping the code that would set whose meta tags (version 2.x already removed that code).
I am marking this report as fixed, as one meta tag is already supported and I don't know what the other meta tag purpose would be.
Comment #5
dave reidYes, XML sitemap moved that functionality to it's own module for site verification so people don't need to install module packages for simple functionality.
Comment #6
andypostI need 2 google verifications so but it's not possible not this nor site_verify module.
Why not make this ability in 1 module?
Comment #7
avpadernoIf the module would add two times the same verification meta tag, then it is probably that only the last one would be used. That is true for each HTML tag; if you would add two tag Title, the browser would use just one of them (probably the last inserted one).
Comment #8
andypostI said about different meta-tags, for example one for dev and another for seo and probably for customer
Comment #9
avpadernoGoogle uses just one meta tag to verify a site. I am not sure which meta tags the module should support, if only one is used by Google.
Comment #10
andypostAre you really sure - i'm using 2-3 file-based verifications which is different for different accounts.
Comment #11
avpadernoNodewords doesn't implement file based verifications, but meta tags based verifications.
Comment #12
andypostYes I know, but you sure that having 2 meta-tags (for ex. ) in head is prohibited?
http://www.google.com/support/webmasters/bin/answer.py?answer=44227
Comment #13
spookypld commentedI opens this issue, because maintaner disunderstood me.
It's not important if Google takes into cosideration first metatag or second or whatever... It's important that there is a lot more Meta name tags possibilities. For example Nodewords is missing Author, Designer, Subject, Publisher, Date... Generally You can add any Meta name You want and this is always correct. There is no "Allowed od Disallowed Meta names list". You can make Your own and it is generally correct, it's validating, it's normal, not prohibited, etc.
So, once again I propose to add option that will add custom meta name.
Comment #14
spookypld commentedComment #15
avpadernoAren't meta tags Author, Designer, Subject, Publisher, and Date part of the Dublin Core metadata?
Comment #16
spookypld commentedGenerally DC is not going to be wide supported standard. It seems that microformats are going to be (because Google uses them). They got it too, but formatting is done outside meta tags.
That's why I opting for custom meta tags, with textarea, so anyone could add any number of custom meta tags that he/she needs. As You see there is ton of meta tags and nobody really knows them all!
Comment #17
avpadernoIn this case, this report is a duplicate of #526934: Allow users to define custom meta tags.