Yoast / wordpress-seo

Yoast SEO for WordPress
https://yoast.com/wordpress/plugins/seo/
Other
1.78k stars 894 forks source link

Let third party plugins register to the readability tab #6721

Open CarolineGeven opened 7 years ago

CarolineGeven commented 7 years ago

Currently it's not possible for third party plugins to register for a custom marking in the plugin (readability/keyword tab). They should be able to.

Pcosta88 commented 7 years ago

Please inform the customer of conversation # 181617 when this conversation has been closed.

quadcom commented 7 years ago

Is this ever getting fixed? It's been this way for YEARS!!

When using Yoast SEO with the Divi theme, no images are indexed in the XML sitemaps!!

quadcom commented 7 years ago

conversation # 181617 goes to a 404. Dead end.

CarolineGeven commented 7 years ago

@quadcom conversation # [number] is a way for us to keep track of issues in our internal contact system for premium users. You won't be able to see this online. The issue you describe is different from the issue that is explained here. We cannot register images that are used in the Divi theme, Divi has to register images to our sitemap, which is already possible with the wpseo_xml_sitemap_img filter.

lots0logs commented 7 years ago

Related: https://github.com/Yoast/wordpress-seo/pull/7251

quadcom commented 7 years ago

@CarolineGeven I was referred here by Elegant Themes. Their support isn't the greatest. However, this problem still exists and Elegant Themes pushes back saying it's your problem. Then, you push back saying it's their problem. I wish you two could talk to each other and sort this problem out.

ElegantThemes Forum • View topic - Divi Theme and Yoast SEO.pdf

quadcom commented 7 years ago

How about this, can you provide me with a document that would outline what ElegantThemes needs to do in order for this to function properly? I can then provide this to ET and get them working on fixing the problem.

lots0logs commented 7 years ago

@quadcom There's no need. We (Elegant Themes) have been and still are discussing possible solutions to the issue (see #7251)