Errors in GSC caused by smushing – when will fix be implemented?

  • Resolved zoes0702

    (@zoes0702)


    4 years, 11 months ago

    Hi there,

    Yesterday I upgraded to Smush pro but it’s resulted in the following AMP errors on GSC. https://prnt.sc/qgvfzj

    I asked the AMP team on this thread:
    https://www.ads-software.com/support/topic/getting-the-following-amp-error-on-google-search-console-details-below/

    They pointed me in the direction of it being a possible smush issue and suggested that you might be aware of this issue causing those pages to be affected, and those results now crashing in the SERPS as they have this issue.

    My question is, when will the issue be fixed? As I can’t afford that my most important blog article, to plummet in the rankings, is a workaround to deactivate smush, to turn off AMP sitewide, or to wait it out?

    If you have a fix that’s great, but I’d like to get this info ASAP as the fix will need to be manually validated on GSC before the page can rank again.

    Thanks in advance for your help.

    The page I need help with: [log in to see the link]

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

  • @zoes0702,

    The fix in the AMP thread will be available in the upcoming update. I’m not sure it’s the case, but you can just add /amp to the Smush lazy load exclusion list to force the fix.

    Best regards,
    Anton

    Thread Starter zoes0702

    (@zoes0702)

    @vanyukov Thank you! I have implemented the change and have started the validation process on GSC which in my experience can take a few days. Will report back if the issues persist. Thank you!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Errors in GSC caused by smushing – when will fix be implemented?’ is closed to new replies.