Client portal

Sign in to manage tickets, messages, and your account.

Sign in to portal
NexusByte banner
Australia Migration Centre
Australia Migration Centre website homepage, showing visa categories and consultation booking, built by NexusByte
Web Development

Australia Migration Centre

Australia Migration Centre is a migration practice established in 2005, working out of Kellyville with MARA-registered agents and immigration lawyers on the team. australiamigration.net.au runs on Next.js with Strapi managing the content.

The taxonomy problem

Australian migration is administered as a large set of visa subclasses identified by number, and that is how the Department documents them. It is not how anyone arrives at a migration agent's website. A visitor knows their situation — my partner is a citizen, my student visa expires in March, my application was refused — and almost never knows which subclass that maps to. Any site that leads with subclass numbers has already lost the reader it was built for.

So the information architecture is organised around self-description: visiting, working and skilled, studying and training, family and partner, humanitarian and refugee, and an "other" grouping that honestly collects the awkward remainder — bridging visas, medical treatment, crew. Citizenship sits alongside them for permanent residents taking the last step, and appeals to the AAT and the Federal Court sit apart, because someone who has been refused is in a different emotional and legal position from someone starting an application.

Why repealed visas stay published

One category on this site is worth explaining, because it looks like an error and is not: repealed visas. These are subclasses that no longer exist. Most sites delete that content the moment a pathway closes. Keeping it serves two real audiences — people still holding a visa granted under a repealed subclass who need to understand where they stand, and people researching a pathway they read about years ago and do not yet know is gone. Answering "this no longer exists, here is what replaced it" is genuinely useful, and it is the kind of page a competitor will not have.

It also explains the technical decision underneath the site. Migration policy changes continuously; categories open, close and are renamed. None of that could be hard-coded into components. Every visa category is a Strapi content entry, so adding a pathway, rewriting eligibility or retiring a subclass is an editorial action taken by the practice on the day the change lands, not a development ticket that waits for a deployment window.

Credentials, and where they belong

Migration advice is a regulated profession and an area with a real problem of unregistered operators, so the MARA registration number is treated as part of the offer rather than as fine print — visible site-wide, not parked on an About page. That the team includes both registered agents and immigration lawyers matters too, particularly for the appeals work, where the question stops being procedural and becomes legal. The four-stage process — consultation, document preparation, lodgement, decision — is published for the same reason: it tells an anxious reader what the next twelve months look like.

The consultation form carries a visa-type field, so an enquiry arrives already sorted and can be routed to the right person before anyone reads the message. Behind it sit an FAQ covering the questions that would otherwise consume a first appointment, and a blog working through individual visa topics in depth. Professional practices with this shape of problem are covered by our law firm and professional services website work.

The SEO build

Migration is one of the most competitive search categories in the country and one of the least trustworthy, which makes the technical groundwork matter more than usual. Six blocks of structured data ship on the homepage, canonicals resolve consistently to the www host so the site is not competing against a second copy of itself, and the social layer runs to ten Open Graph properties and a full Twitter card set — worth having when links are shared privately between family members far more often than they are posted publicly.

The content architecture does the rest of the work. Because every visa category is its own page rather than an anchor on a services page, each one can carry its own title, description and canonical and compete for its own searches — which is the whole reason the taxonomy was modelled in Strapi in the first place. The 27-URL sitemap is declared in robots.txt and regenerates as categories are added or retired, so a repealed pathway leaves the index cleanly instead of lingering as a broken result.

The Challenge Of Project

  • Turning a subclass-numbered legal taxonomy into categories a person can recognise themselves in, without losing the precision a regulated practice is obliged to keep.
  • Modelling visa categories as content rather than code, so a repealed subclass or a policy change is an edit made on the day, not a development ticket.
  • Publishing repealed pathways rather than deleting them, since people still hold those visas and still search for them years after the subclass closed.
  • Making the MARA registration visible site-wide, in a field where unregistered operators are a genuine problem and the credential is the differentiator.
  • Routing enquiries by visa type at the point of capture, so a consultation is triaged to the right agent before anyone opens the message.