On 27 June 2017 at 19:11, George Burgess IV via llvm-dev <llvm-dev at lists.llvm.org> wrote:> There was some kind of server move that happened recently; I'm > assuming this is a side-effect of that.I'd vaguely understood the old links had been deprecated for a while. Unfortunately they're still the top Google results when you search for the relevant classes, which is really annoying. If anyone knows any active measures we can take to hasten that being fixed, I think we should try. Tim.
> On Jun 27, 2017, at 22:33, Tim Northover via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 27 June 2017 at 19:11, George Burgess IV via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> There was some kind of server move that happened recently; I'm >> assuming this is a side-effect of that. > > I'd vaguely understood the old links had been deprecated for a while. > Unfortunately they're still the top Google results when you search for > the relevant classes, which is really annoying. > > If anyone knows any active measures we can take to hasten that being > fixed, I think we should try.I think the standard way is to HTTP 301 to the new location. I'm pretty sure Google picks up on that. -- Stephen Checkoway
Will a permanent redirection (mod_rewrite) from old links to new links for a few days help Google learn faster? On 27 June 2017 at 20:33, Tim Northover <t.p.northover at gmail.com> wrote:> On 27 June 2017 at 19:11, George Burgess IV via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > There was some kind of server move that happened recently; I'm > > assuming this is a side-effect of that. > > I'd vaguely understood the old links had been deprecated for a while. > Unfortunately they're still the top Google results when you search for > the relevant classes, which is really annoying. > > If anyone knows any active measures we can take to hasten that being > fixed, I think we should try. > > Tim. >-- Thanks & Regards, Dipanjan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170627/5e16561a/attachment.html>
The docs found on google have been vastly out of date for quite a while. For that time, http://llvm.org/doxygen/ has been the correct home of the API docs. See also http://llvm.org/pr32412. The server move last weekend dropped the legacy files. It'll take the google index a bit to notice. robots.txt currently prevents indexing of /doxygen, because there was an issue with the robots, I've been told. Cheers, Philip 2017-06-28 6:41 GMT+02:00 Dipanjan Das via llvm-dev <llvm-dev at lists.llvm.org>:> > Will a permanent redirection (mod_rewrite) from old links to new links for > a few days help Google learn faster? > > On 27 June 2017 at 20:33, Tim Northover <t.p.northover at gmail.com> wrote: > >> On 27 June 2017 at 19:11, George Burgess IV via llvm-dev >> <llvm-dev at lists.llvm.org> wrote: >> > There was some kind of server move that happened recently; I'm >> > assuming this is a side-effect of that. >> >> I'd vaguely understood the old links had been deprecated for a while. >> Unfortunately they're still the top Google results when you search for >> the relevant classes, which is really annoying. >> >> If anyone knows any active measures we can take to hasten that being >> fixed, I think we should try. >> >> Tim. >> > > > > -- > > Thanks & Regards, > Dipanjan > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170628/027ef9e8/attachment.html>