On maybe a longer time scale I'd recommend output/s which retain more of the meaning than you can put into a web page.
Outputs like that would appeal to existing and new audiences, but I don't know what the uptake would be. The new audiences would potentially include, corporate users who automate processes and the current crop of developers who are experimenting with (and sometimes using) Facebook, twitter, bitly... API's.
The idea I'm thinking of here is to have additional "serialisers/serializers" in addition to the existing web page serialiser. (In the work I do this might be a call to an uber-serialiser that then fires off parallel serialisations, maybe implemented as stringwriters...)
Two come to mind. An XML and a JSON. From what I've seen the JSON might be more popular, though an XML serialisation, with a few supplied XSLT's would be very easy to use (even directly into a browser!).
One use would be customised "bad link" reports which could be distributed to suit the situation. (email, RSS, blog, messaging...)
A simple file drop output would do the job, but if there were also a way to directly fire a handler program that would be more useful to some. Maybe the "call" would be a configurable external program with a signature something like.
<drive:\dir1\...\Handler.exe> (String-With-XML-OR-JSON, ConfigParameter)
(Pure fire and forget, no callbacks/return values.)
Where the single ConfigParameter gives options to handle things differently, if you want. (i.e. different targets from different batch runs!) If you wanted to ignore the config, your own handler would accept it then ignore it!
That's a quick brain dump of an idea that sprung to mind when I read this. If it isn't clear just ask...