Google has added a new set of event markup filters under the search appearance in Google Search Console performance reports.
The new filter lets site owners filter data by event listings and event details to see how often their event listing posted on their website appear in the Google Search results.
“With these additional filters, you can break out just event listings or event detail pages,” Google stated in the help document.
An image overview of the new event filters showing in the search appearance option:
In order to show an event happening at a certain time and location, like a concert, lecture, or festival, users need to use the event markup on their event landing pages.
Once the markup is added on the events page, then Google may show richer search results for those events.
An example of how event listing may show up in Google search:
In the picture above, on the left is an initial short list view, while on the right is a details view. A Google help document explaining the difference between ‘event listings’ and ‘event details’ said,
“Some rich result types have two search result views: a list view and a details view. The initial search result is a list containing the top results, with minimal information about each. The user can either expand the list to show more list items or click a specific result in the list to open a details view with more information about the selected item.”
The Search Console will then track the data, a user will then see click, impression, position data, and the URL of the provider in both List view and Details view.
Here is how Search Console records list view data:
- Click: Counts a click when an item in is clicked in the list view for provider shown in the list item.
- Impression: Counted when a list item is visible in the short list view, and when the list view is expanded.
- Position: When a list item is viewed in the short list view, all visible items are assigned a single position. When the list is expanded and scrollable, each item is assigned a position according to where it appears in the list.
Here is how details view data is recorded in Search Console:
- Click: Clicking a details item counts as a click for the provider selected in the details view.
- Impression: An impression is counted when a user lands on the details view, whether they clicked on it or followed a direct link.
- Position: For a details view, the position is always 1.
Google also has started sending out notices to webmasters whose web pages are loading slow via Search Console.
Google has a new Speed update which is aimed at reducing the search rankings of really slow mobile pages.
This notice references how slow specific pages are on the website referencing the measurement data from the Chrome User Experience Report.
Here is a screenshot of GSC notice shared by Oliver H.G. Mason on Twitter:
As shown in the picture above, the message specifically mentions the following metrics that Google’s’ Chrome team has been experimenting:
- First Contentful Paint: The point immediately after navigation when a browser renders pixels to the screen.
- Time to Interactive: The time at which a page is visually rendered and can reliably responding to user input.
- First Input Delay: The time when a user first interacts with a site, to the time when a browser is able to respond to that interaction.
Through the warning, Google also is offering recommendations to fix the issue, including:
- Use Lighthouse to audit pages
- Fix low performing pages
- Update your sitemap
In another webmaster related news, Google has released a new SEO help document that aims to help webmasters make sure their lazy-loading image and video content can be crawled, indexed and ranked in the Google Search.
“Deferring loading of non-critical or non-visible content, also commonly known as ‘lazy loading’.”
After setting up the implementation, webmasters can make use of a “Puppeteer” script to locally test their implementation of lazy-loading works correctly.
Google provides the Puppeteer script and it needed Node.js to run.
The new document can be found in the Google developer guides over here.
Google recently sent out tweets to let know site owners about the delay in some reports in Search Console, while also noting that the delay will not affect search results.
According to Google, the following reports were delayed due to issues in the reporting pipeline, “AMP, Rich Results/Structured Data, Hreflang, Index Coverage, and Mobile Usability.”
“Some Search Console reports are now a bit more delayed due to issues in the reporting pipeline (AMP, Rich Results / Structured Data, Hreflang, Index Coverage, & Mobile Usability). This doesn’t affect your site in search. We’ll let you know when things are back up to speed!,” tweeted Google Webmasters.