MariusG
Forum Replies Created
-
Hi @kevs23,
Unfortunately, WordPress does not create these redirects automatically and it cannot be done using Yoast SEO either. The feature which automatically creates redirect from the old slug to the new one is part of Yoast SEO Premium.
Alternatively, you can manually create a 301 redirect as in this guide.
Hi @insideril,
Are you referring to the plain permalink structure
?p=123? If so, then you will not be able to use the XML Sitemaps of Yoast SEO.Hi Jeen,
The robots.txt file should always be in the root domain. If you add it in subdirectories (corresponding to each language), those robots.txt files will get ignored by the search engines.
You can create/edit the robots.txt file using Yoast SEO by following this guide.
Forum: Plugins
In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] {“..Hi Craig,
Are you using the latest version of Yoast SEO, 8.1.2? If you’re using an older version, please update and let us know if the issue persists. If it does, please include a link to your website so we may further investigate it.
We are looking forward to hearing from you.
Hi @danniee,
Content that is not visible (such as your hidden H1) tag is usually ignored by the search engines. That being said, the additional hidden H1 tag is not doing anything in terms of SEO.
Hi @demente1987,
Can you send us a screenshot of how your URL looks when being shared on Facebook? I’ve just tried sharing your URL (image here) and the title and description match the ones generated by Yoast SEO:
<meta property="og:title" content="AntofaDatos" /> <meta property="og:description" content="Portal de Anuncios Clasificados & de Informacion,con Blog Informativo,Chat y Musica las 24 Horas!!! Todo esto y Mucho mas en un Solo Lugar. Facil y Rapido!!" />We are looking forward to hearing from you.
Hi @folgerj,
Please note that Facebook is caching URLs which have been previously posted. This means they will not check your URLs for changes until their cache expires, even though you may have made the correct changes in Yoast SEO.
n order to force Facebook to clear the cache of a URL, please submit it to their Sharing Debugger and click the Scrape Again button several times. After you have done this, you can try sharing your URL on Facebook again and it should show the updated Open Graph tags.
We went ahead and rescraped your URL, the current image shown when displaying your URL on Facebook is this one. Does this match the image you have set with Yoast SEO?
We are looking forward to your reply.
“Cleaning” errors in Google Search Console (marking them as fixed) does not actually change anything in terms of SEO, that list is there to help you find issues which you might have missed. Whether you mark them as fixed or not has no effect, what matters is to actually fix the issues, which the Search Index Purge plugin is currently doing.
When did you install the Search Index Purge plugin? We have inspected your website and no attachment pages seem to be indexed anymore, meaning you can now remove the Search Index Purge plugin (and new crawl errors about attachment pages should stop showing up in Search Console).
We hope to have cleared things up for you and please don’t hesitate to let us know if you have any further questions.
Hi @bertvangoo,
Thank you for getting back to us.The xmlrpc.php file is unrelated, it’s possible that a security plugin changed the permissions on that file. Are you sure there is no existing file in the root folder of your website called sitemap_index.xml? If so, please try enabling and disabling the XML Sitemap feature by going to SEO → General → Features in your WordPress dashboard.
Does this fix your issue?
Hi @tizeta,
Where exactly are you getting the website seen as insecure? This snippet
prefix="og: http://ogp.me/ns#"should not influence whether a website is secure or not.Using HTTPS, in this case, would be incorrect, as
https://ogp.me/ns#does not have an SSL. There is no secure version of this URL.We are looking forward to hearing from you.
@sarkove and @bdempleos, please send us screenshots that reflect the issue, so that we may better understand what’s causing it and how it might be fixed. In addition, can you confirm that the issue persists when Yoast SEO is the only plugin active on your website?
We are looking forward to hearing from you.
Thank you for getting back to us.
Posts with a rel canonical tag will not be shown in the sitemap, as they are not indexable. For example, this post does not show up in the XML Sitemap.
If you check the source of that URL, you can notice the following tag:
<link rel="canonical" href="https://www.cubix.co/blog/customer-centric-app-focus-ui-ux/" />Notice the /blog/ part, it is a different URL. We believe you might have manually set canonical tags to your posts, which are now outdated and thus they are preventing the posts from being indexed. Please refer to this guide to set/remove canonical tags from your posts. It is safe to leave the canonical tag field empty, it will point to the current post’s URL automatically.
We hope to have cleared things up for you and please don’t hesitate to let us know if you have any further questions.
Please go to Users → Your Profile and check if this box is checked when editing the user where you are experiencing this issue.
Have you fixed the issue in the meantime? I’ve checked your XML Sitemap multiple times, from multiple browsers and could never experience the issue which you have mentioned.
Can you try and gather as much information for us as possible? Please perform the following:
1 Check for conflicts.
2 Check for JavaScript errors with your console.If you find any JavaScript errors related to Yoast SEO or if there is a conflict with a plugin or a theme, you can create a new GitHub issue for our developers.