Priscilla Chapman

Hi @djonyf,

We see from the screenshot that Bing isn’t recognizing the sitemaps in the sitemap index. Have you used the “Re-submit” button in the top right corner to see if this solves the problem?

If not, can you test to see if the sitemaps links in the sitemap index display correctly and don’t have any errors?

If you’re not sure, you’re welcome to send us a URL or you can test your sitemaps using a sitemap validator tool.

Hi @itons,

To see if the Google Search Console error still applies or if there is a bug, can you upgrade to 16.5 and test the pages mentioned in the report using the Google Rich Results test?

You can test the upgrade on a staging site if you don’t want to upgrade on a production site. Do you see any errors?

If you see an error or find a bug, please send us more details. You’re welcome to send us a link to a screenshot or an example URL.

Hi Yahaira,

To be sure that Yoast SEO is adding this og:locale:alternate, can you temporarily disable the Yoast SEO plugin, then check to see if the tag still appears? You may need to clear any caching from plugin or your server and refresh the page to see the change.

We recommend doing this on a staging site or using the?Health Check & Troubleshooting?plugin.

We have a step-by-step guide here:?How to check for plugin conflicts.`

Hi @mmwbadmin,

To make sure that the errors were related to the schema output for version 16.5, can you update or use a test site to check the schema data using the Google Rich Results test?

If the same error appears, please try the following steps to reindex the SEO data on your site:

1. Install and activate the Yoast Test Helper plugin
2. Go to Tools -> Yoast Test
3. Click the “Reset indexables and migrations” button
4. Go to SEO -> Tools and under “Optimize SEO Data” click the “Start SEO data optimization” button.

For sites with more than 10,000 posts, we’d advise using the WP CLI command to do the indexation on the server instead of going to SEO > Tools. You can read more about this here: WP CLI – Reindex Indexables command

Can you let us know the results?

Hi @neutralgroundnews,

It looks like the homepage is set to show the latest posts (see Settings > Reading). If so and you’re using Yoast SEO 16.5, you can change the default social titles by going to SEO > General.

You can find the social settings under the Homepage section and remove the title variable if it appears. Does this solve the problem?

Hi @christiemade,

We’re not able to reproduce the problem you’re seeing, so here are some other troubleshooting steps you can try:

1. Check for JavaScript errors with your console on the edit screen.

2. Check your PHP error log for any error messages. You can do this by enabling WordPress debugging or on a production site, contact your web host.

3. Confirm that your site and developement server meets the plugin’s minimum requirements? You can often find these details by going to Tools > Site Health > Info in WordPress.

If you didn’t find any conflicts or errors, we think the issue is specific to your site. We’d need to investigate further but are unable to do so on these forums. You can purchase Yoast SEO Premium and receive our Premium email support and we can help you further.`

Hi @arindamg,

We were able to reproduce the problem in the Yoast SEO snippet preview on the edit screen, so we created a bug report for review. You’re welcome to comment on it or follow the issue on GitHub to be notified of updates.

As for Google search results, does asking Google to reindex the page solve the problem? You can find the details in this guide: How to update information in Google search results. Please know that it may take a few days or more time for Google to update the search results.

Hi @akiraanastasia,

Thanks for more information. Just a few points to help you solve the problem:

1. The warning is related to a missing HTML language attribute, so it’s not related to the schema data. To make sure, we checked the homepage in the the Google Structured Data Testing tool and found that the language appears with no errors. See a screenshot.

2. The lang attribute would be set by themes or multilingual plugins, not by Yoast SEO. The most common practice is to add the language using the html tag, not a meta tag. See the language_attributes() example in the WordPress code reference.

The page source of the example pages shows that open <html> tag after the doctype is missing, so this is most likely the cause of the warning. See the following screenshot.

We recommend adding this to your theme or contacting your theme developer to solve the problem.

3. If the theme does have the html tag, we recommend completing a conflict check to see if you can identify the problem.

Hope this helps!

Hi @ajisimplifymecom,

There doesn’t seem to be a problem with the example code you shared. Can you give us more information about what error you’re seeing related to Yoast SEO?

It’s a bit out of our scope to troubleshoot custom code, but it may help to check the Yoast developer documentation.

If you’re not familiar with what custom code to add or how to use WordPress hooks, we highly recommend contacting a web developer. You can also check out sites like?Codeable.io?for available freelance WordPress developers.

Hi @jmires,

Thanks for sending details about what you’ve already done to troubleshoot this problem. The edit screen shouldn’t take that much time to load and the SEO data optimization should complete.

Here are a few more things to check:

1. Can you let us know how many ACF custom field values are on a typical page and what field types you’re using?

2. Check for JavaScript errors in the console on the edit screen. If you find them, please send a link to a screenshot.

3. Check your PHP error log for any error messages triggered while editing a page. You can do this by enabling WordPress debugging or contact your web host.

4. Can you give us more details by installing the Query Monitor plugin? Please go to a page where the problem is happening and check for any errors or slow queries. Are there any warnings related to Yoast SEO?

5. If you’re not able to use the Health Check plugin or deactivate plugins during a maintenance window on your production site, we recommend testing on a staging site. See our guide for checking for conflicts.

6. We see that your site is running PHP 5.6, but this is not the recommended version. PHP 7.4 is now the minimum requirement for WordPress WordPress and PHP 5.6 has already reached its end of life.

Hi @oliverhamburg,

There are only a few scenarios that would cause Yoast SEO to add redirects and they depend on your SEO settings. For example, if you set Yoast SEO to remove the category prefix or if you disable date archives, it will create redirects for you.

To see if we can help, can you give us an example URL or let us know what type of page is being redirected?

Also, please check for conflicts by temporarily deactivating all plugins except for Yoast SEO and switching to a default WordPress theme like Twenty Twenty-One. Does the redirect still happen?

Hi @sign003,

Sorry to see a deprecated warning on your site related to Yoast SEO. This error usually appears when another plugin or theme is using an outdated Yoast SEO function or API.

To see what is causing this conflict, you can do a test to see if this error still happens if you?deactivate all plugins except for Yoast SEO and switch to a standard theme?like?Twenty Twenty-One.?

We recommend doing this on a staging site or using the?Health Check & Troubleshooting?plugin.

We have a step-by-step guide here:?How to check for plugin conflicts.`

We also recommend contacting your web host to change your site’s error settings if you’d like to avoid seeing these types of errors from appearing on the frontend of your site.

Hi @suryaadidarma30,

We tried to view the image set as the og:image and it returned with a 403 Forbidden error.

Can you check your site settings or your server configuration files to remove any restrictions blocking access to this file? You may need to contact your web host to help you investigate.

Hi @debbiefromdelburne,

Thanks for the information about the steps you’ve already taken. We can confirm that the homepage is set to noindex.

To help us find out why this is appearing, please send us the information below:

1. Go to SEO > Search Appearance > Content Types. Under Pages, is “Show in search results” set to “Yes”? If not, does changing the setting solve the problem?

2. Edit the homepage and expand the “Advanced” section in the Yoast SEO metabox. Is “Show is search results” set to “Yes”?

3. Does clearing your cache from caching plugins, the server, a CDN like Cloudflare resolve the issue? If you are not sure how to clear the cache from a plugin, please contact the plugin author. If you’d like to clear the cache from the server, please speak to your host provider.

4. There could be a conflict with another plugin or the settings on your site. Does the noindex appear if you?deactivate all plugins except for Yoast SEO and switch to a standard theme?like?Twenty Twenty-One?

We have a step-by-step guide here:?How to check for plugin conflicts.`

Since your question about old blogs isn’t related to this problem, we recommend creating a new thread for it. That way it’s easier for us to match replies with a specific problem. Thanks!

Hi @gipsy84,

Sorry to hear that this problem is happening with every update. Server errors like 502 Bad Gateway errors are usually related to caching or security settings. These errors are usually temporary and disappear after the update once the cache has been cleared.

If that’s the case for your site, it’s not something that can be fixed in Yoast SEO, but you can take the following steps to see if there is a problem:

1. Confirm that your version of WordPress and the server meets the plugin’s minimum requirements. You can often find these details by going to Tools > Site Health > Info in WordPress.

2. Clear or disable your cache from caching plugins, the server, a CDN like Cloudflare. If you are not sure how to clear the cache from a plugin, please contact the plugin author. If you’d like to clear the cache from the server, please speak to your host provider.

3. Check your PHP error log for any error messages. You can do this by enabling WordPress debugging or contact your web host.