MariusG
Forum Replies Created
-
In order to access the Titles & Metas tab, please enable the advanced settings as in this guide.
Upon checking the source code your URL, we found that there are 2 sets of Open Graph tags, one of them being generated by a different plugin or your WordPress theme.
In this manner, it would be best to perform a conflict check to find out what other plugin (or your theme) is adding the extra set of Open Graph tags. This guide explains more about how to perform one.
In order to find what plugin/theme is adding the extra OG tags, you should check the source code of your URL after activating back each plugin, one at a time.
When you are able to find 2 lines of
<meta property="og:description"in your source code, then it means you have found what other plugin adds Open Graph tags.Additionally, after you have found the conflicting plugin, you should clear all your caches, then submit your URL to Facebook’s Sharing Debugger and click Scrape Again, to make sure the correct open graph tags are used (e.g. image, title, description)
If left empty, Yoast SEO will pick the meta description from the first words in your product’s short description. That is because the short description is closer to what the meta description is, a short paragraph which briefly describes the product.
However, for best results, we recommend manually creating a meta description for each of your products. If you need help on setting them, we recommend checking out this guide.
Hi Chis,
If your post starts with an image, even though the focus keyword might be in the alt text, then Yoast SEO will not detect it as appearing in the first paragraph. In this case, it is safe to ignore the warning.
The markup for price structured data is being generated by WooCommerce. It would be best to create a topic here to ask if it’s possible to remove that markup.
The title and meta description of your URL are currently empty:
<title></title>
<meta name="description" content="">These do not seem to be generated by Yoast SEO, as even if you leave the title and description empty, they would get replaced with the default values set in the templates from SEO → Titles & Metas → Post types.
Is the /portfolio/ page is built using a custom page template? We ask as we could not find any of the tags generated by Yoast SEO (which we could find on other pages of your website). In that case, then you might have to edit the template and make sure that it includes the header.php file, as it does not seem to be loaded. Does this fix your issue?
Are you referring to a text counter? Because there already is a progress bar right under the meta description which shows how close you are to reaching the maximum length.
If you’d like a text counter instead, then it’s not possible at the moment. We’re actively using the bug tracking on our GitHub repository so your best next step would be to create a new feature request for our developers at https://github.com/Yoast/wordpress-seo/issues/new. You can create a new issue to submit your feature request. You will need an account to create one.
Don’t forget to include the URL to this conversation in your feature request!
Thank you for bringing this issue to our attention. We apologize for the trouble you are experiencing with Yoast SEO 6.1. A bug report is currently open with our development team for this issue.
If you have further information or would like to follow the progress of the report, you can do that here: https://github.com/Yoast/wordpress-seo/issues/8634
In the meantime, a temporary workaround would be to edit the
/wordpress-seo-premium/inc/sitemaps/class-sitemap-image-parser.phpfile and replace the 239 line to thisreturn array_unique( $attachments, SORT_REGULAR );. However, we would recommend waiting for a plugin update to fix this issue. It is not recommended to modify the core plugin files, but this could be a temporary workaround.Thank you for bringing this issue to our attention. We apologize for the trouble you are experiencing with Yoast SEO 6.1. A bug report is currently open with our development team for this issue.
If you have further information or would like to follow the progress of the report, you can do that here: https://github.com/Yoast/wordpress-seo/issues/8634
In the meantime, a temporary workaround would be to edit the
/wordpress-seo-premium/inc/sitemaps/class-sitemap-image-parser.phpfile and replace the 239 line to thisreturn array_unique( $attachments, SORT_REGULAR );. However, we would recommend waiting for a plugin update to fix this issue. It is not recommended to modify the core plugin files, but this could be a temporary workaround.Thank you for bringing this issue to our attention. We apologize for the trouble you are experiencing with Yoast SEO 6.1. A bug report is currently open with our development team for this issue.
If you have further information or would like to follow the progress of the report, you can do that here: https://github.com/Yoast/wordpress-seo/issues/8634
In the meantime, a temporary workaround would be to edit the
/wordpress-seo-premium/inc/sitemaps/class-sitemap-image-parser.phpfile and replace the 239 line to thisreturn array_unique( $attachments, SORT_REGULAR );. However, we would recommend waiting for a plugin update to fix this issue. It is not recommended to modify the core plugin files, but this could be a temporary workaround.Hi Dan,
When checking your post-sitemap6.xml, we got an HTTP ERROR 500, which suggests the error is on the side.
Are you using the latest version of Yoast SEO? We ask as there is a known issue which we’ve recently found where some of the sitemaps would return a 500 error code.
If that is the case, a temporary workaround would be to edit the
/wordpress-seo-premium/inc/sitemaps/class-sitemap-image-parser.phpfile and replace the 239 line to thisreturn array_unique( $attachments, SORT_REGULAR );. In general, it is not recommended to modify the core plugin files, as this issue will be fixed in the next plugin update, but this could be a temporary workaround.While we could not say for sure whether you will encounter any issues, we do know there are many other websites which run their main website on a different platform and their blog (under the same domain name) on WordPress.
From an SEO perspective, having WordPress installed on a subdirectory of your main website is not a problem, you should not experience any crawling issues.
Hi,
Can you check if your expired job listings have a noindex meta robots tag? This would sound like a plausible scenario for WP Job Manager. If you do not know how to check, you can ask the developers here
If expired listings have a noindex tag, then that is the reason why they cannot be found in the sitemap.
Forum: Plugins
In reply to: [Cache External Scripts] Cache other scripts too?Hi Diego,
Thanks for the quick reply, looking forward to see the update.
I’ll go drop a review, this plugin needs more love 🙂Best,
MariusForum: Plugins
In reply to: [WooCommerce Multiple Free Gift] Keeps popping up with the gift dialogAny updates here? I’m having the same issue.