These two page types look similar on the surface, but they have different trust contracts. If they blur together, the site stops being reliable.
Official authority lists stay official-first. Directory pages are clearly labeled as non-official and only exist when there is real public inventory to show.
These pages are selected from the utility records most relevant to this guide and ranked by structured evidence.
These routes carry concrete local intent: portal names, annual notices, inspection language, tester gates, and utility-specific report acceptance.
Austin search demand already shows WEIRS language, so the city route should carry the portal, tester, and report-submission path directly.
Use this path when the notice or tester workflow is about SwiftComply report entry, device records, failed tests, or accepted submission proof.
Fort Worth has separate annual-testing, portal, failed-test, and report-submission intent. Do not flatten those into one generic backflow page.
GSC shows VEPO backflow demand landing on Southlake. Keep the annual letter, VEPO records, registered tester search, paperless submission, and device fee close together.
Aurora already has search visibility. Keep the utility workflow, inspection language, and portal path close together.
Anaheim has installation and prevention impressions, so the route should make the official program and tester path easy to reach.
Hillsborough is already getting impressions and clicks. Keep annual-testing, cost, and utility source context linked from the guide layer.
An approved tester page can point to an official utility list or city-maintained lookup. It can also show clearly separated directory inventory, but only below the authority block and without implying endorsement.
A non-official directory can help users discover local testers, but it cannot borrow the language or visual hierarchy of an authority list. If there is no real public inventory, the page should not render.
The common failure mode is taking a city page that mentions tester registration and presenting it as though the site itself maintains the approved roster. That is exactly the ambiguity this project avoids.
Official tester lists and commercial directories must stay separate. Authority pages lead with the governing source; non-official directories are explicitly labeled and only go live when real inventory exists.
What to check when a city, utility, BSI, SwiftComply, VEPO, or water district sends a backflow test notice.
What counts as an official source, how local utility pages override generic assumptions, and how stale pages are re-verified.
What a failed backflow test usually means, how repair and retest sequencing works, and where owners lose time.
How annual backflow test cost changes when the utility requires registered testers, repairs, retests, BSI fees, or online reporting.