---

***Under Construction***

Organic SEO Implementation

For every Web page being optimized, several page elements need to be abstracted for ease of maintenance and to ensure a consistent implementation across all Web pages. Updating individual pages using a design tool such as Dreamweaver is NOT a good process for several reasons:

• Cost: A copy of Dreamweaver is expensive to buy and install. As well, Dreamweaver has its own learning curve which although based on W3C standards, has its own, separate menus and organization to learn. Although Dreamweaver, in the hands of skilled user, is an excellent tool for template design, I question its value for Web page production.
• Inefficiency: Although you can build a model Web page very effectively in Dreamweaver, using Dreamweaver to update 10s to 100s of Web pages is very inefficient:
  • Meta tags are far above the are where the page content is defined. Looking at meta data while editing content involves scrolling up and down.
  • Dreamweaver is slower at opening documents than a good text editor.
  • A good text editor is very fast at finding a line and column to inspect a W3C error on a Page (view source). Using Dreamweaver would be more combersome.
  • Dreamweaver will create new styles while you edit. This is undesirable from a consistency across the entire Web site perspective.

A content management system, Web page composition (templating) strategy and dynamic content management is a much better choice for implementing anything but the very smallest Web site. Before looking further at the Web site organization, it is important to build a check list of what attributes a Web site implementation strategy should have. A working list of must have attributes follows:

• For every Web page, the following elements should be presented for review/change in a view unhindered with XHTML boilerplate:
  • Edit Meta data Title
  • Edit Meta description
  • Edit Meta keyworkds
  The meta data should be seen immediately above the start of content capture in content management system or template.
• Clean CSS page with color theme abstracted to a few PHP variables (or equivalent) to update the Web site's color scheme. Making multiple #xxxxxx edits through a style sheet is unacceptable.
• Flexible navigation menu bar across the top of page. Sub menus and sub sub menus should be available and highlighted based on current page.
• Flexible usage of hi, h2, h3, body, p, etc. elements for capturing page markup. There should be minimal non standard W3C syntax and little dependence of complex W3C syntax.
• Fully defined css style sheet. Mark-up elements in the content should be limited to h1, h2, etc. elements, p, ul, and b elements. Other aspects of layout belong in the style sheet.

---

---

Invoke W3C Validator Service for this page.