Ticket #11856 (new defect (bug))
URL for 1st comments page is not canonical
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | Future Release |
| Component: | Canonical | Version: | 3.0 |
| Severity: | major | Keywords: | needs-patch reporter-feedback |
| Cc: |
Description
When WP generates URL for comments, it always includes comments page number. It should not do this when URL is for 1st comments page - in this case post URL is sufficient.
WP should also redirect to canonical URL version when someone will try to load URL like site.com/some-post/comment-page-1.
Change History
Related:
- #7635 - Threaded Comments
- #7919 - After leaving new comment, not redirected to proper page with comment paging enabled
- #7927 - Paged comments should show the LATEST page of comments by default, not the EARLIEST
- #7942 - Enable pretty permalinks for comment paging
- #7956 - get_comment_link() should be paged comments aware
- #8583 - If you're using paged coments, 'first' is selected in the options and wp_list_comments is used, then the comment permalinks on the first page will be broken
- #8630 - Wrong Paged Comments Logic
- Keywords gsoc removed
Any chance for a patch? Any feedback from GSOC which is over now?
- Keywords needs-patch, reporter-feedback added; needs-patch removed
This report properly is not valid. If there is a theme that seperates comments on a page "on it's own" next to the page "that is post content", then this information is needed.
Probably that sort of canonicalization is something a theme need to take care of.
- Keywords needs-patch added; needs-patch, removed
- Severity changed from normal to major
Can this be revisited?
/comment-page-1 is extraneous and bad for SEO due to duplicate content for situations where the total number of comments is < 1 page (new replies are automatically redirected to /comment-page-1 instead of the canonical url).
For the case when the total number of comments is > the per-page one, either comment-page-1 or comment-page-LASTNUM is superfluous, depending on the sort order.
http://www.blindfiveyearold.com/wordpress-duplicate-content describes this problem (canonical works well in the latest WP, but search engines may not care about canonical when spidering as evident by an example in the link).

Punting to Future Release pending patch.