Automated Content Access Protocol ("ACAP") was proposed in 2006 as a method of providing machine-readable permissions information for content, in the hope that it would have allowed automated processes (such as search-engine web crawling) to be compliant with publishers' policies without the need for human interpretation of legal terms. ACAP was developed by organisations that claimed to represent sections of the publishing industry (World Association of Newspapers, European Publishers Council, International Publishers Association).^[1] It was intended to provide support for more sophisticated online publishing business models, but was criticised for being biased towards the fears of publishers who see search and aggregation as a threat^[2] rather than as a source of traffic and new readers.

In November 2007 ACAP announced that the first version of the standard was ready. No non-ACAP members, whether publishers or search engines, have adopted it so far. A Google spokesman appeared to have ruled out adoption.^[3] In March 2008, Google's CEO Eric Schmidt stated that "At present it does not fit with the way our systems operate".^[4] No progress has been announced since the remarks in March 2008 and Google,^[5] along with Yahoo! and MSN, have since reaffirmed their commitment to the use of robots.txt and sitemaps.

In 2011 management of ACAP was turned over to the International Press Telecommunications Council and announced that ACAP 2.0 would be based on Open Digital Rights Language 2.0.^[6]

In April 2007 ACAP commenced a pilot project in which the participants and technical partners undertook to specify and agree various use cases for ACAP to address. A technical workshop, attended by the participants and invited experts, has been held in London to discuss the use cases and agree next steps.

By February 2007 the pilot project was launched and participants announced.

By October 2006, ACAP had completed a feasibility stage and was formally announced^[7] at the Frankfurt Book Fair on 6 October 2006. A pilot program commenced in January 2007 involving a group of major publishers and media groups working alongside search engines and other technical partners.

ACAP rules can be considered as an extension to the Robots Exclusion Standard (or "robots.txt") for communicating website access information to automated web crawlers.

It has been suggested^[8] that ACAP is unnecessary, since the robots.txt protocol already exists for the purpose of managing search engine access to websites. However, others^[9] support ACAP’s view ^[10] that robots.txt is no longer sufficient. ACAP argues that robots.txt was devised at a time when both search engines and online publishing were in their infancy and as a result is insufficiently nuanced to support today’s much more sophisticated business models of search and online publishing. ACAP aims to make it possible to express more complex permissions than the simple binary choice of “inclusion” or “exclusion”.

As an early priority, ACAP is intended to provide a practical and consensual solution to some of the rights-related issues which in some cases have led to litigation^[11][12] between publishers and search engines.

The Robots Exclusion Standard has always been implemented voluntarily by both content providers and search engines, and ACAP implementation is similarly voluntary for both parties.^[13] However, Beth Noveck has expressed concern that the emphasis on communicating access permissions in legal terms will lead to lawsuits if search engines do not comply with ACAP permissions.^[14]

No public search engines recognise ACAP. Only one, Exalead, ever confirmed that they will be adopting the standard,^[15] but they have since ceased functioning as a search portal to focus on the software side of their business.

The project has generated considerable online debate, in the search,^[16] content^[17] and intellectual property^[18] communities. If there are any common themes in commentary, they are

1. that keeping the specification simple will be critical to its successful implementation, and
2. that the aims of the project are focussed on the needs of publishers, rather than readers. Many have seen this as a flaw.^[2][19]

• Sitemaps

• Official website
• Google's hunger for the news in The Guardian newspaper
• Why you should care about Automated Content Access Protocol (Steve Yelvington)
• Automated Content Access Protocol: Why? – Wildly Appropriate
• Acap: flawed and broken from the start – Martin Belam
• Automated Content Access Progress
• WAN calls on Google to embrace Acap^{[permanent dead link‍]} – Editor and Publisher