Non-canonical page in sitemap

Hi,

Could you confirm you are using WordPress 5.5 and Yoast SEO for WordPress 14.8.1?

Just to clarify, we checked on https://reeferboss.com/apparel/ and saw that the canonical URL is https://reeferboss.com/product-category/apparel/. Did you make this change in the advanced tab of the Yoast SEO meta box?

We also checked your product category sitemap https://reeferboss.com/product_cat-sitemap.xml. Is your expectation that the URL that would show in the sitemap would be https://reeferboss.com/product-category/apparel/ and NOT https://reeferboss.com/apparel/?

Yes i’m using wordpress 5.5 and yoast 1.4.8.1.

I haven’t touched anything in the advanced tabs.

I would like the canonical URL to be the URLs that are in the sitemap which have the “/product-category/” slug removed.

Desired canonical: https://reeferboss.com/apparel/
Current canonical: https://reeferboss.com/product-category/apparel/

I’ve disabled all plugins aside form woocommerce and yoast and resaved my permalinks but they don’t change. Here’s my cyurrent permalink settings: https://prnt.sc/u9mosl

Another issue I see if the primary categories are being ignored and not inputted in the breadcrumbs https://prnt.sc/u9n1ro, not sure if this issue is related to the canonical URL issue.

Hi @anjoid,

Thank you for your reply.

1) Canonical URLs

We’ve checked your product category sitemap, and all but one have the /product-category/ in the URL. Only one does not have it which is the /apparel/socks/ category.

We would encourage you to not remove the product-category out of the URLs. We know you want them shortened, but WooCommerce itself, the plugin, recommends not to do this. You can read about this here: https://docs.woocommerce.com/document/removing-product-product-category-or-shop-from-the-urls/.

2) Primary category

We’ve checked your screenshot. We see ‘Google Feed’ and ‘Google Feed 2’ in the breadcrumbs and are not sure where those are coming from. Do you have any custom setting for this?

We are going ahead and marking this issue as resolved due to inactivity. If you require any further assistance please create a new issue.