You would need to look in the Yoast plugin to find what the global class is that is referred to as $this, so that you can access it outside the class context. If it was for example, $wpseo, in your functions.php you could do something like: $wpseo = WPSEO_Frontend::get_instance(); remove_action( ‘wpseo_head’, array( $wpseo, ‘canonical’ ), … Read more
Yoast SEO can have limitations for archive pages. Try a different SEO plugin such as Rank Math perhaps. Your other option would be to open the archive.php file of your theme and add your custom code in there if required. You may also contact the developers of that podcasting plugin to see if they have … Read more
Here’s how I fixed it. If you paste this code in your theme’s functions.php, it will use the image set for Facebook also for Twitter if no image is set for Twitter. If there is not image set for both Facebook and Twitter, it falls back to the default Facebook image in the Yoast settings … Read more
Install “Yoast Test Helper” Plugin Navigate to Tools -> Yoast Test Under Yoast SEO, Click the “Reset Indexables tables & migrations”
Throw this into your functions.php: function clear_yoast_metadesc( $metadesc ) { return ”; } add_filter( ‘wpseo_metadesc’, ‘clear_yoast_metadesc’, 99, 1 ); If you set the $metadesc to empty like that, it won’t be echoed. BTW, bulk editing is very hard on my to-do list, so you would be able to switch back completely 🙂
You can use the wpseo_title filter to read the tag for your site title after WPSEO creates it, and if it’s not there, add it on. add_filter( ‘wpseo_title’, ‘wpse137502_wpseo_title’ ); function wpse137502_wpseo_title( $title ) { $site_title = get_bloginfo( ‘name’ ); if ( ! strpos( $title, $site_title ) ) { $title .= ” | ” . … Read more
I would read this article, its from Yoast. I don’t think you are understanding what the focus keyword feature does. This article talks about that as well as how adding the keyword meta tag is a waste of time (in most cases). I wouldn’t worry about adding it BUT if you still want to I … Read more
There is indeed an unwanted ; (semicolon) in your function (try to look at line 99 in the twentytwentyone-child/functions.php file) which likely is the cause to the syntax error. So just remove that ; and the error would be gone: function my_service_template_footer_data() { echo “<script type=”application/ld+json”> { ‘@context’: ‘https://schema.org/’, ‘@type’: ‘Service’, ‘serviceType’: ‘ ” . … Read more
You have introduced 2 additional problems by adding the jQuery from Google CDN. The admin interface needs jQuery called in no conflict mode so it won’t interfere with the other scripts WordPress uses for the dashboard. The WordPress dashboard is not yet compatible with jQuery 1.5 thats why it was pulled from trunk right before … Read more
ASCII characters will not cause any issues with search engines and they will be displayed properly. SEOmoz does this to avoid any chance of sql injection via its form fields.