CSS, AJAX, Web 2.0 & Search Engines, Friday April 13, 2007 12:30 pm Organic Track
Moderator: Danny Sullivan
Speakers: Shari Thurow, GrantasitcDesigns.com Jim McFadyen, CriticalMass Dan Crow, Google Amit Kumar, Yahoo! Search Ryan Johnston - Critical Mass
This is the final session for me today and one of the last for the conference. Again, it is being held in a ballroom sized room and it's cold in here (but better than being in some of the hot rooms.) I didn't have info in advance on who would be moderating, but Danny Sullivan just appeared and it will be he who moderates this session. Two minutes to go and the room is starting to buzz and fill up.
Danny is at the podium and cracking jokes. Last session of the last day. This will be the "best session" he jokes. The web has evolved as more people are making use of css, ajax. Issues for SEO? Shari leads off.
I think everybody who attends the last session deserves a reward. CSS - html addition that allows webmasters to control design, font, link appearance, etc. It’s a text file. SE's can read it. Decreases download time of page. Easier to control elements on a page. Communicates visited and unvisited links. Ability to control look of a site. SE's monitor hidden links. Disadvantages - end users have to have the fonts you call in stylesheet. users prefer a font that is not commonly installed on all computers; they often prefer odd typefaces found in print. Css hyperlinks clutter a page. Sometimes there is unusual text wrapping when a stylesheet is changed, like changing font sizes. CSS can be used to hide text on a page. SE's don't use alt text to determine relevancy. Some people use h1 tags as workaround and they make a lot of content h1 tags in CSS. CSS layer coordinates are something SE's can detect. Some SEO's try to hide content in negative coordinates. CSS makes it easy to put layers on top of each other, making it easier to use CSS to hide text. They myth is that you can use CSS to hide things from SE's. Drop down menus are not considered spam because text is meant to be read by humans and so are the links.
Ryan and Jim co-present:
AJAX enhances the user experience. Engineers come in and change anchors on the page to change function to AJAX calls. Ensure your baseline app supports non-AJ users, including spiders. AJ can help a site be more interesting for users. make it run faster. offer assistance, like Google suggest.
Ex - Rolex.com
copy in nav wanted nav accessible from every page
They didn't want all content indexed by SE's. Solution was AJAX.
[This is a very techy presentation. He is having trouble showing his examples from a live site due to FLASH. It's hard to take notes on this session because he is showing AJAX solutions in use.]
[Note: This session was about conflicts, or not, with CSS and AJAX with search engines. It was a little hard to follow if you don't know about AJAX and what it is used for. It was interesting to hear what the search engine reps had to say. I think as AJAX solutions become more popular, we'll be hearing more about this and getting more details on actual applications for use.]