| 11:44 am on Mar 1, 2011 (gmt 0)|
A simple redirect using a RewriteRule can fix it, but you need to decide whether you want to redirect just this one exact URL, or a bunch of URLs that follow a similar pattern. If the latter, you need a very exact definition of that "pattern" in order to get the correct code installed in your .htaccess file. The redirect(s) goes ahead of any other WP code in the .htaccess file.
| 12:44 pm on Mar 2, 2011 (gmt 0)|
Thanks a lot. But pardon my ignorance as I am not a techie.
How will that rewrite rule look like? What's the code I need to ask them to put on the site? Thanks
| 3:13 pm on Mar 2, 2011 (gmt 0)|
First we would need to know what the duplicate URLs look like. There could be several reasons
- that page could be accessible by two URLs
- that page was at the top of the "current" list when the site was crawled and it was effectively both its own page and the category page.
So first find out where the dupe titles are coming from, then find out if other pages could have the same problem. Then we can look to finding a solution.
| 3:50 pm on Mar 2, 2011 (gmt 0)|
The site is accessible with the two URLs. This is a blog, and using a subdomain of the main site.
One problem is that the main site's search results listing the blog posts are all using the
URL, and not the designated permalink structure /2009/06/11/title-of-the-post/
So that's one problem we're working to address internally.
GWT is listing about 9,000+ pages with this dupe problem
| 5:00 pm on Mar 2, 2011 (gmt 0)|
well... there's your answer. You need to do two things
1. quit publishing those URLs anywhere on your site
2. send a 301 for all such URLs to the permalink. I believe that nowdays Wordpress should be doing this by default if permalinks are set up right.
So really #1 is your main problem.
One thing, can you explain what you mean by "accessible"? Does that URL end up as the final URL in the address bar, or do you end up with the permalink? And what headers is it sending? Is it currently sending a 301 of ?p=8428
| 12:05 am on Mar 3, 2011 (gmt 0)|
The /?p=8428 is ending up as the final URL in the address bar. It does not redirect to the permalink currently set up /2009/06/11/title-of-the-post/
| 12:56 am on Mar 3, 2011 (gmt 0)|
Use the "Live HTTP Headers" extension for Firefox to deduce what HTTP status code is returned for that URL. That's important too.