A guest WiFi deployment should be tested like any other customer-facing service. Do not wait until opening day to discover that the SSID is missing from one AP, guests can reach an internal device, or the portal works only on one phone.
Use this checklist with real client devices at the venue.
1. Test the SSID and VLAN
Walk through every guest area and confirm that the intended SSID is visible where expected.
Verify:
- The client receives an IP address.
- The client is assigned to the intended guest network or VLAN.
- AP uplinks carry the required VLAN.
- The guest network has working DNS and internet access.
- Staff and private SSIDs remain available and separate.
Ubiquiti notes that incorrect VLAN tagging on an upstream switch can prevent clients from connecting to a WiFi network. (help.ui.com)
2. Test isolation with two devices
Connect two test devices to the guest network. Confirm that they cannot communicate with each other unless the venue specifically requires peer-to-peer features.
Then test access to representative internal resources, such as:
- Gateway or management addresses
- Staff network services
- Printers
- Cameras
- Point-of-sale systems
Public guest WiFi should be isolated from internal networks. UniFi provides separate controls for network isolation, switch ACLs, and AP-level client isolation. (help.ui.com)
Do not treat a successful internet speed test as proof that isolation is working.
3. Test the customer journey
Use a fresh phone and laptop. Record what a first-time visitor experiences:
- Join the guest SSID.
- Open a browser.
- Confirm the expected authentication or landing experience.
- Complete the required step.
- Confirm that ordinary browsing works afterward.
- Close and reopen the browser.
- Repeat from another operating system.
If an external portal is used, confirm that authorization completes before the guest is sent to the final destination. UniFi’s external-portal flow begins with an unauthorized guest and ends with client authorization through the Network API. (help.ui.com)
4. Walk the venue and test coverage
Test from the areas where guests will actually sit, queue, eat, work, or wait—not only beside an AP.
Record:
- Signal strength
- Connection stability
- Roaming between APs
- Loading time for ordinary websites
- Performance in busy areas
Ubiquiti’s current troubleshooting guidance identifies signal strength, airtime, interference, retries, and channel congestion as useful indicators. It describes signal stronger than approximately -60 dBm as excellent, -60 to -70 dBm as acceptable, and below -80 dBm as likely to be unstable. Treat these as diagnostic guidance rather than a substitute for an on-site survey. (help.ui.com)
5. Test roaming deliberately
Walk slowly through the venue while streaming or maintaining an active session. Watch for disconnects when moving between AP coverage areas.
Avoid changing Minimum RSSI or roaming settings immediately before opening without testing again. Ubiquiti warns that poorly tuned Minimum RSSI can repeatedly disconnect clients and create instability. (help.ui.com)
6. Test busy-period behavior
If possible, run a controlled load test with several devices. Check whether guest traffic affects staff-critical services.
Review:
- Per-client or SSID speed limits
- Airtime utilization
- High-interference areas
- Excessive broadcast or multicast traffic
- Application policies for bandwidth-heavy traffic
Ubiquiti recommends tools such as AirView, Client Inspector, and Environment views to investigate RF and airtime conditions. (help.ui.com)
7. Test the failure path
A good deployment should fail clearly and recover predictably. Test what happens when:
- A guest enters an invalid portal value.
- The portal service is temporarily unreachable.
- A device leaves and rejoins the network.
- A guest moves between APs.
- The internet connection is interrupted and restored.
- The venue uses a restrictive firewall or DNS policy.
Record the user-visible result and the operator action required to recover.
8. Capture evidence for handover
Before opening, save:
- SSID and VLAN names
- AP coverage areas
- Isolation test results
- Test devices and operating systems
- Portal or authentication behavior
- Speed and signal observations
- Known limitations
- Date and time of the test
This gives the venue owner and support team a baseline for future changes.
Final sign-off checklist
- Guest SSID appears in all intended areas
- Guest clients receive valid network settings
- Guest VLAN is carried across the network
- Guests cannot reach protected internal resources
- Guest-to-guest communication behaves as intended
- Portal or authentication works on multiple devices
- Internet access works after authentication
- Coverage and roaming are acceptable
- Busy-area performance has been checked
- Failure and recovery paths are documented
- Results have been handed over to the venue operator
Next step
Once the guest WiFi experience is tested, the venue can evaluate whether a hosted marketing portal fits its customer journey.
Want to assess LiquidEdge for a hosted UniFi portal? Contact us for an availability check and deployment discussion.
Self-service account creation and proposed plan terms should be confirmed before any signup or pricing commitment is presented.