- 48
- Sphinn It!
Posted By: tonyp 258 days ago
Topic Type: News Story (Jump to http://searchenginewatch.com)
Category: SEO
8 Comments
8 Comments
Save the date for:
SMX East (New York City) - Oct.
6-8: See the agenda or register today and save!
SMX London - Nov. 4-5: Pre-agenda rate now available. Click here.
SMX West - Feb. 10-12
Learn more about search marketing through free online webcasts and webinars from our sister site Search Marketing Now.
Comments
I wish folks wouldn't say "title tag" (a thing that doesn't exist anywhere, but can mean title element as well as title attribute, or even the 1st heading of a page).
http://www.w3schools.com/tags/tag_title.asp
Errornous + invalid reference, who cares?
Actually, my nitpicking comment wasn't meant to bash the post. That's solid advice, but old news for me, hence I wouldn't have read it knowing that it's about the title element's content and not the seldomly mentioned title attribute. I apoligize for my superficiality.
Judging from the story title's first four words, spotting the "SEO" context but truncating "strategy" I had expected to read something different (an attribute's value is often a tag). Of course that's just me skimming headlines expecting geek speech.
However, calling a spade a spade enhances every communication. When folks call elements, attributes, values and even list items a tag and then all of them are somewhat related to "title", that's confusing for many newbies who aren't capable to get the meaning from the context at first sight, and every once in a while jargon like that might even confuse more savvy folks guilty of skimming links lists in compiler mode.
Hi Sebastian,
I'm sorry if you were misled or confused by the title of my article. Honestly I'm not a designer and when I send title "attributes" or "elements" to my designers for implementation I say "Make 'x' the title tag and they understand that"
Most of my readers understand basic coding terms, and in my experiece, calling the title "element" an "HTML title tag" seems to work best to get my meaning across.
Thanks for your feedback, and again sorry for the confusion.
~Carrie
No need to say sorry, Carrie! I could have invested more than one second to read the title before clicking the link, so it's my fault. Actually, I was referring to Corey's short reply and the negative vote on my initial comment. Of course I'm guilty of using not exactly precise jargon in tens of thousands of posts myself, but I've learned that it doesn't pay - at least not in Webmaster support communities and educational articles. "Most" is not enough to avoid irritated follow-up queries that cost much more time than the original statement that irritated the newbie. Not to speak of an unknown number of disappointed readers who surf away and don't return. Again, that's just my experience, and please take into account that english isn't my first language, thus I might prefer precise wording more than a native speaker.
i didn't vote you down, sebastian
I voted you up, Sebastian. I think it's always valuable to try to get precise usage accepted and people at least thinking about this. It won't stop the confusion but hopefully there will be a little less when the dust settles.
Corey, I didn't say that - and even if you'd have voted my first comment down that would have been perfectly Ok, since it was off-topic.
Thanks, Barry.