Rumejan
Forum Replies Created
-
I checked the source code of your site and compared the link preview result being shown in the Facebook debugger, both the title and description match.
Permalink – could include your domain
Slug – the piece of the URL that comes after the domainPlease refer to this kb article: https://kb.yoast.com/kb/google-shows-different-titles-for-my-site/
Have you configured the Twitter card to show the large image with the summary for the preview to appear while sharing the post? If you haven’t, please go to SEO > Social > Twitter(tab) and select the option “summary with large image”. Please refer to this Kb article for more details.
Hello,
Sorry to say we’re unable to assist you with that. Please refer to WPML support here.You mentioned that when you or other users log in with his/her credentials, everything is ok. This could just be a local issue. Have him/her use another browser or another machine and see if there’s any difference.
Sorry to say we’re unable to do the test for you. I suggest you run the conflict check as previously instructed.
I tested your site on Google here and it’s appearing correctly in the search results. This means that Google already indexed your site. Also tested your site in Google’s mobile friendly test here and Google was able to run the mobile friendly test for the domain. This means that Google can also spider the domain.
If the Facebook debugger returns a “More Than One OG URL Specified” error, that means, another plugin (aside from the Yoast plugin) or your theme, is generating another OG meta tags. Please try deactivating all of your plugins except the Yoast plugins and switch to a default theme like Twenty Seventeen. If the problem goes away, activate your plugins one at a time and check if the issue comes back for every plugin activated. Finally, after all plugins are active, switch to your theme and see if the problem recurs. This will narrow down the conflict to a specific plugin or your theme.
Hello,
Being able to find your site in the search result when searching for “Folha Camocim Blog” means that your site was crawled by Google. I also tested your site in Google’s mobile-friendly test here and Google was able to run the mobile friendly test for the domain. This means that Google can also spider the domain. In this case, the Ryte (formally OnPage.org) warning is just wrong.
You can deactivate and reactivate the Ryte feature directly from Yoast SEO -> Dashboard -> Features (tab) and fetch the index status again to see if this resolves the issue. If it’s still the same, we suggest three actions.
1. Ignore the issue. Your site is appearing on Google.
2. Deactivate the Ryte feature.
3. Contact Ryte here.The focus keyword not in first paragraph warning is often thrown out if there is an HTML element, code, image, or whitespace around the keyword which is affecting Yoast’s ability to scan for it. Can you please switch to classical or code view and inspect the post and check if there’s anything above the first paragraph?
Also, the Yoast SEO 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. 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.
Can you please confirm that the SEO and Readability are enabled on the posts? You can check by going to SEO->Titles and Metas->Post Type and the Yoast SEO Meta box should be marked as “show”.
Please also make sure you’re running the latest version of WordPress (4.9.1) and Yoast SEO (6.0).
Unfortunately, there’s really not much we can do if it’s a plugin conflict. We regularly update our plugins for continuous improvement and bug fixes but we just can’t have our plugin work with all other plugins out there.
Our usual suggestion with plugin conflicts is for you to use another plugin that won’t conflict. You may also contact the developer of the other plugin and have them work with our developers directly through this GitHub repository to find a solution that won’t conflict.
Can you please clear your browser’s cache and cookies then try it again? If it’s still the same, try another browser or another machine. Let us know what happens.
Hi Airat,
Check whether your theme’s header.php file contains a call to wp_head(). If it does, please run a conflict check to determine what’s blocking the meta description to show up on these pages.