Friday, 22 August 2025

Is Your Website Content Holding You Back? How to Audit for AI Visibility


As AI-powered search tools like Copilot, ChatGPT and Perplexity become more common, many businesses are starting to realise their website content no longer performs the way it used to – not because people search differently, but because search results are now presented differently.

Recently, a client asked for help improving their search visibility. Their site looked fine on the surface, but after a quick audit it was clear the content hadn’t been touched in years. Service pages were thin, FAQs were buried in blog posts, and key offerings weren’t described in detail. Another client had migrated to a new platform but hadn’t updated legacy content – the structure was solid, but the messaging was still stuck in 2016.

Here’s how we approach content audits to improve visibility in AI-powered search results.

Read the full article 

This article was first published on the WebSolutionZ.com.au blog.  

Share:

Tuesday, 19 August 2025

Corporate Social Engineering 101

Another day, another Australian corporation actively encouraging social engineering. 🤦‍♀️ 

For YEARS, RACV has called from a "Private Number" to discuss a claim, and immediately asked me to confirm my full name, date of birth, and address “for security purposes.” (They're not the only Australian company that does this, but they are today's example).

Whose security?! 

Let’s be clear:

You called me. From a hidden number. Asking for personal details.

That’s not security. That’s textbook social engineering.

When I push back, they read out an obvious script along the lines of "if you're not comfortable with this we will send an SMS to your mobile with details on how to call us back". So they know this is a problem. Yet they persist.

Kevin Mitnick was doing social engineering in the 1990s ("The Art of Deception" was published in 2002). It’s 2025. With scams and identity theft at an all-time high, why are large organisations still normalising insecure behaviour?

We need to stop training customers to hand over personal data to anyone who sounds official.

Do better, for all of our sakes.

This article was first published on LinkedIn

Share:

Sunday, 10 August 2025

Build Solutions for EVERYONE


Inclusive tech starts with challenging the “default user” mindset

When we design digital solutions, the simplistic approach is often to start by defining user personas, a common practice in marketing and communications to help target the desired user base.

But one assumption shows up more often than we realise - the idea of a “default user”. In persona development, this is often the “primary user” or “ideal customer”, and it tends to reflect a narrow, able-bodied, neurotypical profile.

It’s rarely stated outright, but the “default user” persona is baked into countless design decisions, from navigation structures to colour contrast, from form fields to error messages.

The problem? That “default user” might not be very inclusive.

ABC News Australia’s recent explainer titled “Reframing Disability” outlined the difference between the medical and social models of disability, which offers a useful lens for thinking about how we approach technology solutions:
  •  The medical model sees disability as a personal issue - something to be addressed or managed by the individual.
  •  The social model reframes disability as a mismatch between people and their environment. It asks - What barriers are we building in, and how can we not do that right from the start?
In tech, this distinction is actually really important. If we design solutions for a narrow “default user”, we’re essentially saying disability is a “them” problem, and they’ll just have to adapt. Or we end up trying to retrofit accessibility after the fact, which is often inefficient, expensive and incomplete.

Those who know me, know I love a good car analogy so here goes: it’s a bit like designing a car with no seatbelts or child seat anchor points, then trying to add them later. It can be done, but its harder, more expensive, and the outcome is rarely as good. A better approach is to think about a wider audience and design a more inclusive solution right from the beginning.

In digital projects, accessibility shouldn’t be an add-on. It’s a strategic choice - one that reflects our values as technologists, consultants and communicators. With The Future Is Accessible, we’ve tried to deliver a website solution that not only supports accessible browsing, but also enables contributors to create and manage content independently. From platform selection to theme choice and plugin configuration, every decision was made with inclusion in mind. We’re still learning, but the goal remains clear: build with accessibility at the core, not as an afterthought.

Let’s stop designing for a mythical “default” user. Let’s adopt the social model - and build for everyone.

This article was first published on TheFutureIsAccessible.au
Share:

Archive