MariusG
Forum Replies Created
-
Can you send us a list of your active plugins and themes, so that we may replicate the issue on our side?
Hi Kyle,
Can you check again if the issue persists? We ask as we’ve checked your news feed and the image loads correctly on our side: https://i.imgur.com/SnSFKy7.png
Also, if you have any browser extensions, please disable them temporarily. We ask as we weren’t able to replicate the issue.
We are looking forward to hearing from you.
Hi @crwhntt,
Unfortunately, we couldn’t say for sure why those custom fields are not working. Could you share the name of the theme, so that we may try to replicate this issue?
We are looking forward to your reply.
We’re sorry about the inconveniences, a bug fix will be released in Yoast SEO 8.1 to address this issue.
Hi @rameezramzan,
Do you mean that the old URLs are still present in the sitemap, even though the posts have been deleted in the meantime? If so, it may be a caching issue. Please go to SEO → General → Features → XML Sitemaps and follow these steps:
- Turn Off the XML Sitemaps and click Save Changes
- Turn back On the XML Sitemaps and click Save Changes
- Check the sitemap again for outdated links
Does this fix your issue?
Hey guys,
We’re sorry for the troubles you’ve experienced. A bug report is currently open about this issue, you can follow its progress here. The issue is on our high priority queue, we hope to have a fix very soon.
Hey @ilgraziano,
Did you disable the XML Sitemaps generated by Yoast SEO? We ask as we’ve inspected your website and couldn’t locate any XML Sitemaps generated by Yoast SEO.
We are looking forward to your reply.
Hi @phkcwp,
Yoast SEO should not count the focus keywords in your images alt-text. Are you referring to the captions? If so, unfortunately, it is not possible to exclude them from being counted by Yoast SEO when calculating the keyword density.
Hi @wzislam,
Please let us know which extension you are using for debugging, so that we may try to replicate the issue.
I have tried installing Yoast SEO 7.9.1 on a local multisite network and couldn’t find any issues so far. Please update to 7.9.1 and let us know if the issue persists.
In addition, can you check if the issue persists when Yoast SEO is the only plugin activated on your website?
We are looking forward to your reply.
Hi @marcodiversi,
If you can send us the link to your website’s sitemap, we could tell you if the es_template should be indexed or not.
Hi @cbdoel,
Unfortunately, rich pins are not a feature of the free version (Yoast SEO). It requires a premium add-on for this, Yoast WooCommerce SEO .
Hey @fabriziofru,
Did you encounter this issue after updating? Your screenshot does not seem to reflect the same issue as the one mentioned by @jeremiah01292, which has been reported here.
It does seem like a plugin conflict, but not the same issue as the one with Gutenberg and Classic Editor. Can you try and gather as much information for us as possible? Please perform the following:
1. Check for conflicts.
2. Check for JavaScript errors with your console.If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers.
@mitchellalerts if you want to downgrade Yoast SEO, you can do using WP Rollback.
Hi @semseo,
It is only possible to remove those tags if you disable the Open Graph tags from Yoast SEO. To do so, go to SEO → Social → Facebook and select Disable.
Please note this will disable all Open Graph tags generated by Yoast SEO, not just the 3 tags which you have mentioned.
Hey guys,
Thank you for reporting this issue, we’re sorry for the troubles. Upon further investigation, we found that this issue happens when both Gutenberg and Classic Editor plugins are active. When deactivating either of the 2 plugins, Yoast SEO seems to be working as expected.
We have opened a GitHub issue and sent it to our development team, they will provide a solution as soon as possible. In the meantime, you can follow the progress or let us know if you have any other information here.
Hey guys,
Thank you for reporting this issue, we’re sorry for the troubles. Upon further investigation, we found that this issue happens when both Gutenberg and Classic Editor plugins are active.
We have opened a GitHub issue and sent it to our development team, they will provide a solution as soon as possible. In the meantime, you can follow the progress or let us know if you have any other information here.
