Hello.
I have brought this up for before however, I would like to revisit the urgency for the ability to add nofollow to selected flexblocks
My site since moving to this theme has dumped massive amounts of traffic due to the non seo friendliness of this theme. It causes massive page authority to bleed internally causing global rank to decrease.
The best and most simple way to fix this is by simply having the ability to Nofollow selected flex blocks. This would fix everything.
Has this been noted? Is this in your roadmap? how far to implement such a thing? I can’t see it being to hard.
Updates please? This is really urgent for me. Alternately I have no choice by to move to a different theme or go back to my old one that did not have this problem and was super SEO friendly
The huge internal PA bleed has caused my site to go from a global page rank of page 2 back to page 28
Thanks
-
This topic was modified 4 years by
mgiannelis.
-
This topic was modified 4 years by
mgiannelis.
Hi mgiannelis,
Yes, this is on our list, and I think it will be in the coming update.
By the way, what exactly do you need to set on Nofollow on the flex blocks? The link to the images, the link to the posts, the link to the categories, or for all of them?
The file that should be edited to be added the nofollow code is this one -> wp-content/plugins/td-composer/legacy/common/wp_booster/td_module.php
Thank you!
Basically the whole block. So they are not counted as links (by means of nofollowing them) Images, title, expert ect ect.
@TagDiv
Please make this an option, not like the last change where you just made all internal links nofollow because of one request. Every page owner has different needs and for some, internal linking is an important SEO factor supporting a better ranking.
So instead of just removing it like the last time, make it an option where every page owner can decide if they want to make it follow or nofollow. The problem at this time is, that page owners have to edit core files in order to enable follow or make it nofollow again.
Thank you.
@mgiannelis Could you maybe for the audience explain what the issue is in terms of SEO? I asked here around several times but no clear answer to that. Thanks in advance! đ
-
This reply was modified 4 years by
troller.
Hello,
You can find more details about this in these guides https://www.semrush.com/blog/linkbuilding-dofollow-vs-nofollow-semrushchat/
https://www.searchenginejournal.com/ranking-factors/nofollow-links/#close
Thank you!
It might sound harsh but did you guys even read both articles before making the change? I spend the time to read the first one and just glanced at the second one. This is all related to outbound links and not inbound. As a site owner you always trust your own page and can use follow for index purposes. Both articles are talking about nofollow for outbound but we are talking about our internal links.
It would be great if further studies would have been made before switching to nofollow based on one request which is now affecting and hurting all others.
Hello
Can we please get finally a fix for this? You guys were messing with important SEO settings weeks ago and just don’t fix it but yet we have to bear the consequence of it.
It is not just a small issue, it is affecting us. We literally tell search engines to don’t pay attention to our own content by using your flex boxes.
You were quick in turning “follow” off for a request but hesitant to provide a solution to fix this error.
Your ad says that your theme “uses the best clean SEO practices” and yet it does not. I’m sorry but it’s like talking to a wall. There are so many little things that need to be fixed but yet it gets postponed because of the preparation of a big feature update. I can’t imagine what features could make up for two months of lost SEO crawl ability.
Hi,
Until the theme will be updated, you can make the changes in the theme files -> https://i.imgur.com/eV0Uukh.png https://forum.tagdiv.com/topic/outgoing-internal-links-contain-nofollow-attribute-after-the-last-update/
Thank you!
Hi,
Thank you for your waiting. There has ben made an work around and the problem can be fixed now by simply disable the tagDiv Composer and tagDiv Cloud libraries, delete those plugins and reinstall them from Newspaper > plugins, after that in the theme panel a new option will be displayed under the Blocks settings -> https://i.imgur.com/k7jlJki.png
This method can be done by all users that have the Newspaper v11.5.1
Thank you for your time!
