Can wpsso replace Yoast?

WPSSO Core and its WPSSO JSON add-on focus on creating complete and accurate meta tags and Schema markup, where-as the Yoast SEO plugin focuses more on content analysis. If you don’t care about the content analysis, then yes, you’re better off with just the WPSSO plugins.

If Yoast SEO was active when you activated WPSSO Core, you’ll want to review the SSO > Advanced Settings > HTML Tags > SEO / Other tab options (if you have the Premium version) as WPSSO Core would have deactivated some SEO meta tags to prevent duplicates.

As of WPSSO Core Standard v8.8.0-dev.5, those meta tags will be re-enabled automatically (you can download the current development version here https://www.ads-software.com/plugins/wpsso-schema-json-ld/advanced/).

js.

To the point. Thank you.
Correct, I am not interested in the content analysis stuff.

I noticed that recently Yoast has added in index option. https://yoast.com/help/why-does-yoast-seo-ask-to-index-a-sites-seo-data does WPSSO have anything similar?

Now I see that Yoast actually allows you to use variables in the meta data and WPSSO does not.
Also, with Yoast you see the Google preview as you type in the meta data. just a UX thing but it makes a big difference. I wish I use a single plugin that covers it all.

Can I use Yoast for the meta data and hide the options in WPSSO as it comes in very confusing to the authors.

Thank you

There is often a layer of marketing-speak with Yoast SEO documentation – their index table is just a database table where they store information. WPSSO prefers to use the native functionality of WordPress whenever possible, so we use the post/user/term metadata, wp_cache, and transient cache functions to store data, we also crawl the site in background to seed the cache.

WPSSO and Yoast SEO have different approaches to creating meta tags. WPSSO gets information from WordPress, 3rd party plugins, and services (YouTube, Wistia, Vimeo, Bitly, etc.) and creates the most complete and accurate meta tags and Schema markup possible from that data. The Document SSO metabox from WPSSO allows you to customize the information found by WPSSO, but we hope the original information from WordPress, 3rd party plugins, and services is accurate enough that having to customize it is an exception, not the rule. ??

Yoast SEO on the other hand expects you to enter text in their metaboxes. That’s fine – it’s just a different focus. WPSSO focuses on gathering information from WordPress, 3rd party plugins, and services, where-as Yoast SEO focuses more on getting that information from users.

As for the preview, well, that’s a bit of a useless feature, in my opinion. Google is always changing their supported Schema types and search results (see https://developers.google.com/search/docs/guides/search-gallery), so trying to duplicate Google’s display of their search results is a bit pointless. The preview text shown by Yoast SEO is also misleading – Google may use it, but they often ignore it as well, and choose another section of text from the content. WPSSO focuses on including comprehensive descriptions and text in the Schema markup that reflects the content of the webpage, and lets Google pick and choose what to show and how to show it.

js.

I hear you but I don’t think it’s 100% correct and may even be called misleading. though google may not show the meta tag but use other info from the page; the meta tags are there for the purpose of google showing it in the results and that is what we want to preview. the fact that google may not show it is some kind of override that google has.

Please take it as a suggestion to make the UI of WPSSO better look and feel.

And also the other suggestion of allowing variables, it’s a nice enhancement, to say the least.

Thank you

p.s. it’s highly appreciated your prompt responses in this forum. as long as you respond to your users we know this thing is alive ??

Google may use all or part of the description snippet, and WPSSO uses input fields to customize the description snippet for Facebook / Open Graph, Twitter, Google / Schema, etc.

WPSSO supports several inline variables, but although they’ve been available for years, I don’t believe any customers are actually using them. This is actually something that is slatted to be removed eventually. As I said previously, WPSSO gets information from WordPress, 3rd party plugins, and services. If the information that WPSSO gets is incorrect, then the source of that information may need to be corrected. The Document SSO metabox provided by WPSSO is only for occasional fine-tuning or adjustments, in cases where it’s not convenient or appropriate to adjust the actual source of the information.

js.