Difference between revisions of "No Follow for BuiltWith and Alexa"

(Refactored to use standard open task categories Category:OpenTask, Category:DevelopmentTeam)
(Refactored to use standard open task categories Category:OpenTask, Category:DevelopmentTeam)
 
Line 1: Line 1:
<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < [[Category:OpenTask]]
+
<noinclude><big>[[OurWork]] < [[DevelopmentTeam]] < [[DevelopmentTeamPriorities|Priorities]] < </noinclude>('''[[PairDays?|?]]''') [[No Follow for BuiltWith and Alexa]] ('''[[Who?|?]]''') {{JustTinyEditIcon|No Follow for BuiltWith and Alexa}}<noinclude></big>
[[Category:DevelopmentTeam]]
 
</noinclude>('''[[PairDays?|?]]''') [[No Follow for BuiltWith and Alexa]] ('''[[Who?|?]]''') {{JustTinyEditIcon|No Follow for BuiltWith and Alexa}}<noinclude></big>
 
 
__NOTOC__
 
__NOTOC__
 
== What (summary) ==
 
== What (summary) ==

Latest revision as of 21:00, 7 February 2008

OurWork Edit-chalk-10bo12.png

What (summary)

Make links going to BuiltWith, Registrars other than NetworkSolutions.com, Register.com, eNom.com and BulkRegister.com and Alexa into NoFollow links. BuiltWith links are in the domain boxes and Alexa links are generally in the external links area.

Why this is important

This may be affecting us negatively with Google

DoneDone

When all links from out site to BuiltWith and Alexa are NoFollow links.

Steps to get to DoneDone



Retrieved from "http://aboutus.com/index.php?title=No_Follow_for_BuiltWith_and_Alexa&oldid=14740004"