You would love to see your artist's tour dates appear in Google's Knowledge Graph, like in these examples? The concert data already is present on Songkick? Then this web service is for you: it retrieves the event data of your artist from Songkick and returns JSON-LD data ready for you to include in the website of your artist. Google will find this data and eventually display it in their Knowledge Graph.
Background: JSON-LD became an official web standard in January 2014. In March 2014, Google announced support for displaying concert information in their Knowledge Graph for certain artists, supporting the new JSON-LD linked data format. In order to communicate this data to Google, a special JSON-LD data structure needs to be crafted and put it into the artist website, as described here. Eventually, the artist website needs to contain this markup:
<script type="application/ld+json"> [ ... JSON-LD event data ... ] </script>My service provides the
[ ... JSON-LD event data ... ]part. Putting this part into the artist website does not change its visual appearance. Eventually Google discovers this meta data and lists the upcoming events in the Knowledge Graph (I have observed this to take about 2 days). All you need is a specialized service URL to retrieve JSON-LD data for your artist, and then manually or dynamically include this data into your website. Pretty simple.
With the form below, you can generate a service URL for your artist of choice. Using this URL you can at any given time retrieve the JSON-LD data representing the upcoming events.
All form fields are required. The artist website and artist name fields end up in the resulting JSON-LD output, without change. That is, these fields override whatever information is present in Songkick's database. That way, you can precisely control which artist name and website URL are about to appear in the Knowledge Graph.
This web service makes use of aggressive caching and is hosted on a reliable platform. Hence, you could include this data dynamically, from within your web application. In that case, I would recommend performing some caching on your end, too, and query this service only once per day or so, for two reasons: i) event data is unlikely to change more frequently and ii) you surely do not want to increase the load time of all of your page requests.