I am trying to get Yoast SEO to analyse page content stored within a custom post type. It is a WYSIWYG field and it is not including it in the word count, for example.
I have the following versions of WordPress, Yoast and Toolset:
Hello, have you configured this field to be used for Yoast SEO analysis as shown in the document here: https://toolset.com/course-lesson/seo-for-custom-fields-using-toolset-and-yoast-seo/ ? That's usually the first step I would take. Edit the custom field in Toolset > Custom fields > Post fields tab, and turn on the Yoast analysis "raw" setting. If the problem is not resolved, please let me know.
I'm not really a Yoast expert but this article seems to indicate that the premium plugin is required to scan custom fields: https://yoast.com/help/add-custom-fields-to-yoast-seo-premium-plugin-settings/
You may need to contact their support team to see if the premium plugin will include the text from custom fields in text length analysis.
The client has upgraded to the Premium version of Yoast SEO and i have followed the instructions in the link you sent across previously. Unfortunately, still no joy with getting it to analyse the custom field.
Is there anything you can think of from a template/setup point of view that might be preventing it?
We also have some additional information on how to configure custom fields in the Yoast plugin here, although we understand that you already tried this: hidden link
In the past, we have tried to parse custom fields and other content boxes with inferior results. Therefore, we opted to provide plugin and theme developers with an API that they can use to pass their content to our page analysis.
If you are using a plugin or theme that doesn't send their content to our page analysis, please reach out to the developer and ask them about adding the functionality to their code. This KB article will help them with the implementation: hidden link
In step 5 of the premium plugin steps, there is a step where you add the individual custom field names you want to analyze. Types fields use a wpcf- prefix in the database, so you'll need to include that prefix with each custom field slug. If your custom field has a slug of "short-text" in the wp-admin, you would add that custom field slug to the Yoast index using the wpcf- prefix like "wpcf-short-text". Is this how you added the fields? If not, does that change the results?
Thanks for coming back to me again and I hope you had a nice weekend.
I've attached a screenshot of my current setup - the custom field name is "bottom-description", and I have put the "wpcf-" prefix in there but still no joy.
Hope this helps! More than happy to grant you access if required to take a closer look at things?
Okay thanks, I was under the impression that custom fields are currently integrated with Yoast SEO. Let me ask my 2nd tier team for some additional investigation here, because according to our documentation this should work. I will let you know what I find out.
Hello, this is a quick update to let you know my 2nd tier support team did some more in-depth analysis here, and it seems there was a breaking change in the Yoast SEO plugin. According to our research, Types custom field analysis was working as of Yoast SEO 14.5, even in the free version. Users with Yoast versions > 14.5 will experience the same issue you have experienced, where custom fields are not included in the Text Length analysis even if they are configured to be included.
We have escalated this issue to our compatibility team for further investigation, and I will be glad to keep you up-to-date here in the forum as work progresses. For now, there does not seem to be a viable workaround. Downgrading to Yoast 14.5 may fix the problem, but then you won't have access to the latest Yoast bug fixes and features.
Thank you for looking into this further and escalating it with the support team. If you could keep me posted that would be brilliant - is this a bug that the team will look to fix in a future update?
In the meantime I have raised a support ticket with Yoast so they're aware of the issue. I'll keep you posted in here too if any progress made from their side.
Thanks as ever for ongoing support, much appreciated 🙂
is this a bug that the team will look to fix in a future update?
Unfortunately all I know right now is that the problem was introduced during a recent Yoast update. The compatibility team will be able to provide more information eventually, whether this is a bug in the Toolset codebase or a bug in the Yoast codebase, or simply a compatibility issue that arose from some changes. I'll keep you posted here.
