idealmike
Level X3
Write the reason you're deleting this FAQ
So I was just reading an answer given in the CD for Do old pages need to be constantly updated to continue to rank in Google search. And Cristian pointed out that you shouldn't create a new article as well as having the old one around else you'll fall into "keyword cannibalization".
But what if your old content is old and you want to write about the latest version of the product that content was talking about? Should you update your old content? Or should you leave it as is and create new content instead?
Keyword Cannibalization isn't really a term many come across much while doing SEO. I know about it and I know what the gist of what it is in a nutshell, but it's not something I've ever considered trying to avoid for the reasons that you should try to avoid cannibalizing your keywords. I mean I've never considered that I might be cannibalizing my keywords on my site when creating similar posts or pages on the same sort of thing. And sometimes I simply had to create that other post and it simply had to have a very similar title and text on the page as there's no way around it.
Is this something you consider when writing or blogging about something that you've already previously wrote/blogged about before?
What insight into what Keyword Cannibalization do you have and why as webmaster or blogger, should you avoid cannibalizing your keywords?
What are the problems that can come about with Keyword Cannibalization?
And what are the solutions to avoid cannibalizing your keywords when you want to write or post about a very similar or very same subject?
In those cases, is it simply unavoidable?
Thanks!
Are you sure you want to delete this post?
Are you sure you want to delete this post?
Are you sure you want to delete this post?
Are you sure you want to delete this post?
| Match | Count | SQL | Script |
| SELECT * FROM `questions` as q JOIN categories_faq as c ON q.catid=c.CATID WHERE (q.status=1 OR (q.status=2 AND userid='') ) AND q.quesid='18266' | 1 | SELECT q.*, c.seo as CatSEO, c.name as CatName, c.parentid
FROM `questions` as q
JOIN categories_faq as c ON q.catid=c.CATID
WHERE (q.status=1 OR
(q.status=2 AND userid='')
)
AND q.quesid='18266' | /opt/clerks-staging/docroot/viewfaq.php 496 () () |
| SELECT * FROM seoclerks.members WHERE USERID='272' | 1 | SELECT * FROM seoclerks.members WHERE USERID='272' | /opt/clerks-staging/docroot/include/functions/includes/member.php 445 GetAllUserDetails() () |
| SELECT * FROM seoclerks.members WHERE USERID=272 | 1 | SELECT googleplus_profile FROM seoclerks.members WHERE USERID=272 | /opt/clerks-staging/docroot/include/functions/main.php 16914 GetGooglePlusProfileFromId() () |
| SELECT * FROM ratings_faq as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=18266 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faq as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=18266
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| SELECT * FROM answers a, seoclerks.members b WHERE a.quesid='18266' AND a.userid=b.USERID and b.status='1' AND a.status=1 ORDER BY a.combined_votes DESC, a.date_answered asc | 1 | SELECT a.answer, a.USERID, a.upvotes, a.downvotes, a.ansid, a.parentid, a.combined_votes, a.date_answered,
b.username, b.userlevel, b.profilepicture FROM answers a, seoclerks.members b
WHERE a.quesid='18266' AND a.userid=b.USERID and b.status='1' AND a.status=1
ORDER BY a.combined_votes DESC, a.date_answered asc | /opt/clerks-staging/docroot/viewfaq.php 1245 () () |
| SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=100520 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faqanswers as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=100520
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=100648 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faqanswers as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=100648
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=100625 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faqanswers as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=100625
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=100649 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faqanswers as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=100649
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| SELECT * FROM ratings_faqanswers as r, seoclerks.members as m WHERE r.USERID=m.USERID AND r.upvote=1 AND r.PID=151359 LIMIT 5 | 1 | SELECT m.username FROM
ratings_faqanswers as r,
seoclerks.members as m
WHERE r.USERID=m.USERID
AND r.upvote=1
AND r.PID=151359
LIMIT 5 | /opt/clerks-staging/docroot/include/functions/main.php 17159 GetVoters() () |
| UPDATE questions SET total_views = total_views + 1 WHERE quesid='18266' | 1 | UPDATE questions SET total_views = total_views + 1 WHERE quesid='18266' | /opt/clerks-staging/docroot/include/functions/main.php 1765 update_Faqviewcount() () |
| SELECT * FROM questions WHERE quesid!='18266' AND status='1' AND (question like '% Keyword Cannibalization I avoid it?%' OR question like '%Keyword%' OR question like '%Cannibalization%' OR question like '%avoid%') -- ORDER BY RAND() LIMIT 15 | 1 | SELECT quesid, question, seo, userid
FROM questions
WHERE quesid!='18266' AND status='1'
AND (question like '% Keyword Cannibalization I avoid it?%' OR question like '%Keyword%' OR question like '%Cannibalization%' OR question like '%avoid%')
-- ORDER BY RAND()
LIMIT 15 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() () |
| SELECT * FROM seoclerks.members WHERE USERID='147' limit 1 | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='147' limit 1 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture() |
| SELECT * FROM seoclerks.members WHERE USERID='632' limit 1 | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='632' limit 1 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture() |
| SELECT * FROM seoclerks.members WHERE USERID='840' limit 1 | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='840' limit 1 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture() |
| SELECT * FROM seoclerks.members WHERE USERID='3080' limit 1 | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='3080' limit 1 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture() |
| SELECT * FROM seoclerks.members WHERE USERID='1895' limit 1 | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='1895' limit 1 | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_member_profilepicture() |
| SELECT * FROM members_ledger WHERE script='/opt/clerks-staging/docroot/viewfaq.php' AND querystring LIKE '%id=18266%' AND added>=UNIX_TIMESTAMP(NOW())-1200 GROUP BY USERID | 1 | SELECT USERID, username FROM members_ledger
WHERE script='/opt/clerks-staging/docroot/viewfaq.php'
AND querystring LIKE '%id=18266%'
AND added>=UNIX_TIMESTAMP(NOW())-1200
GROUP BY USERID
| /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() () |
| SELECT * FROM categories | 1 | SELECT * FROM categories | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() parseRedundantQueriesCache() |
| select * from categories_software order by name asc | 1 | select * from categories_software order by name asc | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_GetSoftwareCategories() |
| select * from categories_wanttobuy order by name asc | 1 | select * from categories_wanttobuy order by name asc | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_wantcategories() |
| select * from categories_wanttotrade order by name asc | 1 | select * from categories_wanttotrade order by name asc | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_get_tradecategories() |
| SELECT * FROM seoclerks.members WHERE USERID='134.png' | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='134.png' | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage() |
| SELECT * FROM seoclerks.members WHERE USERID='272.jpg' | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='272.jpg' | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage() |
| SELECT * FROM seoclerks.members WHERE USERID='306632.jpg' | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='306632.jpg' | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage() |
| SELECT * FROM seoclerks.members WHERE USERID='600657.jpg' | 1 | SELECT profilepicture FROM seoclerks.members WHERE USERID='600657.jpg' | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() getUserProfileImage() |
| select * from categories_faq order by name asc | 1 | select * from categories_faq order by name asc | /opt/clerks-staging/docroot/libraries/adodb5/adodb.inc.php 1899 CacheExecute() insert_GetFaqCategories() |
| count(*) | sql1 | error_msg |
|---|
| Load | Count | SQL | Max | Min |
| Avg Time | Count | SQL | Max | Min |
Cristian
Yes. I try to avoid smaller, lower quality posts on the same subject. I prefer having everything I can share in one detailed, high-quality article.
I've seen it in action. I've optimized blogs and websites and merged similar articles into one piece of high quality content and the effects were very good.
You get good ranks with any of your target keywords. Or you'll end having a mediocre rank with a lower quality article.
If you plan to write multiple posts on the same subject. Don't.
If you plan to write multiple posts on very similar subject. Well, I don't recommend it. Better to have one monster of an article then bits and pieces all of over the place. Think about giving potential users the full experience and everything they would ever need on that subject in one article, so they won't have to search for additional information. Google will see your effort, the quality of your content and will rank you accordingly.
Hope I've answer all your questions. Cheers. [quote]Is this something you consider when writing or blogging about something that you've already previously wrote/blogged about before??[/quote] Yes. I try to avoid smaller, lower quality posts on the same subject. I prefer having everything I can share in one detailed, high-quality article. [quote]What insight into what Keyword Cannibalization do you have and why as webmaster or blogger, should you avoid cannibalizing your keywords?[/quote] I've seen it in action. I've optimized blogs and websites and merged similar articles into one piece of high quality content and the effects were very good. [quote]What are the problems that can come about with Keyword Cannibalization?[/quote] You get good ranks with any of your target keywords. Or you'll end having a mediocre rank with a lower quality article. [quote]And what are the solutions to avoid cannibalizing your keywords when you want to write or post about a very similar or very same subject?[/quote] If you plan to write multiple posts on the same subject. Don't. If you plan to write multiple posts on very similar subject. Well, I don't recommend it. Better to have one monster of an article then bits and pieces all of over the place. Think about giving potential users the full experience and everything they would ever need on that subject in one article, so they won't have to search for additional information. Google will see your effort, the quality of your content and will rank you accordingly. Hope I've answer all your questions. Cheers.
Are you sure you want to delete this post?