This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Working Links | |
|---|---|
| Name | Working Links |
| Type | Link management |
| Launched | 2000s |
| Owner | Independent |
| Country | International |
Working Links is a system for maintaining, verifying, and presenting active hyperlinks across digital platforms. It encompasses tools, standards, and organizational practices used by institutions, projects, and services to ensure hyperlinks resolve to intended targets. Implementations intersect with archival initiatives, content management platforms, and web indexing services.
Working Links covers processes used by Internet Archive, W3C, Mozilla Corporation, Google LLC, Microsoft Corporation, Yahoo!, BBC, The New York Times Company, The Guardian, Wikimedia Foundation and other entities to detect, repair, or replace broken hyperlinks. It incorporates protocols such as HTTP/1.1, HTTPS, TLS, OAuth, and formats like JSON-LD, XML, HTML and metadata standards from Dublin Core and schema.org. Practitioners include teams from Internet Engineering Task Force, National Information Standards Organization, Association of Research Libraries, Library of Congress, Harvard University, Stanford University and commercial actors such as Amazon (company), Meta Platforms and Cloudflare.
Early efforts trace to hyperlink maintenance work by academics at Massachusetts Institute of Technology and University of California, Berkeley and commercial indexing by AltaVista and Excite. The rise of content management systems like WordPress, Drupal, Joomla! and syndication via RSS and Atom shifted practices. Archival responses from Internet Archive (including Wayback Machine) and preservation projects at National Archives and Records Administration influenced protocols. Later advances emerged alongside web standards committees at W3C and policy discussions at European Commission, United Nations Educational, Scientific and Cultural Organization and National Science Foundation.
Technical approaches include automated link checking using crawlers similar to those employed by Google Search, Bing, DuckDuckGo and Yandex. Systems rely on status codes from HTTP/1.1 (e.g., 200, 301, 404, 410), TLS certificates issued by authorities like Let’s Encrypt, DigiCert and GlobalSign, and redirect handling using 301 Moved Permanently and 302 Found semantics. Metadata-driven link repair uses identifiers such as DOI, ISBN, ISSN and persistent identifiers from Handle System. Integration with content platforms such as GitHub, Stack Overflow, Medium (website), Confluence (software) and Atlassian tools enables continuous integration workflows. Monitoring uses logging and alerting stacks like ELK Stack, Prometheus, Grafana and cloud services from Amazon Web Services, Google Cloud Platform and Microsoft Azure.
Working Links supports digital libraries at institutions such as British Library, Library of Congress, Bibliothèque nationale de France and academic publishers like Elsevier, Springer Nature, Taylor & Francis and Wiley-Blackwell. Newsrooms at Reuters, Associated Press, The Washington Post and broadcasters like CNN employ link verification for sourcing. Legal repositories such as LexisNexis and Westlaw rely on link stability for citations to cases like Brown v. Board of Education and statutes like the United States Code. Educational platforms such as Coursera, edX, Khan Academy and university learning management systems use link management for course materials. E-commerce sites like eBay and Amazon (company) use similar systems to preserve product and review links.
Maintenance strategies mirror practices at National Institutes of Health repositories and large platforms such as Wikipedia and Wikidata with community-driven repair workflows. Reliability engineering borrows from Site Reliability Engineering practices popularized by Google LLC and operational playbooks from Netflix and Amazon Web Services. Automated regression tests, link rot detection, periodic recrawls by entities like Common Crawl and DOI resolution through CrossRef contribute to uptime targets. Backup and disaster recovery reference models follow standards used by ISO/IEC 27001-certified organizations and national libraries including Library of Congress.
Security concerns intersect with certificate management from Let’s Encrypt, threat intelligence from MITRE (e.g., CVE references), and phishing detection used by Microsoft Defender and Google Safe Browsing. Privacy implications involve handling user-tracking signals and consent regimes under laws like the General Data Protection Regulation and California Consumer Privacy Act. Operational security aligns with guidance from National Institute of Standards and Technology and incident response coordination with entities such as CERT Coordination Center and US-CERT.
Legal aspects involve liability considerations seen in cases adjudicated under statutes such as the Digital Millennium Copyright Act, linking disputes in jurisdictions influenced by the European Court of Justice, and contractual obligations of platforms like Facebook and Twitter. Ethical issues include archival responsibility debated at conferences hosted by Society of American Archivists, International Council on Archives and scholarly forums at ACM and IEEE. Copyright, fair use, and preservation rights shape practices employed by cultural institutions such as Smithsonian Institution and Getty Research Institute.
Category:Digital preservation Category:Internet standards