-
Notifications
You must be signed in to change notification settings - Fork 882
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
Better logic and customizability for enabling Text Links indexing on per-post-type basis #8323
Comments
Thank you for opening a feature request. |
Thanks for the detailed comments @boonebgorges! @moorscode can you look at his feedback above re our logic? I think he's right, especially the |
We have added additional filters to facilitate a more granular control on which post-types are placed in specific feature lists. The task at hand here is to add additional filters on our end to strip out the specific arguments on the post types. |
Please give us a description of what happened.
A plugin is causing large numbers of post items to be generated as part of a batch process. In my specific case, it's wp-rss-multi-importer, though what's described here could happen in similar cases. The plugin defines its post type as
public
, and as such, the Text Links module processes the itemwordpress-seo/admin/links/class-link-watcher.php
Line 99 in 7e1d620
In this specific case, the post type (though registered as
public
) is never actually viewed from the front end. So there's no benefit to having Text Links run on its content.Please describe what you expected to happen and why.
The
public
argument for post types is possibly too broad a check. A post type registered withpublic = true
is not necessarily visible on the front end;publicly_queryable = false
orexclude_from_search = true
, for example, overridepublic
. wordpress-seo could probably improve the default logic here.Moreover, it would be nice to allow for the possibility that a plugin will register a post type with arguments values that don't properly match the actual use of the post type. In these cases, developers/site owners should be able to manually disable indexing of these items. For this purpose, a post type blacklist, or a general filter on
is_processable
, would be helpful.How can we reproduce this behavior?
You probably don't really need to reproduce this specific plugin to see what I'm asking for :-D
Technical info
Thanks for considering - and please feel free to close or suggest alternative methods if this is not an appropriate enhancement request.
The text was updated successfully, but these errors were encountered: