Subpages of a web page can be called twice

[manuel10503]

Subpages of any website created with WordPress can be accessed twice.

If you add a /0/ to the end of the regular URL, the same page can be called again.
This page with /0/ at the end of the URL will also be indexed in Google.

Example:
​https://wordpress.org/news/2022/03/wordpress-5-9-2-security-maintenance-release/

​https://wordpress.org/news/2022/03/wordpress-5-9-2-security-maintenance-release/0/

[SergeyBiryukov]

Hi there, welcome to WordPress Trac! Thanks for the report.

Good catch, a similar issue was fixed in [47727] / #40773 for URLs ending with /2/ or /3/ (unless they are intended to be paged). The redirect for /1/ also works as expected, but apparently not for /0/.

[manuel10503]

Replying to SergeyBiryukov:

Good catch, a similar issue was fixed in [47727] / #40773 for URLs ending with /2/ or /3/ (unless they are intended to be paged). The redirect for /1/ also works as expected, but apparently not for /0/.

Thanks for the quick reply. When can I expect approximately a bugfix for this problem?

[ugyensupport]

Yes, I can reproduce above mentioned bug.

[manuel10503]

Are there any news on this topic?

[manuel10503]

May i ask if there are any updates to this problem?

[manuel10503]

Maybe you guys can take a look at it?
@richtabor & @annezazu

Just saw your product presentation of wordpress 6.3 and thought it was really great!

Thank you guys ;)

[manuel10503]

There is a similar problem with special characters. If a special character is appended to the URL of a subpage, this subpage can also be called up with these special characters (+, -,...). These generated pages do not have a canonical metatag and therefore have little impact for SEO, but they should still be cleaned up.

Example
Original page: ​https://wptavern.com/wordcamp-us-2023-contributor-day-signup-is-open

Page with special characters in the URL: ​https://wptavern.com/wordcamp-us-2023-contributor-day-signup-is-open-

[annezazu]

Hey there! Thanks for the kind words and for tagging us in this. We're at RC1 for 6.3, meaning we can only fix bugs related to the release features specifically. As a result, the earliest this could be addressed in 6.4. I'd recommend adding it as a wishlist feature here for possible consideration by the broader release squad: ​https://make.wordpress.org/core/2023/07/18/wordpress-6-4-whats-on-your-wishlist/