{
  "$type": "site.standard.document",
  "canonicalUrl": "https://www.simoncox.com/short-articles/2010-11-09-preventing-deep-linking/",
  "description": "Why preventing deep linking is both technically misguided and bad for the web — exploring the W3C's position and the real reasons IT teams panic about it.",
  "path": "/short-articles/2010-11-09-preventing-deep-linking/",
  "publishedAt": "2010-11-09T00:00:00.000Z",
  "site": "at://did:plc:tki7vwlanxbwrz2er67eaeqa/site.standard.publication/3mp4h4md7zv2y",
  "tags": "Web",
  "textContent": "There really is no reason to prevent links into your website other than to appease Compliance and Legal teams who are covering all options. Some sites have gone down due to high traffic loads when they have been listed on Boing Boing or Slashdot (not mine - not yet anyway) and that could be the reason why IT teams have got into flusters and the legal teams have tried to apply impossible T&Cs. I’m not talking content theft linking here - linking to images on your site or scraping content.\n\nW3C recommendations for deep linking\nAccording to the W3C Technical Architecture Group, \n\n> “any attempt to forbid the practice of deep linking is based on a misunderstanding of the technology, and threatens to undermine the functioning of the Web as a whole”. \n\nThat’s pretty serious - but no compliance/legal team is going to listen to that when their job is potentially on the line.\n\nCouple of good resources that got me writing this short:\nThe insane world of “No linking Policy” – what happened to the interNET?\nand from Sir Tim Links and Law: Myths",
  "title": "Preventing deep linking"
}