Click into Venue Settings > Integrations.

You are able to embed the booking page into your website. Popular website providers like Wordpress, Squarespace are supported. The only requirement is that you have the ability to insert HTML "iframe" markup into your page source.
To get the markup that you need to use, just head to Venue Settings > Integrations, and look under General Integrations.
The first option is code for a simple "Book now" link on your website. This link opens Skedda in a full/new tab. The second option is the 'Embedded Scheduler' option, which displays the full scheduler within your own website.  
In both cases, click "Show code" to the required HTML you can insert into the page source of your own website. Note that the link includes an "embedded" query parameter which additionally hides the normal navigation bar from the embedded view. You're free to remove the "embedded" parameter if you do wish to have the navigation bar also show up.

If you're using Skedda for free, you'll also see some attribution information/requirements (we ask that you kindly respect these).

View-specific links

You also have the ability to tune your website-embedding code to correspond to a particular 'View'.  More information on Views can be found here.

For example, you might have one page on your website that explains your "Rooms", and another that explains your "Studios". With this feature, you can embed one scheduler on each page, one with the "Rooms" code and another with the "Studios" code.

Some notes on security and the mobile user-experience

  • If your own website is not cleanly-optimized for mobile usage, we strongly recommend that you take the simple approach (i.e. the basic link which opens Skedda in a new tab). An embedded scheduler on a webpage with poor mobile optimization leads to a poor experience for users on mobile devices.
  • If your website does not use HTTPS (with a valid SSL certificate), we generally recommend to take the simple approach (i.e. the basic link which opens Skedda in a new tab). The primary reason for our recommendation is that your users might get concerned when looking at their browser address bar (showing your insecure website URL) during the booking process and think that their data-entry and personal details are open to eavesdropping. This is particularly relevant when taking online payments for bookings.

Did this answer your question?