Hmmm My 10 second investigation indicates <http://stackoverflow.com/questions/10178304/github-jekyll-old-pages-redirection-best-approach/19717455#19717455> perhaps we can put placeholder pages to handle the redirect and that will redirect the pages and force google to reindex. Problem is, I don't know which pages have moved.
On Wed, Sep 24, 2014 at 10:22 AM, Alon Zakai <[email protected]> wrote: > Hmm, not sure we can do that. You're talking about github wiki links? All > we can do is keep a page up with a link to the right place. > > - Alon > > > On Mon, Sep 22, 2014 at 8:47 PM, Robert Tweed < > [email protected]> wrote: > >> Please don't forget to set up 301 redirects for Google. I've been >> searching the docs a lot recently and keep landing on "this page has moved" >> pages, which should ideally just be a 301 to the new location. This will >> also force Google to reindex the new content more accurately. >> >> >> On Monday, September 22, 2014, Alon Zakai <[email protected]> wrote: >> >>> Thanks Raúl, I pushed a fix now to incoming. Will push a site update >>> later today. >>> >>> - Alon >>> >>> >>> On Mon, Sep 22, 2014 at 8:37 AM, Raúl G. Roa Gómez <[email protected]> >>> wrote: >>> >>>> Hi Hamish, >>>> >>>> I was just skimming through the first page >>>> <http://kripken.github.io/emscripten-site/docs/introducing_emscripten/about_emscripten.html#porting-code-to-use-emscripten> >>>> of the documentation and was able to catch a dead link. >>>> >>>> In the *Porting to Emscripten* part there's a link to browser >>>> environment differences which points to some page that doesn't exist. >>>> >>>> On Sunday, September 21, 2014 9:42:52 PM UTC-5, Hamish Willee wrote: >>>>> >>>>> Hi All >>>>> >>>>> The Emscripten documentation project is largely complete. I think the >>>>> end result is pretty good - well written and structured, attractive, >>>>> searchable and and easy to navigate. You can see the results here >>>>> <http://kripken.github.io/emscripten-site/>. >>>>> >>>>> If you have any feedback please discuss here, or raise issues >>>>> <http://kripken.github.io/emscripten-site/docs/getting_started/bug_reports.html> >>>>> . The site has instructions >>>>> <http://kripken.github.io/emscripten-site/docs/site/about.html> on >>>>> how you can build and add to this documentation yourself. >>>>> >>>>> Thank you everyone who helped support and contribute to this work. >>>>> I've enjoyed working as part of this community. >>>>> >>>>> Regards >>>>> Hamish >>>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "emscripten-discuss" group. >>>> To unsubscribe from this group and stop receiving emails from it, send >>>> an email to [email protected]. >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "emscripten-discuss" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "emscripten-discuss" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > You received this message because you are subscribed to a topic in the > Google Groups "emscripten-discuss" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/emscripten-discuss/20Hrp5tp06s/unsubscribe > . > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
