Skip to content

Feeds: Return a 404 for feeds of objects that don't exist. - #15352

Open
JDeepD wants to merge 1 commit into
WordPress:trunkfrom
JDeepD:fix/56883-feed-404-missing-object
Open

JDeepD wants to merge 1 commit into
WordPress:trunkfrom
JDeepD:fix/56883-feed-404-missing-object

Conversation

@JDeepD

@JDeepD JDeepD commented Nov 2, 2026

Copy link
Copy Markdown

WP::handle_404() lists is_feed() among the queries that never get a 404. So /tag/no-such-tag/ returns 404, but /tag/no-such-tag/feed/ returns 200 with an empty feed. Search engines keep requesting those URLs.

This patch keeps that exemption only for feeds that aren't about a specific object. Tag, category, term, post type, author and singular feeds now return 404 when the object doesn't exist. Feeds for objects that do exist are already exempted by the existing get_queried_object() and author checks, so empty archives keep their 200 (the behaviour from #18505).

WP_Query::set_404() keeps is_feed, so the response is still a feed, now sent with a 404 status.

Trac ticket: https://core.trac.wordpress.org/ticket/56883

Use of AI Tools

AI assistance: Yes
Tool(s): Claude Code
Model(s): Claude Opus 5.5
Used for: Reproducing the issue, drafting the patch and tests, and writing this description. I reviewed, tested and edited the final implementation and tests.


This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

WP::handle_404() never sent a 404 for a feed, so feeds for tags,
categories, authors and posts that don't exist returned an empty
feed with a 200 status. Search engines keep requesting those URLs.

Feeds now 404 when the queried tag, category, term, post type,
author or post doesn't exist. Empty feeds for existing objects, and
home, search, date and comment feeds, still return a 200, as before.
@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props jdeep.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.


Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

  • @propsbot add <username> to give props to a GitHub user. Requires write access.
  • @propsbot remove <username> to leave a user out of the props. Requires write access.
  • @propsbot refresh to refresh this list. Adding the props-bot label works too.

@github-actions

github-actions Bot commented Nov 2, 2026

Copy link
Copy Markdown

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

  • All changes will be lost when closing a tab with a Playground instance.
  • All changes will be lost when refreshing the page.
  • A fresh instance is created each time the link below is clicked.
  • Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
    it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant