Google site kit error

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support James Osborne

    (@jamesosborne)

    2 years ago

    Thanks for reaching out @biohisto. If you’d like to share the following, I’d be happy to look into this further:

    1. Your Site Health information. You can use this form to share privately if preferred.  
    2. When checking the Site Kit dashboard from a Chrome browser incognito window does the same occur? If so, please share any browser console errors that appear. 
    3. When you mention you always get this error, do you notice this on the main Site Kit dashboard on the Site Kit tab on the WordPress admin bar, or on your main WordPress dashboard?

    Once we have the above we can provide the most suitable troubleshooting suggestions. Let me know if you have any questions with the above.

    Thread Starter biohisto

    (@biohisto)

    2 years ago

    1. As You can see this, I actually also encounter an error like from the start when i created this site firstly I goes fine but after an worpress update came then it all started

    2. yeah I guess i encountered something like this a month ago but it solved after i deleted the plugin and reinstalled it . plus i do also have an extra error on google console the sitemap is good but google is not reading it, It last read on 9th may and I also have robots.txt error where i firstly use the rankmath but unfortunately it have also error so i moved on yoast then i do not found it good then i back to rankmath but the robots.txt file isn’t changing and it’s showing yoast block.

    User-agent: * Disallow: /wp-content/uploads/wpo-plugins-tables-list.json # START YOAST BLOCK # ————————— User-agent: * Disallow: Sitemap: https://biohisto.com/sitemap_index.xml # ————————— # END YOAST BLOCK

    3. i also use the cloudflare recently plus i have additional error like when i open the site it show’s 404 error and home page is not showing in google discover

    Thread Starter biohisto

    (@biohisto)

    2 years ago

    1. Debug mode is often enabled to gather more details about an error or site failure, but may contain sensitive information which should 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.

    The REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.

    2. When testing the REST API, an unexpected result was returned:

    REST API Endpoint: https://biohisto.com/wp-json/wp/v2/types/post?context=edit
    REST API Response: (404) Not Found

    3. The scheduled event, action_scheduler_run_queue, failed to run. Your site still works, but this may indicate that scheduling posts or automated updates may not work as intended.

    4.

    A persistent object cache makes your site’s database more efficient, resulting in faster load times because WordPress can retrieve your site’s content and settings much more quickly.Your hosting provider can tell you if a persistent object cache can be enabled on your site. Your host appears to support the following object caching services: Redis.

    5. Loopback requests are used to run scheduled events, and are also used by the built-in editors for themes and plugins to verify code stability.

    The loopback request returned an unexpected http status code, 404, it was not possible to determine if this will prevent features from working as expected.

    6. Unable to detect page cache due to possible loopback request problem. Please verify that the loopback request test is passing. Error: Forbidden (Code: http_403)

    Page cache enhances the speed and performance of your site by saving and serving static pages instead of calling for a page every time a user visits.

    Page cache is detected by looking for an active page cache plugin as well as making three requests to the homepage and looking for one or more of the following HTTP client caching response headers:cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.

    Plugin Support James Osborne

    (@jamesosborne)

    2 years ago

    Appreciate the update @biohisto. Apart from the loopback requests error above, I don’t see any issues that may be resulting in this error. To troubleshoot this further, if you’d like to share your Site Health information, and whether this error exists when checking the Site Kit dashboard from a Chrome browser incognito window we can hopefully determine more on this.

    If the same does occur from an incognito session, please share any browser console errors that appear. 

    Plugin Support James Osborne

    (@jamesosborne)

    2 years ago

    As we didn’t receive a response I’ll mark this as resolved. Feel free to open a new support topic if you continue to encounter issues, or reopen this topic and we’d be happy to assist.

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Google site kit error’ is closed to new replies.