Search Implemented
Having documented how search will work, implementing it was a breeze:

This screenshot shows results for a search of PhpGedView sites for “Jared”. There is no similarity test yet, so results are shown in the order found. Subsequent searches bring up cached results, but database queries are running far too slow for my taste. The theme of this project seems to be “premature optimization” ;).
Filed in 



Have you looked at Google’s Custom Search Engine. For example, the following query searchs PhpGedView pages across the web:
http://www.google.com/search?q=inurl:individual.php inurl:pid=
And the following quiery pulls up GEDCOM files:
http://www.google.com/search?q=adam filetype:ged
Thanks for the tip! Search agents could definitely be written which leverage Google search to find data. I’m currently working with PhpGedView sites directly because I anticipate some sort of feedback cycle: one where my work impacts the software that runs PGV sites so that they can automatically (or semi-automatically) link up together, creating a distributed network of genealogy in the process. Google search results would certainly bring in more data, but that data won’t be as actionable in this respect. I hope to go down that avenue the future, however.