Forum Moderators: LifeinAsia
As *hit hits the fan over the next year, many clients move hosting elswhere from your old company. They move their site files.
Let's say one day you are checking high profile client sites you optimized just to "see how they're doing" a year later in rankings. To your shock, you see that the set of meta tags that includes your distinctive outline, additions (unlike any other) are still in the client site files on the new company host, but the webmaster has put HIS name in as the Author in the meta information. (You see, one of the things you do for identification of work is to include <meta name="Author" content="YOUR NAME - SEO, SEP ">)
After the gut-stabbing, wrenching betrayal feeling starts to subside a bit, you start to wonder...."Do I email the %^&* and tell him to remove his &*() name out of the code?" just because he didn't do any of it (it's still 100% designed and optimized - NOT by him) - or do you just chew on your lips for 3 days and let it ride?
Or what else crosses your mind?
Ethically I guess if they are attempting to mislead others that the material was created by them and not just bought, you may have cause to get angry. On the other hand they may just have cut and pasted changes to the pages site-wide, without worrying or thinking, therefore it may be accidental. I would send off a polite question email. Do you realise that your pages are blah blah blah?
Usually emails shot off in anger lack objectivity.
Cheesy thing is.....the company had rights to their files - they were transferred to a new host in their entirety.
If it were me (grin again)....all I would want is for the person not to refer to themself as the author. Just clip that one tag out altogether. It's just equating in my brain to something like buying rights to a book to resell and then pasting your name over the authors title or buying a disk of clip art and reselling it as "your own" clip art.
If it was subcontracted and you were actually the contractor (independent contractor) for the job, it's one thing. But if you were an employee it's work_for_hire which is different and the problem is the company's, with you having no recourse but to let the former employer know and do what they want about it. They just need documentation, and if they have it, can have it removed from the host unless they're given proper credit.
That's the way I've seen the difference explained. I suppose it depends on what agreement you had with the employer.
It's hard to back off of something far enough to see it clearly. Thanks for the opportunity and assistance to keep backing up for a while. My eyes were burning there for a bit...
It's real easy to get tweaked off when you know weeks and months go into projects - to see it passed off right in front of you as someone elses work. But....we don't want those hot, incoherent emails going off into cyberspace. Chiyo, the client contract does allow them to have use of the files, but they can not claim development of those files. So, I guess it is time to get to Word and draft out that eloquent "Immediate Request for Removal" in a "sincerely yours" tone. Thanks all.
From a legal standpoint, if this happened to... somebody... there's probably not much to be done. So, should one write a letter asking for the tag to be removed anyway? I think I probably would... and I think most people who received such a message would either to ahead and remove the tag, or make a couple of changes to the pages and laugh, "ha! now I am the author!"
It appears that they want visitors to assume that they created the site by changing the author and "site created by" information since nothing else changed. Hopefully this will have a subtle end with the removal of those claims. Thanks everybody.
but the real question is what do you personally stand to gain or lose by a change of authorship metatag???
>>>you can still say you did the original and it has now been very very slightly modified, can't you?
exactly right, and if you're looking to use the site as an example of your work you still can.
otherwise let it drop, the time, energy and frustration involved in chasing them up will be too costly for you compared to the return.
sidenote, i have no legal background but a very good friend of mine is a contract dispute lawyer, who makes more money than i can dream about - off the back of the fact that contracts are very rarely drawn up watertight and often the side with the most money will win the case
Assuming the other guy is a chump, if questioned on his methodology he may struggle, if he doesn't then. As you were an employee you wouldn't have a leg to stand on in any court I don't think, but all my law knowledge is from LA Law, Ally McBeal, Petrocelli (anyone remember that far back or am I showing my age ?)
Take pride & move on
Here is a nice site with high visibility. The site files identify someone else as author.
Then there you are on another site, politely claiming authorship of site XXXX.
Who would visitors believe? The actual site files say one thing and you say another.
I think that an unfair burden is placed on us to "prove" that our own work is ours. Yes it is time consuming and frustrating. Part of the frustration comes from being put in the position of having to prove anything at all.
I remember a colleague of mine being ordered by a former employer to remove their references to sites from their online resume. Even though the programmer had performed nearly all of the work found on the sites, the employer was trying to regulate what was posted on their website as part of their online resume.
"Tis a sad day when passing ruffians can say NEEE to old ladies at will." - Monty Python and the Holy Grail - Roger the Shrubber.
The person casting the content into HTML and possibly tweaking it for SEO purposes is not necessarily the author. In analogy to print media, maybe there should be an extra "typesetter" meta tag... ;)
Not that this eliminates any issues with the copyright of the site design, just that you might have to look for other methods of reference than a potentially misleading meta tag.