In reply to Bill Bennett. There are different things you could do for these two different implicit questions. I'll address the discoverability piece first since that may open up lots of other creative possibilities. The redirect solution is potentially less useful and while it fixes an immediate problem, there isn't as much as you can do with it.
Discovery
Most good feed readers have discovery code built into them to find the feeds on sites, so you can help the process out by advertising your suggested feeds into the of your pages. In your case you only have the couple of standard feeds that WordPress provides, so that's all they'll find and recommend despite the fact that you've probably got a hundred or more potential feeds that your site could produce. I've outlined a bit of it in the past. There are a number of ways to inject the code, but All in One SEO plugin provides a field to add code to your site's header where you'd want to include something like the following:


Just follow these example lines and you can add as many feeds as you'd like feed readers to be able to discover. You can modify the title element as you wish, keeping in mind that that is what the feed readers will display to the end user to describe them. As an example, putting my URL into most feed readers should pop up about a dozen or so various feeds. Here I'll also note that if you have other sites, there's no reason why you couldn't throw in feeds that cover them as well to give readers options of content that's yours from other locations. Personally, I think it would be cool if outlets would put journalists' personal feeds into the headers of pages for which they've authored content, so that if a reader wanted to subscribe to related off site content, they could.
Redirect solution
Since you can control the URLs, you could also always do a 301 redirect of your basic /feed/ page and point it instead to the /kind/article/feed/ page and current subscribers shouldn't see or feel a difference and future subscribers would similarly be redirected. There are probably redirect plugins that could do this too, but I would simply put the following line of code at the bottom of my .htaccess file to do it: Redirect 301 /feed/ /kind/article/feed/ Here, the general pattern is Redirect, Redirect number (301 for permanent redirects and 302 for temporary ones), the URL you want to redirect followed by the URL you want it to redirect to. I've just used relative paths in the example, but you could include entire URLs if you wanted. (In passing, I'll note that you could post your work for another outlet on your own website to archive it on your backend, but do a redirect for it to the original piece, with something like: Redirect 302 https://billbennett.co.nz/path-on-your-website/ https://nzbusiness.co.nz/article/your-5-step-it-security-parachute Though if you were to do this on a regular basis, a plugin with some more convenient UI may be in order. There are definitely other ways to do all this, but I suspect they wade into some heavy weeds with some serious code. Mucking around in questions and answers on StackExchange may be the place I'd start if you want to customize things to the nth degree.