AskKim
Forum Replies Created
-
Hi karakgogotech,
Thank you for taking the time to work with the JetPack team and find out what was going on and letting us know.
We would much appreciate it if you would take the contents of your ticket here – and submit them as a bug report for the Yoast SEO plugin in the following GitHub repository: https://github.com/Yoast/wordpress-seo
In the meantime, to help you work around the issue…
Some taxonomies are not added publicly and thus do not appear for exclusion within the plugin interface. Use this filter to exclude them: http://kb.yoast.com/article/299-how-to-customize-the-sitemap-index#exclude_taxonomy
You will want to replace ‘taxonomy_slug’ with ‘jetpack-portfolio-type’ in one instance and with ‘jetpack-portfolio-tag’ in another instance.
That should successfully work around the issue while we look into the bug report on GitHub.
~ Kim ~
Support at YoastHi Kate,
When I view the source of your site: http://www.theweddingblissthailand.com/
I see that there are two entries for og:description
That means that multiple items are adding the social meta data… our plugin, and something else (either a plugin or the theme).
You need to tell the other thing to not add social meta data. Generally these tags are added by social sharing plugins and any good social sharing plugin has a checkbox to NOT add the data which you’ll want to check.
Once you fix the code, then use the Facebook debugging tool to clear the Facebook cache: https://developers.facebook.com/tools/debug/
~ Kim ~
Support at YoastThat is not a feature available of the plugin. The items are laid out in chronology for Google.
You might consider submitting that as a feature request to the team who makes your HTML sitemap, to allow entry re-ordering.
~ Kim ~
Support at YoastHi glensickemore,
Unfortunately, this problem comes up from time to time and there still are no perfectly consistent answers from Google.
I would suggest starting a ticket on the Google Webmaster forum, as was proposed in the other thread.
You might even attempt the work-around of submitting the individual sitemaps if you have not already. (Please keep us posted if that does or does not help.)
In addition, you can really help us, and everyone else that may be suffering with this, out by checking the GitHub repository: https://github.com/Yoast/wordpress-seo – seeing if any tickets exist with the issue, and if not, starting a new issue report there.
~ Kim ~
Support at YoastHi Zoee,
In your WordPress dashboard, under SEO, select “Titles and Metas”.
Here, look under both the “Post Types” and the “Taxonomies” tabs and ensure that you do not have a checkmark next to anything related to Events that says “hide”.
~ Kim ~
Support at YoastHi romestylez,
Getting something OUT of Google is much more challenging than keeping it out in the first place.
This post will help you with that: http://just-ask-kim.com/remove-block-prevent-post-google-search-engine/
~ Kim ~
Support at YoastForum: Plugins
In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] H1 tagHi emondoz1,
To do that requires you to add some custom css to your website, as the size of the heading tags are defined by your theme.
You can either edit your style.css directly (not advisable), or edit the style.css of your child theme (better), or use a plugin like My Custom CSS to give you an easy field to insert css code into without messing with your theme.
Each theme will have slightly different requirements:
Here are some related discussions you may find helpful:
https://wordpress.org/support/topic/how-to-change-the-font-size-of-a-page-title?replies=11
https://wordpress.org/support/topic/how-do-i-increase-header-title-font-size?replies=12
http://smallbusiness.chron.com/change-header-tags-font-size-wordpress-50689.html
~ Kim ~
Support at YoastHi bluantinoo,
Unfortunately, I can not see into that forum at the moment.
However, the code needed to filter out those taxonomy from the sitemaps is found here: http://kb.yoast.com/article/299-how-to-customize-the-sitemap-index#exclude_taxonomy
You would replace ‘taxonomy_slug’ with ‘layout_type’ etc
And then insert that code into your functions.php file.
Ideally, one of these days, Divi will do everyone a favor and pre-add that code for you 🙂
~ Kim ~
Support at YoastHi, Emineminero
Google+ seems to have no problem with that URL.
The Error you’ve mentioned commonly happens if you try to share a post/page while it is in DRAFT mode. And if you do that you can result in that data getting stuck in Google+ for a while (caching).
I did however notice that your social media share buttons are not correctly displaying on Firefox for me and so it’s possible that they are contributing to your issue.
Screenshot: http://screencast.com/t/URan3MzLCO
In the screenshot above, you’ll see that Google+ is not rejecting the post.
However, you have not filled in most of the SEO fields and you have not output any Facebook or Google+ data, so there is incomplete data for Google+ to use to build a preview with.
Screenshot 2: http://screencast.com/t/lQT8TvVl
~ Kim ~
Support at YoastHi Kevin,
The Focus keyword and score are only analysis tools. Nothing you enter in “Focus Keyword” outputs to the front of the site. (Unlike SEO Title, Meta Description, etc.)
The Focus Keyword is there to help you understand what Google sees.
If the tool can’t see the field.. then your score will be artificially low from the tool… but will be higher according to Google because Google will see the boxed output.
Our content analysis is just to validate the content of your website and doesn’t really affect how search engines crawl and index your site.
That being said, in the past, we have tried to parse shortcodes and theme content boxes with horrible results so we opted to provide plugin and theme developers with a filter that can be used to pass their content to our page analysis. Please refer to this KB article: Can I add data to the page analysis? http://kb.yoast.com/article/91-can-i-add-data-to-the-page-analysis
Your developer may also need this URL helpful: http://support.advancedcustomfields.com/forums/topic/yoast-seo-acf/
​As long as the content is available to Google, you are good to go. Don’t think that a green light is mandatory if there is a valid reason for our plugin to be unable to see some of the data that you know is there.
​
If you need additional personalized assistance to help you get this solved we also offer Premium support which you can learn more about at http://kb.yoast.com/article/160-support~ Kim ~
Support at YoastYou should be able to close the warning and it should only return when you update plugins… as long as you have made sure to NOT enable the sitemap feature in the Yoast SEO settings. However, it is possible for it to get stuck in caching so you may also need to clear your cache if it is being persistant.
If you need additional personalized assistance to help you get this solved we also offer Premium support which you can learn more about at http://kb.yoast.com/article/160-support
~ Kim ~
Support at YoastThis ticket appears resolved so I am going to close this it. Feel free to follow up if that for some reason does not solve the problem Neil. 🙂
~ Kim ~
Support at YoastThank you for your feedback Paul. I have double checked that this information got passed to the right team. (And am replying so I can close this ticket.)
~ Kim ~
Support at YoastHi nooramansi,
Thanks for emailing us!
Sometimes strange behavior may be caused by a plugin or theme conflict. The fastest way to rule out conflicts is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Fourteen. If this resolves the issue, you have a conflict and should activate one plugin at a time until you locate the conflict. Finally, after all plugins are active, switch to your theme. This will narrow down the conflict to a specific plugin or a theme conflict.
If you are unfamiliar with checking for conflicts, we wrote a small guide that will walk you through the steps. You can find it here: How To Check For Plugin Conflicts: http://kb.yoast.com/article/253-how-to-check-for-plugin-conflicts
Can you please inform me of the results?
Hi YvonneTaylor,
Sometimes strange behavior may be caused by a plugin or theme conflict. The fastest way to rule out conflicts is to deactivate all non-Yoast plugins and switch to a standard theme like Twenty Fourteen. If this resolves the issue, you have a conflict and should activate one plugin at a time until you locate the conflict. Finally, after all plugins are active, switch to your theme. This will narrow down the conflict to a specific plugin or a theme conflict.
If you are unfamiliar with checking for conflicts, we wrote a small guide that will walk you through the steps. You can find it here: How To Check For Plugin Conflicts: http://kb.yoast.com/article/253-how-to-check-for-plugin-conflicts
Generally speaking, that is the fastest way to help you figure out whether the white space is coming from one of the plugins you use, one of the themes you use, or might – unfortunately – but in a human edited file such as your wp-config.
~ Kim ~
Support at Yoast