• Home
  • Get help
  • Ask a question
Last post 2 hours 36 min ago
Posts last week 81
Average response time last week 4 hours 29 min
All time posts 67915
All time tickets 10498
All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#2711 – Help with K2 -- redundant blog/user and feed URLs

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Thursday, 15 September 2016 18:46 UTC
atomhbc
 I wonder what would be your advise re the following.

K2 triggers sh404 creating URLs that appear to be redundant -- what I mean by redundant URL is that the given URL loads a page that doesn't have meaningful content for the visitor and that we want to shield from Google. For example:
  • xxxx.com/blog/gabor (the URL lists the k2 items the user called Gabor created.);
    xxxx.com/search/bed/feed (the combination of search and feed creates 000s of "redundant" URLs. There are two main parts of the URLs: blog/user URLs and the feed URLs. In one of my websites where there is search feature, this creates 000's of more URLs. In another website, I have lots of subscribers, and now there is a blog/user URL for every subscriber.


I asked K2, whether there is a way to stop the K2 sh404 plugin trigger sh404 to create the given URLs. They told that it was not possible.

Regards,
Tom
 
Friday, 16 September 2016 06:39 UTC
wb_weeblr
Hi

URL loads a page that doesn't have meaningful content for the visitor and that we want to shield from Google
You are right in wanting to do that, but this is a totally different thing, and not related to URLs. This would be achieved by adding a "noindex,follow" on all those pages, something indeed K2 could easily add (with a setting to turn it on/off). But again, that's unrelated to the structure of the URLs.

It seems to me that you think if K2 was not doing all those combinations of URLs that you see in the database, things would be better in terms of number of pages submitted to Google. That's not so. Those URLs exist one way or another. When using sh404SEF, you see them because they are listed in the database. Without sh404SEF, you don't see them, but they are there in exactly the same way, they just are different. sh404SEF has no impact on the number of pages on your site.

Rgds
 
Friday, 16 September 2016 15:14 UTC
atomhbc
Thank you for your response.

What I wanted to double-check if
(i) those "redundant" URLs are okay to have in the sh404 and they don't slow down the speed of the website

(ii) there was a way not to have those URLs in the sh404. -- When it comes to managing the website, they make the life difficult: having them in sh404 makes it more difficult to have an overview of your real URLs; when you export the URLS, you have to spend time on filtering out the redundant URLs; plus you need to makes sure that the URLs are search engine disallowed -- so, it doesn't seem to be very smart to have all those "redundant" URLs. I know this is not sh404, but K2 -- I wonder if you think K2 could do something to make the system work smarter.

You answered my first question .
The second question goes beyond the regular scope of support -- please feel free to closing this ticket if you are short of time.

Have a great weekend,
Tom
 
Friday, 16 September 2016 16:42 UTC
wb_weeblr
Hi

I understand your second question from a practical standpoint. As mentioned, there are things they could do, like adding noindex, follow to category pages like /blog/gabor.
Another things would be to change the /feed format, and instead use a query var such as /blog?format=feed.
That would drastically reduce the number of URLs in the database, but is not backward compatible, which is a major issue (ie URLs will change when using the new format)

Rgds
 
Saturday, 01 October 2016 05:34 UTC
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.