Depends,
Provide your network diagram and config.
Is your router an MT router with wifi or are you talking about an AP or a router being used as a switch and AP.
Personally vlans and multiple wlans go well together.
Actually you need both VLAN and firewall rules. V in VLAN stands for “virtual” meaning it’s a separate LAN but sharing physical infrastructure with other VLANs. But when it comes to routing, router (with this I mean routing function of the device) treats all networks equally … it doesn’t know that 192.168.1.0/24 is any different than x.y.z.w/16. And by default router gladly forwards packets, received through one interface, to another interface depending on routing tables. And VLANs for routers are yet another interfaces. Router only cares about IP addresses, it doesn’t care about protocols etc.
So using VLANs indeed separates devices on same LAN infrastructure (AP, switch, …), but when those packets arrive to router, VLANs stop being relevant.
Luckily ROS offers another function (apart from routing) on all devices: firewalling. Which sits between ingress interface and routing engine. So firewall can inspect packet (in more detail than router does: it also cares about protocols and ports, etc.) and discard it if some rule requests so.
If you want to block traffic between guest LAN and “owner’s” LAN, you have to add rule in firewall which will block such traffic.
You can block traffic between certain IP subnrts using routing filters. These are much more resource friendly than firewall. However they generally lack flexibility which only stateful firewall can provide.
Or simply ( on a router )
vlans separate users at layer 2, mac address
firewall rules separate users at layer 3, ip addresses ( needed because a router knowing all local interfaces will route requests between subnets or vlans if not told otherwise )