Home > SEO > SEO Considerations

SEO Considerations

February 4th, 2010 Leave a comment Go to comments

Here are some of the SEO considerations that I make when building a website. Let fellow readers know what you think I may have missed and what your thoughts are in the comments.

Domain Name

The first consideration is the Domain Name. I normally aim to get a dot com but failing that, a dot net is probably the next best option.

In the domain name, aim for about 2 keywords and avoid dashes and numbers. Also, try and come up with a domain name that can be verbally told to somebody without confusion as to how to type it into a keyboard e.g. crazyfrog.net rather than 2leap-4joy.com as an extreme example.

Registering a dot com helps people to key in the correct domain name for your site since they are likely to assume that it is a dot com unless it’s regionally specific such as .au or .co.uk for example.

URL Format

Here I tend to go for a URL stub that is formed from my post title (post/my-keywords/). I avoid the query string format (post?id=44)

In WordPress, you enter /%postname% in the admin area under Settings->Permalinks->Custom Structure Then, your post name (post title text) will be used to form this link. You just have to be careful not to use the same post title again.

Page Title

This is the most important thing to get right for on-page SEO. Check out search engine results and see how they highlight the keywords in the page titles. So if your web page is about SEO Considerations, only have these words in the Title tag of the page.

Description

This is a meta-tag which means it slots into the header part of your page, I tend to avoid using this and prefer to let the search engine grab my first paragraph of my post. So we need to remember this when writing our post, that the first paragraph is important for SEO and should strongly relate to the keywords in our title tag and the URL.

Keywords Meta Tag

I try to avoid using this since it is old-in-the-tooth and has a history of keyword manipulation. One reason that I avoid the Description meta tag too. These can be a signal to a search engine that you are trying too hard to optimize your site for SEO and not naturally posting content.

On a side-note, the popular plugin “All in one SEO pack” does make heavy use of these tags, and it comments on every page of your site in hidden text as to what changes it made to your pages.

Duplicate Content

Avoid replication of large amounts of content on your website. This is recommended by Google in their webmaster guidelines.

Unfortunately, WordPress out-of-the-box does this in the archives and on the home page. So they introduced a band-aid solution in the form of the canonical meta tag that is designed to indicate which page is to be recognized as the main one. And All-in-one SEO pack makes use of this coupled with search engine robot meta tags to no-index pages.

But I would rather not use these work-arounds.

What I did was to set up my blog to only display 1 post on the home page, and excerpts in feeds and archive pages. So I now have substantially different pages on virtually every area of my blog (latest post excepted). Or at least, once I post more content.

Providing only excerpts as part of feeds is a good way to avoid having your entire blog posts republished all over the web (since syndication means you want what you syndicate in feeds to be republished according to any license agreement that you may attach to the feed). Check out the creative Commons license if you would like to insist on attribution links back to your site.

OK, that is me done for now on on-page SEO, I have more to add on this later. But I welcome your comments and questions …

Post to Twitter

Categories: SEO Tags:
  1. February 5th, 2010 at 02:45 | #1

    One great coding tip for onpage SEO is markup hierarchy.

    regards,
    pffmihai

  2. Andrew
    February 5th, 2010 at 03:17 | #2

    For folks that are interested in markup hierarchy it concerns the structure of your website in the interests of extreme SEO like the order of how your page content is delivered to the search engines.

    This topic will be covered in detail later on from this site together with extreme optimization, obfuscation, compression and zipped-up delivery of web content for maximum speed.

    We will lead where others follow!

  3. February 5th, 2010 at 04:17 | #3

    Sorry, Andrew!

    First of all, I apologize. I realized now that I did not offer here anything for your readers.

    Second, that’s not my website, although I wish it was :)

    The Markup hierarchy, as you said concerns the order the website serves the content to search engines crawl bots.

    For example, we all know the classic/basic of a website content structure:

    1. Header
    2. Content
    3. Sidenav
    4. Footer

    Using absolute position in CSS one can place the content part at the top in the code so crawlers get the important content first. And then we serve the header, sidenav, footer.

    The beautiful thing about absolute positioning in CSS is that although the content is served first hand to crawlers, we can make the browers render the page normally for visitors.

    I’m sure that you Andrew already knew that, I just wanted to join/start a conversation.

    regards,
    pffmihai

    PS: Bookmarked your site after I found a comment of yours on John Chow’s blog.

  4. Andrew
    February 5th, 2010 at 20:04 | #4

    Hey pffmihai

    no problem, thanks for your input on the topic.

    I used to spend time using absolute positioning to move my content above the navigation links etc. but now I think that the search engines are likely to grab the whole page content and analyze all of it.

    In the dial-up days, I was thinking that if I coded a search engine spider, I would save bandwidth by only grabbing the first part of a page.

    But now, the html size in bytes can’t be much of an issue in most cases I think.

    I noticed that Google has a team working on page speed and provide recommendations for speeding up page load times. The main thing is to minimize the number of http requests, but I see this as more concern to very high traffic sites.

    For our blogs we can install a cache plugin to lighten the load on the server. This is where static versions of the posts are delivered rather than building the same page over and over via the database.

    Another way to streamline web pages is to strip out comments and whitespace and line breaks. Also we can minimize the length of ID and Class names and remove surplus HTML by switching to HTML 4.

    To go more extreme, we can ignore standards and code with minimalist code that still renders OK in browsers such as omitting the doc type declaration.

  1. No trackbacks yet.

CommentLuv Enabled