Google Patent Application - SEO Highlights

Written by Halstatt Pires


The recent patent application filed by Google details numerous itemsrepparttar search engine uses to rank web pages. The specific application is summarized as:

“A method for scoring a document, comprising: identifying a document; obtaining one or more types of history data associated withrepparttar 105824 document; and generating a score forrepparttar 105825 document based onrepparttar 105826 one or more types of history data.”

The patent application sheds significant light for those pursuing search engine optimization with Google. Patent applications can be difficult to understand, so following are highlights that you should consider for your SEO efforts.

Update Your Site

Updating your site is important when it comes to maximizing your rankings on Google. In addition torepparttar 105827 manipulation of keyword density and meta tags,repparttar 105828 patent application reveals that Google places significant value on how often your content is updated. The more often you update,repparttar 105829 timely and relevant your site will appear to Google. In turn, this leads to higher rankings.

To appease mighty Google, considerrepparttar 105830 following plan of action:

1. Update pages frequently, 2. Add new pages to your site, 3. Interlinkrepparttar 105831 new pages with others on your site, and 4. Add new pages on a weekly basis instead of all at once.

When Google returns torepparttar 105832 site, you want to make sure that there is new content. The high rankings of blog sites are evidence of this approach.

An Introduction to ROR (Resources of a Resource)

Written by The Add Me Team


An Introduction to ROR (Resources of a Resource)

*** What is ROR? ROR (Resources of a Resource) is an XML format for describingrepparttar content, objects, and structure of websites in a generic fashion so search engines and other web applications can find and understand information more easily.

For example if your website is selling products, ROR enables you to document your product names, descriptions, prices, images, availability, affiliate programs, etc. Or if your site or blog provides information on a given topic, it allows you to describe how this information is organized (sitemap, topics, categories, new information, archive, blogroll, etc). ROR also provides terms for documenting objects such as contacts, articles, newsletters, feeds, images, audio, links, reviews, privacy policy, copyrights, and more.

*** ROR File ROR information can be easily added to your website by adding a ROR File called ror.xml. ROR is actually quite simple. It is built on top of RDF,repparttar 105823 W3 Resource Description Language (http://www.w3.org/RDF). If you are not familiar with RDF, don't worry, I won't go into any details here.

With ROR, all objects are represented by a <Resource> tag, and can optionally have a <type> property to determinerepparttar 105824 type (or class) ofrepparttar 105825 object (e.g. Product, Article, Event, etc). The other properties are typically determined byrepparttar 105826 type you choose. Here is a simple example of a product described by ROR:

 <Resource>   <type>Product</type>   <title>My Product</title>   <desc>My great new product</desc>   <url>http://www.my-web-site.com/my-product.htm</url>   <price>19.95</price>   <currency>USD</currency> </Resource> 
Pretty simple, isn't it? And if you want to describe other objects, ROR provides other types like Contact, Article, Feed, Event, etc. You can findrepparttar 105827 current list of object and their properties inrepparttar 105828 ROR Specification at http://www.rorweb.com/spec.htm.

Now let's see how to assemble several objects together in a ROR file. In a ROR filerepparttar 105829 meaning of information is determined by bothrepparttar 105830 objects andrepparttar 105831 relationship between them. Depending how an object is linked to another object, it will provide a different meaning. To link two objects togetherrepparttar 105832 property <resourceOf> is used. Here is an example:

 <Resource rdf:about="object-1">   <title>Object 1</title>   ... </Resource>

<Resource>   <title>Object 2</title>   ...   <resourceOf rdf:resource="object-1" /> </Resource>

<Resource>   <title>Object 3</title>   ...   <resourceOf rdf:resource="object-1" /> </Resource>

The first object usesrepparttar 105833 rdf:about attribute to identify itself so it can be referenced elsewhere. The <resourceOf> property is then used to attachrepparttar 105834 second and third objects torepparttar 105835 first. Attachingrepparttar 105836 two objects torepparttar 105837 first one is a way to say that they contain information that relates to or further describes that object.

That's pretty much it! Now that you knowrepparttar 105838 essential about ROR, let's create a simple ROR file. Again I won't go intorepparttar 105839 details of RDF, but let's just say this; since ROR is built on top of RDF, it is enclosed inrepparttar 105840 <rdf:RDF> tag. Notice thatrepparttar 105841 first object in this file has a type property set to Main. This designates it asrepparttar 105842 entry point intorepparttar 105843 data structure ofrepparttar 105844 ROR file.

<?xml version="1.0" ?>  <rdf:RDF   xmlns="http://rorweb.com/0.1/"   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"> 

Cont'd on page 2 ==>
 
ImproveHomeLife.com © 2005
Terms of Use