[Yanel-dev] yanel prefix link in order to activate the Yanel toolbar

Guillaume Déflache guillaume.deflache at wyona.com
Fri Sep 25 17:25:53 CEST 2009


Michael Wechner schrieb:
> Guillaume Déflache schrieb:
>> Michael Wechner a écrit :
>>>> To fix indexing issues, we would have to make sure to add 
>>>> rel="nofollow" 
> 
> I have set this now
>>>> on the link *and* set the HTML robots meta attribute to 
>>>> "noindex,nofollow,noarchive,nosnippet" ( cf. 
>>>> http://en.wikipedia.org/wiki/Nofollow#Interpretation_by_the_individual_search_engines 
>>>> and http://en.wikipedia.org/wiki/Meta_element#The_robots_attribute )
> 
> it's not clear to me when exactly this html meta tag needs to be set
> 
> <html>
>  <head>
>     <meta name="robots" content="noindex,nofollow,noarchive,nosnippet"/>
> 
> 
> because I would assume on pages where this is set, these pages are not 
> idexed.

Indeed

> And how does this interact with the robots.txt file?

It complements and supercedes it.


>>>> But anyway we should really use POST-then-redirect there instead, 
>>>> and only use GET for debugging.
> 
> can you explain this a bit more?

What I was trying to say is generally for all actions that have 
side-effects we should use POST instead of GET to avoid that user-agents 
aggressively prefetching -- like Google Web Accelerator[1], Firefox for 
now seems to be much more conservative[2] -- or crawling -- like 
Googlebot[3] -- Web pages trigger nasty things like page deletions...
And there are also always more of these page-preview thingies (that I 
personally find horrible) that fetch a miniature of the page when you 
roll over a link: I presume they do not pay too much attention to where 
they point to... If you add that feature in a Yanel site this may lead 
to surprises!

[1] 
http://37signals.com/svn/archives2/google_web_accelerator_hey_not_so_fast_an_alert_for_web_app_designers.php
[2] https://developer.mozilla.org/en/Link_prefetching_FAQ
[3] http://thedailywtf.com/Articles/The_Spider_of_Doom.aspx [ i wonder 
which CMS it was! :P ]

On POST-then-redirect / redirect-after-POST / POST-redirect-get (PRG), 
for overview see http://en.wikipedia.org/wiki/Post/Redirect/Get and for 
a good rationale see 
http://www.theserverside.com/tt/articles/content/RedirectAfterPost/article.html


For the toolbar or editing UI in general we could also require another 
subdomain, e.g. rww.yanel.org (Read/Write Web...), and 127.0.0.1 for 
testing instead of localhost, but then LAN usage to test fron coworker 
machines would require machine names or at least 2 IPs...


More information about the Yanel-development mailing list