Diosa locco

To publish the Podcasts on iTunes:

1. Open the iTunes application on your computer.
2. Pull down the "Advanced" menu and select "Subscribe to Podcast...."
3. Paste the URL for the RSS file in the dialogue box.
4. iTunes should begin downloading the most recent episodes of your podcast.
5. Open the latest episode of your podcast once it becomes available by double-clicking on its title.
6. If you can hear your podcast, the RSS is fine, and you can continue. Otherwise, you'll need to check for mistakes in your RSS file.
1. Go to the iTunes Store in iTunes.
2. Follow the link for "Podcasts."
3. At the very bottom, on the left side of the page, follow the link for "Submit a Podcast."
4. Enter the URL for your feed and click "Continue."
5. Complete the requested information and follow any instructions to complete your submission.
6. Wait several days, then search for your podcast in iTunes. Eventually, it should also show up in the iTunes category you provided.
7. iTunes has further instructions on updating and troubleshooting your feed.http://www.apple.com/itunes/store/podcaststechspecs.html

1. Validate your RSS file. We can do this for free at a number of websites:
2. Simply enter the URL for your RSS file:
1. RSS.scripting.com - http://rss.scripting.com/
2. FEED Validator: http://feedvalidator.org/
3. RSS Advisory Board: http://www.rssboard.org/rss-validator
3. Create a link to the RSS file's URL on the website.

1. Make sure that your blog has enclosure links enabled.
   (See: http://help.blogger.com/bin/answer.py?answer=80259&topic=12466)
1. Go to "Formatting" in your blog's "Settings" tab.
2. Choose "Yes" from the pull-down menu next to "Show Link fields."
3. Click the "Save Settings" button at the bottom of the page.
2. Create a new post for the podcast episode.
3. Give the post a Keyword Rich title.
4. Below the "Link" field, click on "Add enclosure link."
5. Enter the URL for the actual audio file.
6. Enter keyword rich text to accompany the audio podcast in the body of the post.
7. Click on "Publish Post" at the bottom of the page to publish the podcast.

With the Robots Exclusion Protocol, we add or edit the robot.txt file to instruct search engines on what to index. The robots.txt allows us to hide files or directories we don’t wish the search engine spiders to find. 

Robots.txt syntax examples

To disallow the entire website:

User-agent: *

Disallow: /

To disallow Google from indexing the entire website:

User-agent: googlebot

Disallow: /

To disallow one specific file in a specific folder:

User-agent: *

Disallow: /folder/file.html

To disallow one specific folder and its contents AND any file or folder

that begins with the characters "folder":

User-agent: *

Disallow: /folder

To disallows all files beginning with subfolder in the folder directory :

User-agent: * 

Disallow: /folder/subfolder 

To disallow multiple files and directories:

User-agent: * 

Disallow: /folder/post- 

Disallow: /folder/posting 

Disallow: /folder/search 

Disallow: /forums/login 

Disallow: /forums/memberlist 

 <a href="login.php" rel="nofollow">Log in Here</a>

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9"

        xmlns:image="http://www.sitemaps.org/schemas/sitemap-image/1.1"

        xmlns:video="http://www.sitemaps.org/schemas/sitemap-video/1.1">

  <url> 

    <loc>http://www.example.com/foo.html</loc> 

    <image:image>

       <image:loc>http://example.com/image.jpg</image:loc> 

    </image:image>

    <video:video>     

      <video:content_loc>http://www.example.com/video123.flv</video:content_loc>

      <video:player_loc allow_embed="yes" autoplay="ap=1">http://www.example.com/videoplayer.swf?video=123</video:player_loc>

      <video:thumbnail_loc>http://www.example.com/thumbs/123.jpg</video:thumbnail_loc>

      <video:title>Grilling steaks for summer</video:title>  

      <video:description>Get perfectly done steaks every time</video:description>

    </video:video>

  </url>

</urlset>

W3c Validation

The Markup Validation Service by the World Wide Web Consortium (W3C) allows us  to check HTML documents for conformance to HTML or XHTML and is also a quick method to check for errors in code. We validate sites as per W3C guidelines.

This is a good test to run after completing as much onsite SEO as possible as a "double-checking" process for other on page errors we may have missed or would not otherwise know about.

The validation can be run from here:

http://validator.w3.org/

We install a usability tool (JavaScript) on the site to track user behavior of visitors on the website. This helps track strengths & weaknesses as we record the visitor experience.