Opened 5 years ago
Closed 4 years ago
#4282 closed defect (bug) (fixed)
301 feed URLs.
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | lowest | |
| Component: | General | Keywords: | seo performance |
| Cc: |
Description
https://wordpress.org/feed/ exists, but is empty.
https://wordpress.org/news/feed/ returns the expected content/behaviour, so let's 301 redirect https://wordpress.org/feed/ to https://wordpress.org/news/feed/.
https://wordpress.org/news/comments/feed/ returns content from 2010, and should 301 to https://wordpress.org/news/feed/.
Change History (8)
#1
in reply to:
↑ description
@
5 years ago
#2
@
5 years ago
Ack, yes, good point. In the meantime, this is still spitting out 2010 content (which we're actively exposing/promoting).
Any ideas on alternative solutions?
#3
@
5 years ago
I mean, we could stop linking to it?
However, interestingly, those all look like Pingbacks.. which AFAIK are not supposed to show up in comment feeds?
We can probably just disable the feed entirely until it's needed.
#4
@
5 years ago
Ah, interesting. Can we filter out pingbacks? That should lead to an empty feed, right?
And/or let's just disable it.
This ticket was mentioned in Slack in #meta by tellyworth. View the logs.
5 years ago
#8
@
4 years ago
- Resolution set to fixed
- Status changed from new to closed
as of r16041-dotorg the comments feed is no longer linked in the <head>.
I'm going to leave https://wordpress.org/news/comments/feed/ as-is, it's old content, but it's no longer linked to and it's not worth the effort hiding.
Replying to jonoaldersonwp:
Is that ideal? Redirecting it to an entirely different content-type? There's also the possibility that we'll have comments on news articles turned on in the future.