Are you a Google Analytics enthusiast?
More SEO Content
The Curious Case Of "what Is Duplicate Content?"
Posted 28 November 2012 - 11:46 PM
There are many reasons for having duplicate content within a website. Some seem to be practical techniques in providing a good user experience (navigation, columns, footer, etc) in helping your audience find and navigate to quality content. However, do these cases also draw you into the dark, dank, dingy realm of duplicate content?
1) You have a common CMS-managed site. With it you have much flexibilty but also a core framework which commonly includes common main menu navigation, header, footer, right and/or left columns and perhaps some spotlight type blocks above the footer. These elements may contribute substantial duplicate content but help the view to get around. How serious is this concern?
2) A blog commonly contains an entry page with blog titles and limited intro text, perhaps 50-100 words max each and links to each blog page. How relevant is the blog entry page as a unique page in its own right as compared to the individual page entries? How about those little sidebar type extensions where you take a few blog titles with introtext and dump them on every page of your site in the right or left column? Do you see that on this site?
3) The FAQ page - There are some extensions that allow you to build a FAQ page out of individual articles. There is an accordion version that is really pretty slick in that it builds a question/problem/symptom list that can be sorted alphabetically, by date, author etc. Regardless of sorting, you click on the FAQ title and it exposes the solution content (stored in a hidden div which is indexed). The usefulness is there - you can have lots of content on the page but it doesn't come off as overwhelming to the visitor.
Caveat #1 - each FAQ is stored in individual articles as well and these are also indexed. Is there a duplicate content concern between the master page and children, article pages? Which page is likely to score higher, the master with all content or the slimmer single article/faq pages.
Caveat #2 - The master page method works pretty well to deliver long or short answers, one-liners. With FAQ articles where the answers are wordy those individual articles stand a chance of hitting 50% unique content, when you add in the core page elements, header, navigation, footer, boxes, etc. But those one-liner FAQ they seem doomed in this scenario. They could easily fall into 90% + similar content when you add in the core page elements.
So now that you have a compilation of 10 of these tiny FAQ pages, how will the SE respond to your apparent disregard for duplicate content? It is not intentional but it is a byproduct.
Posted 29 November 2012 - 09:08 AM
Posted 29 November 2012 - 11:06 AM
Caveat #2 sticks in my craw. So you have these pages Q/A type which are created as individual articles and get indexed as such. With a really short question and answer the pages could easily be 95% similar, maybe 98%.
text content sum:
main menu +
right column content (latest posts) +
above footer spotlights (boxes of whatever) +
95% - 98% of page text
Short Q/A body content
+ meta title
+ meta description
2% to 5%
You have 10-15 similarly short FAQ pages. No problem?
Would the search engines smile happier at the master FAQ pages that combines all individual FAQ files rather than these dainty little morsels?
And yes we do believe that search engines are smart enough to know the natural structure of pages and navigation and such.
Posted 29 November 2012 - 11:16 AM
That said, the way you describe doesn't sound very user friendly, so yeah, I'd combine them into one page.
Posted 29 November 2012 - 11:44 AM
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users