Viewing 10 replies - 1 through 10 (of 10 total)
  • Suwash

    (@suascat_wp)

    @vevanegas

    We understand Google Search Console is showing an error for the sitemap.

    We looked at the sitemap index https://myeatingright.com/sitemap_index.xml on your site and we see the following line of code at the bottom of the sitemap source on there.

    <b>Deprecated</b>: Directive ‘allow_url_include’ is deprecated in <b>Unknown</b> on line <b>0</b><br />

    It looks like something on your site is interfering with the Yoast SEO generated XML sitemap and as such, there’s a deprecation notice outputting on there. So, to find out the exact cause of this, we’d like you to please perform a conflict check first. This will help us narrow down the exact cause and determine what the next steps are while saving you time.

    Just to be sure, we would like to rule out any plugin or theme conflicts that may occur. The fastest way to do this is to?deactivate all non-Yoast plugins and switch to a standard theme?like?Twenty Nineteen.?

    Test this on your development or staging site, if you have one. If not, we recommend using the?Health Check & Troubleshooting?plugin. This plugin allows you to run a conflict check?without affecting normal visitors to your site.

    As we can imagine that you’re unfamiliar with checking for conflicts, we’d like to point you to a step-by-step guide that will walk you through the process:?How to check for plugin conflicts.

    Let us know the results.

    Thread Starter vevanegas

    (@vevanegas)

    Hello Suwash Kunwar :

    I think I know where the problem originates.

    My website reported a security critical issue, stating “site is set to display errors to visitors”. It also reported “The REST API does not process the context query parameter correctly”.

    Let me elaborate on the first critical issue.”Debug mode is often enable to gather more details about an error or site failure, but may contain sensitive information which would not be available on a publicly available website. The value WP_DEBUG_ DISPLAY has either been enabled by WP_DEBUG or added to your configuration file. This will make errors display on the front end of your site”

    Could this has been the culprit?

    In any case it has now been fixed. The second one remains.

    Please let me have your thoughts on this one

    Suwash

    (@suascat_wp)

    @vevanegas It’s a likely cause that you’ve enabled the debug mode as such error got displayed on the source and eventually Google unable to parse the sitemap. We recommend you disable it soon after you finish the troubleshooting.

    Regarding REST API, some host providers may restrict the amount of REST API calls made. You may need to verify with your host that no restrictions are in place.

    Thread Starter vevanegas

    (@vevanegas)

    Hello Suwash Kunwar :
    Thank you again for your prompt response.

    As I mentioned earlier, I did not proceed to perform a conflict check because the critical security issue causing Google to show errors for the sitemap has been fixed by my web host.

    Are you in agreement? Has my site stop interfering with Yoast SEO generated XML sitemap? Could you please check this out?

    Looking forward to your reply.

    Ps. I wasn’t notified via email of this reply. Please make sure you do this time around

    Plugin Support Michael Ti?a

    (@mikes41720)

    Hi @vevanegas

    If you want to make sure you receive notifications from replies on this forum thread, please do make sure that you are subscribed by clicking on the ‘subscribe’ button on the side of this forum thread.

    We tried to check your website https://www.myeatingright.com/ and it’s still displaying the error (Deprecated: Directive ‘allow_url_include’ is deprecated in Unknown on line 0) on the front-end as well as in the source code of the sitemap https://www.myeatingright.com/sitemap_index.xml.

    We recommend you check the set-up of your website to ensure that the errors don’t display on the front-end of your website. Once this has been resolved, we would expect that resubmitting the sitemap to Google Search Console would result in the sitemap being read and processed as expected — https://yoast.com/help/submit-sitemap-search-engines/#google-remove

    Thread Starter vevanegas

    (@vevanegas)

    Hi Michael Tina:

    Thank you for your advice.

    I went back to my web host and assured me they disabled the display error in php.ini. Now, they say, my site is no longer showing that error message.

    Regarding REST API issue, web host disabled the error on my site and added this code in my config file: define (‘WP_DEBUG’, false).

    My question now is do I resubmit the sitemap (https://www.myeatingright.com/sitemap_index.xml.) to Google Search Console?

    Looking forward to your comments.

    Best regards,
    Enrique Vanegas

    Plugin Support devnihil

    (@devnihil)

    @vevanegas Thanks for your reply.

    We rechecked your site’s sitemap and were able to confirm that the ‘Deprecated: Directive ‘allow_url_include’ is deprecated in Unknown’ error is no longer displaying and the sitemap does appear to be output correctly now (see image here).

    In addition we checked the XML sitemap in a validator and confirmed that no issues were detected.

    Regarding Google Search Console, yes, at this time we would recommend resubmitting the sitemap to Google to verify that it is now able to crawl it as expected.

    Thread Starter vevanegas

    (@vevanegas)

    Hi Devnihil:
    Thank you for your prompt reply.
    What of these two following sitemaps do I resubmit to Google Search Console: (a) or (b)?:
    (a) https://www.myeatingright.com/sitemap.xml
    (b) https://www.myeatingright.com/sitemap_index.xml

    Thank you.

    Best regards,
    Enrique Vanegas

    Pcosta88

    (@pcosta88)

    Hi Enrique!

    You should submit the sitemap_index.xml version to Google.

    Thread Starter vevanegas

    (@vevanegas)

    Thank you Pcosta88!

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Submitted sitemap reports 3 errors’ is closed to new replies.