Rich Snippet / Event Markup error from Google Search Console team

Hey @paulscurrah @12thkey @mrfix3 @angkorgolf ,

This article really helps! https://www.marksmen.studio/blog/fix-issues-squarespace-schema-markup

Same problem, very interested in a fix.

I also am seeing this issue, tried adding Google Calendar links to the Events page via the Styles and that doesn't make any difference.

I have the same issue, even i try to overwrite the structure data....anyone has solution?

I have the same issue. I have read the marksmen.studio blog about a solution, but these solutions are manual and require ongoing evaluation and work. I've gone through the data highlighter steps myself but Google still reports the pages with errors.

It would be nice if SquareSpace could just update their code to provide the startDate and location.

Agreed - it’s very simple, obvious and repeated data (surely?) so why SS hasn’t catered for it I don’t know.

Has anyone found a solution to this yet?

I've got 2 article schema errors with this web page: https://charlottewiseman.com/workplace-wellness-blog/what-is-mindfulness

Thanks!

I'm having a similar issue: six warnings in google search console on my squarespace site. i'm going to go into each warning, identify the content issue, and attempt to address within squarespace, and i'll report back with my results. 

update: wasn't able to address the specific warnings on my site. found this update on the google search console forums claiming it wasn't a big deal & wouldn't impact search performance. i'd still hope it's an update squarespace has in the works!

update 2: found a blog post explaining how to add custom code to address these warnings (won't work for me, as i'm on a cheap plan, but may work for you!)

2 hours ago, MTM_emi said:

update: wasn't able to address the specific warnings on my site. found this update on the google search console forums claiming it wasn't a big deal & wouldn't impact search performance. i'd still hope it's an update squarespace has in the works!

update 2: found a blog post explaining how to add custom code to address these warnings (won't work for me, as i'm on a cheap plan, but may work for you!)

Thanks @MTM_emi