http://trailfire.com/sidisinsane/trails/16279sidisinsane/trails60http://trailfire.com/sidisinsane/marks/23420Google - SEO+sidisinsaneSun, 29 Oct 2006 12:21:48 -0800trailfire:markId:23420http://trailfire.com/sidisinsane/marks/23422Google - SEO+sidisinsaneSun, 29 Oct 2006 12:22:46 -0800trailfire:markId:23422http://trailfire.com/sidisinsane/marks/23425Google - SEO+sidisinsaneSun, 29 Oct 2006 12:24:24 -0800trailfire:markId:23425http://trailfire.com/sidisinsane/marks/23427Google - SEO+sidisinsaneSun, 29 Oct 2006 12:25:28 -0800trailfire:markId:23427http://trailfire.com/sidisinsane/marks/23428Google - SEO+sidisinsaneSun, 29 Oct 2006 12:26:46 -0800trailfire:markId:23428http://trailfire.com/sidisinsane/marks/24695Google - SEO+sidisinsaneWed, 01 Nov 2006 21:02:52 -0800trailfire:markId:24695http://trailfire.com/sidisinsane/marks/24707Google - SEO+sidisinsaneWed, 01 Nov 2006 21:53:43 -0800trailfire:markId:24707http://trailfire.com/sidisinsane/marks/24711Google - SEO+sidisinsaneWed, 01 Nov 2006 22:17:13 -0800trailfire:markId:24711http://trailfire.com/sidisinsane/marks/24712Google - SEO+sidisinsaneTue, 18 Dec 2007 10:59:42 -0800trailfire:markId:24712http://trailfire.com/sidisinsane/marks/26182Google - SEO+sidisinsaneTue, 07 Nov 2006 11:49:03 -0800trailfire:markId:26182http://trailfire.com/sidisinsane/marks/26750Google - SEO+sidisinsaneThu, 09 Nov 2006 22:28:00 -0800trailfire:markId:26750http://trailfire.com/sidisinsane/marks/27150Google - SEO+sidisinsaneSun, 12 Nov 2006 11:39:29 -0800trailfire:markId:27150http://trailfire.com/sidisinsane/marks/27552Google - SEO+sidisinsaneTue, 14 Nov 2006 17:49:02 -0800trailfire:markId:27552http://trailfire.com/sidisinsane/marks/30024Google - SEO+sidisinsaneSat, 25 Nov 2006 13:43:36 -0800trailfire:markId:30024http://trailfire.com/sidisinsane/marks/30026Google - SEO+sidisinsaneSat, 25 Nov 2006 13:58:09 -0800trailfire:markId:30026http://trailfire.com/sidisinsane/marks/30562Google - SEO+sidisinsaneTue, 28 Nov 2006 02:08:09 -0800trailfire:markId:30562http://trailfire.com/sidisinsane/marks/32432Google - SEO+sidisinsaneTue, 05 Dec 2006 00:01:22 -0800trailfire:markId:32432http://trailfire.com/sidisinsane/marks/33633Google - SEO+sidisinsaneFri, 08 Dec 2006 22:16:56 -0800trailfire:markId:33633http://trailfire.com/sidisinsane/marks/34980Google - SEO+sidisinsaneThu, 14 Dec 2006 21:31:01 -0800trailfire:markId:34980http://trailfire.com/sidisinsane/marks/37836Google - SEO+sidisinsaneThu, 28 Dec 2006 03:06:34 -0800trailfire:markId:37836http://trailfire.com/sidisinsane/marks/37839Google - SEO+sidisinsaneThu, 28 Dec 2006 03:18:32 -0800trailfire:markId:37839http://trailfire.com/sidisinsane/marks/42509Google - SEO+sidisinsaneFri, 12 Jan 2007 21:14:45 -0800trailfire:markId:42509http://trailfire.com/sidisinsane/marks/44283POP3 and SMTP configuration for Outlook 2003.
]]>Google - SEO+sidisinsaneThu, 18 Jan 2007 13:19:51 -0800trailfire:markId:44283http://trailfire.com/sidisinsane/marks/46796]]>Google - SEO+sidisinsaneThu, 25 Jan 2007 11:46:41 -0800trailfire:markId:46796http://trailfire.com/sidisinsane/marks/46971]]>Google - SEO+sidisinsaneThu, 25 Jan 2007 22:01:34 -0800trailfire:markId:46971http://trailfire.com/sidisinsane/marks/53151]]>Google - SEO+sidisinsaneMon, 05 Feb 2007 22:37:51 -0800trailfire:markId:53151http://trailfire.com/sidisinsane/marks/56497.. how to get around them and exploit their loop holes by Joe Whyte]]>Google - SEO+sidisinsaneWed, 14 Feb 2007 04:42:32 -0800trailfire:markId:56497http://trailfire.com/sidisinsane/marks/62797Google - SEO+sidisinsaneTue, 27 Feb 2007 01:37:36 -0800trailfire:markId:62797http://trailfire.com/sidisinsane/marks/67010Robots Exclusion Protocol.]]>Google - SEO+sidisinsaneTue, 06 Mar 2007 22:00:50 -0800trailfire:markId:67010http://trailfire.com/sidisinsane/marks/70464Google - SEO+sidisinsaneFri, 16 Mar 2007 22:48:01 -0700trailfire:markId:70464http://trailfire.com/sidisinsane/marks/82665Google - SEO+sidisinsaneThu, 05 Apr 2007 23:49:34 -0700trailfire:markId:82665http://trailfire.com/sidisinsane/marks/83840Google - SEO+sidisinsaneMon, 09 Apr 2007 23:59:04 -0700trailfire:markId:83840http://trailfire.com/sidisinsane/marks/86650Google - SEO+sidisinsaneTue, 17 Apr 2007 22:15:37 -0700trailfire:markId:86650http://trailfire.com/sidisinsane/marks/120060Google - SEO+sidisinsaneMon, 02 Jul 2007 23:11:41 -0700trailfire:markId:120060http://trailfire.com/sidisinsane/marks/121759

Try to use Flash only where it is needed. Many rich media sites such as Google's YouTube use Flash for rich media but rely on HTML for content and navigation. You can too, by limiting Flash to on-page accents and rich media, not content and navigation. In addition to making your site Googlebot-friendly, this makes you site accessible to a larger audience, including, for example, blind people using screen readers, users of old or non-standard browsers, and those on limited low-bandwidth connections such as on a cell phone or PDA. As a bonus, your visitors can use bookmarks effectively, and can email links to your pages to their friends.

sIFR: Some websites use Flash to force the browser to display headers, pull quotes, or other textual elements in a font that the user may not have installed on their computer. A technique like sIFR still lets non-Flash readers read a page, since the content/navigation is actually in the HTML -- it's just displayed by an embedded Flash object.

Non-Flash Versions: A common way that we see Flash used is as a front page "splash screen" where the root URL of a website has a Flash intro that links to HTML content deeper into the site. In this case, make sure there is a regular HTML link on that front page to a non-Flash page where a user can navigate throughout your site without the need for Flash.

]]>Google - SEO+sidisinsaneFri, 06 Jul 2007 08:40:39 -0700trailfire:markId:121759http://trailfire.com/sidisinsane/marks/148677How can URL parameters, like session IDs or tracking IDs, cause duplicate content?
When user and/or tracking information is stored through URL parameters, duplicate content can arise because the same page is accessible through numerous URLs. It's what Adam Lasnik referred to in "Deftly Dealing with Duplicate Content" as "store items shown (and -- worse yet -- linked) via multiple distinct URLs." In the example below, URL parameters create three URLs which access the same product page.]]>Google - SEO+sidisinsaneWed, 12 Sep 2007 23:17:01 -0700trailfire:markId:148677