By Sean Carney on Wednesday, 17 October 2018
Posted in Technical Issues
Replies 6
Likes 0
Views 495
Votes 0
I have worked hard to create menu based urls and they are working beautifully. I am now trying to submit all the old URLs to Google as no longer valid. Unfortunately they are resolving as duplicate URLS:

Good: https://www.drcarney.com/blog/health-issues/share-healthy-habits-with-your-children
Unwanted: https://www.drcarney.com/blog/entry/share-healthy-habits-with-your-children

Good: https://www.drcarney.com/resources/people-of-interest/cathy-fisher
Unwanted: https://www.drcarney.com/blog/entry/cathy-fisher

Good: https://www.drcarney.com/science/disease-conditions/kidney-disease/chronic-kidney-disease/carbonated-beverages-and-chronic-kidney-disease
Unwanted: https://www.drcarney.com/blog/entry/carbonated-beverages-and-chronic-kidney-disease

I am trying to get the /entry/ string out of the url and only display /blog/ if the item is under the /blog/ category which is assigned to the /blog/ category.

I have selected Simple URL for the type of display:
Simple
http://yoursite.com/menu/title

Sean

PS. Access instructions are in the
Hey Sean,

It seems like i can't find it which page generated these blog URL /blog/entry/ on the site.

Is it this reported from the Google webmaster tools? If yes, can you add my email address arlex.wong@stackideas.com into your current site property so I can take a look what is those crawl errors?

By the way, may i know how you re-submit those old URL on Google?
·
Wednesday, 17 October 2018 12:21
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Sean,

It seems like i can't find it which page generated these blog URL /blog/entry/ on the site.


I have worked really hard to create menu driven URLs where my menus match my categories so that the /blog/entry/ urls will all go away and be replaced by more seo friendly urls.

Those /blog/entry/ urls were created (I believe) for every page previously that did not have a good menu based URL. But, now that should not be happening any more. Previously in the EasyBlog->Settings->SEO->General->URL Format For Every View setting was set to Default (http://yoursite.com/menu/view/title). This is what created the /blog/entry/ urls since /entry/ is the "view".

Now we have changed that to use the option Simple (http://yoursite.com/menu/title) and so were expecting all the "view" urls to go away.

Is it this reported from the Google webmaster tools? If yes, can you add my email address arlex.wong@stackideas.com into your current site property so I can take a look what is those crawl errors?


Google webmaster tools knows about all of these /blog/entry' urls because they were our site urls previously. We are trying to get rid of them though and now all our menus are creating longer better urls that are more descriptive. I have given you access to my webmaster tools so you can look and also so you can see how I am attempting to remove the /blog/entry/ urls from Googles search results. However, the fact that Google sees these URLs is not bad since I have not yet removed all of them. It is taking me a long time. What I am doing on my server host is searching for all the old URLs in my database and replacing them with the new good urls. Then at that point I submit the old url to Google for removal.

By the way, may i know how you re-submit those old URL on Google?


The process to remove a url is to login to webmaster tools and then click on the Google Index-> Remove URLs. There you will see the URLs I am submitting to be removed from their Index. The way to add a url to be removed is to click on the button that says "Temporarily hide" and then they will remove it from the index. And, provided that the page never comes back it will be permanently removed. However, if they can go to the old url and get served a page then they will add it back into their index. So, now you see why I want to much to get the /blog/entry/ urls to go away. In theory they should no longer be available.

Thank you much for considering this. I am afraid that after all my time to get these urls removed that they will all become indexed again by Google because they are not going away.

In order to replicate this on my site you can go to any urls via the menus and then you can also go to it's /blog/entry/ duplicate as follows.

https://www.drcarney.com/science/lifestyle-choices/coffee/long-term-coffee-consumption-and-risk-of-gastric-cancer-a-prisma-compliant-dose-response-meta-analysis-of-prospective-cohort-studies

https://www.drcarney.com/blog/entry/long-term-coffee-consumption-and-risk-of-gastric-cancer-a-prisma-compliant-dose-response-meta-analysis-of-prospective-cohort-studies

etc...

Sean
·
Wednesday, 17 October 2018 22:55
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Sean,

Thanks for took your time to explained this, now I got some understanding how to remove those old indexed URL from Google webmaster tool.

Actually everything you have done correctly for those setting like how to get rid of /entry/ view from the blog URL.

As long as your site page doesn't show these /entry/ blog URL, Google will not index it.

So this is not a problem if you can manually access this page https://www.drcarney.com/blog/entry/long-term-coffee-consumption-and-risk-of-gastric-cancer-a-prisma-compliant-dose-response-meta-analysis-of-prospective-cohort-studies on the browser.
·
Thursday, 18 October 2018 11:12
·
0 Likes
·
0 Votes
·
0 Comments
·
I hope you are right. :-)

We are certainly no longer producing any links to /blog/entry/ urls, and I am working to change all the wrong hyperlinks using a find and replace tool from cloudaccess.net.

So Google should not index the pages going forward.

However their documentation seems to indicate that the urls will be temporarily removed and then be added back to the index at a later date if it is found the page had not been removed. And so there is a chance Google may add them back.

Only time will tell... :-)

Sean
·
Thursday, 18 October 2018 11:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Yes, keep us update then.
·
Thursday, 18 October 2018 13:16
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post