-
Notifications
You must be signed in to change notification settings - Fork 885
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Too broad "is_multiple_terms_query" check in WPSEO_Frontend #8447
Comments
Thanks for your bug report. We've been able to reproduce the issue and have therefore labeled the issue as a bug. Unfortunately we're not able to fix this at short notice. Currently we're focusing on issues that affect many users. We've concluded that this issue is not experienced by many users, therefore we are not able to fix this short-term. However, if more users are affected by this bug, we'll of course revisit this issue. Additionally, we'd like to point out that we welcome contributions to our product. If you are able to submit a patch to fix this issue, we'll be able to get the bug fix through faster. Thanks for your understanding. |
It is, obviously, sad to hear that it will not get prioritised but I understand I'll see if I can squeeze in some time between Christmas and New Year's Day for a patch. |
Can you please add a filter to override this logic? There are cases when multiple multiple terms query wanted to be indexed |
Issue still relevant in latest version of the plugins: Yoast SEO 10.1.3, ElasticPress 2.8.2 and WooCommerce 3.5.7. |
Please inform the customer of conversation # 493461 when this conversation has been closed. |
Hello, I raised this issue via email sometime ago too, but was told to wait for the next updates, but nothing improved. Are you looking to fix this, or are we expected to pay for licenses without issues being fixed? This is affecting a number of our sites and it would be nice to have it sorted. many thanks, |
Please give us a description of what happened.
When using external search-index plugins that have to specify all child terms that they want to query for when
WP_Query
containsinclude_children
then the check fails and says that the archive page is a "multiple terms" page. This ends up addingrobots => noindex
in the head.Example: A webshop have a product category with child categories (bikes > race-bikes).
If "race-bikes" does not have any children, then this page will be indexed but "bikes" will not.
It is possible to read more here in an ElasticPress issue where one of the contributors semi-concludes:
I figure this is a regular case but I have only tested with ElasticPress but it would be awesome to hear what you feel.
Please describe what you expected to happen and why.
I expect taxonomy terms with child terms to be indexed with external search-index plugins so they will show up on Google 😅
How can we reproduce this behaviour?
Technical info
The text was updated successfully, but these errors were encountered: