A home wifi router is usually an access point, glued to a switch, glued to a Linux based router with 2 network interfaces (LAN going into the switch section, and WAN). Linux based router part of it will come with a statically defined IP address, and will run a DHCP server which will help others hosts automatically get non conflicting IPs.
What you want is, more than one AP, and perhaps more than one switch.
If you use home routers for this. You need to not have more than one DHCP server (disable DHCP), and you need to have non conflicting IPs on the LAN (change IP), and you need to not use the WAN port on one not connecting to the internet.
Connect the two devices using their LAN ports after you’ve set them up.
An access point is there to allow replacing an ethernet cat5/cat6 wire with a radio. It doesn’t do DHCP serving, routing, firewalling and so on.
Usually, an added bonus is that they might be intended for business use, where you might have a few dozen of them per building floor and will get more frequent security updates and for longer. (motivated by businesses being more likely to be repeat customers and or potentially being open to paying for support contracts). They might be POE powered (instead of through a wall wart), which means you can put them on the ceiling next to a smoke detector more easily and get better signal and range because of less furniture clutter. They might have a more utilitarian unobtrusive less alien spider spaceship design (useful if you want to put one in the kitchen), typically come in white/as is the color of most ceilings.
Often times, you end up managing their wifi settings as a group of devices through a single interface, rather than logging into each one individually.
Typically they’ll allow multiple VLANs out of the box, same AP can emit multiple virtual SSIDs e.g. for guest network, for employees (or apartment owners) and for iot stuff.
For typical home/multi access point network setups, I’d consider / recommend either Ubiquiti or TP-Link Omada setups.