<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<!--Web 2.0 Content Powered by MyST Blogsite® (http://blogsite.com)-->
<!--A service of MyST Technology Partners, Inc. (http://myst-technology.com)-->
<?xml-stylesheet href="http://blogsite.com/public/styles/etc/object.xsl" type="text/xsl"?>

<?myst-baseUrl http://blogsite.com/public/?>

<MySmartChannels Public="true" UserID="76091" dT="51" t0="1227168262825">
     <GetChannelItem_Result>
      <Item>
       <Resource>
        <ObjectID>192402</ObjectID>
        <ObjectClass>Resource</ObjectClass>
        <OwnerID ObjectClass="Domain" Title="[Weblog] Marketing. Communication. Results.">76407</OwnerID>
        <CreatedByID ObjectClass="User" Title="bfrench">24</CreatedByID>
        <ModifiedByID ObjectClass="User" Title="$Admin">1</ModifiedByID>
        <CreateTime Title="2007-12-13 17:41:52 EST">1197585712822</CreateTime>
        <ModifyTime Title="2008-09-30 07:40:17 EDT">1222774817982</ModifyTime>
        <SecurityModel>Controlled</SecurityModel>
        <Name>Don't Cut Corners on Technical or Content Quality</Name>
        <Summary>Content quality has a significant impact on search and discoverability of your information - don't risk all your blogging effort with substandard publishing practices.</Summary>
        <Description>
&lt;p&gt;I was doing some support maintenance today on a few blogsites and I happened to notice how clean &lt;a href="http://www.phoenixmarkettrends.com/"&gt;this blogsite&lt;/a&gt; (&lt;a href="http://www.phoenixmarkettrends.com/"&gt;phoenixmarkettrends.com&lt;/a&gt;) is in terms of quality. This includes content, links, and the general theme of the information - it was quite inviting and informative. But&amp;nbsp;quality&amp;nbsp;can also&amp;nbsp;be measured in terms of &lt;em&gt;&lt;u&gt;technical requirements&lt;/u&gt;&lt;/em&gt; such as broken links, missing images, and missing&amp;nbsp;keywords&amp;nbsp;or&amp;nbsp;alt image attributes.&lt;/p&gt;&lt;p&gt;I also took a closer at&amp;nbsp;this client's&amp;nbsp;&lt;u&gt;&lt;em&gt;Blogsite Quality Assurance Report&lt;/em&gt;&lt;/u&gt; and I was surprised to find they had just a handful of technical defects in spite of the fact that they had more than 200 posts this year and&amp;nbsp;&lt;a href="http://www.google.com/search?hl=en&amp;q=site%3Aphoenixmarkettrends.com"&gt;2,000 blogsite pages&lt;/a&gt; indexed in Google.&lt;/p&gt;&lt;p&gt;It's hard to say whether technical defects affect search visibility, but there's no debate that broken links and other content problems create a poor experience for your visitors. Since most search engines are designed to create good recommendations, it's likely that technical quality is yet another&amp;nbsp;good metric that they use to identify good content. &lt;a href="http://technical-itch.co.uk/"&gt;TechnicalItch&lt;/a&gt; says you can &lt;a href="http://technical-itch.co.uk/2007/08/16/increase-traffic-by-fixing-broken-links/"&gt;Increase Traffic By Fixing Broken Links&lt;/a&gt;. &lt;a href="http://www.problogger.net/"&gt;ProBlogger&lt;/a&gt; is far more critical of &lt;a href="http://www.problogger.net/archives/2007/08/23/go-on-a-dead-link-hunt/"&gt;dead links&lt;/a&gt;...&lt;/p&gt;&lt;blockquote dir="ltr" style="margin-right: 0px; "&gt;&lt;p&gt;&lt;em&gt;&amp;quot;I&amp;rsquo;m not sure of the technicalities of it or what the latest research shows but from what I can tell a dead link is not looked upon favorably by search engines and you run the risk of penalties.&amp;quot;&lt;/em&gt;&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Imagine how many links and images accumulate after four&amp;nbsp;years of&amp;nbsp;blogging -there may be as many as&amp;nbsp;2,000 posts, 1,100 images, and 3,800 links. How do you make sure they all continue to work?&amp;nbsp;One way is to use&amp;nbsp;website&amp;nbsp;testing tools such as &amp;nbsp;Google's &lt;a href="https://www.google.com/webmasters/tools/docs/en/about.html"&gt;Webmaster Tools&lt;/a&gt;; it includes a way to review all the failures their crawlers have encountered. This is certainly good data but the process is a bit tedius. This is why we include integrated quality assurance reports right in your blogsite.&lt;/p&gt;&lt;p&gt;Every week we scan 100% of&amp;nbsp;our client's blogsite posts and report defects across six primary error types. The report even includes explanations and links links directly to the posts for quick repair. Automated reporting systems such as this are key success factors for businesses that have little tollerance for excessive use of their time. &lt;/p&gt;&lt;p&gt;If you're tired of blogging alot and achieving little, give us a call or &lt;a href="mailto:bfrench@myst-technology.com"&gt;drop me a note&lt;/a&gt; - 415-683-6126.&lt;/p&gt;</Description>
        <ResourceTypeID ObjectClass="ResourceType" Title="Item:Link">9</ResourceTypeID>
        <ContentType>application/xml</ContentType>
        <ContentDocument>
         <ItemProperties>
               <CommonProperties>
                <Hidden>false</Hidden>

                <Keywords>
                 <Keyword>blog content quality assurance</Keyword>

                 <Keyword>broken images</Keyword>

                 <Keyword>broken links</Keyword>

                 <Keyword>content quality</Keyword>

                 <Keyword>technical quality</Keyword>

       </Keywords>

                <Links>
                 <Link>
                  <Title>Increase Traffic By Fixing Broken Links</Title>

                  <Synopsis>One of the things I recommend you do once or twice a year is to run an audit of your blog. The purpose of this audit is to fix errors in your blog such as links to pages not found.</Synopsis>

                  <URL>http://technical-itch.co.uk/2007/08/16/increase-traffic-by-fixing-broken-links/</URL>

        </Link>

                 <Link>
                  <Title>Webmaster Help Center -- How do I view crawl errors?</Title>

                  <Synopsis>The Web crawl errors page provides details about the URLs in your site that we tried to crawl but could not access.</Synopsis>

                  <URL>http://www.google.com/support/webmasters/bin/answer.py?answer=35120&amp;topic=8474</URL>

        </Link>

                 <Link>
                  <Title>Bug Check Your Blog! Resources for Fixing Code and Improving Accessibility</Title>

                  <Synopsis>Sometimes it can be really difficult to track down bugs that cause your blog to display improperly?</Synopsis>

                  <URL>http://www.typepadhacks.org/2006/05/bug_check_your_.html</URL>

        </Link>

                 <Link>
                  <Title>Go on a Dead Link Hunt</Title>

                  <Synopsis>What happens when one of the blogs that you?re linking to is retired, is deleted, changes it?s link structure, moves etc? The link is a dead one (also known as Link Rot) and can cost your blog on two fronts.</Synopsis>

                  <URL>http://www.problogger.net/archives/2007/08/23/go-on-a-dead-link-hunt/</URL>

        </Link>

                 <Link>
                  <Title>Yahoo! Search Content Quality Guidelines.</Title>

                  <Synopsis>Yahoo! strives to provide the best search experience on the Web by directing searchers to high-quality and relevant web content in response to a search query.</Synopsis>

                  <URL>http://help.yahoo.com/l/us/yahoo/search/basics/basics-18.html</URL>

        </Link>

       </Links>

      </CommonProperties>

               <ns3:Details xmlns="urn:MyST-Technology.Structured.Details" xmlns:ns3="urn:MyST-Technology.Structured.Details">
                <ns3:Collection name="Quote" type="urn:MyST-Technology.Structured.Collection.Captyx.Quote">
                 <ns3:Attribute name="Quote" type="large-text">
                  <ns3:Value>... there may be as many as 2,000 posts, 1,100 images, and 3,800 links. How do you make sure they all continue to work?</ns3:Value>

        </ns3:Attribute>

                 <ns3:Attribute name="Name" type="text" value="Bill French"/>

                 <ns3:Attribute name="Blog" type="url"/>

                 <ns3:Attribute name="Title" type="text"/>

                 <ns3:Attribute name="Company" type="text"/>

                 <ns3:Attribute name="Web" type="url" value="http://blogsite.com/contact"/>

                 <ns3:Attribute name="Icon" type="checkbox" value="true"/>

                 <ns3:Attribute name="Frame" type="text" value="bars"/>

                 <ns3:Attribute name="HTML" type="checkbox" value="false"/>

                 <ns3:Attribute name="Alignment" type="text" value="left"/>

                 <ns3:Attribute name="Text Size" type="text" value="large"/>

                 <ns3:Attribute name="Container" type="text" value="div"/>

                 <ns3:Attribute name="Container ID" type="text"/>

                 <ns3:Attribute name="Container Class" type="text" value="Quote"/>

                 <ns3:Attribute name="Container Style" type="text"/>

                 <ns3:Attribute name="_captyx.position" type="text" value="_top"/>

                 <ns3:Attribute name="_captyx.embargo" type="checkbox" value="false"/>

                 <ns3:Attribute name="_captyx.scope" type="text"/>

                 <ns3:Attribute name="_captyx.sortkey" type="text"/>

       </ns3:Collection>

      </ns3:Details>

               <RemoteInfo>
                <UserAgent>Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/525.13 (KHTML, like Gecko) Chrome/0.2.149.30 Safari/525.13</UserAgent>

                <RemoteHost>127.0.0.1</RemoteHost>

                <RemoteAddr>127.0.0.1</RemoteAddr>

                <RemoteUser>$Admin</RemoteUser>

                <ForwardedFor>76.120.48.245</ForwardedFor>

      </RemoteInfo>

     </ItemProperties>
        </ContentDocument>
       </Resource>
       <Shares/>
       <Subjects/>
       <UserPermissions>
        <CanDelete>false</CanDelete>
        <CanDiscover>true</CanDiscover>
        <CanEdit>false</CanEdit>
        <CanEditPermissions>false</CanEditPermissions>
        <CanRead>true</CanRead>
       </UserPermissions>
       <CommentInfo>
        <CommentChannelRef AllowAnonymous="true" Inherited="true">
         <ChannelID ObjectClass="Channel" Title="[Public] Public Comments">174050</ChannelID>
         <UserPermissions>
          <CanCreateChannelItem>false</CanCreateChannelItem>
          <CanDelete>false</CanDelete>
          <CanDiscover>true</CanDiscover>
          <CanEdit>false</CanEdit>
          <CanEditPermissions>false</CanEditPermissions>
          <CanPublish>false</CanPublish>
          <CanRead>true</CanRead>
         </UserPermissions>
        </CommentChannelRef>
        <Comments/>
       </CommentInfo>
       <Views>
        <SourceID ObjectClass="Channel" Title="[Weblog] Marketing. Communication. Results.">76407</SourceID>

               <View>
                <Name>blog</Name>

                <Model>blogsite/Blogsite/web</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>edit-item</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>left</Name>

                <Model>blogsite/Blogsite/left-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>right</Name>

                <Model>blogsite/Blogsite/right-content</Model>

                <Style/>

                <Scheme/>

       </View>

               <View>
                <Name>wide</Name>

                <Model>blogsite/Blogsite/wide-content</Model>

                <Style/>

                <Scheme/>

       </View>

      </Views>
        <Views>
         <SourceID ObjectClass="Channel" Shared="true" Title="[Public] What's New">102736</SourceID>

                <View>
                 <Name>blog</Name>

                 <Model>blogsite/Blogsite/my-whatsnew</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>edit-item</Name>

                 <Model>blogsite/Blogsite/right-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>left</Name>

                 <Model>blogsite/Blogsite/left-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>right</Name>

                 <Model>blogsite/Blogsite/right-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

                <View>
                 <Name>wide</Name>

                 <Model>blogsite/Blogsite/wide-content</Model>

                 <Style/>

                 <Scheme/>

       </View>

      </Views>
        </Item>
       </GetChannelItem_Result>
      </MySmartChannels>
