AskKim

Hi rimoreno,

If the developer of that plugin wants to be in touch, they are welcome to open a report on our Github at https://github.com/Yoast to discuss getting this solved.

Unfortunately, there are hundreds of thousands of plugins today and sometimes conflicts can and do happen.

~ Kim ~
Support at Yoast

There are a number of problems that can cause this same issue.

1. You first need to add your site as a property to Google Search Console (formerly known as Google Webmaster Tools). This ensures the profile that we want to connect too exists and gets verified.

https://support.google.com/webmasters/answer/34592?hl=en

http://kb.yoast.com/article/164-how-to-connect-your-website-to-google-webmaster-tools

2. If your property is already correctly entered, but the BUTTON will not work, it is likely a browser issue. Please try a different browser.

3. You can improve the odds of the connection happening correctly if you log into Google Search Console BEFORE attempting to make the connection. This avoids several problems.

4. If the WRONG profile has gotten attached – it may be very challenging to get the RIGHT property profile attached if you have not taken these steps to manually clear the GSC code: http://kb.yoast.com/article/136-how-can-i-reset-the-auth-code-for-webmaster-tools

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 Yoast

Hi jbattams,

Welcome to the world of WordPress… there’s nothing wrong with this question at all as it’s actually not all that intuitive.

Outside of the templates – which are all in the area we call the “plugin settings”… each page/post/etc of the website has its own page (or post) within the site, and the home page is no different.

In you WordPress dashboard, in the left-hand menu, go to Settings and then select “Reading”.

You will see settings that look somewhat like this: http://screencast.com/t/YCpHHwKn

If yours is set for “static page” now you will now the name of the home page. If it’s set for “latest post” your home page may STILL be named that but it may not be either.

(In this example, the home page is literally named “Home”.)

Once you know that… go into your PAGES section (in your left side bar) and locate the page by that name.

Open up the page editor for that page and scroll down until you find our Yoast SEO box.

Now, there, is will you will fill out all the SEO details for this page.

~ Kim ~
Support at Yoast

Hi Overcranked and tabasco86,

If you are both using Divi theme, and that is the origin of those terms, then what you want to look at is this:

http://kb.yoast.com/article/299-how-to-customize-the-sitemap-index#exclude_taxonomy

There is a code block on that page that you will put into your theme’s functions.php file.

For each one of the problematic, three, terms, you would replace “taxonomy_slug’ with the term such as layout_type

When editing PHP, always be sure to make a backup before you proceed, as a single error or typo can temporarily take your site offline.

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 Yoast

Hi MissJaki,

Are you specifying particular images for Facebook, Twitter, and Google+, including paying attention to the recommended image sizes, in the social tab of our plugin in the editor page when you create the post/page?

~ Kim ~
Support at Yoast

Nile has the correct answer here. (I’m simply replying so I can close this ticket as it seems solved.)

~ Kim ~
Support at Yoast

This is a list of the custom values available: http://kb.yoast.com/article/146-yoast-wordpress-seo-titles-metas-template-variables

You may possibly be able to do that with a custom field value:

%%cf_<custom-field-name>%% Replaced with a posts custom field value

~ Kim ~
Support at Yoast

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

~ Kim ~
Support at Yoast