I've been cc'd into an argument on a forum (not our Opentalk
) and I'm taking great care not to join in or read deeply into what looks like a feud between a couple of folks who, frankly, should agree to disagree. However, I did pick up: "Speaking for myself, I [ac] Ä ve never bothered Googling anyone -- my time is worth more to me than to indulge in such pointless activities."
and felt it worthy of comment.
Googling people is, at times, a far from pointless activity. Just yesterday, I was answering a training query and I wasn't sure of the physical location of my correspondent; a quick Google search indicated a probable London location and that meant that my answer was tailored towards UK courses in the knowledge that my potential delegate could attend a course in Melksham. Had I turned up New Zealand, then my answer would have had a very different slant.
But there's two sides to a coin ... and information that's placed our there, labelled up with your name and public readable, can come back to "haunt" you. I could come up with examples, especially where people have placed what's supposed to be a personal message, a joke, or a thoughtless rant when they're upset. There's other examples around where person "x" has talked about person "y".
My Web content will be read by whom?
Whenever I post with my name (Graham Ellis of Melksham, Wiltshire, England) I do so with three eyes.
One eye is for my target audience - just WHO am I writing this entry for today?
The second eye is for Joe Public, coming here accidentally - perhaps as a new potential customer of our Well House Consultants training courses
or wanting to stay at our hotel in Melksham
, but more likely sent here by a search engine that feel that we're a good site for "Clock Image", where we're #2 on Google at the moment.
The third eye is for people researching us - they may be benign in the form of someone checking up on me / us before booking a course. They may be competitors (Hello, wwwalt, xxxirect and yyyyyingtree - you watching us?). And they just could be all sorts of people I would rather NOT have seeing any soft underbelly I might have - from people looking to rubbish my Save the Train
campaign because they've a vested interest in killing the service before it gets too strong and takes passengers off their buses, through to snooping government agencies who at times seem to draw the net far too wide and wrongly assume the worst of people.
My main posting is - has to be - for my first and second eyes. For my target audience of regular readers and people who come, previously unknown to me, to our web site to look for and find tips and techniques on MySQL
or some similar topic.
Fixing my web content
What if - like the person I originally quotes - I want to squash some web content that I regret putting up, or that someone else has written. Alas, just as building up a web profile is rather like starting an oil tanker (takes a long time to see much effect), so breaking one down can be like stopping an oil tanker. Search engines cache pages and some (such as the Way Back machine
) make a point of keeping copies over the years.
a) Visit posts on forums that you wish you had not made, and where you can, edit them. Where you can't, a friendly message to the administrator - if still active - will help.
b) Alter pages that you control yourself to remove the problem content (and perhaps supply a graveyard page
. That's far better than deleting the page, as anyone who searches for the page should be given the new copy (what you want) and not the cached copy (what you don't want). With a deleted page, all the search engine CAN offer is the cache.
c) Where you don't control a page, you may control or influence some links to it. Change these!
d) If you've access to the robots.txt
file, tell the search engines to exclude pages that you no longer want indexed.
e) In an extreme case, you may wish to ask search engines to delist you; you should find details of how to request this on their web sites.
f) If you don't like content on a page that's NOT under your control, you should go through and ask the information provider, then the webmaster, then perhaps the hosting ISP to remove the content - but if your case is not compellling you may well be out of luck. Friendly is usually best, but if there are copyright or other legal issues involved pointing them out gently will usually help. (written 2006-06-13)
Associated topics are indexed as below, or enter http://melksh.am/nnnn for individual articlesG907 - Well House Consultants - Recruitment and Career Development 
The next generation of programmer - (2004-11-13) 
A new skill may not be quick and easy - (2005-02-02) 
Finding the right holes - (2005-03-21) 
What career opportunities for web designers - (2005-04-20) 
Tough Love - (2005-07-25) 
Can an older person learn a programming language - (2005-08-10) 
10 years C# knowledge please - (2005-11-23) 
Looking for Python staff - (2006-02-01) 
Job vacancy - double agent wanted - (2006-02-02) 
I'm answering a job applicant - (2006-05-16) 
Career development advice - (2006-05-23) 
Want to be a technical trainer in the UK? - (2006-06-08) 
Staff Meeting - (2006-08-30) 
Best source to learn Java (or Perl or PHP or Python) - (2008-12-28) 
LinkedIn - Thrice Asked, and joined. - (2008-12-30) 
Why most training fails ... - (2009-03-30) 
Past PHP delegates / others - coding help needed for next 3 months - (2009-06-23) 
Can you learn to program in 4 days? - (2009-07-16) 
Research is exciting. But should routine be automated? - (2011-09-14) 
How not to call when job seeking ... - (2011-10-20) 
Back to Uni - (2012-01-26) 
Looking and Learning - even on Holiday - (2012-05-22)A213 - Web Application Deployment - Commercial and Legal Aspects 
Colour for access - (2004-12-06) 
Responding to spam - (2005-03-27) 
Colour blindness for web developers - (2005-04-22) 
Ordnance Survey - using a 'Get a map' - (2005-05-22) 
More maps - (2005-05-23) 
Copyright - how much can I legally copy? - (2005-12-17) 
Domain Listing Center and Domain Registry of America - (2006-06-06) 
Remember a site's non-technical issues too - (2006-07-07) 
Making pages clearer - easy Disability Discrimination Act Compliance - (2006-09-23) 
Training on Cascading Style Sheets - (2006-12-17) 
UK legal requirements for your commercial web site - (2007-01-27) 
Getting the community on line - some basics - (2007-11-13) 
Copyright and theft of images, bandwidth and members. - (2007-12-26) 
Does anyone understand Lithuanian? - (2007-12-27) 
Ongoing Image Copyright Issues, PHP and MySQL solutions - (2008-01-14) 
Who is watching you? - (2008-08-10) 
Validating Credit Card Numbers - (2008-10-14) 
Getting hold of the wrong end of the stick - (2008-12-12) 
Beware - giving copyright away when you upload a picture - Dogs Trust - (2009-04-25) 
Leaping dog, Leaping horse, copyright of old masters - (2009-06-20) 
Re-using our pictures - (2010-01-21) 
Freedom of Information - consideration for web site designers - (2010-03-20) 
The legal considerations of your web presence - revisited - (2010-10-26) 
Catering in Syracuse, the Saigon Cafe, stolen images and Christmas - (2010-12-25) 
Web Sites - Subject to Advertising Standards from 1st March - check your sites - (2011-02-13) 
Google Analytics and the new UK Cookie law - (2012-06-02) 
An easy way to comply with the new cookie law if your site is well designed - (2012-06-02) 
Change to Libel and Defamation laws from 1st January 2014 - (2013-12-31) 
Can a legitimate forum post become illegal a year later? - (2014-07-11)
Some other Articles
Much more that the world cupHuge data files - what happened earlier?Great new inventionsSelf help in PerlWatch your Google profileVery good for woodliceHorse and Python trainingSeeing the bricks for the treesUsing different URLs to navigate around a single scripttar, jar, war, ear, sar files