terry’s Weblog

weblog for terry’s finding

SEO – what you don’t do…

Accompany with those “What You See Is What You Get” webpage editor being common such as Frontpage and Dreamwaver, it’s not a big thing to build a web site for personal or company. As web page editor being commonly use, a primary school student also know how to build up a website for their classmates’ visit.

But the problem is how to bring traffic for the website, carry some amorous pics? Make your site searchable in popular search engine should be one of the main source for traffic. SEO (Search Engine Optimization) becomes a hot and important topic nowadays.

SEO – http://en.wikipedia.org/wiki/Search_Engine_Optimization

Since the indexing rules of some search engines will change it from time to time, search engine optimization need enhancement frequently too. Of course, SEO we have thousand thing need to do but in the same time something we must to know what we DON’T do.

DON’T DO:
http://www.dailyblogtips.com/seo-its-about-what-you-dont-do/

  • Keywords stuffing – don’t spam keywords in you site, just use keywords when it need.
  • Mirrored Sites and Content Duplication
  • Hidden Text and Images

http://www.practicalecommerce.com/articles/166/Optimizing-HTML-Code-for-Maximum-SEO/

  • Image header and menu – it’s good for human to read but not search engine
  • Nested table – it can help your page easily indexed by search engine

http://seo-tutorial.seoadministrator.com/

  • Redirects
  • Session identifier – it make every ppl access with differnt URL. Search engine will treat it as a new page

If you want 100% sure your site prompt in the first few rows of those search engine, other than SEO, you might better pay the Adwords (Google) or YSM (Yahoo)

Good luck!

Filed under: Finding, Uncategorized

table or tableless?

This week start to have assignment on XHTML and CSS. Actually, it’s wonderful experience to know CSS implementation can separate the page content and design for editor and developer & designer to handle different files. Designer only need to have some amendment on the CSS file, page can look totally different instantly with same content. It might be a common practice today but not years ago.

Before CSS supported by widely browsers, most of developer also using nested tables to control web page layout instead of. Also CSS only use for font declaration. But after years, most of ppl would propose to use “Tableless” for code web page and leave “Table” for data presentation use.

Why? It’s really good? and How-to?

http://en.wikipedia.org/wiki/Tableless_web_design

“Tableless web design”

Pros:

  1. Accessibility: Easy to linearize the web page and help special screen like mobile & PDA access. It also good for search engine.
  2. Bandwidth saving: CSS can cache in browser and use for the rest of pages in the same site. No need to download those “style layout” html every time.
  3. Maintainability: Only change in 1 CSS and effect on pages using the same CSS.

Cons:

  1. Not good for some old browsers
  2. Different interpretatin of CSS for browsers
  3. Bugs

How-to:

A article from W3C for tableless layout how-to:

http://www.w3.org/2002/03/csslayout-howto.html.en

Enjoy and Happy CNY!

Filed under: Finding

Web to-go?!

Mobile phone or handheld devise should play a important role in the concept of “always connect”. Especially the so call 3.5G HSDPA become more common on those mobile devise and also carrier’s network.

To help the web page easier access by mobile devise, it’s better serve different set of CSS for page rendering. It could help web page looks better for specific devise OS. There is a CSS property, media type, can provide some logic for developer serve different set of CSS base on the user agent.

Media type info at w3: http://www.w3.org/TR/REC-CSS2/media.html

e.g. The following code can let different user agent render the web page with different font size.

@media print {
BODY { font-size: 10pt }
}
@media screen {
BODY { font-size: 12pt }
}
@media screen, print {
BODY { line-height: 1.2 }
}

The “media type” application might not properly work in the real world. It caused by some devise agent will not follow the definition to declare itself. e.g. a cell phone browser declare itself as a “screen” instead of “handheld”.

Filed under: Finding