{"id":625,"date":"2007-06-18T22:37:43","date_gmt":"2007-06-18T20:37:43","guid":{"rendered":"http:\/\/planetozh.com\/blog\/2007\/06\/wordpress-duplicate-content-and-wrong-seo-plugins\/"},"modified":"2007-06-27T09:02:32","modified_gmt":"2007-06-27T07:02:32","slug":"wordpress-duplicate-content-and-wrong-seo-plugins","status":"publish","type":"post","link":"https:\/\/planetozh.com\/blog\/2007\/06\/wordpress-duplicate-content-and-wrong-seo-plugins\/","title":{"rendered":"WordPress, Duplicate Content, and Wrong SEO Plugins"},"content":{"rendered":"

I've seen recently a lot<\/a> of<\/a> plugins<\/a> for WordPress aimed at taking care of the duplicate content issue in search engines. Don't get me wrong, those plugins are doing well what they were created for : adding a meta tag in some pages so that Googlebot and its friends don't index them. The problem is that doing such a thing is, in my very humble opinion, a bad idea<\/strong>.
\n<\/p>\n

Duplicate Content ? Duplicate Content ?<\/h2>\n

First of all, if you don't know what's wrong with duplicate content, read this nicely illustrated article<\/a> from SEOmoz. In short, when a search engine bot sees the same content on different pages, let alone different websites, it doesn't like it, tries to identify the original source for it and puts a penalty on others. Duplicate content is a real cross site issue, often synonym to spam, splog and content stealing.<\/p>\n

Inside your own blog, duplicate content might<\/em> be a problem. You have original content on your post page, you have the very same content in the timely archives for the same day, month and year, and again the same in each category archive page under which you filed your post. Four, five, six times the same content? This has to be a bit confusing for our friend Googlebot, and it might<\/em> put a penalty on some and any of these pages.<\/p>\n

Note the emphasize on might<\/em>. The real problem here is that you want to have control over which page is the most important, and not let search engines decide for yourself.<\/p>\n

What to do, then ?<\/h2>\n

At this point, you have 3 possibilities :<\/p>\n

    \n
  1. Do nothing<\/b>
    \nLet search engines index 6 times the same content and decide which is best. That could<\/em> work. Or that could<\/em> painfully decrease your visibility in search engine pages, since you can't decide what page should be proeminent over others. Not an option for those who want to fine tune things.<\/p>\n<\/li>\n
  2. Use a "don't index this" plugin<\/b>
    \nBasically, those plugins will simply add something like <meta name=\"robots\" content=\"noindex,follow\" \/><\/tt> in some pages, so that search engine bots will follow links but won't remember what they've seen on that page.
    \nAs I've said in the intro, this seems a dumb idea to me. Why? Mainly for two reasons. First of all, it's much better for your site to have 6 pages indexed instead of 1. Or 6,000 instead of one thousand. And second reason, simply because it's up to you<\/b> not to serve duplicate content.<\/p>\n<\/li>\n
  3. The right way : just give different<\/em> content<\/b>
    \nReason #771 why WordPress is great is you can customize just everything to suit your needs. Like, having a smart theme with smart archive pages<\/em>. Instead of displaying each post in its entirety, display an excerpt of it, and<\/b> get your page indexed<\/li>\n<\/ol>\n

    The Right Way™ to do it<\/h2>\n

    "The right way" purposely emphasized: as usual and as with most things, There's More Than One Way To Do It<\/a>. But at least that's my way to do it, and judging by my referrer visits, it's not working too bad.<\/p>\n

    Keeping your site safe from the duplicate content issue, and more generally getting things optimized for search engines, should not be a plugin's job, it must be<\/b> your theme's job, it must be coded and designed for it. Just like looking good, using good markup, being crossbrowser friendly, etc…<\/p>\n

    WordPress themes have a template page specifically made for those pesky archive pages, be they year, month, day, category, author, whatever archives. You need at least one file, located in wp-content\/themes\/yourtheme\/<\/em>, named archive.php<\/strong>.<\/p>\n

    If your theme does not have an archive.php, it sucks<\/del> is incomplete. Create one, for example by duplicating and editing the file you'll find in the default theme directory. If your theme has an archive.php and displays whole posts, hack it. An example (and rather minimalist) template to display post excerpts would be:<\/p>\n

    \n\n\t\t
    \n\n\t\t
    \n\t\t\t\t\t\t< View plain text<\/span> ><\/a>\n\t\t\t\t\t<\/div>\n\n\t\t
    php<\/div>\n\n\t\t\n\t\t
    \n\n\t<\/div>\n\t\n\t
    \n\t\t
    1. <?php<\/span> get_header(<\/span>)<\/span>;<\/span> ?><\/span>  <\/div><\/li>\n
    2.  <\/div><\/li>\n
    3. <<\/span>div id=<\/span>"content"<\/span>><\/span><\/div><\/li>\n
    4.  <\/div><\/li>\n
    5. <?php<\/span> if<\/span> (<\/span>have_posts(<\/span>)<\/span>)<\/span> :<\/span> ?><\/span><\/div><\/li>\n
    6. <?php<\/span> while<\/span> (<\/span> have_posts(<\/span>)<\/span> )<\/span> :<\/span> the_post(<\/span>)<\/span> ?><\/span><\/div><\/li>\n
    7.     <<\/span>div class<\/span>=<\/span>"post"<\/span>><\/span><\/div><\/li>\n
    8.     <<\/span>h2><\/span><?php<\/span> the_title(<\/span>)<\/span>;<\/span> ?><\/span><\/<\/span>h2><\/span><\/div><\/li>\n
    9.  <\/div><\/li>\n
    10.     <<\/span>div class<\/span>=<\/span>"storycontent"<\/span>><\/span><\/div><\/li>\n
    11.     <<\/span>p><\/span><?php<\/span><\/div><\/li>\n
    12.     $short<\/span> =<\/span> get_the_excerpt(<\/span>)<\/span>;<\/span><\/div><\/li>\n
    13.     if<\/span> (<\/span>strpos<\/span>(<\/span>$short<\/span>,<\/span>'&#91;...&#93;'<\/span>)<\/span> ===<\/span> false<\/span>)<\/span> $short<\/span>.=<\/span>'&#91;...&#93;'<\/span>;<\/span><\/div><\/li>\n
    14.     echo<\/span> $short<\/span>;<\/span><\/div><\/li>\n
    15.     ?><\/span><\/div><\/li>\n
    16.     &<\/span>rarr;<\/span> <<\/span>strong><<\/span>a href=<\/span>"<?php the_permalink() ?>"<\/span>><\/span>Read more<\/<\/span>a><\/<\/span>strong><\/<\/span>p><\/span><\/div><\/li>\n
    17.     <\/<\/span>div><\/span><\/div><\/li>\n
    18.  <\/div><\/li>\n
    19.     <\/<\/span>div><\/span> <!--<\/span> post --><\/span><\/div><\/li>\n
    20.  <\/div><\/li>\n
    21. <?php<\/span> endwhile<\/span> ?><\/span><\/div><\/li>\n
    22.  <\/div><\/li>\n
    23. <\/<\/span>div><\/span> <!--<\/span> content --><\/span><\/div><\/li>\n
    24.  <\/div><\/li>\n
    25. <?php<\/span> get_sidebar(<\/span>)<\/span>;<\/span> ?><\/span> <\/div><\/li>\n
    26.  <\/div><\/li>\n
    27. <?php<\/span> get_footer(<\/span>)<\/span>;<\/span> ?><\/span><\/div><\/li>\n<\/ol>\t<\/div>\n\n<\/div>\n\n

      Does that really matter ?<\/h2>\n

      My theme is serving archive pages using the example above. While most of my incoming search engine visitors land on post pages directly, I do have visitors landing on category archives. Oh, not much, about 2 or 3% of them. Just checking the past hour referrers, I've found people coming from Google and looking for :
      \n      lolcat + javascript<\/a> (go figure)
      \n      french lolcats<\/a> (ho hai i'm fwench!)
      \n      php bitwise gd function<\/a><\/p>\n

      So they came here, and actually they probably didn't find what they were looking for : I've never written anything about javascripted lolcats. But I've posted about lolcats, and about javascript, for sure. I've never written anything about bitwise operations in gd, but I've posted about gd, and about bitwise operators. Yet, Google showed them results that made these people think they would find what they were looking for on my site, and they came. And that would never have happened if I made my site with this noindex<\/em> meta tag on archive pages.<\/p>\n

      So, why would I want to cut my visitor number by 2 or 3 percent with a noindex<\/em> directive for bots ? Would that make 3 visitors a day, or 3 visitors and hour, that's still 3 potential readers, 3 potential ad clickers, 3 potential bloggers who will like and link my site. That'd be silly to tell Google not to send those fine people to my site.<\/p>\n

      Summary<\/h2>\n

      Do stay away from the duplicate content problem. But it's definitely a theme<\/strong> issue, not a plugin's business.<\/p>\n","protected":false},"excerpt":{"rendered":"

      I've seen recently a lot of plugins for WordPress aimed at taking care of the duplicate content issue in search engines. Don't get me wrong, those plugins are doing well what they were created for : adding a meta tag in some pages so that Googlebot and its friends don't index them. The problem is […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[],"tags":[42,216,85,119,245,108],"class_list":["post-625","post","type-post","status-publish","format-standard","hentry","tag-google","tag-noindex","tag-plugins","tag-seo","tag-wordpress","tag-wordpress-theme"],"_links":{"self":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/625","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/comments?post=625"}],"version-history":[{"count":0,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/posts\/625\/revisions"}],"wp:attachment":[{"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/media?parent=625"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/categories?post=625"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planetozh.com\/blog\/wp-json\/wp\/v2\/tags?post=625"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}