Editing Events

Seminole Theatre ★ Staff Reference
Editing Events · Revised July 2026

A working guide

Every field, every spec, in the order you’ll fill them.

This is the reference for adding and editing events on seminoletheatre.org. It is written for a working staff member with the browser open — each step maps to a specific spot in the admin, with the exact size, format, and word count you need. Keep this bookmarked.

Admin URL   seminoletheatre.org/wp-admin/
Sign in as   info@seminoletheatre.org

Video walkthrough

Prefer to watch instead of read? This walkthrough covers the whole guide, start to finish.

01

Signing in

Open the site’s admin dashboard. Everything you’ll do lives there.

Go to seminoletheatre.org/wp-admin/. Sign in with:

  • Username: info@seminoletheatre.org
  • Password: (kept in the theatre’s password manager — ask if you don’t have it)

If the password isn’t working, use the Lost your password? link on the login screen. A reset email lands at info@seminoletheatre.org within a minute. Do not share the login with vendors; if a designer or promoter needs access, request a separate account through the site administrator.

Never do this

Do not edit code, plugins, or the theme through the admin. If a “There is a new version available” notice appears at the top of the screen, ignore it — the site administrator handles updates on a schedule.

02

Creating an event

Events live under their own menu — not Posts, not Pages.

In the left sidebar, click Events → Add New. A blank event editor opens. This is where the entire show record lives: title, description, poster, date and time, ticket link, and the price that drives Google search.

Naming the event

The title is the show’s name, exactly as you want audiences to read it. Two rules that keep things clean:

  • Use title case (Opera Meets Zarzuela, not opera meets zarzuela).
  • For multi-date runs where each performance is a separate event, add the specific date at the end: Opera Meets Zarzuela — Aug 22. This makes the admin list and Google search results readable, and it makes each URL descriptive by default.
03

Every field, in order

Fill these top to bottom. Fields marked Required are not optional — the “Buy Tickets” button and Google search listing depend on them.

Field 01
Title

The show name. See the previous section for naming rules. Whatever you type here becomes the H1 on the event page and the label on every card that links to it.

Field 02
Description

The rich-text body directly below the title. Keep the first paragraph short and readable — it’s what Google shows in search results and what appears in the event card preview.

Structure the content clearly:

  • Opening paragraph: one or two sentences of context. Who is presenting the show, what it is.
  • About the Program: full description of what the audience will experience.
  • About the Producing Organization: history, mission, credits.
  • Rental disclaimer (when applicable): “This production is not presented or produced by the Seminole Theatre…” — copy from an existing rental event.

Why it matters: the first 160 characters populate the event’s meta description automatically if you don’t override it, and the whole body feeds the search-result snippet.

Field 03
Featured Image Required

In the right sidebar, under Featured Image → Set featured image. This is the poster that shows on the event page, on the homepage cards, on social shares, and in Google search results.

See Image specs for exact dimensions.

Why it matters: without a featured image, the event card renders blank on the homepage and the Google search preview has no thumbnail.

Field 04
When (Date & Time) Required

Scroll below the editor to the The Events Calendar section. Set:

  • Start Date & Time — the exact door-open-to-house time (usually 30 minutes before curtain). Most theatre teams put curtain time here.
  • End Date & Time — realistic end. If you don’t know, add 2 hours 15 minutes to the start (typical show + intermission).
  • Time Zone — always America/New York. Do not change.

Why it matters: the end date is what makes the event disappear from “upcoming” listings after it has happened. If it’s blank or wrong, the event lingers indefinitely.

Field 05
Where (Venue)

In the Location section, pick Seminole Theatre (Auditorium) from the dropdown for any main-stage show. If it’s in a rehearsal room or an off-site space, add a new venue with the full address.

Field 06
Event Website URL Required

In the Event Website field, paste the Tixr link (or Google Form link) for this exact performance. Example: https://www.tixr.com/groups/seminoletheatre/events/opera-meets-zarzuela-194624.

Why it matters: this is the single input that powers the branded call-to-action button on the event page, on every homepage card, and in Google’s event carousel. Leave this blank and the button never renders. Whether the button reads Buy Tickets, Register Now, or Learn More is controlled by the next field.

Field 07
CTA Button

Where to find it: in the right sidebar of the event editor, in a metabox labeled Event CTA Button. Single dropdown with four choices.

Pick the option that matches what the audience is doing at the other end of the link:

  • Auto (default) — the site reads “Buy Tickets” for Tixr URLs and “Register Now” for Google Forms URLs. Safe for standard shows.
  • Buy Tickets — forces the ticket icon and Buy Tickets label. Use for paid ticketed performances.
  • Register / Sign Up — forces the person-plus icon and Register Now label. Use for auditions, workshops, classes, free signups — any time the Tixr link is collecting information but not money.
  • Learn More — forces an info icon and Learn More label. Use when the URL just goes to a page with more information (no purchase, no signup).

Where the setting shows up: the button on the single event page, on the homepage Featured Shows and Current Shows cards, and — if you’ve also ticked Post to Google Business Profile — the Google Business Profile post’s CTA type (“Book”, “Sign up”, or “Learn more” on Google search).

Why it matters: auditions and free signups feel wrong when the button says “Buy Tickets” — patrons expect a checkout screen and paying to sign up. Picking Register / Sign Up matches audience expectations and also tells Google to show the right button on the theatre’s Google Business Profile.

Field 08
Event Cost Required

In the Cost field, enter the ticket price. Formats accepted:

  • A number: 30 — the site displays it as $30.
  • A range: 25 - 50 — displayed as $25–$50.
  • The word Free — displayed as Free.

Do not put “$” here yourself; the site adds it.

Why it matters: this feeds Google’s event rich results AND how AI assistants (ChatGPT, Google Gemini, Perplexity) answer questions like “how much are tickets to X at Seminole Theatre.” Without a price: no “Things to do” carousel placement, no ticket badge in search, AI assistants say “price not listed” — every one of those costs organic reach. Fill the Cost field on every event, no exceptions.

Field 09
Category

In the right sidebar under Event Categories, tick Seminole Theatre Calendar for standard shows. Use additional categories (Concert, Theatre, Family, Comedy, Dance) if they help patrons filter — but always include Seminole Theatre Calendar.

Field 10
Featured Event

Where to find it: in the right sidebar of the event editor, in a metabox labeled Featured Event. It’s a single checkbox: Feature Event.

What ticking it does: the event appears in the Featured Shows section on the homepage (top of the page, above the fold) with its poster, date, and Buy Tickets button. Featured events also get priority placement in the site’s schema markup, which helps them appear in Google’s “Things to Do” carousel.

When to tick it:

  • Any show you’re actively promoting — new season announcements, opening night, high-priority runs.
  • Turn it OFF once the run is over or once ticket sales are strong enough that you don’t need the homepage placement. Featured events auto-drop from the homepage after their end date, but leaving many on the list dilutes attention.

Multi-date shows: important exception

If you’re using a Show Run hub landing page (see Section 5) — like In the Heights with four separate performance events — leave every individual performance unchecked. The hub’s Featured Show Hub setting is what appears on the homepage instead, so patrons see one card (“In the Heights, July 24–25”) not four cards for the same show.

Why it matters: the homepage Featured Shows section is the single most-viewed placement on seminoletheatre.org. Whether a show appears here is the largest single lever you have on ticket sales through the site.

04

SEO & meta description

The Rank Math box below the editor is where the search-result snippet is written.

Meta title

Leave the default (%title% %page% %sep% %sitename%) unless the event needs a different search headline. If overriding, keep it under 60 characters. Format:

Show Title — Date | Seminole Theatre

Meta description

150–160 characters. Include the show name, the date, one specific hook, and the venue. Write it as if it’s the first sentence a patron will read on Google.

Fill-in template
[Show Title] at Seminole Theatre in Homestead, [Date]. [One-line hook — the thing that makes this show worth attending]. Tickets from $[price].
Worked example
Opera Meets Zarzuela at Seminole Theatre in Homestead, Aug 22. The Opera Atelier presents a rare pairing of Juana Inés and La Revoltosa. Tickets from $1.

Focus keyword

One or two words the show would be searched for — usually the show title itself (Opera Meets Zarzuela). Rank Math will grade the page against it in real time; a green or orange score is fine, red usually means the meta description is too short or the focus keyword doesn’t appear in the title.

Why bother

Meta descriptions do not affect ranking directly, but they dramatically affect click-through. A meta description that reads like an ad copy line will pull double the clicks of one that Google auto-generates from the first sentence of your description.

05

Multi-date shows

When a single production runs across four or five performances, do not put four featured events on the homepage. Use the pattern below.

The site has a purpose-built system for shows like In the Heights, where one production plays on multiple nights. The pattern is:

  1. Create one event per performance, using the naming convention in Step 2 (e.g. In the Heights — Jul 24). Each performance has its own event page with its own Tixr URL and its own Cost.
  2. Do not tick “Feature Event” on any of those individual performances.
  3. Create a Show Run (Show Runs → Add New) as the umbrella. The Show Run has one poster, one synopsis, one creative-team block, and a repeatable list of every performance date with its own Buy Tickets button. Past dates automatically render as Event Ended.
  4. Create a Post to host the Show Run. Give it the show’s slug (in-the-heights-show-dates). Paste the shortcode the Show Run gives you: [seminole_show_run id="XXX"]. This is the URL you promote in marketing.
  5. Turn on “Featured Show Hub” on that Post (right sidebar metabox). Set the run’s start and end dates. This shows one card on the homepage that links to the show landing page — instead of four event cards that all say In the Heights.

Why this pattern

Patrons decide “am I going to see this show?” before they decide “which night?” The hub answers the first question. The individual event pages answer the second. Google, meanwhile, sees each performance as its own indexable event with its own start time, which is exactly what its structured data expects.

06

Image specs

The site uses your uploaded image for the poster, the card thumbnail, the social share, and the Google search result. One well-prepared file covers all four.

Featured image (event poster)

Minimum
1200 × 675 px — the size Facebook and X require for share images
Recommended
1600 × 900 px or larger, 16:9 landscape — future-proof, crisp on retina screens
If vertical poster
1200 × 1500 px (4:5) — the site handles portrait cleanly
File format
JPG for photography, PNG for graphics with typography
File size
Under 500 KB. The site auto-compresses on upload, but starting under 500 KB keeps quality high
Alt text
Describe what’s in the image, not “poster for X”. Example: Two dancers in bright costumes mid-performance

Show Run hero (landing page banner)

Recommended
1920 × 900 px to 1920 × 1080 px, landscape — spans the full width of the show page
File size
Under 500 KB after compression. If the image is text-heavy, PNG. If it’s photographic, JPG at 80% quality

Playbill front cover (for the archive card)

Recommended
850 × 1100 px (letter portrait), the first page of the PDF exported as PNG
Why
The archive at /playbills/ lays out covers in a grid — a portrait aspect keeps every card looking like a real playbill

Do not upload straight from phone

A raw iPhone photo is often 4032 × 3024 and 4 MB — five times what the page needs. Resize to 1600 × 900 in Preview (Mac) or Windows Photos before uploading. Otherwise mobile visitors watch a 4 MB image download over cellular for a card that will render at 400 px.

07

Adding a playbill

Digital programs use the same flipbook viewer used on Playbill.com. The process is three steps.

  1. Upload the PDF at Media → Add New. If it’s over 10 MB, ask the site administrator to compress it before publishing — mobile visitors will bounce off a 40 MB PDF.
  2. Create a DearFlip Book at DearFlip Books → Add New. Title it [Show Title] Playbill. Set the Source Type to PDF, paste the PDF’s URL from the Media Library into PDF Source, set the Featured Image in the right sidebar to the show’s front-cover page (as a JPG or PNG), and Publish. Copy the shortcode it gives you: [dflip id="XXX"]].
  3. Create the Playbill Post at Posts → Add New. Title it [Show Title] Playbill. Slug: [show-slug]-playbill. Set the Featured Image to the same front cover. Tick the Playbill category so it appears on /playbills/. In the body, paste the shortcode plus a download link. Publish.
Playbill post body template
[[dflip id="XXX" height="800"]][[/dflip]

<p><a href=”URL_TO_PDF” target=”_blank” rel=”noopener”>Download the PDF</a></p>

08

Publish & preview

Preview before publishing. Once live, verify the ticket button works.

Before hitting Publish:

  1. Click Preview in the top-right. A new tab opens showing the event page exactly as visitors will see it.
  2. On the preview page, click the CTA button (Buy Tickets, Register Now, or Learn More — depending on what you picked in Field 07). It should open the correct Tixr or Google Forms page in a new tab. If it goes somewhere wrong or is missing, the Event Website field is empty or has a typo — fix that and preview again.
  3. Check the cover image renders full-width and isn’t sideways.
  4. Check the date on the page — verify AM vs. PM and month.

When the preview is clean, click Publish. If you catch a mistake after publishing, edit and click Update — changes go live within a minute.

Scheduling for later

To publish at a specific date/time (e.g. announce a season lineup at 10 AM Monday), click the Publish immediately link in the right sidebar → set the date/time → click Schedule. The event stays hidden until that moment, then appears automatically.

09

Pre-publish checklist

Tick these before every event goes live. If any one is missing, the event isn’t ready.

  • Title uses title case and, for multi-date runs, ends with the specific date.
  • Description opens with a strong two-sentence lede — this is what search results show.
  • Featured image uploaded, at least 1200 × 675 px, under 500 KB, with descriptive alt text.
  • Start Date & Time set to curtain time; End Date & Time is realistic (not blank, not 11:59 PM).
  • Time Zone is America/New York.
  • Venue selected — Seminole Theatre (Auditorium) for main stage.
  • Event Website filled with the exact Tixr URL for this performance.
  • Event Cost is a number (or Free), no dollar sign.
  • Category is at least Seminole Theatre Calendar.
  • Rank Math meta description is 150–160 characters, includes show title, date, and price.
  • Feature Event ticked only if the show should appear on the homepage.
  • Previewed in a new tab; Buy Tickets button opens the correct Tixr page.
End of guide