Place an eero mesh before chasing speed
A placement and backhaul guide that treats every wireless node as a relay, not a magic dead-zone endpoint.
Direct answer
The shortest reliable path.
Place a wireless eero between the gateway and the weak area—not inside the dead zone—then check its mesh connection before judging client speed. Keep nodes open, elevated, and away from dense or metal obstructions. Use Ethernet backhaul where practical.
System view
Check the whole path.
- 01Modem / ONT
- 02Gateway eero
- 03Mesh link or Ethernet
- 04Room eero
- 05Client device
Scope before steps.
eero systems using one gateway and one or more wired or wireless eero nodes.
Exact radio behavior for other mesh brands, ISP faults, Ethernet wiring certification, or advanced managed-switch design.
Procedure
Do this in order.
- 01
Keep the gateway in the open
If cabling allows, move the modem and gateway out of a basement, cabinet, or position blocked by large electronics and metal.
- 02
Place the next node before the dead zone
Start roughly halfway between the gateway and the weak area, in an open and elevated location. Use the app’s connection-strength view to adjust.
- 03
Compare the same client in two places
Toggle Wi-Fi off and on, then test near the gateway and in the target area with the same client and service.
- 04
Wire the backhaul when the house allows it
Connect Ethernet-capable nodes to the gateway eero directly, by daisy chain, or through a compatible switch downstream of the gateway.
- 05
Preserve the gateway topology
Keep the gateway eero directly after the modem or ONT. Place a switch after an eero, not between the modem and gateway eero.
Diagnostic matrix
Read the result, not the guess.
| What you see | Check next | What it means |
|---|---|---|
| One client is slow; others are normal | Reconnect or restart that client and confirm which eero it uses. | The mesh may be healthy; investigate the client connection first. |
| All clients are slow near one wireless node | Inspect that node’s mesh-strength bars and move it closer to the gateway. | The node-to-node backhaul is the likely bottleneck. |
| Speeds are low everywhere | Test the gateway’s wired WAN path and the ISP connection. | Adding or moving a mesh node will not repair an upstream limitation. |
| Wired node is not reported as wired | Verify cable, switch position, ports, and the app’s connection type. | The node may have fallen back to wireless or the Ethernet path is incomplete. |
Stop conditions
Know when not to keep changing things.
- Stop adding nodes when existing nodes report weak backhaul; improve their path first.
- Do not place a switch between the modem and gateway eero in the supported routed topology.
- Escalate when a node remains poor or offline after a known-good cable, power cycle, and location swap.