What you are building Go is a good fit when Think twice if
An API or webhook receiver other systems depend on It handles many requests at once and needs to answer fast without a large server bill. Traffic is light and your team already knows another backend language well. That language may be the simpler build.
A data pipeline or background worker It reads from queues or files and processes items in parallel, with steady memory use. The work is mostly data analysis. Python's libraries may get you there faster.
Infrastructure tooling or a command-line tool You want one binary you can drop on a server or hand to a colleague, with nothing else to install. It's a one-off script nobody will run twice.
A web app with lots of screens The backend is an API and the screens live in a separate front end. You want server-rendered pages, admin panels and forms out of the box. A framework like Laravel or Rails covers more of that.
Code that has to be as fast as possible Fast enough is the goal, and garbage-collection pauses are fine. You need predictable, very low latency or tight memory limits. That's where Rust comes in.