1. Advertising
    y u no do it?

    Advertising (learn more)

    Advertise virtually anything here, with CPM banner ads, CPM email ads and CPC contextual links. You can target relevant areas of the site and show ads based on geographical location of the user if you wish.

    Starts at just $1 per CPM or $0.10 per CPC.

All You Need to Know About SEO

Discussion in 'Search Engine Optimization' started by Dan Schulz, Jul 25, 2007.

Thread Status:
Not open for further replies.
  1. #1
    Yes, I know the thread title is rather "authoritative" and that people will think I'm talking out of my rectum, but I don't care. I've seen enough garbage, baloney, and flat out lies about SEO to gag a maggot a thousand times before getting to Hell and back, and I've had enough of it.

    Earlier tonight I wrote a post in another thread, which had started out as a "what to do before SEOing a site" but I got carried away and ended up belting out a "bunker buster" as you may choose to call it.

    Now, while the topic at hand may not have anything to do with the Google Sandbox effect (I won't even debate if it's real or not, since I could honestly care less) or how to pick your keywords (or what tools to use - and let's face it, like coffee, everyone has their favorite brand and flavor), this WILL teach you what you really need to know. You'll learn a bit about HTML semantics, how to properly use HTML elements and attributes, so even if you're an HTML coder, you might want to listen up and pay attention anyway, ya just might learn something.

    Now, I know I'm going to get flamed for this, especially by the radicals among us, but you know what? I don't care. You can negative rep me all you want, and it still won't matter. I'm a developer by trade, and among my sites under development is a search engine site for a niche I'm very passionate about (table-top warfare gaming). Anyway, on to the show as they say. :D

    Update: Due to the 20K character limit, one tip got added to the third post in this thread - please consider that part of the second post. Also, while the content is copyrighted BY ME (and yes, I will not hesitate to issue DMCA takedown notices if I find it published elsewhere without my permission), the three column layout example is in the public domain; this means you can do anything you want with it except copyright it and pass it off as your own work.
    Dan Schulz, Jul 25, 2007 IP
  2. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Contrary to popular belief and accepted conventional wisdom, search engine optimization should be done before you write one line of code. After all, a big part of SEO is actually marketing - in this case, you're marketing the Web site to search engines. And the best way to market to the search engines is to market the Web site to your potential visitors and customers. So how do you do that?

    • Pick a topic you want your site to discuss (or a product/service you want your site to sell).
    • Plan out the major sections of the Web site (home, about, news, contact, and so on are good places to start).
    • Write the content for the pages and sections of the site bearing in mind what keywords you want to target. If you don't know how to do this, go to your local public library and borrow a copy of "Web Copy That Sells" by Maria Veloso.
    • When you're done writing the content of each page, look at the content and see how much of the "fat" you can remove. Users generally prefer text that is short, sweet and gets right to the point. If you're going to be talking about items in a list, use a list (as I am here).
    • When reducing your page content, make sure you keep the content as naturally flowing and organic as possible, without shooting yourself in the foot or removing any keywords you want to target (remember to keep the keywords relevant to the topic you're writing the page about or the product/service you're promoting, reviewing or trying to sell - again, "Web Copy That Sells" by Maria Veloso will show you how to do this).
    • Review your page content again. By now it should be short, sweet and to the point. Your visitors will thank you (since they don't sit down and read, they skim), and if your keywords are still blending in with the content, then you're 1/3 of the way there.
    Once that's out of the way, and you've chosen how your Web site will look (which fortunately has NOTHING to do with the search engines), you will have to focus on the site's development. It doesn't matter a bit if you use static HTML, XHTML, PHP, ASP, Perl, Python, etc. All a search engine sees is the (X)HTML and the text content. Search engines have gotten better at indexing .pdf files and are now starting to be able to index Flash files, but for the purpose of this post I'm going to concentrate on plain old (X)HTML. So let's get started.

    • First and foremost, use the least amount of clean, semantic and valid HTML markup possible. Web pages follow a natural flow order of header, menu, content, sidebar(s), and footer. Structure your Web pages like this whenever possible. While search engines may not care if your pages are constructed with semantic markup or layout tables, your users will benefit from the use of semantic markup (since it'll be easier to access the page from a Web browser, screen reader, mobile phone, PDA, or whatever comes along in the next few years) - and it'll mean less work for the search engines as well (piggy-backing on the "human effect").
    • While really not a tip, I have to say this anyway; following the advice in the previous point will also help ensure that your pages load quickly (especially for dial up users). Which is a bonus, since if the page loads quickly, you won't be wasting as much time getting the visitor's attention (meaning you'll be more likely to keep them at your site longer - which can easily lead to conversions of regular repeat visitors or even customers); this can lead to other sites linking to yours later on (it also makes it easier for the search engines to get to the chewy content goodness in your pages as well).
    • Validate your code. This really isn't an SEO trick, but a page that is error free will be easier for the user agent (whether it's a browser, cell phone, PDA or search engine spider) to deal with than an error-ridden page.
    • Use headings appropriately (again with the semantics!). H1 is for the page title, not the site title. Don't use more than one H1 heading per page. If you think need more, then that means the page in question probably has two or more topics that are competing for attention, and thus should be separated (have one topic per page). H2 through H6 should be used when necessary, and always use at least two of them in the same nesting when you do (a great example of this at work is your local newspaper - pick one up and read an article or two).
    • Title attributes (title="text goes here") are good places to place keywords, but make sure the ones you use are appropriate to the page - and the section of the page you are placing them in. If it looks unnatural, it probably doesn't belong. Remember, title attributes are like tool tips - great sources of additional information. Just don't abuse them (if you're going to use them in your menu, try not to place keywords in them, just provide a brief description of what the page is about instead).
    • Same thing goes with image alt="alternative text" attributes. Use the alt attribute to identify what the image is about (if you're selling puppies, and you have a picture of a Jack Russell Terrier in your page, have the alt="" text identify the picture as a Jack Russell Terrier puppy). Note in this example that I used some keywords with the attribute. Let's say someone looks for Jack Russell Terriers (or "rat dogs" as I like to call them - hey, you don't like it, blame it on the movie "Crimson Tide") in a search engine; in this case, the keywords "Jack Russell Terrier" would be picked up in the search results, and if given enough weight by supporting content around it, can even drive human visitors to the Web page in question by ranking well.
    • I know I'm beating a dead horse here, but don't forget about semantics. If you have only a sentence or two, don't use a <p></p> element block to mark it up (as always there are exceptions, for example if you have blocks of paragraphs and one of them happens to be only a sentence or two). Either leave it alone, or use something more appropriate (depending on the situation, it may either be a DIV or a SPAN). Mark up your menus (and other lists of links) as unordered lists.
    • When adding classes and IDs, keep the semantics in mind. Just because your sidebar may be on the left today doesn't mean it will be tomorrow (if you change the design). So don't use "left-column" for your sidebar, just use "sidebar" instead. If your sidebar contains nothing but advertisements, mark it up as "advertisements" or "ads" instead. As for the menu, I prefer to identify the list menu (the main site navigation) as "menu" rather than "nav" or "navigation".

    There are some common "SEO Myths" that the crackpots and frauds will try to sell you on (like with the rest of their snake oil offerings - which are just that - snake oil). Some of the leading ones are "content first page design" "multiple H1s per page" and keyword stuffing. Let's look at these real quick and find out why they're about as reliable as spreading butter on a fresh burn wound.

    Content First
    Content First design centers around keeping the page content as close to the top of the Web page as possible. While I don't disagree that this can help the search engines (it does - as I've said before in other threads), what "content first" in this sense does is puts the page content (what you read) before the menu - sometimes even other page elements like the header (which, along with the menu, should be the only things between the content and the top of the page, unless you want to include helpful links like those to a site map, FAQ or help page, or a search box). Yes, the search engine spiders will have to go through the links to get to the content, but as long as your menu isn't as long as the Brooklyn Bridge, it won't matter since the search engines will still get to the content and index all of it anyway (which is doubly true if the page content is short, sweet, and to the point - which I talked about earlier).

    If you want to help your visitors get to the content right away (while still having the search box/menu between the header and content), then include a skip link between the header and menu. It's really simple, and looks like this:

    Code (Text):
    2. <div class="skip">
    3.     <a href="#content">Skip to Content</a>
    4. </div>
    The DIV is around the link because inline content cannot be a direct descendent of the opening <body> tag in Strict (X)HTML DOCTYPES. Also by using a class of "skip" on the DIV, you can style the link to appear when hovered over (you can see this in action over at www.molly.com; just hover over the header - she even has a blog post on how to make your own). If you have a DIV wrapping your page's content, then you can safely remove the DIV and apply the class to the anchor instead.

    The #content ID will lead the visitor (or search engine) to the DIV with the ID of "content" on the current page. I chose "content" because that's what the main page content is. Whether you're selling tickets to a Cubs game, CDs of Rush's latest album "Snakes and Arrows" or blogging about how much the new Fantastic Four movie sucked (if you thought the movie was great, you can replace "sucked" with "rocked"), the DIV that holds the content should have an ID that you can refer to with the skip link.

    Now, if you want to see an example of a Web site that has so many links and other detritus that it will take a search engine or mobile user FOREVER to get to the content, check out my city's Web site (no I did not design it) at http://www.aurora-il.org. Turn off the CSS in your browser, or take a peek at the source code. That's a LOT of menu links - most of which shouldn't even be where they are. Especially the left side menu's links (those should be after the content, and positioned on the left side using floats and negative margins). The top menu is pushing it (it's a large dropdown menu), but since it actually serves a purpose, I can forgive that.

    Multiple H1 Headings
    H1 should be used to identify the title of the Web page. Which means it should be used once. This element is often abused as the Web site's title, even though that job should be left to a DIV container with an ID of "header" with an IMG element inside it (containing appropriate alt="" text; I also advocate using an empty title="" attribute to overcome an Internet Explorer bug, but that's one of the few times I suggest breaking my rules about Web semantics) for the actual logo (other branding, like a background, can be applied to the DIV via a stylesheet instead). If you're using more than one H1 heading, you're either abusing the search engines like Jacko would... :eek: -- ok I'll shut up before I get banned :), not using the element properly, or have two or more topics on the page that should be divided into separate pages (this will also help prevent keyword dilution, which I'll touch upon briefly a bit later). One H1 heading per page, that's it.

    As for other headings, use them as needed, but always maintain an outline-like structure when using them. Here's an example of what I mean (bear in mind this is only an example).

    Code (Text):
    2. [b]H1 Heading[/b]
    3.     [b]H2 Heading[/b]
    4.         Ooh, yummy page content.  I wonder if I can have cake and ice cream with it.
    5.         Ooh, yummy page content.  I wonder if I can have cake and ice cream with it.
    6.             [b]H3 Heading[/b]
    7.                 Speaking of cake and ice cream, Oberwies Dairy has the best ice cream in the Midwest.
    8.                 Speaking of cake and ice cream, Oberwies Dairy has the best ice cream in the Midwest.
    9.             [b]H3 Heading[/b]
    10.                 But where will I get the cake?  I want to have my cake and eat it too!
    11.                 But where will I get the cake?  I want to have my cake and eat it too!
    12.             [b]H3 Heading[/b]
    13.                 Oh well, I guess I can still have ice cream for breakfast tomorrow morning.
    14.                 Oh well, I guess I can still have ice cream for breakfast tomorrow morning.
    15.     [b]H2 Heading[/b]
    16.         Speaking of cake and ice cream, I like chocolate cake and Neapolitan ice cream.  Especially when watching the Cubs and Bears beat up on everyone.
    17.         Speaking of cake and ice cream, I like chocolate cake and Neapolitan ice cream.  Especially when watching the Cubs and Bears beat up on everyone.
    See how neat and structured that is? (Please forgive the wacky comments, they're just illustrative fluff.) If I had, for example, one H2 and two H3s, I'd look at how the page's content was written and re-write if necessary so I wouldn't need to use the H3s (I'd probably replace them with H2s if the content was appropriate). Also, if I had two H2s but one H3, I'd get rid of the H3 entirely if I couldn't get another sub-section of content related to the content identified by the H2.

    Keyword Stuffing
    Keyword stuffing is a rampant problem. Often times you'll see sites stuffing keywords for things that have absolutely nothing to do with the Web page. Other times you'll see relevant and appropriate keywords, but you'll also see too many of them. How many is too many? Usually when you have more than three in a single element (excluding paragraphs) or attribute. If it looks unnatural to you (as a regular user), then you're probably using too many of them and should cut them back a bit (or a lot, depending on how many are there).

    When you do use keywords, make them blend in with the content as much as possible (you should have done this before you even sat down to write one line of code or let your WYSIWYG editor barf up the code for you). For example, last year I wrote a post elsewhere on Digital Point's forums about how to use PHP and server side includes to make it easier to maintain a Web site over time. Take a look at that last sentence. Notice how I used "PHP" and "Server Side Includes" in the link? Those are keywords that are included naturally in the link to reinforce what the link to the forum post is about. I also didn't stuff the link to the gills with keywords either. Just two (in this case "PHP" and "Server Side Includes") was all I needed. And chances are you probably didn't realize it (or the link to Cubs.com earlier). Also remember that having too many keywords can dilute the strength of the keywords you have.

    The Truth About Page Rank
    Warning: PageRank is a moving target - what was written here today may not be true tomorrow or next week. use it as a baseline and conduct your own research afterwords. Heck, I may have even gotten a thing or two wrong here (I'm only human afterall).

    Speaking of links, don't forget that PageRank is all about links. Google has a preference for natural links (like the one I gave in the above paragraph) and will give them more weight if used properly. The more natural links pointing to your Web page, the higher your page rank will probably be. The more links pointing from your page to other pages, the lower your page rank will most likely be. Ideally, you want MORE links pointing to your page than you want pointing out. Bear in mind this works for EACH page, not your whole site or domain. Google doesn't care about your whole site's PR (which doesn't exist) - it weighs pages, not sites, after all.

    One thing I like to do, and this has far more to to do with usability than search engine optimization (the search engines will benefit from the human-first approach, which confuses many people and convinces them that the search engines prefer this method when they really don't care either way) is to include natural, relevant links to other pages of my Web site in my page content. I'm not talking about the menus, or a site map here. I mean organic links, like the one to the PHP/SSI tutorial I wrote last year. Obviously, the link would lead to a page on my site that was related to (and relevant to) the page I'm linking from (for example, if my page is about teaching people how to review movies, and I have a review of "Pirates of Caribbean 3" elsewhere on my site, I'd probably link to the page as an example of how to write an effective movie review), rather than something totally unrelated (like vacation trips to the Caribbean). What I'd be doing is giving some weight (or credibility) to the Web page I was linking to. While this will bleed some PR (PageRank) from the current page, if you link your own pages into a "web" of pages (responsibly, don't over-do it), it'll balance out in the end, and you may (doesn't mean it always will) even enjoy a net profit on your individual pages' PR before the external links to your pages start coming in.

    And please, for the love of all that is good, don't use nofollow on links - you're doing the owner of the page you're linking to more harm than good, so if you do, you might as well just use plain text anyway and avoid linking altogether.

    What about META tags?
    5-10 minutes at most. They're practically worthless, but they're nice to have, since they will remind you what keywords you're targeting. Unfortunately this means your competition will too, but you can't win them all. Spammers and black-hatters abused these elements so much that the search engines give them about as much weight (and credibility) as a bouncer at a private nightclub gives a person who's name is not on the guest list.

    Ok, now that all that's out of the way, and your site's done, go out there and promote it. Submit the site to the search engines (preferably by hand, it only takes a couple minutes), include a link to the site in your forum signatures, comment on blogs (leaving a link to your site in the "Your Web site" form input field if it's related to the blog and not otherwise spammy). Don't worry about buying links or submitting to directories - Google's actually discounting "paid links" (they're even suggesting people report paid links to them), and most directories aren't worth submitting to anyway (especially if you have to pay). If you find a couple reputable free directories to submit to, go ahead and submit your site to them (since you won't be losing anything) and spend your advertising/marketing/promotion dollars (or Euros or yen or rubles, or whatever currency you use) elsewhere. Traditional marketing and advertising (there is a difference between the two) will kick in at this point.

    The TITLE Element
    Not much to say here, other than to keep them short, to the point, and make sure the page title comes first. You can (and should) put your site title afteword, but use a delimiter so people can tell the difference between the page title and the site title (even though they're in the same element). Here's an example.

    Code (Text):
    2. <title>Chicago Cubs Win 2007 World Series - Skewed View of the News</title>
    Don't expect quick results (though you CAN get them if you follow my advice), since "quick results" can be lost just as quickly. What I suggested above is a proven method for long-term sustainable growth, which is what you want anyway. It's better to be strong and stable for a long time (like a large rock) than to be like a shooting star - you get noticed quickly, but you'll be gone just as fast if you choose the latter.

    After that, just continue writing quality content that others will kill their own mothers to link to, continue promoting your Web site to the public, and you'll most likely be fine. Then, and ONLY then, should you worry about optimizing your site for the search engines - oh wait, no you shouldn't, since you'll have done that already without even realizing it. :D
    Dan Schulz, Jul 25, 2007 IP
  3. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Ok, I'm supposing you want an example of what I mean by a Web site layout that has the header, search form, menu, content, sidebars and footer, right? Ok, the code isn't 100% perfect, but I'm going to give you one of my sample three column layouts that I'm going to use once I tweak a few things (it's just positioning with floats and negative margins, no images, which need to be added later via CSS). Internet Explorer has a few problems with the search form and the menu interacting when the text is resized (not to be confused with page zoom), but that can easily be corrected by using a negative margin to push the search box above the menu's row with CSS.

    Also note that you should separate your stylesheet and JavaScript files into separate files and link to them from the Web page. I don't remember if I covered that or not in the previous post, but if I didn't consider this to be part of the "SEO Gospel" (I didn't separate the XHTML and CSS in this post since the sample is still a work in progress).

    Code (Text):
    2. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    3. <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
    4. <head>
    5.     <title>Three Column Layout with Horizontal Main Menu Site Template</title>
    6.     <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
    7.     <meta http-equiv="imagetoolbar" content="no" />
    8.     <meta name="keywords" content="Keywords go here" />
    9.     <meta name="description" content="A description of this page goes here." />
    10.     <style type="text/css" media="screen,projection">
    12.     * {
    13.         margin:0;
    14.         padding:0;
    15.     }
    17.     html, body {
    18.         height: 100%;
    19.     }
    21.     body {
    22.         background: #EEE;
    23.         color: #000;
    24.         font: normal 85%/140% tahoma, verdana, arial, helvetica, sans-serif;
    25.     }
    27.     #container {
    28.         min-height:100%;                                    /* squashes an IE 7 bug */
    29.     }
    31.     * html #container {
    32.         height:100%;                                        /* IE 5.x and 6 treat height as min-height */
    33.     }
    34.         #header {
    35.             background: #FCF;
    36.             color: inherit;
    37.             height: 80px;
    38.         }
    40.         #wrapper {
    41.             float: left;
    42.             padding-bottom: 32px;
    43.             width: 100%;
    44.         }
    45.             #search-form div {
    46.                 background: #CCC;
    47.                 color: inherit;
    48.                 float: right;
    49.                 height: 2em;
    50.             }
    51.                 * html #search-form div {
    52.                     position: relative;
    53.                         right: 3px;
    54.                 }
    56.                 #search-form input {
    57.                     float: left;
    58.                     margin: 0.25em;
    59.                     padding: 0 0.4em;
    60.                 }
    62.                 * html #search-form .submit {
    63.                     margin: 1px 0 -1px 0;
    64.                     padding: 0;
    65.                 }
    67.                 *:first-child+html #search-form .submit {
    68.                     margin-top: 1px;
    69.                     padding: 0;
    70.                 }
    72.             #main-menu {
    73.                 background: #CCC;
    74.                 color: inherit;
    75.                 height: 2em;                                /* IE Haslayout - fix double margin */
    76.                 line-height: 2em;
    77.                 list-style: none;
    78.             }
    79.                 #main-menu li {
    80.                     display: inline;
    81.                     white-space: nowrap;
    82.                 }
    83.                     #main-menu a {
    84.                         background: #0E0;
    85.                         color: inherit;
    86.                         float: left;
    87.                         height: 2em;
    88.                         margin-right: 1px;
    89.                         padding: 0 0.5em;
    90.                         text-decoration: none;
    91.                     }
    93.                     #main-menu a:active,
    94.                     #main-menu a:focus,
    95.                     #main-menu a:hover {
    96.                         background: #FF8;
    97.                         color: #000;
    98.                     }
    100.             h1 {
    101.                 background: #FFF;
    102.                 clear: both;
    103.                 color: inherit;
    104.                 font-size: 1.75em;
    105.                 line-height: 1.8em;
    106.             }
    108.             h2 {font-size: 1.5em;}
    109.             h3 {font-size: 1.05em;}
    110.             h4 {font-size: 0.95em;}
    111.             h5 {font-size: 0.85em;}
    112.             h6 {font-size: 0.75em;}
    114.             #content {
    115.                 float: left;
    116.                 margin-bottom: 0.5em;
    117.                 width: 100%;
    118.             }
    119.                 #content .section {
    120.                     background: #CCF;
    121.                     color: inherit;
    122.                     font-size: 1em;
    123.                     height: 1%;                             /* triggers hasLayout in IE 5/6; ignored by other browsers due to lack of height definition in #content */
    124.                     margin: 0 14.5em 0 9.85em;
    125.                     padding: 0.5em;
    126.                 }
    127.                     #content h2 {
    128.                         background: #CCF;
    129.                         border-bottom: 1px solid #000;
    130.                         color: inherit;
    131.                         margin-bottom: 0.2em;
    132.                         padding-bottom: 0.25em;
    133.                     }
    135.             #sidebar {
    136.                 background: #FFD;
    137.                 color: inherit;
    138.                 float: left;
    139.                 margin: 0 0 0.5em -14em;
    140.                 padding: 0.5em 0;
    141.                 width: 14em;
    142.             }
    143.                 #sidebar h2 {
    144.                     background: #FFD;
    145.                     border-bottom: 1px solid #000;
    146.                     color: inherit;
    147.                     margin-bottom: 0.2em;
    148.                     padding-bottom: 0.25em;
    149.                     text-align: center;
    150.                 }
    152.                 #sidebar p {
    153.                     padding: 0 0.5em;
    154.                 }
    156.             #secondary-menu {
    157.                 float: left;
    158.                 list-style: none;
    159.                 margin: 0 0 0.5em -100%;
    160.                 width: 9.75em;
    161.             }
    162.                 #secondary-menu li {
    163.                     float: left;
    164.                     padding-bottom: 1px;
    165.                 }
    166.                     #secondary-menu a {
    167.                         background: #FCC;
    168.                         color: inherit;
    169.                         display: block;
    170.                         padding: 0.25em 0.5em;
    171.                         text-decoration: none;
    172.                         width: 8.25em;                      /* IE will mouseover highlight but not let you click link in 'non-text' area unless you set width */
    173.                     }
    175.                     * html #secondary-menu a {
    176.                         width: 9.25em;
    177.                         w\idth: 8.25em
    178.                     }
    180.                     #secondary-menu a:active,
    181.                     #secondary-menu a:focus,
    182.                     #secondary-menu a:hover {
    183.                         background: #FF0;
    184.                         color: #000;
    185.                     }
    187.     #footer {
    188.         background: #8EF;
    189.         color: inherit;
    190.         float: left;
    191.         font: normal 12px/16px tahoma, verdana, arial, helvetica, sans-serif;
    192.         margin-top: -32px;
    193.         padding: 8px 0;
    194.         text-align: center;
    195.         width: 100%;
    196.     }
    198.     </style>
    199. </head>
    200. <body>
    201. <div id="container">
    202.     <div id="header">
    203.         <img src="#" width="300" height="80" alt="Web Site Title" />
    204.     </div>
    205.     <div id="wrapper">
    206.         <form action="#" id="search-form" method="get">
    207.             <div>
    208.                 <input type="text" id="search" name="search" size="25" />
    209.                 <input type="submit" class="submit"value="Search" />
    210.             </div>
    211.         </form>
    212.         <ul id="main-menu">
    213.             <li><a href="#">Menu Item</a></li>
    214.             <li><a href="#">Menu Item</a></li>
    215.             <li><a href="#">Menu Item</a></li>
    216.             <li><a href="#">Menu Item</a></li>
    217.             <li><a href="#">Menu Item</a></li>
    218.             <li><a href="#">Menu Item</a></li>
    219.         </ul>
    220.         <h1>Top Level Heading</h1>
    221.         <div id="content">
    222.             <div class="section">
    223.                 <h2>Second Level Heading</h2>
    224.                 <p>
    225.                     Lorem ipsum dolor sit amet, consectetuer adipiscing elit. In quis erat. Nulla
    226.                     auctor consectetuer erat. Sed est tellus, laoreet et, faucibus et, cursus ut,
    227.                     lectus. Nulla scelerisque, mi vel commodo consequat, turpis ligula congue ligula,
    228.                     eget pellentesque turpis augue quis diam. Nulla facilisi. Etiam commodo quam in
    229.                     metus. Etiam nec nisi ac nisl molestie fermentum. Donec ligula ipsum, venenatis in,
    230.                     egestas vel, commodo bibendum, est.
    231.                 </p>
    232.             </div>
    233.             <div class="section">
    234.                 <h2>Second Level Heading</h2>
    235.                 <p>
    236.                     Lorem ipsum dolor sit amet, consectetuer adipiscing elit. In quis erat. Nulla
    237.                     auctor consectetuer erat. Sed est tellus, laoreet et, faucibus et, cursus ut,
    238.                     lectus. Nulla scelerisque, mi vel commodo consequat, turpis ligula congue ligula,
    239.                     eget pellentesque turpis augue quis diam. Nulla facilisi. Etiam commodo quam in
    240.                     metus. Etiam nec nisi ac nisl molestie fermentum. Donec ligula ipsum, venenatis in,
    241.                     egestas vel, commodo bibendum, est.
    242.                 </p>
    243.             </div>
    244.         </div>
    245.         <div id="sidebar">
    246.             <h2>Sidebar Heading</h2>
    247.             <p>
    248.                 Lorem ipsum dolor sit amet, consectetuer adipiscing elit. In quis erat. Nulla auctor
    249.                 consectetuer erat. Sed est tellus, laoreet et, faucibus et, cursus ut, lectus. Nulla
    250.                 scelerisque, mi vel commodo consequat, turpis ligula congue ligula, eget
    251.                 pellentesque turpis augue quis diam. Nulla facilisi. Etiam commodo quam in metus.
    252.                 Etiam nec nisi ac nisl molestie fermentum. Donec ligula ipsum, venenatis in, egestas
    253.                 vel, commodo bibendum, est.
    254.             </p>
    255.         </div>
    256.         <ul id="secondary-menu">
    257.             <li><a href="#">Menu Item</a></li>
    258.             <li><a href="#">Menu Item</a></li>
    259.             <li><a href="#">Menu Item</a></li>
    260.             <li><a href="#">Menu Item</a></li>
    261.             <li><a href="#">Menu Item</a></li>
    262.             <li><a href="#">Menu Item</a></li>
    263.             <li><a href="#">Menu Item</a></li>
    264.         </ul>
    265.     </div>
    266. </div>
    267. <div id="footer">
    268.     Copyright &copy; 2006-2007, The Monster Under the Bed. All Rights to Scare Unsuspecting Children Reserved.
    269. </div>
    270. </body>
    271. </html>
    Dan Schulz, Jul 25, 2007 IP
  4. gerritpoel

    gerritpoel Active Member

    Likes Received:
    Best Answers:
    Trophy Points:
    Thank you.
    I had a great read. It's a good summary of what to do for optimization.
    I don't see why this should get flame, when there is so much junk out there.
    Keep it up.
    gerritpoel, Jul 25, 2007 IP
  5. Relivo

    Relivo Member

    Likes Received:
    Best Answers:
    Trophy Points:
    Great post :) A few good tips there ;)
    Relivo, Jul 25, 2007 IP
  6. netstorm

    netstorm Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Good post, I just brushed over it but most I read is pretty dead on.
    netstorm, Jul 25, 2007 IP
  7. androomidaa

    androomidaa Active Member

    Likes Received:
    Best Answers:
    Trophy Points:
    yah i enjoyed it too Dan Schulz. have bookmarked and to make sure i dont miss a thing, would you mind if i copy everything? not to make another seo book but for my sites. im a newbie and every read is a good lesson for me. thanks for the infos by the way....great stuff keep it up and dont bother if anyone drops bunker busters...u know what to do right?
    androomidaa, Jul 25, 2007 IP
  8. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    I had to edit the post a bit (I originally wrote it on the fly as a response to another poster's question in another thread). As for the layout, if you want to use it in your own work, go right ahead. It's officially PUBLIC DOMAIN (meaning you can do whatever you want with it, except copyright it).

    Just don't copy the post. I'll be reproducing this post in a Web site to be launched later this year. If you wish to link to the article, feel free to (cite this thread as the source until the site goes live).

    EDIT: If you want to copy it for your personal use (meaning to print to paper or save on your computer), go right ahead. Just don't re-publish the content elsewhere.
    Dan Schulz, Jul 25, 2007 IP
    Mikesblank likes this.
  9. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Actually, and I hope you don't get offended, but I would mind. I'm planning on cleaning this up and putting it on a site I'm working on. However, if you like, you can write a review on it, citing excerpts from this thread as needed, and then just cite the thread as your source (I'll even get the site URL to you afterword so you can amend your page when it goes live if you like).

    EDIT: If you want to copy it for your personal use (meaning to print to paper or save on your computer), go right ahead. Just don't re-publish the content elsewhere.

    But as for the Web page template, see above. :)
    Dan Schulz, Jul 25, 2007 IP
  10. MasterG

    MasterG Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Very good knowledge. Thank you very much.
    MasterG, Jul 25, 2007 IP
  11. princess.donna

    princess.donna Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    thanks for sharing this one :)
    princess.donna, Jul 25, 2007 IP
  12. androomidaa

    androomidaa Active Member

    Likes Received:
    Best Answers:
    Trophy Points:
    okay no problem...
    androomidaa, Jul 25, 2007 IP
  13. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Just so you know, I updated a few things, cleaned up the second post, and added some new content. I really don't like the 20,000 character limit but I can understand why it's there.
    Dan Schulz, Jul 25, 2007 IP
  14. Zanswer

    Zanswer Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Good stuff. People can easily get carried away by fancy SEO ideas and often forget about fundamentals. Thanks.
    Zanswer, Jul 25, 2007 IP
  15. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    It's really not just the fundamentals of SEO. It's also the fundamentals of Web development, which unfortunately really isn't taught by anybody (especially schools and books).
    Dan Schulz, Jul 25, 2007 IP
    Halobitt likes this.
  16. Epica

    Epica Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    Excellent post - good read!
    Epica, Jul 26, 2007 IP
    thaisbo likes this.
  17. trichnosis

    trichnosis Notable Member

    Likes Received:
    Best Answers:
    Trophy Points:
    it's a great post. i loved to read it :)
    trichnosis, Jul 26, 2007 IP
  18. kthor

    kthor Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    great reading I actually read all of it
    kthor, Jul 27, 2007 IP
  19. Dan Schulz

    Dan Schulz Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    There's more coming, trust me on this. :D

    It's just going to come in fits though, given the demands of my schedule (and helping people out here and on SitePoint when I'm not too busy dealing with the rest of the forum staff - fresh squeezed Mentor, served daily).
    Dan Schulz, Jul 27, 2007 IP
    Veroissa likes this.
  20. GeorgR.

    GeorgR. Peon

    Likes Received:
    Best Answers:
    Trophy Points:
    will bookmark and read later more in detail...but from what i saw...can it be that you do NOT have a big priority on page title ? My experiences are that page title is extremely important, so..defintly put keywords in the title !
    GeorgR., Jul 27, 2007 IP
Thread Status:
Not open for further replies.