Ordered by leverage, not by effort. Phase 0 is roughly one engineering day and unblocks everything after it. Do not start content until 0.1 and 0.2 ship.
This week. All config level.
| # | Action | Why | Sev |
|---|---|---|---|
| 0.1 | Make /event/<invalid> return a real 404 | Kills the infinite crawl space. Highest severity item | Critical |
| 0.2 | Ship sitemap.xml from the event DB, auto-updating, with lastmod. Submit in Search Console | The only crawl path to event pages | Critical |
| 0.3 | Ship robots.txt referencing the sitemap | Trivial, currently 404 | High |
| 0.4 | Add self-referencing canonicals sitewide | Collapses the already-indexed truncated duplicates | Critical |
| 0.5 | One H1 per page | Currently zero across the entire site | High |
| 0.6 | Homepage meta description + OG tags | Missing | High |
| 0.7 | Fix /privacy, it serves the homepage title | Duplicate title | Med |
| 0.8 | Drop no-store on public marketing pages | Defeating the CDN on a static homepage | Med |
Weeks 2 to 4.
| # | Action |
|---|---|
| 1.1 | Server-render event content. Name, date, venue, city, price and availability in the initial HTML. Next.js already supports this, the data is just fetched client-side today |
| 1.2 | Event JSON-LD on every event page: name, startDate, location, offers (price, currency, availability, url), performer, eventStatus, image. Feeds Google Events and AI answers directly |
| 1.3 | Organization + SoftwareApplication schema with sameAs to LinkedIn, X, Instagram, both app stores and the Galway address. This teaches AI the category |
| 1.4 | Browsable index pages: /ireland, /galway, /gaa, /concerts, /festivals, /venues/duggan-park. Gives crawlers a link path and these are the pages that rank |
| 1.5 | Standardise the title separator, kill the generic "Event details" fallback |
Weeks 4 to 8.
| # | Action |
|---|---|
| 2.1 | Get listed on Capterra, GetApp, G2, Software Advice, Product Hunt, Crunchbase. Every AI answer that beat them was assembled from these. Cheapest citation lever available |
| 2.2 | Ship a public pricing page. Every competitor cited in the US round was cited with their pricing |
| 2.3 | Comparison pages: vs Future Ticketing, vs Tixserve, vs Fanbase (IE), vs Eventbrite, vs Ticket Tailor, vs TicketSpice (US) |
| 2.4 | llms.txt stating what TicketSoft is and that it is unrelated to ticketsoft.nl, Ticketsoft Colombia, Ticket Soft or the former Dallas Ticketsoft |
| 2.5 | Fix the social handle fragmentation. Instagram, X and LinkedIn are all @ticktsoft, missing the "e", while the domain is ticketsoft. That splits the entity across two strings for every engine |
| 2.6 | Put the team on the site. An /about page with Person schema. Right now the only reason AI knows who runs it is RocketReach |
Weeks 6 and beyond. This is where the leverage is.
| # | Action |
|---|---|
| 3.1 | Build the definitive /gaa-tickets hub, county by county, competition by competition, fixture by fixture. Target the 9,900/mo head term with real inventory behind it |
| 3.2 | Own "how to buy tickets for [county] [code] matches" as indexable pages. AI currently answers that with the county board site |
| 3.3 | Replicate the Galway Camogie link pattern with every new county board. Make a linked fixtures integration a standard onboarding clause. A link-building engine disguised as a sales motion |
| 3.4 | Irish tech press on the Galway, PorterShed and first-county-contract story: Silicon Republic, Galway Daily, Business Post, TechIreland, ThinkBusiness |
NOW 0.1 soft-404 -> 0.2 sitemap -> 0.4 canonicals
WEEK 1 0.3 robots · 0.5 H1s · 0.6 meta+OG · 0.7 privacy · 0.8 cache
WEEK 2-4 1.1 SSR content -> 1.2 Event schema -> 1.4 index pages
WEEK 4-6 2.1 review listings · 2.2 pricing page · 2.5 social handles
WEEK 6+ 3.1 GAA hub · 3.3 county link engine · 2.3 comparisons