Live @ SMX Advanced: Platform Considerations
Platform Considerations for the Microsoft Stack and LAMP Stack - Practical tips, tricks, and workarounds for search-friendly architecture.
- Microsoft Stack
- Including IIS, ASP.Net, Silverlight, Microsoft SQL Server
- LAMP Stack
- Including Apache, PHP, Ruby, Flash/Flex, mySQL
- CMS Considerations (such as .NET Blog Engine, AxCMS, Wordpress, Movable Type, Drupal, Joomla)
Moderator: Vanessa Fox, Features Editor, Search Engine Land
Speakers:
Colin Cochrane, SEO Analyst and Web Developer, Metamend Search Engine Marketing
Thomas Deml, Senior Program Manager, Internet Information Services, Microsoft
Nikhil Kothari, Principal Architect, Microsoft
Duane Nickull, Senior Standards Strategist, Adobe Systems
Jeff Pollard, Chief Technology Officer, SEOmoz, Inc
Came in late, I will do the best to catch up.
Jeff Pollard: Discusses LAMPrelated URL re-writting, URLs, redirects. The standard stuff. I assume he is discussing the Apache considerations.
PHP Some versions of PHP have a session id whole that can cause security issues and create problems for your canonicalization efforts.
Send the Correct Response Headers: Verify the responses and provide user friendly error pages.
MySQL; may have performance optimization issues. You should adjust your query_cache and key_Cache.
Is there an easier way?
Use web frameworks to make sure you are friendly to the engines.
- CakePHP
- Zend
- Ruby on Rails
- Merb
Colin Cochrane: Counter point to Jeff.
Issues are similar to LAMP stack for MS stack; URL rewriting, Custom error pages, Meta Data management, etc.
URL Canonicalization
Missing 301 redirects, doesn’t preserve the Path and Query and case insensitive URLS. Colin is showing the management console for a domain in IIS. Lots of issues fixed in II7. Canonical Character casing … I will get the slides and update this later
URL rewriting. again a huge amount of stuff here, but there are ways to handle this.
Customer Error Pages: rarely handled well. Content from a static file needs to preserve the response code. Request is handled by IIS. it gets tricky with the execution of a URL. There is an additional request made.
Intercepting Application errors. Use HttpModule set eventHandler for Context.Error event. avoid poor error capturing.
Meta Data management. Web.Sitemap; Easily extendible with additional sitemapnode attributes. Saves coding when master pages are used. This one page will centralize your management.
Performance: HTTP Compression rarely used, but should be. Static and Dynamic resources are your implementation types, but test before going down the dynamic route. Content expires. Set the expires HTTP header to minimize requests. Viewstate. Keep it underwraps. It adds no value to the search engine.
Duane Nickull:
Adobe plays nicely with all the stacks. Can’t force engines to read stuff. Render stuff out like in PHP. Open Screen Project: making Flash, Flex, AIR crawlable. Shows a site written entirely in flash that is ranking after 3 weeks. Google is reading inside of the Adobe TV. {Fail didn’t work on stage}. Cream rises to the top. Pitched MVMC Multiple views, Multiple clients. which is a cloaking technique.
Now he is talking about engine considerations. Nothing new versus the other speakers thus far.
Nikhil Kothari: Search engine friendly Silverlight apps.
Standard Microsoft stuff applies. Indexability, what and where. What do you want to index? How do you want to get the right search behavior from the engines. Gives classic web app versus RIAs. Silverlight wants to restore indexability to RIAs . Add indexable content. Publish content in line with RIA content. Design the RIA to consume the content and create a richer presentation.
Demo time…. Search unfriendly APP built in Silverlight. How could we fix this? Shows the bad source for the original page. Uses ASP.net to render out some alternate content. Same photos, Same code. Now the source code has all the detail with sematically correct markup to get the correct SE behavior. More steps to make content available to the SE. Builds on alternate content with Javascript.
Use Sitemaps to help discover other content around the application. Web development is about patterns. These patterns serve multiple purposes.
Q and A:
When is .Net going to work around the MVC framework?
Nikhil: We already are. It is on codeplex and we are sharing the source code in a completely open way.
Gotta run I will provide more feedback later.
Permalink http://thecubiclepunk.com/2008/06/live-smx-advanced-platform-considerations/




