That’s how ARP works. ARP stands for Address Resolution Protocol and as a protocol it lives low level of the network stack. It provides a mapping between a MAC address and an IP address.
In plain language an ARP request goes something like this:
Requestor: “Hey everyone! Who has IP address 22.214.171.124?”
Everyone on the local area network: “Hmmmm, is that my address? Nope. Am I router? Nope, so I won’t respond.”
The Router: “That’s not my address but I’m a router. Maybe I’m connected to a network that has that address. Yep, that address is on my WAN port.”
The Router: “That’s me! Use my MAC address for packets that need to be sent to 126.96.36.199. I’ll forward them to where it needs to go.”
All of this communication is taking place at the Link layer of the TCP/IP networking stack and it basically helps the hardware on the LAN understand when a packet is destined for that device and to know which device to send packets to. This traffic never leaves the local network, and in some cases it’s even more constrained.
So of course an ARP for Google’s IP address is going to give you the MAC address of your gateway router.