The most commonly asked question on the internet relating to the musculoskeletal system is a simple one: “Why do I have lower back pain?” Shortly followed by "Why do I have neck pain?".
Up until very recently, we used the internet a bit like a library. We’d go to Google with a problem, type in a short question or a few key words, and then work our way through pages of information—some relevant, some less so, and plenty of adverts—until we found an answer that felt convincing and hopefully reasuring. A question like “why does my back hurt?” could take time to answer, not because the information wasn’t there, but because we had to interpret it. We were relying on someone else’s explanation of anatomy, movement, and injury, often shaped, consciously or not, by their own perspective.
That process is changing. Increasingly, people are turning to their AI of choice and asking questions in a more natural, conversational way. Instead of typing a few keywords, it might sound more like:
“My lower back’s been giving me grief since yesterday after I mucked out my mum’s six horses. Why do you think that is? Should I be worried? Have I damaged something?”
It’s a subtle shift, but an important one. That question contains far more useful information. It tells us where the pain is, when it started, what may have triggered it, and what the person is concerned about. With that context, it becomes much easier to give advice that is relevant, practical, and reassuring. Talking face to face with a healthcare professional would result in very similar answers.
This is where tools like AI can be genuinely helpful. Not because they can pinpoint a precise diagnosis (they can't), but because they can respond to the whole situation, not just a fragment of it. When a question includes meaningful detail, the answer is more likely to reflect real-life decision-making rather than a long list of possible causes.
If you’re confident that the question you’re asking includes the key details, there’s nothing inherently wrong with taking reassurance from an AI response. In many cases of uncomplicated lower back pain, that reassurance, along with simple advice to keep moving and gradually return to normal activity, is often exactly what’s needed. It can be both helpful and cost-effective, particularly when symptoms are recent, uncomplicated and behaving in a predictable way.
Of course, the quality of the answer still depends on the quality of the question. A vague question tends to produce a vague answer, whereas a more specific one - where it hurts, when it started, what you were doing at the time, and how it behaves - provides a much better foundation for useful guidance. Even small details, like whether the pain travels into the leg or changes with movement, can influence the advice in a meaningful way.
None of this means that every answer should be taken at face value, or that professional advice is no longer required. However it does help us to realise that how we ask about pain will shape the answers we receive.
“Why does my back hurt?” isn’t a bad question. It’s just an incomplete one. Adding a bit more context - when, what, where and how? - turns it into a far more useful starting point. In fact this is nearly identical to the way that your chiropractor will ask about your pain.
And while better questions can lead to better answers, there are still times when nothing replaces a proper assessment. If you still have concerns, your symptoms are persistent, worsening, or simply not making sense, seeing a chiropractor who can assess you in person is still the most reliable way to get clear, individualised advice and support.
