Google & BingBot are hitting our site hard with pifragment in the querystring. How can we add rel="nofollow' to pagination URLs?
Google & BingBot are hitting our site hard with pifragment in the querystring. How can we add rel="nofollow' to pagination URLs?
I'm going to preface this by saying I don't know the answer, but I was curious. I took a look at the Forum - Thread List widget in the list.vm file. At the end of the file, it looks like this is controlled using https://community.telligent.com/community/12/w/api-documentation/68649/core_5f00_v2_5f00_ui-script-api#Pager. I wonder if maybe the Template parameter can be used ("Template source code or id of template to use when rendering pager links") or possibly another one of the options on that widget and others that use pagination. I also found Implementing Paging, in case that helps at all.
I know you know more about this type of customization than I do, Stephen Vicino, but I figured I'd share this in case it sparks any ideas for you.
This is a great find! Thank you, I didnt even see the Template input. Now the task to figure out how that works
Nice! Please share if you figure out how to get this working. It'd be a huge help since we're in the same boat with Google and Bing.
To try to combat this, I removed a bunch of our "paginated" widgets, like the Forum - Thread List, and replaced them with Activity Streams, but apparently (according to coworkers who are helping with this) the back-end request to "load more" functions very similar, just the front-end URL doesn't change, so it doesn't seem to have helped.
I sure will. The biggest issue now is figuring out what that default tempalte is. Its not listed anywhere in the documentation.
I found these two pages that may help: evolutionPager jQuery Plugin & page UI Component
They have this code reference/example (I think it's the same in both examples)
template: typeof options.configuration.Template !== 'undefined' ? options.configuration.Template : '' + ' <% foreach(links, function(link, i) { %> ' + ' <% if(link.type === "first") { %> ' + ' <a href="<%: link.url %>" class="first" data-type="first" data-page="<%= link.page %>" data-selected="false"><span>«</span></a> ' + ' <% } else if(link.type === "previous") { %> ' + ' <a href="<%: link.url %>" class="previous" data-type="previous" data-page="<%= link.page %>" data-selected="false"><span><</span></a> ' + ' <% } else if(link.type === "page") { %> ' + ' <a href="<%: link.url %>" class="page<%= link.selected ? " selected" : "" %>" data-type="page" data-page="<%= link.page %>" data-selected="<%= link.selected ? "true" : "false" %>"><span><%= link.page %></span></a> ' + ' <% } else if(link.type === "next") { %> ' + ' <a href="<%: link.url %>" class="next" data-type="next" data-page="<%= link.page %>" data-selected="false"><span>></span></a> ' + ' <% } else if(link.type === "last") { %> ' + ' <a href="<%: link.url %>" class="last" data-type="last" data-page="<%= link.page %>" data-selected="false"><span>»</span></a> ' + ' <% } %> ' + ' <% if(i < (links.length - 1)) { %> ' + ' <span class="separator"></span> ' + ' <% } %> ' + ' <% }); %> '
I'm not sure how'd you drop that into the list.vm (I'm guessing maybe add a new file in the widget and call that file in $pagerOptions or $core_v2_ui.Pager?), but it seems like that's building the URLs, and maybe you could drop the rel="nofollow" into those <a> tags?
I discovered this as well and was able to update my theme.js file to reflect the nofollow! Thanks for the tips to get this accomplished
I discovered this as well and was able to update my theme.js file to reflect the nofollow! Thanks for the tips to get this accomplished