[wp-trac] [WordPress Trac] #23602: Incorrect canonical redirect if p=123 query argument present in "paged" archives

WordPress Trac noreply at wordpress.org
Mon Feb 25 08:34:19 UTC 2013


#23602: Incorrect canonical redirect if p=123 query argument present in "paged"
archives
-----------------------------+--------------------------
 Reporter:  kasparsd         |       Type:  defect (bug)
   Status:  new              |   Priority:  normal
Milestone:  Awaiting Review  |  Component:  Canonical
  Version:  3.5              |   Severity:  normal
 Keywords:                   |
-----------------------------+--------------------------
 URLs that include `page/n` AND `p=n` query variable, such as:

 http://example.com/page/3/?p=123

 will issue a 301 redirect to the homepage. This is being reported as
 incorrect behaviour in Google Webmaster Tools, because:

   The target URL does not exist and your server is not returning a 404
 (file not found) error.

   Your server is redirecting requests for a non-existent page, instead of
 returning a 404 response code. This creates a poor experience for
 searchers and search engines.

 A fix would be to strip the `p=` query variable and redirect to the paged
 archive.

 From:

 http://example.com/page/3/?p=123

 to:

 http://example.com/page/3/

-- 
Ticket URL: <http://core.trac.wordpress.org/ticket/23602>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software


More information about the wp-trac mailing list