I'm saos@ngmo

1. Sử dụng .htaccess để chuyển tên miền từ non-www thành dạng www (sử dụng redirect 301)
2. Gia hạn tên miền của bạn thêm vài năm (khuyến khích trên 5 năm)
3. Đảm bảo răng khi khách click vào logo của site bạn thì họ dc đưa trở lại trang chủ
4. Nếu font chữ của website bạn quá nhỏ, hãy cho nó về mức tiêu chuẩn (như thế này nè ), SE có thể bỏ qua site bạn nếu font chữ quá nhỏ (continue reading…)

This should be usefull here are 250 free blog sites List to build some blogs and get some good links from them.

http://www.blogger.com/

http://www.myspace.com/

http://www.livejournal.com/

http://wordpress.com/

http://geocities.yahoo.com/

http://www.filefront.com/ (continue reading…)

Out of all the questions that I see throughout the forums, there is one that really stands out that we will explore today. How to get Google to index your site fast. (continue reading…)

Making basic alterations to a website to improve search engine performance is not rocket science. Here is a quick guide to the factors that can be easily manipulated yet yield big improvements. They are worth bookmarking or printing off, so that they can be used in the future as a checklist when creating new pages or reviewing old. (continue reading…)

This is a compilation of stuff Matt Cutts has said historically, minus some of the more recent stuff here, here, and here.  I decided I’d dig backwards and document some of the older stuff.  I dated it accordingly.  Here it is:

1. http://www.mattcutts.com/blog/dashes-vs-underscores/
Matt recommends using dashes over underscores to delimit words in urls. 2005.
Google does not algorithmically penalize for dashes in the url despite the fact that some have raised it as a possible heuristic for spam detection. I think WordPress pretty much precludes this anyway. 2005.

2. http://www.mattcutts.com/blog/seo-mistakes-sneaky-javascript/
Google takes action on individual instances of spam when they find it, but they focus on creating better algorithmic solutions. He states that he would not recommend using sneaky JavaScript redirects because your sites may get nailed in the near future. 2005.

3. http://www.mattcutts.com/blog/whats-an-update/
Google updates their index data — including backlinks and PageRank all the time.  However, they export and publish new backlinks and PageRank data approximately every three months.  New backlinks and PageRank are meaningless — it is not an update.  The information is likely already factored in for awhile before you see it. 2005.

4. http://www.mattcutts.com/blog/seo-mistakes-nearly-hidden-text/
Hiding text using similar colors and background colors can actually be worse than using the same colors. Using “#EEEEEE” instead of solid white on a solid white background can look worse — as if you’re trying to hide it.  I suspect this is a heuristic for detecting hidden text. 2005.

5. http://www.mattcutts.com/blog/q-a-thread-march-27-2006/
If you sell links, Matt says you should use link condoms.  Otherwise your reputation may fall.  I assume this means they will devalue your outbound links. 2006.

6. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Googlebot can only crawl the free portions that non-subscribed users can access since it does not log in.  Therefore, be sure to excerpt material in the free version that that offers value. Vanessa Fox. 2006.

7. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
If you must use Flash, you must also make an HTML version available as well. Block the Flash version from the crawlers with a robots.txt file. Vanessa Fox. 2006.

8. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Use user-friendly URLs like “african-elephants.html,” and not “343432ffsdfsdfdfasffgddddd.html.” Don’t overdo it either — african-elephants-and-their-habitats-etc-etc-etc-etc.html. Vanessa Fox. 2006.

9. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Assign unique, descriptive <title> tag and headings to every page. Vanessa Fox. 2006.

10. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Minimize the number of redirects upon hitting a URL. Vanessa Fox. 2006.

11. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Minimize the number of URL parameters — 1-2 parameters if possible. Vanessa Fox. 2006.

12. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Don’t use a parameter named “id=” in a URL for anything other than a session ID. Otherwise, it may not be included in the index. Vanessa Fox. 2006.

13. http://www.mattcutts.com/blog/guest-post-vanessa-fox-on-organic-site-review-session/
Earned-links are earned and given by choice.  Google does consider buying text links for PageRank purposes to be outside our quality guidelines. Vanessa Fox. 2006.

14. http://www.mattcutts.com/blog/google-analytics/
Blackhat SEOs may be leery of using Google for analytics, but regular site owners should be reassured. Vanessa Fox. 2006.

15. http://www.mattcutts.com/blog/text-link-follow-up/
Google’s is against selling/buying links, and Matt indicates they are good at spotting them — both algorithmically and manually. Sites that sell links can lose their trust in search engines. 2006.

16. http://www.mattcutts.com/blog/seo-mistakes-spam-in-other-languages/
Google is focusing on detecting spam in other languages in 2006 — Italian, Spanish, Chinese, etc. 2006.

17. http://www.mattcutts.com/blog/seo-advice-discussing-302-redirects/
External (domainA -> domainB) 302 redirects are largely treated as 301s now. 2006.

18. http://www.mattcutts.com/blog/seo-advice-url-canonicalization/
Canonicalization is the process of picking the best url when there are several choices, and it usually refers to home pages — www.example.com vs. example.com vs. www.example.com/index.html.  Since all these urls are different, a web server could return completely different content for all the urls above. When Google “canonicalizes” a url, it tries to pick the best one and elimintes the others. To help Google, link to resources on a site consistently, and use 301 redirects to enforce it. 2006.

19. http://www.mattcutts.com/blog/seo-advice-url-canonicalization/
Do not use the URL removal tool to remove domain.com if you are worried about URL canonicalization and have both domain.com and www.domain.com in the Google index. This will remove the entire site. 2006.

20. http://www.mattcutts.com/blog/seo-advice-url-canonicalization/
Search engines can perform canonicalization for things like keeping or removing trailing slashes, upper vs. lower case, or removing session IDs from bulletin board or other software. 2006.

21. http://www.mattcutts.com/blog/sitemaps-interview/
404s (Gone, but may reappear) are treated the same as 410s (Gone, but will not reappear).  Most web masters use 404s as 410s anyway. 2006.

Following these tips will probably help you rank better, so long as you actually trust Matt Cutts.  I’d assert it’s wise to approach some of his advice with skepticism, since I’m sure Google gives him guidelines as to what he can actually say, but following the advice above won’t get you into any trouble.

First, How Does AdSense Work?

You set up an account with Google and specify the ads you want. I said “Images if you have them but text if not” and specified some medium and large banners and squares in certain color schemes. Google then generated some small JavaScript blocks for me to place as I want within my pages.

The JavaScript I place within my page is short and simple so that I and my server have little to do.

When you view my page, you direct your browser to retrieve data from a specified URL. My server sends over an XHTML document. If you have JavaScript enabled in your browser, it then executes each JavaScript block on your computer.

The simple JavaScript blocks I added to my pages just set four variables and then it retrieves and executes a program from pagead2.googlesyndication.com. That automatically retrieved JavaScript program does the real work of getting the ad itself.

The ad retrieved is the result of doing something like the reverse of the typical Google search. Instead of answering the question, “What pages related to this search string?” it’s more like “To which search strings or ad descriptions would this page relate?” Put another way, it tries to automatically select ads on topics similar to the topic of the page. One of those four original variables specifies my Google account, so if you happen to retrieve an ad that interests you and you click on it, Google knows whom to credit.

A side effect that I didn’t anticipate is that it shows me what Google thinks my pages are about. It does a good job selecting relevant ads on many of my pages, like TCP/IP, Unix/Linux, some of my information security pages, my attempts to understand Turkish grammar, travel suggestions, and Toilets of the World.

It gets a little confused on many of my information security pages, obsessing on the term “security” appearing in the URL and throughout the page, and frequently offering ads for the vast and largely non-technical physical security industry in the U.S.

It just can’t figure out what some pages are about, like one explaining how to create Cyrillic text in Unicode, the L_AT_EX markup language, and Postcript. If it cannot decide what the page might be about, it tends to offer “public service ads”, generally promotions for charities.

OK, that’s what AdSense is and how it works. Why is this page here?

The Problem and the Solution

Google AdSense ads are based on JavaScript using document.write() calls. However, that doesn’t work within an XML/XHTML document. Here is the workaround!

In more detail, a Google AdSense ad looks like the following within a web page. The first block sets values for four variables, and the second effectively says “Set some variables, and then retrieve a JavaScript program from the following location and execute it.” Google suggests that you simply insert this JavaScript into an HTML file, but that doesn’t necessarily work — hence the reason for this page!

<script type="text/javascript">
    <!--
        google_ad_client = "pub-5845932372655417";
        /* Top Banner */
        google_ad_slot = "1979399418";
        google_ad_width = 728;
        google_ad_height = 90;
    //-->
</script>
<script type="text/javascript"
        src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
</script>

The problem is that the retrieved program show_ads.js contains calls to JavaScript’s document.write() function, and that is not allowed within an XHTML or XML page. Depending on your browser and how strict it is, you might get the ad, or maybe an error message, or maybe nothing at all.

How do I know what’s in the JavaScript program? I wondered why it didn’t work and so I retrieved a copy with wget:

$ wget http://pagead2.googlesyndication.com/pagead/show_ads.js
$ vim show_ads.js

Sure enough, document.write(); plays a crucial role. Some XML/XHTML solution is needed….

Here is the workaround: step by step:

Create a Proper HTML Document Containing the JavaScript

I created the below HTML file as:
/var/www/html/ads/banner-728x90.html
so it could be retrieved as:
http://cromwell-intl.com/ads/banner-728x90.html
It’s just the JavaScript from above as the body of a small HTML file:

<?php header("Content-Type: text/html;charset=utf-8"); ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
    <head>
        <title>Sponsorship</title>
        <style type="text/css">
            body { margin: 0; padding: 0; }
        </style>
    </head>
    <body>
        <script type="text/javascript">
        <!--
            google_ad_client = "pub-5845932372655417";
            /* Top Banner */
            google_ad_slot = "1979399418";
            google_ad_width = 728;
            google_ad_height = 90;
        //-->
        </script>
        <script type="text/javascript"
                src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
        </script>
    </body>
</html>

Create a “Wrapper” to Minimize Code Maintenance

I next created the below HTML file as:
/var/www/html/ads/banner-728x90-wrapper.html
Note that it specifies the width and height of the included HTML object in pixels, and it sets the MIME type of just this encapsulated object as text/html so that document.write(); will work. Without the explicit definition of width and height, the browser will not know in advance how to lay out the page and the result may look very strange.

<div style="width: 728px; height: 90px">
	<object data="/ads/banner-728x90.html"
		type="text/html"
		style="width: 728px; height: 90px">
	</object>
</div>

I can make a number of wrappers to pull in the same file and underlying ad code with different styles. For example, those wrappers could make the ad “float” to the left margin of the page:
<div style="width: 728px; height: 90px; float: left;">
or to the right margin:
<div style="width: 728px; height: 90px; float: right;">

I could have put the six-line block of <div>...<div> directly in an HTML file, but then I have six-line blocks to maintain! The next step makes it much easier.

Include The Ad by Pulling in the Wrapper with PHP

All I have to do now is add one PHP line to a file to include the wrapper and let it pull in the code. This page, for example, literally begins as shown here. See how it pulls in two ads at the very beginning, before the large header “How To Use Google AdSense Within XML/XHTML“ — a 728×90 banner across the top and a 200×200 box that floats to the right:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
	"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
	<head>
		<title>How To Use Google AdSense Within XML/XHTML</title>
		<meta name="description" content="How to use Google AdSense
			within XML/XHTML pages.
			Google AdSense uses JavaScript document.write();,
			which is not allowed within XML/XHTML.
			Here is a simple solution to the problem." />
		<meta http-equiv="content-type" content="application/xhtml+xml; charset=iso-8859-1" />
		<link rel="stylesheet" type="text/css" href="../css/style.css" media="screen" />
	</head>

	<body style="background: #f4e4b0">

		<?php @ include ('../ads/banner-728x90-wrapper.html'); ?>
		<?php @ include ('../ads/square-200x200-wrapper.html'); ?>

		<h1>How To Use Google AdSense Within XML/XHTML</h1>

The overall result making up the entire page is a valid XML/XHTML document encapsulating a short HTML block of specified size containing nothing but Google’s JavaScript program.

The only remaining annoyance, and it’s fairly minor, is PHP’s inability to easily deal with absolute paths. The include is relative to that page’s location, so I need the ../ shown above.

The supposedly “easy” fix it to instead use all this:

<?php include($_SERVER['DOCUMENT_ROOT'].'/ads/banner-728x90-wrapper.html'); ?>

Ugh. I’ll just keep track of how many instances of ../ are needed….

When it comes to SEO (Search Engine Optimisation) many people have no idea why they should implement it and how it can effect there site. Properly implemented SEO can increase your websites search engine rankins on multiple keywords and will increase your traffic.

I will go through a list of 3 plugins and or modules you should install on your joomla 1.5 website to increase it’s visibility on themajor search engines. (continue reading…)

(continue reading…)

(continue reading…)