A page called "Who are we ………………"
Sits at a public URL with trailing full stops. Nobody intended it. It is a symptom.
Craig — you came to us because the QCRU website isn't pulling its weight. This document walks you through what's happening today, what a rebuild needs to look like if it's going to serve the union for the next decade, and how we'd structure the work so the board knows exactly what it's getting.
The platform isn't the real problem — although it has real problems. The deeper issue is that the site has been built once, handed over, and quietly drifted. A volunteer committee inheriting a website without a technical partner is how you end up here.
Sits at a public URL with trailing full stops. Nobody intended it. It is a symptom.
For a site whose job includes being found on Google, this is a structural error.
Analytics tracking is partially broken. Nobody caught it when it was deployed.
The authority and experience behind QCRU cannot be read by Google or AI search.
The moment someone wants to participate, they leave the QCRU site entirely.
A visitor today has no way of knowing whether the union is still active.
The representative pathway — Heelers, Orchids, Blue Heelers, Blue Orchids, QCRU Pups — is the thing that distinguishes country from city rugby in Queensland. On the current site it's the least visible section. No dedicated team pages. No selection policies. No success stories. Competition pages for Teenage, Seniors and Community Rugby each contain between 8 and 12 words.
If we stop at the rebuild, eighteen months from now you're looking at a shiny new site with the same empty competition pages and the same stale news section. The platform was never the problem.
We want to give QCRU a site that punches above its weight — the strongest digital position of any country rugby union in Australia — and a commercial arrangement that keeps a technical partner in the relationship so a broken GTM tag doesn't sit unnoticed for two years.
Astro plus Sanity. Static pages that load instantly. Structured content volunteers cannot break. Custom schema from day one.
The representative pathway gets the section it deserves. Named coaches, real bios, selection policies, success stories. Every page is real on launch day.
A monthly fee keeps us on the hook for the site. Fixtures posted, news after matches, issues fixed inside a business day. No drift.
The current site has 27 pages, most of them thin. The new site has fewer pages, every one of them earning its place. Here is the structure we'd propose — signed off with the board before a pixel is drawn.
The shop window. Hero story, pathway teaser, latest news, fixture ribbon, and a clear path into each of the three audiences.
Who runs the union and why they do it. Every bio rendered as plain text with Person schema — so Google and AI search can actually read it.
The mission of the union, made visible. Each representative side gets its own page with coaches, selection policy, current squad, and history. Success stories link out to players who've gone higher.
The product pages of country rugby. No more 8-word Teenage Rugby page — each competition gets a real page with structure, contacts, and this season's story.
The Find-a-Club journey lives on the QCRU site instead of handing visitors to australia.rugby. North / Central / South structure explained, every club findable, resources in one place.
How to get involved, written for actual humans. Players, coaches, officials, and volunteers each get a page that answers "what do I do next?"
Embedded from Rugby Explorer (xplorer.rugby/qcru). Rugby Australia has already invested in that infrastructure — we link and embed, we don't rebuild.
Alive. Structured News schema on every article with author, date, hero image. Posts appear in rich results. Videos and gallery are separate tabs.
Downloads, FAQs, and a member-only zone for committee documents and club resources — gated without being hostile.
A real page with real people. Not a form that goes into a black hole.
Astro ships static HTML by default. No heavy JavaScript runs on the page unless we explicitly ask it to — which means the site loads instantly on a phone at a country ground with patchy signal.
A content-heavy site like QCRU — news, fixture links, pathway explainers, champions archives — does not need a single-page app. It needs pages that open in under a second and rank well on Google.
Sanity is where volunteers edit the site. A news article has a title field, a date field, an author field, a body field, and an image field — and there is no way to paste in a press release with the wrong formatting or accidentally delete a section.
Content is structured at the database level, not free-form HTML. The design is locked in the code. Editors cannot break the design, and every piece of content has the metadata Google and AI search need to surface it.
Schema is the invisible markup that tells search engines what a page is about. A SportsOrganization isn't a generic Organization. A coach bio is a Person, not a paragraph. A news article is a NewsArticle, not a blog post.
When a parent searches "Queensland Country Heelers fixtures" or asks ChatGPT about the country rugby pathway, the site has a real chance of being the answer — not just a blue link in the middle of page two.
The current site uses a generic Organization type.
That's wrong for a sporting body. We fix it at the foundation.
Every page validates with Google's Rich Results Test before it goes live.
SportsOrganization QCRU itself. Sits on the home page and the about section. Tells Google this is a sporting body, not a generic non-profit.
Person Every coach, selector, board member, and standout pathway player. Plain-text bio. Links to clubs and sub-unions where relevant.
NewsArticle Every news post. Title, date published, author (a Person), hero image with alt text, publisher (the SportsOrganization). Eligible for rich results.
SportsEvent Representative fixtures, where Rugby Explorer doesn't already provide its own. Prefer linking through when they do.
Every integration and plugin is something we'd maintain for you over the next two years. We want to keep that list honest.
No plugins, no theme porting, no Gutenberg blocks. That's what got the site here.
Rugby Explorer is Rugby Australia's investment. We embed and link.
We link to existing forms. Revisit if it becomes a priority.
If a page doesn't have real content on launch day, it doesn't go live.
Three lenses we apply to every engagement. Build the right thing. Grow it with a monthly rhythm. Report honestly on whether it's working. Skip any one of these and the site drifts back to where it started.
A site that reads like it was planned — not a collection of pages bolted on over five years.
Most proposals go quiet here. Ours doesn't — because the WaaS retainer is how this works.
You get a proper read on whether the site is doing its job. No vanity metrics.
Six phases. Clear ownership on every deliverable. The shape of the work from first call to DNS cutover — with the honest caveat that content readiness, not build complexity, drives the schedule.
Thirty-minute discovery call with Craig and nominated board members. We leave with a signed-off sitemap, a content inventory, and an assigned owner for every page.
Visual language locked. Brand, typography, colour, component library. The things that make every future page look right without starting from scratch.
The hands-on build. Static Astro pages, Sanity schemas for every content type, custom schema markup (SportsOrganization, Person, NewsArticle, SportsEvent) wired into every template.
Review cycles and the long-tail content work. Rugby Explorer embedded on fixtures & results. Club directory populated. News section seeded with three real posts so launch day doesn't look empty.
The unglamorous week. WCAG 2.1 AA audit, schema validation on every template, Core Web Vitals tuning, cross-browser and mobile QA. Nothing ships with known issues.
Go-live. DNS cutover at an agreed time (out of hours, not match day). 301 redirect map for every legacy URL. Post-launch monitoring for the first 72 hours.
Timeline is driven by content readiness, not build complexity. If QCRU moves quickly on reviewing drafts and signing off board bios, we can pull a week or two forward. If reviews take longer, the build waits. We'd rather launch a complete site a fortnight late than a patchy site on time.
We operate on a Website-as-a-Service model. You don't pay anything upfront. You pay a fixed monthly fee that covers build, hosting, monitoring, SEO, accessibility, and capped ongoing updates — amortised across 24 months.
No surprise invoices. No "scope creep" conversations. These are the things we do because they're part of what you pay for.
We can do this because we run the same stack across multiple clients, we have an in-house team rather than agency overhead, and the WaaS model smooths the cashflow for both sides.
Five articles per month, drafted by our team and sent for committee review. For when the news calendar gets busy.
A dedicated onboarding programme for the QCRU volunteer(s) who will publish on Sanity. Recorded. Reusable.
Season opener content swap, sponsor updates, champions archive added, success stories expanded. One per year, included in the retainer.
A handful of representative sporting bodies whose sites do one or two things better than QCRU's current site does them. We'd borrow the principle, not the pixels.
Directional, not aspirational. These sites do one or two things exceptionally well that we want to borrow — not templates we'd copy. The QCRU site should look and feel like Queensland Country, not like World Rugby or the Lions.
Directional reference
News velocity. When the governing body is posting daily and the union below it is quiet, visitors notice.
Directional reference
Pathway pages done properly. Dedicated sections per representative team with history, current squad, and bios.
Press, fixture, and results integration. Clean separation of "what happened" from "what's coming".
Directional reference
Storytelling on identity. How a heritage brand makes its history feel current without looking like a museum.
Three steps between today and a live site. No bespoke contract drafting, no procurement gauntlet — just a conversation, an agreement in principle, and a target date.
Forward the URL. It reads in about fifteen minutes. Collect questions or objections before the call so we can address them directly.
A short call with Craig and whoever from the board should be in the room. We confirm the sitemap in principle, agree on a content approach, and answer whatever's still open.
From sign-off we aim for launch in the first week of July — a clean runway to the winter rugby season and the second half of the representative calendar.
The site is the shop window of the union — the first impression for every parent, every volunteer, every prospective sponsor, every journalist covering a representative fixture. Let's make it one worth standing behind.