November, 2006 Results

SEO Videos by Matt Cutts

Thursday, November 30th, 2006

SEO guru and Google representative, Matt Cutts has put together some short videos in which he answers questions about search engine optimization.

Session 1 – Qualities of a good site
Session 2 – Some SEO Myths
Session 3 – Optimize for search engines or for users?
Session 4 – Static vs. Dynamic URLs
Session 5 – Site Structure
Session 6 – Supplemental Results
Session 7 – Webspam
Session 8 – Google Terminology
Session 9 – Datacenters
Session 10 – Lighting Round
Session 11 – Reinclusion requests
Session 12 – Tips for Search Engine Strategies (SES) 2006
Session 13 – Google Webmaster Tools

PageRank Decoder Support

Wednesday, November 1st, 2006

What is the PageRank Decoder?
The PageRank Decoder allows you to visually see how Google factors PageRank based off of link structure. Be sure to view the Demo first.

What’s it good for?
You can examine different link topologies and see how PageRank is passed amongst pages. This allows you to see if your websites link structure is as optimized as possible.

How should I start?
I would recommend that you start by adding a bunch of pages to the canvas and then start interlinking them – then hit the calculate button and hover over the toolbars for their PR value. This allows you to see how different link topologies pass PR.

Later, for fun you can start looking up pages by entering in their URL in the textbox.

How does it work?
You should start by reading the article, “Google’s PageRank Explained.” Once you have a firm understanding of the article you will have a better understanding of how the PageRank Decoder is working.

Is this thing really accurate?
Yes and no?

To calculate the PageRank for a page, we use Google’s original formula:

PR(A) = (1-d) + d(PR(t1)/C(t1) + … + PR(tn)/C(tn))

If the above code looks foreign to you and you have never seen this formula before, then start by reading, “Google’s PageRank Explained”.

It’s accurate if all pages start with a PageRank of 0. If you looked up a page or set a page’s PR at something other than 0 it can mess up the formula. This is because that page now starts off with a PR other than 0 and that then gets compounded in the formula.

Google doesn’t do this; they start all pages at 0 (or rather 0.15) and then run their formula for each page factoring all incoming links. Google’s database exceeds a million pages and for each page they look at its incoming links, some pages may have well over 1000 incoming links. It takes Google somewhere around a month to update all pages.

The PageRank Decoder is not working with a database to track incoming links for a page; rather it just looks at what’s on the canvas. So instead the PageRank Decoder allows you to artificially set a page’s PR.

I thought a ranking can’t go beyond 10?
Remember, there’s a difference between PageRank score and the toolbar-shown PageRank. The toolbar has a max score of 10. I don’t know Google’s scale when setting the PageRank in the toolbar so it gets inflated quickly.

WebPod Support

Wednesday, November 1st, 2006

Be sure to read the ‘READ ME’ file…no really…

* use myPod.html and myPod-slim.html as an example if need be

copy and paste the below 2 scripts between your <head> </head> tags

  1. <script type="text/javascript" src="swfobject.js" ></script>
  2. <script type="text/javascript" src="js-to-flash.js" ></script>

copy and paste the below code where you want the webPod in your page

  1. <div id="flashcontent" style="text-align:center;">
  2. You need to download the Flash player from Adobe to use the webPod.
  3. </div>
  5. <script type="text/javascript">
  6. var so = new SWFObject("webPod.swf", "webPod", "165", "265", "8", "#ffffff");
  7. so.addParam("quality", "best");
  8. so.addParam("wmode", "transparent");
  9. so.addParam("flashvars", "xmlFile=tunes.xml");
  11. so.write("flashcontent");
  12. </script>

– In the above code, modify the path to the webPod.swf file.
– If you’re using the webPod-slim then change the above code from webPod.swf
to webPod-slim.swf and change the width from 165 to 125.
– change the flashvars “xmlFile=tunes.xml” to the correct path if need be.

make sure the song title in the playSong method is identical to the one in
the title in the XML file. IT IS CASE SENSITIVE

  1. <a href="javascript:playSong('Lost Someone')">Lost Someone</a>

Upload your MP3s and modify the tunes.xml file

mulberry sale spyder womens jacket cheap new balance 574 mulberry outlet cheap new balance 574 arcteryx outlet mulberry sale spyder womens jacket mulberry sale spyder womens jacket mulberry outlet mulberry outlet new balance 574

Popular Articles

Top 10 Commentators

Subscribe to this feed! Subscribe by Email!

Random Bits Podcast

Blogs Worth Reading