Posts
5
Questions
13
I am trying to upload an image on my WP editor. But i am constantly getting the error.
The uploaded file could not be moved to wp-content/uploads/2019/10.
Help a
See more comments
Am I stuck with this wp error?
I am trying to upload an image on my WP editor. But i am constantly getting the error.
The uploaded file could not be moved to wp-content/uploads/2019/10.
Help a
I've had this error before, on another Word press host. There, the site support fixet it. Something went astray with the PHP update. After that was fixed, all was well.
See more comments
Guys I have successfully been using the webmaster tools for some time now. But today, I've done a lot of changes to my site and I tried to submit my site maps on both google an
Hey Sidharthan,
Assuming you have verified for yourself that your sitemap actually works, it might be better to wait a few days and then try submitting your sitemap with Bing again, as they may be experiencing issues as Google's Analytics has been lately.
Hope you find this helpful.
Why am I unable to submit sitemap in bing webmaster tools?
Guys I have successfully been using the webmaster tools for some time now. But today, I've done a lot of changes to my site and I tried to submit my site maps on both google an
Hey Sidharthan,
Assuming you have verified for yourself that your sitemap actually works, it might be better to wait a few days and then try submitting your sitemap with Bing again, as they may be experiencing issues as Google's Analytics has been lately.
Hope you find this helpful.
Hello! I was checking through the training if I had missed anything and as it turns out I had forgotten to no index the privacy policy and when I check it on google webmasters,
Hi Sidharthan,
The information below comes directly from the training page.
Your Privacy Policy is duplicate content because it is a stand document. The reason you want to create this as a Page, not a Post is because Pages don't allow for comments. You don't want people commenting on your Privacy Policy,
After you publish your Privacy Policy, you are going to want to log into the back office of your website (Wordpress Admin area) through the SiteManager or through SiteContent.
When you are within the editor for this page, scroll down to the bottom of the page and you will see the following settings.
Check off the Robots Meta NOINDEX and the Robots Meta NOFOLLOW.
These will make sure this page (which is all duplicate content) does not get indexed in Google. The Privacy Policy is the ONLY page you want to do this for as it is duplicate content.
I hope this answers you question. Much success to you!
Kind regards,
Nichola
Privacy policy was indexed as well is that a problem?
Hello! I was checking through the training if I had missed anything and as it turns out I had forgotten to no index the privacy policy and when I check it on google webmasters,
Hi Sidharthan,
The information below comes directly from the training page.
Your Privacy Policy is duplicate content because it is a stand document. The reason you want to create this as a Page, not a Post is because Pages don't allow for comments. You don't want people commenting on your Privacy Policy,
After you publish your Privacy Policy, you are going to want to log into the back office of your website (Wordpress Admin area) through the SiteManager or through SiteContent.
When you are within the editor for this page, scroll down to the bottom of the page and you will see the following settings.
Check off the Robots Meta NOINDEX and the Robots Meta NOFOLLOW.
These will make sure this page (which is all duplicate content) does not get indexed in Google. The Privacy Policy is the ONLY page you want to do this for as it is duplicate content.
I hope this answers you question. Much success to you!
Kind regards,
Nichola
I've had this error before, on another Word press host. There, the site support fixet it. Something went astray with the PHP update. After that was fixed, all was well.
Yes! I did too today! But site support helped me out, now I'm good to go with my posts! :)
I'm glad to hear it's fixed.!