Using the <localfile> block is correct, however, there are two small adjustments I wanted to clarify, which are needed to make it work properly:
For the eventchannel format, Wazuh expects the "Channel Name", not the file path itself. You should change "<location>C:\Windows\...\Google.evtx</location>" to "<location>Google</location>" (check that the "Channel Name" is the same as how it is listed in the Event Viewer properties for those logs).
Ensure this configuration is placed in the ossec.conf of the Wazuh Agent installed on the Windows server, rather than the Wazuh Manager.
About verifying the configuration using Filebeat, I wanted to point out that Filebeat handles the transport of alerts from the Manager to the Dashboard, so it won't help you verify the ingestion on the Windows side. Instead, I recommend enabling the archives.log on your Wazuh Manager. This will allow you to see the raw events coming in from the agent in real-time to confirm the connection is active and the logs are being processed correctly. You can find more information about localfile configuration and enabling the archives.log below:
Local configuration (ossec.conf) | Wazuh Agent
Enabling archiving | Wazuh Manager