Home/Guides/OBS and output

Embed the scorebug on your website

Put a live scorebug on your school or club website with a copy-and-paste iframe from the public match page. It keeps itself up to date during the game.

Updated 3 min readFree

Your school or club website already gets traffic on game day. A live scorebug on the home page or the team page lets visitors see the score without leaving. ScoreCastr makes one for every match, as a small iframe you paste into the page. This guide covers getting the code, choosing a size, and what to expect once it's live.

Short versionOpen the match's public page with Share Match, go to the Share tab and click Embed This Match. Pick a size and a background, click Copy Embed Code, and paste it into an HTML or embed block on your site.

Get the embed code

  1. On the match's Control Dashboard, click Share Match in the sidebar. The public match page opens in a new tab. See Share the public match page.
  2. Open the Share tab on that page.
  3. Click Embed This Match. The Embed Scorebug card opens.
  4. Pick a size and a background (below). The code underneath updates as you choose.
  5. Click Copy Embed Code. The button changes to Copied! and you'll see "Embed code copied!".

Embedding comes with every plan, including Free, and anyone with the public page can get the code. The scorebug link inside the code is /embed/scorebug/ followed by the match number.

Pick a size

Size Width by height
Small 400 by 100
Medium (the default) 600 by 150
Large 800 by 200
Custom Your own Width (px) and Height (px)

Pick the size closest to the space on your page, then adjust with Custom if you need to. The iframe never grows wider than the space it's in, so on a phone it narrows to fit the screen. Its height stays the same.

Soccer, baseball and softball embeds reserve extra room below the bar. If the bottom is cut off, switch to Custom and add height: start around 180 for soccer and 260 for baseball and softball.

Background on or off

Next to the copy button, Background has two choices:

  • On puts a dark panel behind the scorebug. It reads well on any page.
  • Off makes the area around the scorebug see-through, so your page's own background shows. This adds ?bg=false to the link in the code.

Choose Off when the scorebug sits on a dark banner or header. Choose On for a white page, where a light background would leave the scorebug floating.

Add it to your site

Paste the code into a block that accepts HTML. Most site builders have one, called something like Custom HTML, Code or Embed. Save, then view the published page, not just the editor preview, since some editors don't run iframes.

Some school website platforms block iframes or strip them out. If the block shows nothing after publishing, ask whoever manages the site whether embeds are allowed.

How it updates

The embedded scorebug checks for a new score every 3 seconds, so it trails the broadcast by a few seconds at most. Visitors don't need to refresh. It keeps checking as long as the page is open, even in a background tab.

A few things to know:

  • It always uses the Classic scorebug design, whichever template your broadcast uses.
  • It shows whether or not the scorebug is on air. Hiding the scorebug, or going to break, doesn't hide the embed.
  • It shows the final score after the match is over, so you can leave it up after the game.

One code per match

Each match has its own embed code. For next week's game, create the match, then copy new code and replace the old one. If you delete a match, its embed stops showing a score. To restart the same game instead, use Reset Match: the code keeps working with the fresh score. See Reset or delete a match.

TipRunning several games at once? Put one embed per match on a scores page, each with its own heading. See [Run several matches at once](/guides/multiple-matches).

Checklist

  • Embed code copied from Embed This Match on the public page
  • Size picked, Custom height added if the bottom was cut off
  • Background on or off to suit your page
  • Code pasted into an HTML or embed block and checked on the live page
  • Code replaced with the new match's code before the next game