Rumejan Barbarona

We don’t have any recommendations. If the plugin isn’t causing any issues with how Yoast SEO works, you can just disregard the warning. Otherwise, you can try some other plugins that do the same and won’t cause such warning. There’s quite a lot of them here.

v.2 looks just as v.1 is – with square thumbnail to the left of the text. Please refer to this link.

Please refer to this Kb article: https://kb.yoast.com/kb/yoast-wordpress-seo-titles-metas-template-variables/

If you’re still unable to log in, access your site via FTP and look for the .htaccess file. Rename that file to something else. If that’s the file that caused the issue, you should be able to log in after renaming that. You may need to check the contents of your .htaccess file to see if there are invalid redirects. You need to fix them.

The Yoast plugin only analyses the default WordPress content areas. It will not recognize texts in custom fields or other plugin/theme content boxes as well as those contained in widgets. In your case, widgets can be used on any page, and on multiple pages, so there’s no way for our plugin to know where the content is. This doesn’t mean though that Google won’t be able to crawl them. Google will still crawl them it’s just that our plugin isn’t capable of analyzing them.

If you go to your posts or pages list, there’s a column there that says “Focus KW”. If you don’t have that, go to “Screen Options” and see if “Focus KW” is checked.

You go to “Add Media” when you add an image, video or audio. You don’t go to “Add Media” if you’re trying to add an internal link.

Please make sure you’re running the latest version of WordPress (4.8) and the latest version of your theme. Also, we’ve seen similar issues reported by other users and it turned out that certain browser extensions and versions are causing the issue. Can you also try using another browser like Chrome or Edge?

There are various reasons why Google does that. Please refer to this link.

Looks like the Yoast plugin is in conflict with something. Have you tried running a conflict check?

Hi Gav,
No, you can’t. You need another plugin for that. Unfortunately, can’t recommend as I’m not familiar with a plugin for that purpose.

@esmi, yes I followed the Relocate Method.

@ben, haven’t looked into that but now that you mentioned it, will take a look.

Oh.. so it was cached in the browser. Thanks a lot Esmi!

Below is menu in style.css:

[CSS moderated as per the Forum Rules. Please just post a link to your site.]

it works! there’s this “redirection” plugin that I deactivated and that took away the /168/:. Thanks govpatel! more power to you..