devnihil
Forum Replies Created
-
@viablethought We’re sorry to hear you are experiencing this issue on your site.
Regarding your issue, can you please confirm you are using the most recent version of Yoast SEO, version 20.0? You can learn more about updating here: How can I update my free plugin?
Also, can you confirm you are using WordPress 6.1.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: Why we don’t support old WordPress versions.
If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?
If you have already confirmed that both Yoast SEO and WordPress are up to date and the issue is still occurring, we would next recommend performing a conflict check to determine whether another plugin or theme is interfering with the Yoast plugin.
The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like TwentyTwentyOne.
Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.
We’re sorry to hear you are experiencing this issue on your site.
Regarding your issue, can you please confirm you are using the most recent version of Yoast SEO, version 20.0? You can learn more about updating here: How can I update my free plugin?
Also, can you confirm you are using WordPress 6.1.1? You can check by clicking on the W in the top left and selecting About. If you need to update, please check with your host provider. Please know that if you are using an older version of WordPress Core you may experience unexpected behavior with Yoast. This guide explains more: Why we don’t support old WordPress versions.
If you update to the most current version of WordPress and Yoast SEO, does this resolve the issue?
If you have already confirmed that both Yoast SEO and WordPress are up to date and the issue is still occurring, we would next recommend performing a conflict check to determine whether another plugin or theme is interfering with the Yoast plugin.
The fastest way to do this is to deactivate all non-Yoast plugins and switch to a standard theme like TwentyTwentyOne.
Test this on your development or staging site, if you have one. If not, we recommend using the Health Check & Troubleshooting plugin. This plugin allows you to run a conflict check without affecting normal visitors to your site.
If you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process: How to check for plugin conflicts.
@soporteaeuroweb We’re sorry to hear you are experiencing this issue on your site.
Can you please confirm whether you are using the most current version of Yoast SEO, version 20.0 and that the issue occurs when only Yoast SEO, LearnPress, and a default theme such as TwentyTwenty are active?
@ppeter12 The ‘SEO Title’ field will be what is output for the html
<title>tag. The value of the html<h1>tag is typically generated using the value of your Post Title. There isn’t a way to set a value for the<h1>tag from the Yoast meta box though.We also have more information on this topic here: What’s the difference between an H1 heading and the SEO title?
@zetamayo Thanks for your reply and for confirming you’ve performed a conflict check.
We understand that the issue still occurs with only the free version of Yoast SEO, but if you have Yoast SEO Premium we’d recommend contacting us for support directly at [email protected] where our support engineers can investigate this further for you and offer support through emails privately. Due to the nature of the issue, we’d need to take a look at your setup to see what’s going on there, and we are unable to do so here since this is a public forum.
@mumbomedia Thanks for confirming that corrected the issue.
Also, whereas the release containing the fix for this bug will be available on Feb 7, in the meantime you can use the release candidate available here to immediately correct the issue.
@arjn Thanks for your reply.
Regarding your issue, the only other thing I can think to suggest is for the affected author pages, to try toggling the ‘Do not allow search engines to show this author’s archives in search results’ setting to On, saving the profile, then unchecking, and saving it again.
Can you please try the aforementioned suggestions and let us know whether this resolves your issue?
@wicaodian We’re sorry but we aren’t able to provide this level of support in the forums. These forums are dedicated to offering support for the plugin, but this unfortunately doesn’t include development support related to coding.
Unfortunately, there’s a difference between the support we can offer and the level of programming needed to change (core) features of our plugin. Since we don’t want to take the risk that we break your website by suggesting incorrect or incomplete code, we cannot advise you on how to make such changes. And even though we cannot be of any assistance, you’re completely free to change anything in the plugin to better suit your needs.
Maybe someone watching these forums can assist you further, but if your topic is inactive, we’ll mark it as resolved to keep the overview. Thank you for your understanding.
You can find the developer documentation for the REST API available here: https://developer.yoast.com/customization/apis/rest-api/
@rieiirir If you have purchased News SEO you would need to contact us directly at [email protected] for assistance. As per the forum guidelines, we cannot answer questions about our premium products, as this forum is reserved for support of the free version of Yoast SEO only.
For questions or support for our premium products, please contact our support team directly. Thanks for your understanding.
@arjn We’re sorry to hear you are experiencing this issue on your site.
Regarding your question, even if author archive pages are set to be shown in search results in the global settings, they can be set on an individual per author basis in the user profile settings.
To set an individual author pages to be indexed you would need to perform the following steps:
- In WordPress, go to Users>All Users
- Click ‘Edit’ beneath the user to edit
- Scroll down to the ‘Yoast SEO settings’ area
- Uncheck ‘Do not allow search engines to show this author’s archives in search results’
- Click ‘Update Profile’
We also have a guide on this located here: How to noindex individual author pages.
Can you please try the aforementioned suggestions and let us know whether this resolves your issue?
@nick1234567 Thanks for confirming that you were already able to solve your issue, and for posting the solution as well.
We’re going ahead and marking this as resolved but if you should need any further assistance, please do not hesitate to let us know.
@webmastert We’re sorry to hear you are experiencing this issue on your site.
We checked on your site’s homepage and do see the ‘No information is available for this page’ message for it in Google’s search results.
We verified the page source of your site homepage has no ‘noindex’ tag as expected. We went ahead and checked the robots.txt file. Per Google here, robots.txt file might be the possible cause.
We do recommend you edit the file and just have this standard rule for better crawlability of the site.
User-Agent: *
Disallow: /wp_admin/
Allow: /wp-admin/admin-ajax.phpThis would allow GoogleBot to crawl all the links on your site and better understand how the pages are viewed and displayed. This guide explains more: https://yoast.com/ultimate-guide-robots-txt/. We have additional recommendations on robots.txt here: https://yoast.com/wordpress-robots-txt-example/.
Once done, we recommend that you submit the Yoast-generated sitemap https://film-book.com/sitemap_index.xml and to delete any other sitemaps. In addition, please follow these steps:
- Please submit your website to the Google search console, if you haven’t done so, by following the steps given in <u>this guide.</u>
- Please submit your sitemap to your Google search console, if you haven’t done so, by following the steps given in <u>this guide</u>.
- You can then try to use “Fetch as Googlebot” on your homepage and verify if the search results for your site are updated.
It might take some days for Google to fully crawl your site and index URLs in the search result.
@kashifbaloch12 Whereas the Yoast SEO plugin doesn’t have a built in function to create an HTML sitemap, we do have a guide on how to create one available here: https://ww.wp.xz.cn/support/topic/how-to-add-html-site-map/
@jpnl Thank you for bringing this issue to our attention! I’m sorry that our plugin caused a problem on your site. A bug report has been created and is under review by our product team.
Workaround
We are aiming to release a bug fix for this in the 20.1 release, but until then this can be fixed by using the release candidate here.What’s next?
Our product team will assess the severity of the issue and assign a priority level to the report. Our developers work on the highest priority issues first. We cannot give you an estimate of when they’ll start working on the issue.If you have any further information that may affect the prioritization or help our development team solve this bug, please leave a comment or subscribe to the GitHub report to get updates on the issue.