Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Claushingebjerg 936 posts 2571 karma points
    Jan 26, 2010 @ 15:38
    Claushingebjerg
    0

    inheritance worries

    Cool package, but i  think it is pretty bad idea, that it looks anywhere but on $currentpage for meta tags.

    I can imagine the site returning som pretty crazy results if certain a page does'nt have meta tags attached, and the package then goes to some other part of the website to get them. I think Meta tags should be descriptive of the contet and therefore unique for the page in question.

  • Chris Houston 535 posts 980 karma points MVP admin c-trib
    Feb 24, 2010 @ 01:42
    Chris Houston
    0

    Hi Claushingebjerg.

    I do agree with you, but I also have a lot of very lazy clients who never bother to fill in their Meta tags for any of their user generated content pages, so they have the choice of inheriting the parent node's details ( e.g. in the news section.. it might say "News Articles" ) or if we don't use a script like this, they just end up with either an even less descriptive generic meta tag or, worst of all, no meta tags at all.

    I totally agree though, best practice is for the content editors to supply unique meta tags on every page.

    One senario where the Meta tags are somewhat of no use is within secure private sites and this is where at least having a title saying "News Articles" is better than nothing, IMHO.

    Cheers,

    Chris

Please Sign in or register to post replies

Write your reply to:

Draft