By conshelfwebguy on Friday, 13 February 2015
Posted in Technical Issues
Replies 6
Likes 0
Views 409
Votes 0
Hello,

Is there a way to remove the blogger link but not remove the posted by?

Basically, what I want to do is make it so the blogger profiles are not indexed and flagged as duplicate content.

The blogger listings are cause a big SEO issue in my opinion.

Thank you,
John
I figured it out.

I added a template override for the blog.item.php file.

1. Copied the blog.item.php file from the Easyblog theme I am using (in my case vintage).
2. Created a com_easyblog folder in the html folder of my main template folder, Ex. /templates/YOUR_TEMPLATE/html/com_easyblog
3. Added the blog.item.php to that new folder, path looks like this: /templates/YOUR_TEMPLATE/html/com_easyblog/blog.item.php
4. I removed the hyperlink html from this line in the blog.item.php

					<span class="blog-author">
<?php echo JText::_( 'COM_EASYBLOG_BY' );?>
<a href="<?php echo $row->blogger->getProfileLink(); ?>" itemprop="author"><?php echo $row->blogger->getName(); ?></a>
</span>


To look like this:


<span class="blog-author">
<?php echo JText::_( 'COM_EASYBLOG_BY' );?>
<?php echo $row->blogger->getName(); ?> </span>


Hope this helps someone needing the same.

To the masters of EasyBlog; Duplicate content is a huge issue these days and can really effect you negatively with Google. please look at adding ways to make sure that the only indexable content is the stuff on the Frontpage Blog Layout. That is really the only this that needs to be indexed. At least give us the options to turn items on/off

The print pages, blogger profiles (well they could is it was just the profile. the articles is what cause the problem there) categories, tags, etc. All of these items make it more difficult to rank.

May be necessary to adjust the com_easyblog plugin for Sh404sef too since this is probably the most popular URL rewriter. Anyway, just adding my 2 cents.

Thank you,
John
·
Saturday, 14 February 2015 00:00
·
0 Likes
·
0 Votes
·
0 Comments
·
Sorry, 1 more thing.

Same process needs to be applied to the blog.read.php file
·
Saturday, 14 February 2015 00:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Ok, looks like Sh404sef is still creating a URL for the blogger listing. I must be missing something else.

i thought I solved this, if someone could point me to the correct file that would be great.

Maybe just a simple adjustment to the sef_ext file com_easyblog to stop Sh404sef from creating the blogger URLS.

Thank you,
john
·
Saturday, 14 February 2015 00:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello John,

I am really sorry for the delay of this reply as it is a weekend for us here. I am not really sure why would you say that the blogger listings are causing "duplicate contents"? The blogger layout is a different page altogether and why would that result in a duplicate content?

Would you mind elaborating more on this please?
·
Saturday, 14 February 2015 13:37
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark,

I could be wrong in this, but google indexes the blogger listings and the copy for the articles posted is indexable on that page as well. The link to the article does route correctly, maybe I'm just over paranoid about duplicate content. Siteliner.com flags all indexable pages that have copy matches.

I personally just want one area of the site to be indexed. Here's another example of duplicate content to try and explain. The frontpage blog layout creates two URLS; press-releases/ and press-releases/latest -- Google indexes both pages. Both pages are the same and include the same copy, to mean thats duplicate content and I believe Google would think the same.

I'm just trying to optimize my sites as best as I can. Nothing against EasyBlog, I really like the software and appreciate your help
·
Wednesday, 18 February 2015 00:05
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

I'm sorry for the late reply. May I have the access to your site and also the backend so I can have a better look on your page structure.
·
Wednesday, 18 February 2015 17:29
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post