Dear Ismael,

lstoudenmire and I have already given you all the answers.

Your unqualified answer reflects your lack of knowledge. You connect your idea with the wrong, missing background knowledge and nonsensical answers.

Indexing is NOT prevented by NOFOLLOW. I already wrote that in the first thread, which you did not read. YOAST and John Müller also give you the answers. Likewise, the Google Help, which you do not understand properly. Especially what stands between the lines.

Your Comment shows all:

“By adding the” nofollow “attribute to the search link, we are telling the crawlers not to follow, and in turn not index, the items on the search results page, which is reported to be duplicate contents. “

1. Noindex is and was always the command to avoid duplicated content, to deindex existing content and to prevent indexing as much as possible.
From what source do you have this nonsense that Nofollow is used to prevent indexing? Right: You do not know and tell nonsense here. But Google clearly tells you
https://support.google.com/webmasters/answer/93710?hl=en

2. Google Say something quite clear:
Nofollow now also prevents the deindexing of existing content because the crawl is aborted: The crawl ends here because the crawler can no longer follow the page structure. At some point Goopgle realizes: OK, I can not get any further here … after the 3-10 crawl. Then the deindexing may take place. But that is not the solution that is always propagated. It is always: Noindex !!!

3. Google tells you something else. Exactly, when Nofollow is applicable. And only then. And not as you think in your very individual interpretation

4. As an SEO service provider, my clients get reports. And they were always clean. Now I have to explain why there the site rating has deteriorated. There are now tons of warnings. Many thanks to Kriesi.

5. Why you do not allow the crawler to move freely, You also do not know it and can’t explain it with nonsense answers.

6. Noindex, used right away, would solve the problem of duplicate content. Here is the link from MOZ
https://moz.com/learn/seo/duplicate-content

“It’s important that the duplicate page can still be crawled, even though you’re telling Google not to index it, because Google explicitly cautions against restricting crawl access to duplicate content on your website. (Search engines like to be able to see everything in case you’ve made an error in your code. It allows them to make a [likely automated] “judgment call” in otherwise ambiguous situations.)”

7. Just ask experts before you make such cuts (just like the H1 breadcrumb).

8. At no other premium theme I manage for clients, I see this nonsense.

9. And again: Instead of implementing optimal solutions: Again the recommendation of kriesi is to manipulate the functions.php. Looking back, it was a mistake to offer Enfold and Kriesi to my regular customers. Thus, you now have a regular customer less, the enfold has bought tons of you or has made customer orders with you. But that’s just the way it is when you have so many customers: Then Kriesi’s Customer Care moves into the background.

Cheers

• This reply was modified 7 years, 3 months ago by Hokuspokus.

I fixed it myselft, by changing the funtions-enfold.php. Due to the fact that we are using Zen Menu Logic the theme_location is not set to “avia” but the function is looking for this to add the search icon. So I have added this.

function avia_append_search_nav ( $items, $args )
{
if(avia_get_option(‘header_searchicon’,’header_searchicon’) != “header_searchicon”) return $items;
if(avia_get_option(‘header_position’, ‘header_top’) != “header_top”) return $items;

if ((is_object($args) && $args->theme_location == ” or $args->theme_location == ‘avia’ ) || (is_string($args) && $args = “fallback_menu”))
{
global $avia_config;
ob_start();
get_search_form();
$form = htmlspecialchars(ob_get_clean()) ;

$items .= ‘<li id=”menu-item-search” class=”noMobile menu-item menu-item-search-dropdown menu-item-avia-special”>
<span class=”avia_hidden_link_text”>’.__(‘Search’,’avia_framework’).'</span>
‘;
}
return $items;