WordPress.org

Ready to get started?Download WordPress

Forums

WordPress SEO by Yoast
Yoast does not apply the_content filter on content before extracting data (8 posts)

  1. RonDsy
    Blocked
    Posted 1 year ago #

    Question: Is it not good policy to apply the_content filter on post content before extracting data? Yoast SEO (WordPress SEO) does not apply the_content filter on post content before extracting data such as meta tags. This causes problems with other plugins that follow this practice. Why is Yoast the exception? Is this an oversight?

    http://wordpress.org/extend/plugins/wordpress-seo/

  2. hardyakka
    Member
    Posted 1 year ago #

    I'm interested in buying a plugin where this issue with WP SEO was noted as an issue and because of it content created in the plugin was invisible to WP SEO. The plugin creator stated that he had contacted Joost (some time ago) but and was not responded to in relation to the compatibility issue.
    It seem to be a given that it is not "best practice" not applying the filter. Joost's silence on the matter says quite a lot, I'd say.

  3. RonDsy
    Blocked
    Posted 1 year ago #

    Yoast SEO seems to have it all: great docs, interface, great help guides, easy to understand on "how to," however it misses out on a key function.

    Not applying the_content filter on post content before extracting data such as meta tags is a major failure in a key process. Many individuals are not even aware of this failure of Yoast and therefore its impact.

    This is causing content managed by several plugins to be left out from the SEO. ref: http://talkingmanuals.com/wordpress-plugin-reviews/content-builder-review/

  4. hardyakka
    Member
    Posted 1 year ago #

    I've Googled "the_content" and though I don't know PHP it was clear enough to me to understand that use of the_content permitted undesirable/unwanted/unexpected injection of content (as far as I understood it) in areas where it was not meant to be. In each case, other PHP/code methods could be used to obtain the result that the_content was meant to achieve (again, as far as I understood what was being described).

    Subsequently, I had the chance to communicate with Joost. He confirmed the understanding that I gleaned from my brisk Google research. He said that although there are pros and cons to the use of the_content, it slows things down when turned on and with plugins like sociable, all kinds of links can appear. He went on to say that because of WP's lack of pre_the_content and after_the_content filters, the_content is abused a lot.

    I hope this provides an insight into why WP SEO doesn't use the_content filter. It is unfortunate that plugin developers who claim their plugins require the_content compatibility are not able to work around it and come up with a more reliable and secure solution.

  5. RonDsy
    Blocked
    Posted 1 year ago #

    Hi Hardyakka,

    Great that your interest has taken you to a deeper investigation on not applying the_content filter on post content before extracting data such as meta tags.

    What I did not read is the resolve. The bottom line is that content within the <div> of a plugin is not being S-E-Optimized. What methods have Yoast taken to resolve this? I will continue this discussion with other SEO authors over at Talking Manuals to find a balance if not a solution.

    The apparent concern is that you are under the false pretense thinking your content is being S-E-Optimized but it really is not. If elements of a post or page is being managed by a plugin, the content or tags may not be seen by the SEO plugin.

    Possibly core developers of WP need to address this concern in the WP CODEX/API. For example, another area of concern is the WP taxonomy schema.

  6. hardyakka
    Member
    Posted 1 year ago #

    I hear what you're saying RonDsy, but the detail of most of that stuff is going way over my head. You bring up many other issues that I have no doubt are indeed valid, but the finer details eclipse my understanding. You clearly have developer level concerns; I think I understand what you are saying, but I can't be sure.

    The the_content issue didn't directly apply to me; I was interested in the plugin that is referred to in what you linked to (above), but I hadn't gotten it yet and based on the other bad press that the page you referred to gives, I don't think I will. I was more interested in WP SEO being accountable for doing something or not doing something. For the level of my understanding (non-dev), Joost did that to my satisfaction.

    When I communicated with Joost, it was by twitter (@yoast). I was surprised that he responded to me. Have you tried bringing your concerns to his attention? He first advised me that if I felt it was a bug, I should open an issue (I think he meant raising a support ticket on his site). When I told him I didn't consider it a bug and I was just interested to know why it wasn't implemented in WP SEO, he gave me the response I have passed on to you. Raising a support issue might be the way to go if you think it is warranted.

    Another thing. Joost made it clear to me that the issues raised in this support area are not of immediate concern to him. That should be clear by the number of threads that have 1 as the number of posts in them. If you have something that warrants his or his developers' attention, here is not the place to get it responded to. I suggest going to his site and hopefully, it will get the attention it deserves there.

  7. grigione
    Member
    Posted 6 months ago #

    jrfnl commented 12 hours ago

    Sorry, this will not be changed. There are too many plugins out there who are doing things wrong, applying the the_content filter in another place than where it is meant to be used therefore breaks lots and lots of websites.

    https://github.com/Yoast/wordpress-seo/issues/491

  8. jrf
    Member
    Posted 6 months ago #

    Just to be clear: this is my opinion, not an official stance, though I suspect that @yoast agrees.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.