-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
We have already added JSON-LD data to a couple of pages. This is a blob of Json data that describes the current page/content/entity in a way that is easy for Google (and others) to understand and allows them to show them in a custom ways/locations in search. Ex. if we create JSON-LD for a product, Google could (at least in theory) decide to show this product in their product search section, and not just as regular page in search.
Useful links
- What the data might look like for events
- Tool to validate JSON-LD data on html page (the "code" variant is super useful when developing locally)
What we want
- Expose a single event on a specific url so that Google can find and parse it (They don't support/recommend multiple events per page)
- We could do this by creating a new
/schedule/[id]
page dedicated to a single event - ...or perhaps by allowing a
/scheduled?event=id
argument to pin/highlight a specific event as part of regular calendar view
- We could do this by creating a new
- Add as much JSON-LD Event data as possible (but some validation warnings, and skipping data it will be hard for us to manually produce, are absolutely fine)
- A nice way to link from an event to this detailed or pinned view, so that it
- Is something search engines can follow, and know is also theoretically available to users
- Users can share this link with friends if they want to
Metadata
Metadata
Assignees
Labels
No labels
Type
Projects
Status
Ideas / Inbox