Last Updated: 27 August 2026 · By Ehtisham Saeed, RTO Marketing Specialist
Most RTO owners judge their website on whether it looks professional. Prospective students, Google, your own systems and ASQA all judge it on something else.
Ask an RTO owner what they think of their website and you usually get an aesthetic answer. It looks dated. It looks clean. We had it redesigned two years ago. Aesthetics are the one thing every visitor notices and almost the only thing that does not determine whether the site produces enrolments.
Your website is the only asset every marketing channel points at. Google Ads sends paid traffic to it. Organic search sends prospective students to it. Meta ads, your Google Business Profile, your email nurture sequence and your word-of-mouth referrals all end at the same place. When the site fails at one of its jobs, every channel upstream gets quietly less effective, and the diagnosis usually lands on the channel rather than the destination.
This guide covers the seven jobs an Australian RTO website has to do, what failure looks like for each, and where the operational detail lives. It anchors the web design cluster and sits beneath the broader how to market your RTO framework.
Four Audiences, Four Different Tests
The reason “does it look good” is the wrong question is that four audiences assess your website and only one of them cares how it looks.
Prospective students arrive with a specific question (can I do this qualification, in this delivery mode, for roughly this price) and leave within seconds if the page does not answer it. Google reads structure, speed, schema and content depth to decide whether you appear for qualification searches at all. Your own systems need the site to hand enquiries and tracking data across cleanly, or your cost per enrolment stays invisible and your follow-up runs late. ASQA reviews your public marketing surfaces during the desktop phase of a performance assessment, before anyone visits your premises.
A website can satisfy the first audience and fail the other three. That is the most common pattern in the sector: a good-looking site that ranks for nothing, drops enquiries into an unmonitored inbox, and carries three prohibited phrases on the homepage.
How This Relates to the Marketing Framework
Our marketing pillar works on three layers: being found, being chosen, being trusted. That framework covers your whole marketing system across every channel. This guide covers what the website specifically has to deliver, which overlaps on the first three jobs and then keeps going into four the marketing framework never touches: accessibility, systems integration, and whether the site can be maintained without a developer.
Job 1: Get Found
Prospective students search for qualifications, not for RTOs. They search “Certificate III in Individual Support Parramatta” and “CHC33021 online”, not “best training provider Australia”. If your website has one page per qualification, structured for those searches, you can appear. If your courses live inside a single “Our Courses” page or a PDF download, you cannot.
How to tell your site fails this job: open Google Search Console and look at the queries bringing impressions. If almost all of them are your brand name, the site is being found only by people who already know you exist. That is not a marketing channel; that is a business card.
What good looks like: a dedicated, indexable page for every qualification on your scope, carrying the code and title as published on training.gov.au, the unit list, delivery modes, locations, duration and fees. Course schema markup so Google can parse what you deliver. Fast mobile loading. A Google Business Profile carrying your campus locations into the local pack for suburb-level searches.
The strategy sits in our RTO SEO pillar, the technical fixes in the website SEO audit guide, the page-level optimisation in the course page SEO guide, and the local layer in our Google Business Profile guide.
Job 2: Pass the Five-Second Test
A prospective student lands on your course page from a search result or an ad. Within about five seconds they decide whether to keep reading or go back to the results page. Three questions decide it: is this the qualification I was looking for, can I do it the way I need to (online, evenings, on campus near me), and roughly what does it cost.
How to tell your site fails this job: open your busiest course page on a phone. Without scrolling, can you see the qualification code and title, the delivery modes, the duration and a fee figure? If any of those requires scrolling or a click, most visitors leave before finding it. Bounce rates above 70 percent on course pages usually trace back to exactly this.
What good looks like: an above-fold summary block on mobile and desktop carrying qualification code and title, delivery modes, duration and next start dates, fee information including funding eligibility, and brief entry requirements. Everything else follows below in a predictable order.
Hiding the fee behind an enquiry form is the most common self-inflicted wound here. It reduces enquiry volume and lowers enquiry quality at the same time, and clear fee representation is an expectation under the Information and Transparency Practice Guide regardless. The full specification is in our course page design guide.
Job 3: Convert the Enquiry Into a Contactable Lead
A visitor who reads the whole course page and leaves without acting is a marketing cost with no return. The site has to make the next step obvious and make the resulting enquiry actionable.
How to tell your site fails this job: count the distinct calls to action on a course page. If there are five (enquire, download the brochure, call us, chat, subscribe), there are effectively none. Then check what happens after submission: if the enquiry lands in a shared inbox nobody owns, the conversion problem is downstream of the website but caused by it.
What good looks like: one primary action per page. A short form asking only what you need to make the first contact useful, not the full enrolment dataset. An immediate on-screen confirmation telling the student what happens next and when. An automated acknowledgement within minutes. A real human contact within the hour during business hours, because speed to contact is one of the highest-leverage conversion factors in RTO marketing.
Form design detail is in the course page design guide, the speed-to-contact framework in our Facebook Lead Ads guide, and the multi-touch follow-up in the enquiry nurture sequence guide.
Job 4: Prove Legitimacy, to Students and to ASQA
Prospective students are making a decision worth months of their life and often thousands of dollars, and they are aware the sector has had bad operators. ASQA reviews the same pages for different reasons. The useful insight is that both audiences read the same signals.
Your RTO code displayed correctly is a compliance requirement and a trust marker. Your legal name matching training.gov.au exactly is a compliance requirement and lets a cautious student verify you on the National Register in thirty seconds. Named trainers with real credentials satisfy transparency expectations and answer the question every serious student has about who will actually teach them. Real graduate outcomes with consent on file are compliant evidence and the most persuasive content on the page.
How to tell your site fails this job: search your own site for the words “guaranteed”, “fast-track”, “accredited” and “100%”. Each hit is a potential prohibited phrase and a credibility problem with sophisticated buyers, who read outcome guarantees as a warning rather than a promise.
What good looks like: RTO code and legal name in the footer template so they cannot be omitted, NRT logo used within the conditions of use and only against nationally recognised training, no course listed that is not on your current scope, trainer profiles with real credentials, and testimonials attributed to real people with documented consent.
The full element list is in our ASQA-compliant RTO website guide, the language rules in the prohibited phrases guide, and the review and social proof system in our reputation management guide.
Job 5: Be Usable by Everyone
This is the job almost no RTO website guide mentions, and the one with a legal dimension most RTO owners have never been told about.
Around 5.5 million Australians, roughly 21 percent of the population, live with disability. Some proportion of your prospective students, current students and employer contacts are among them. Separately from any commercial argument, the Australian Human Rights Commission administers complaints under the Disability Discrimination Act 1992, which makes discrimination unlawful in access to services, and the Commission’s guidance treats public-facing websites and digital services as within scope. In April 2025 the AHRC published updated guidance affirming the Web Content Accessibility Guidelines version 2.2 at Level AA as the minimum standard, and extending the expectation to SaaS platforms, mobile apps and AI-driven tools.
Australian government websites are required to meet that standard. Private organisations are not named in the legislation the same way, but they can be, and have been, the subject of DDA complaints over inaccessible digital services. The practical position is that WCAG 2.2 Level AA is the benchmark Australian regulators and courts reference, and that a complaint costs time and reputation regardless of outcome. This is general information rather than legal advice, and an RTO with a specific concern should take proper advice.
Why this bites twice for RTOs. Under the 2025 Standards, prospective students must be able to access information about fees, entry requirements, support services and delivery before they enrol. If that information is on a page a screen reader cannot parse, or behind a form that cannot be completed with a keyboard, the information has not genuinely been provided to that student. An accessibility failure on an RTO site is a potential DDA exposure and a potential pre-enrolment information problem at the same time. Add the wellbeing and support obligations under the Standards and the picture gets sharper: a provider that must support students with disability, operating a website those students cannot use.
How to tell your site fails this job: the base rate is discouraging. A 2026 WebAIM analysis of a large sample of homepages found roughly 95 percent had detectable WCAG failures, so assume yours has issues until tested. Three quick manual checks: try to complete your enquiry form using only the keyboard (tab, arrow keys, enter), check whether your images carry descriptive alt text, and run your main colour combinations through a contrast checker.
What good looks like: body text at readable size and at least a 4.5:1 contrast ratio, every interactive element reachable by keyboard, descriptive alt text on images, visible labels on every form field rather than placeholder text that vanishes when typing starts, and captions on video. The tactical checklist sits in our course page design guide; what this section adds is the reason it is not optional.
Job 6: Feed Your Systems
A website that produces enquiries into a void is doing half a job. The site is the top of a pipeline that runs through your CRM, your student management system, and your reporting.
How to tell your site fails this job: ask what your cost per enrolment was last month, by channel. If the answer requires a spreadsheet reconciliation, or does not exist, the tracking layer is broken. The related test: pick an enquiry from six weeks ago and trace it. Do you know which page it came from, which campaign, and what happened next? If not, every optimisation decision you make is guesswork.
What good looks like: enquiry forms writing directly into the CRM with source and campaign attribution attached. Conversion tracking configured so paid channels report actual enrolments rather than form fills. Analytics installed and tested, not installed and assumed. A clean handover from enquiry record to student record when someone enrols, so the marketing and delivery sides are not maintaining separate versions of the same person.
System selection is covered in our CRM buyers guide and LMS and SMS buyers guide, the tracking setup in our conversion tracking guide, and the numbers worth watching in our marketing KPIs guide.
Job 7: Stay Accurate Without a Developer
An RTO website is not a static asset. Qualifications supersede. Fees change annually. Intake dates move. Trainers leave. Funding programs open and close. Every one of those events makes part of your website wrong, and wrong content on an RTO site is a compliance exposure rather than a cosmetic issue.
How to tell your site fails this job: find the most recent qualification change on your scope and check how long the website took to reflect it. If the answer is “we are not sure” or “we are still waiting on the developer”, the site cannot be maintained at the speed compliance requires. Then check whether a superseded code is still live somewhere: an old course page, a PDF, a blog post from 2024.
What good looks like: someone in your organisation who is not a developer can update a fee, add an intake date, publish a new qualification page and take down a superseded one, on the same day the change happens. A quarterly reconciliation between your live course catalogue and your current scope on training.gov.au. A documented owner for that review, so it is somebody’s job rather than everybody’s assumption.
This job is where the platform-versus-custom-build decision gets real. A custom build where every content change is a developer invoice at Australian hourly rates will drift, because the friction is high enough that small corrections wait. The scope reconciliation process is covered in our training.gov.au listing guide, and the ongoing monitoring cadence in our marketing compliance pillar.
The Seven-Question Diagnostic
Answer each one yes or no about your current website. Count the noes.
- Do non-brand qualification searches bring impressions in Google Search Console?
- On a phone, without scrolling, does your busiest course page show the qualification, the delivery mode and a fee?
- Does each course page have exactly one primary call to action, and does a real person respond within an hour during business hours?
- Can a cautious student verify your legal name and RTO code against training.gov.au from your footer in under a minute?
- Can your enquiry form be completed using only a keyboard?
- Do you know last month’s cost per enrolment by channel without building a spreadsheet?
- Can someone who is not a developer update a fee today?
Zero or one no is a healthy site. Two or three means targeted fixes. Four or more usually means the structure is the problem rather than the content, and patching will cost more over two years than rebuilding. For the full audit methodology, our website SEO audit guide covers the technical side and our ASQA-compliant website guide covers the compliance side.
What Fixing This Costs
The honest answer depends on how many jobs are failing and whether the structure supports the fixes. Content-level failures (weak course page copy, missing fee display, prohibited phrases) are cheap and fast. Structural failures (no per-qualification pages, no CRM integration, a theme that cannot support the summary block) usually are not worth patching.
Current Australian market ranges, and the five ways to buy, are covered in detail in our RTO website cost guide, including the course page volume problem that makes RTO quotes different from every other small business quote.
Frequently Asked Questions
What are the minimum requirements for an RTO website in Australia?
At minimum: your legal name exactly as registered and your RTO code displayed, the NRT logo used within its conditions of use, a page for each qualification on your scope carrying the code and title from training.gov.au with fees, delivery modes and entry requirements, no prohibited phrases in the copy, no courses listed outside your scope, and pre-enrolment information genuinely accessible to prospective students. Everything else in this guide is about whether the site works commercially, not whether it passes review.
Does my RTO website legally need to be accessible?
The Disability Discrimination Act 1992 makes discrimination unlawful in access to services, and the Australian Human Rights Commission treats public-facing websites and digital services as within scope. The Commission’s 2025 guidance references WCAG 2.2 Level AA as the minimum standard. Government websites are required to meet it; private organisations can be the subject of DDA complaints over inaccessible services. For RTOs there is a second dimension, because information a student cannot access has arguably not been provided under the 2025 Standards pre-enrolment requirements. This is general information rather than legal advice.
Can a DIY website builder do all seven jobs?
Realistically no. DIY builders can handle jobs 2 and 3 reasonably and part of job 5. They struggle with per-qualification page structure at scale, course schema, CRM integration and maintainable bulk updates. They can be a defensible bridge for a pre-registration operator or a single-qualification micro RTO, and a poor destination for anyone spending money on marketing.
How do I know whether to rebuild or fix my current site?
Run the seven-question diagnostic. If the failures are content-level, fix them; that is a fraction of the cost of a rebuild. If the failures are structural (no per-qualification pages, no integration path, a theme that cannot support proper course page structure, or content changes that require a developer), rebuilding is usually cheaper over three years than repeatedly patching.
How often should I review my RTO website?
Quarterly at minimum, aligned with your scope reconciliation against training.gov.au. Monthly spot checks of any new pages or campaigns published since the last review. The Practice Guide expects RTOs to be able to answer how often marketing materials are checked for accuracy and currency, and an annual review is not a strong answer under the self-assurance expectations of the 2025 Standards.
Who is responsible if my web designer builds something non-compliant?
The RTO. ASQA assesses the provider, not the provider’s contractors. A designer who did not know the Practice Guide existed is an explanation, not a defence. This is why sector knowledge matters more than design quality when choosing who builds your site, and why the compliance review before launch belongs to you regardless of who writes the copy.
What Happens Next
Run the seven questions. The pattern of failures tells you what kind of problem you have: content, structure, systems, or process. Content problems are the cheapest and most common, and the ones most likely to be creating compliance exposure right now without anyone noticing.
Start there. RTO Scanner checks your live website copy against the phrases ASQA flags and validates your RTO code against training.gov.au in real time, free, in under five minutes. It answers job 4 directly and tells you how much of your problem is language rather than architecture.
From there, the cluster covers each job in depth: search visibility, course page conversion, compliance elements, technical health, and what the fixes cost. If you would rather start from a platform that handles jobs 4, 6, and 7 out of the box, Easy RTO is built for exactly that.
