[Gelöst] Toolset blocks is not ready for Yoast SEO analyzer
This support ticket is created vor 4 Jahren, 11 Monaten. There's a good chance that you are reading advice that it now obsolete.
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
Heute stehen keine Supporter zur Arbeit im Werkzeugsatz-Forum zur Verfügung. Sie können gern Tickets erstellen, die wir bearbeiten werden, sobald wir online sind. Vielen Dank für Ihr Verständnis.
Hi,
The page: versteckter Link versteckter Link
It has internal links (Toolset view block), however the Yoast SEO analyzer indicates that it has no internal links:
"Internal links: There are no internal links on this page, be sure to add one!"
Look at the screenshots.
Regards,
Jose
I believe this one is not a fixable issue on our end as you can see the view is being generated dynamically a preview on the backend. This content isn't actually stored on the post.
What yoast is looking for is content actually stored on the post. In the case of the view block what is stored is the shortcode to call the view and not the actual content that the view will replace.
Please let me know if this clears things up for you.
Hi Shane,
That is not correct, Yoast incorporates a special mechanism so that plugin designers can pass texts from shortcodes, etc. to their analyzer. versteckter Link
If Toolset has not taken into account this is a very serious limitation for the SEO analysis of a page.
If you want Toolset Block to be your system to make pages and posts you will have to implement this system.
Tell me something about it.
Regards,
Jose
Currently our developers are looking into the Yoast API on how to add this dynamically generated content on the backend.
However the documentation on how to integrate this for Yoast to recognize isn't so clear but I do suspect that we are not the only plugin experiencing this issue.
Any plugin that uses dynamically generated contents in a block will have this issue as well. This is on our To Do list but there won't be a patch for this anytime soon as our developers are working to understand the Yoast documentation.
