Title: search console error Last modified: January 2, 2025 --- # search console error * Resolved [ali1010](https://wordpress.org/support/users/ali1010/) * (@ali1010) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/) * Hello, unfortunately, we are experiencing errors on the website and Google Webmaster. Will this bug be resolved soon? * CSS syntax error in tag ‘style amp-custom’. * AMP pages with this issue are invalid. Invalid AMP pages aren’t served on Google * Cannot read properties of undefined (reading ‘prevOffset’)detailTypeError: Cannot read properties of undefined (reading ‘prevOffset’) at jM ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:8:4990](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:8:4990)) at PM ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:8:5783](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:8:5783)) at eO ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:26:1053](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:26:1053)) at Ap ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:355134](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:355134)) at Lc ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:414075](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:414075)) at ma ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403327](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403327)) at qa ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403255](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403255)) at Aa ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403118](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:403118)) at pa ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:399953](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:399953)) at ba ([https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:398509](https://parswebserver.com/wp-content/plugins/amp/assets/js/amp-settings.js?ver=b567fc663892cfaf251e:1:398509)) Viewing 5 replies - 1 through 5 (of 5 total) * Plugin Support [Milind More](https://wordpress.org/support/users/milindmore22/) * (@milindmore22) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18222276) * Hello [@ali1010](https://wordpress.org/support/users/ali1010/) * Thank you for reaching out to us. When we checked your website’s AMP page, we found out that you are using AMP plugin in Reader Mode. Also, we didn’t encounter any issues with the AMP page. We also tested your AMP pages on [AMP test](https://search.google.com/test/amp/result?id=Rzvvs-YUDqHpH34Ve0J76A), which didn’t report any errors. * If you were on different template mode before (Transitional or Standard) the error might be from the old settings and will clear over time. * We also noticed that you are using Elementor editor, which is not AMP compatible, so we will recommend adding the [AMP enhancer](https://wordpress.org/plugins/amp-enhancer/) plugin which fixes some compatibility issues with AMP. * We hope this helps! * Thread Starter [ali1010](https://wordpress.org/support/users/ali1010/) * (@ali1010) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18222438) * Thank you for your response. I understand that you are on holiday, and I apologize for disturbing you.Merry Christmas! * I am experiencing an error in the admin panel and cannot access the settings. Please review the attached image. * ![](https://i0.wp.com/parswebserver.com/wp-content/uploads/2025/01/Screenshot- 2025-01-02-at-17.39.05.png?ssl=1) * Thread Starter [ali1010](https://wordpress.org/support/users/ali1010/) * (@ali1010) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18222449) * This is the response from Google Search Console during the error fix. * ![](https://i0.wp.com/parswebserver.com/wp-content/uploads/2025/01/Screenshot- 2025-01-02-at-17.46.40.png?ssl=1) * Plugin Support [Milind More](https://wordpress.org/support/users/milindmore22/) * (@milindmore22) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18222494) * Hello [@ali1010](https://wordpress.org/support/users/ali1010/) * Thank you for contacting us. * The first issue you’re encountering with the AMP plugin settings appears to be caused by a conflict with the Litespeed plugin. It seems the Litespeed plugin is adding comments to the JSON response, which can interfere with the AMP plugin’s functionality. * To resolve this, please try adding the following code snippet to your active theme’s functions.php file or within a custom plugin: * `add_filter( 'litespeed_comment', '__return_false' );` * This code snippet should disable the Litespeed plugin’s comments in the JSON response. * The second issue you mentioned, the error in Google Search Console, seems to be related to an invalid CSS rule being added to your website. This CSS rule includes a browser-specific path for the background image: * `
` * The AMP validator of Google Search Console requires that background images have a valid URL with the `https://` or `http://` protocol. Since this CSS rule uses a `moz-extension://` path, it’s considered invalid, leading to AMP errors. * To fix this issue, you’ll need to locate and remove this CSS rule from your website. This might involve inspecting your theme’s files, checking for any active plugins that might be adding this code, or using a browser developer tool to identify the source of this CSS rule. * We hope this information helps! * Plugin Support [Milind More](https://wordpress.org/support/users/milindmore22/) * (@milindmore22) * [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18240109) * [@ali1010](https://wordpress.org/support/users/ali1010/) As we didn’t receive a response I’ll mark this as resolved. Feel free to open a [new support topic](https://wordpress.org/support/plugin/amp/#new-post) if you require any further assistance. Viewing 5 replies - 1 through 5 (of 5 total) The topic ‘search console error’ is closed to new replies. * ![](https://ps.w.org/amp/assets/icon.svg?rev=2527602) * [AMP](https://wordpress.org/plugins/amp/) * [Frequently Asked Questions](https://wordpress.org/plugins/amp/#faq) * [Support Threads](https://wordpress.org/support/plugin/amp/) * [Active Topics](https://wordpress.org/support/plugin/amp/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/amp/unresolved/) * [Reviews](https://wordpress.org/support/plugin/amp/reviews/) * 5 replies * 2 participants * Last reply from: [Milind More](https://wordpress.org/support/users/milindmore22/) * Last activity: [1 year, 3 months ago](https://wordpress.org/support/topic/search-console-error-12/#post-18240109) * Status: resolved