Site Map module
https://www.zengenuity.com/
enAn SEO Problem with Drupal's Site Map Module & How to Fix It
https://www.zengenuity.com/blog/2010-11/seo-problem-drupals-site-map-module-how-fix-it
<span class="field field--name-title field--type-string field--label-hidden">An SEO Problem with Drupal's Site Map Module & How to Fix It</span>
<div class="paragraph html">
<div class="container">
<p>Having recently rebuilt the Zengenuity website, it just was this week that I finally got around to setting it up on our SEOmoz account. After the initial site crawl, I was surprised to discover this:</p>
<p><img src="https://www.zengenuity.com/sites/default/files/migrated/errors.png" alt="Duplicate Page Title Erros" width="163" height="81" /></p>
<p>Duplicate content in <a href="https://drupal.org">Drupal</a> is often a problem. The URL alias system causes content to show up at multiple URLs by default. <a href="https://zengenuity.com/blog/a/201011/fixing-duplicate-content-seo-problems-drupal">I’ve posted about this problem (and it’s solutions) before</a>. But, I thought we doing everything right, so I was surprised to see so many duplicate content errors.</p>
<h2>The Problem: The Site Map Module’s Default Settings</h2>
<p>After chasing down the issue, I found that the <a href="https://drupal.org/project/site_map" title="Site Map module">Site Map module</a> was the culprit. Site Map creates a simple, human-readable list of your website content using your menus items and taxonomy terms. It’s a good way to ensure that both real users and search engines know about all the content on your site. However, the default settings for the taxonomy part of the module can cause a duplicate content to show up. Here’s how:</p>
<p>Drupal has a built in page for each taxonomy term on your site. The URL for this page looks something like this: </p>
<p><span><strong><span>https://zengenuity.com/taxonomy/term/8</span></strong></span></p>
<p>If you have installed and configured the <a href="https://drupal.org/project/pathauto" title="Pathauto Module">Pathauto module</a>, this URL will probably look more user friendly. Ours looks like this: </p>
<p><span><strong>https://zengenuity.com/blog/tags/panels-module</strong></span></p>
<p>Theses aliases work great for normal taxonomy page links, like the ones that appear at the bottom of our blog posts. However, the aliases don't work with Site Map. Instead of using the friendly URLs by default, it appends “/all” to the original URLs. So, all the taxonomy links look like this:</p>
<p><span><strong>https://zengenuity.com/taxonomy/term/8/all</strong></span></p>
<p>The configuration option that controls this is here:<br /><img src="https://www.zengenuity.com/sites/default/files/migrated/site_map_seo_1.png" alt="Site Map Taxonomy Settings" width="550" height="186" /> </p>
<p>The reason "all" is the default is that websites with hierarchal taxonomy structures will likely want to display all content tagged with a term or any of its children. That’s what the “/all” option does. However, most sites, including this one, do not use hierarchical tags. So, this option has no effect other than to create duplicate content. When Google and other search engines index the site map page and see these "/all" links, they will index them separately from your friendly taxonomy links, and you may end up getting penalized for the content duplication.</p>
<h2>The Solution</h2>
<p>You should change the Site Map taxonomy setting setting to “-1” instead of “all”. <br /><img src="https://www.zengenuity.com/sites/default/files/migrated/site_map_seo_2.png" alt="Site Map Taxonomy Settings" width="550" height="186" /> </p>
<p>Once this is done, all the links in your Site Map page will change to their Pathauto-generated values. For sites with a flat taxonomy, there is no downside to doing this. For sites that do have hierarchical taxonomies, you can replace the standard Drupal taxonomy pages with the taxonomy_term view that comes with Views. Once you do that, you can remove the depth argument and manage the depth you want to display with the term argument.</p>
<h2>Conclusion</h2>
<p>Over 30,000 sites currently use the Site Map module. I’m betting that many of them have never noticed this issue before, since as site builders we rarely actually look at the site map. Luckily, this problem is pretty easy to fix, once you know it’s there. It’s just one more thing to add to your pre-launch checklist. </p>
</div>
</div>
<span>Wayne Eaker</span>November 16, 2010 <div class="tags">
<div class="container">
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/drupal" hreflang="en">Drupal</a></span>
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/drupal-planet" hreflang="en">Drupal Planet</a></span>
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/search-engine-optimization" hreflang="en">Search Engine Optimization</a></span>
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/seo" hreflang="en">SEO</a></span>
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/site-map-module" hreflang="en">Site Map module</a></span>
<span class="tag"><a href="https://www.zengenuity.com/blog/tags/taxonomy-module" hreflang="en">Taxonomy module</a></span>
</div>
</div>
Tue, 16 Nov 2010 15:05:26 +0000Wayne Eaker116 at https://www.zengenuity.com