Water Verdict logo

Private Well Decision Engine

Water Verdict

Public tool surface

Private Well Water Decision Tool

Wide public surface, narrow decision wedge. Start from one clue, get the next safe path, and use longer reading only when the first routing pass is not enough.

Start With A Lab Result I Only Have A Symptom
Tool first Guide second Private result wedge

Inputs

Pick the clue you already have

The first move should be choosing an input, not opening a long article. Each route narrows the problem before product research or treatment comparisons begin.

Lab result

One analyte line is enough to start

Enter analyte, value, and unit. Add qualifier, state, household, or companion lines only when they materially change the next step.

Symptom

Start from what you can observe

Smell, stain, taste, or nuisance signals can still route to safer testing steps even when the data is incomplete.

Trigger

Use the event that changed the water

Floods, repairs, drought shifts, or transfer timing are often strong routing signals before a clean report exists.

State context

Apply local rules only when they change the answer

State guidance and home-sale timing belong in the decision path when they alter what should happen first.

Outputs

What the engine gives back

The output is not a generic article. The engine narrows the next move, the follow-up tests, and the places where you should slow down before buying anything.

Decision call

What matters first

The result surface separates health-risk routing from nuisance routing so one symptom or one report line does not drive the wrong purchase.

Recommended tests

What to verify next

You get the ordered next tests, retest logic, and state-aware handoff when local programs or certified labs matter.

Treatment hold

What not to buy first

The tool deliberately slows category shopping until scope, claims, and evidence are clear enough to compare real options.

Context links

Why the routing happened

Method pages, state pages, and public guides sit behind the output to explain the reasoning after the route is already clear.

Wide Surface

Public pages should feed the tool, not replace it

This is the broad surface strategy: public pages stay indexable where they earn it, but they should route into the wedge instead of becoming the product by accident.

State router

Regional family

Use state pages when geology, required panels, or certified-lab paths change what should happen first.

 Method router

Authority family

Use method pages to choose the right decision path, not to browse in the abstract before starting.

 Transaction route

Home-sale by state

Lead with transfer timing and state context when they materially change testing scope and urgency.

 Decision page

Nitrate example page

A strong public page should still push the user toward diagnosis, scope, and result-specific next steps.

Boundary

What stays public and what stays private

The public surface should be crawlable enough to explain the product. The result wedge should stay private enough to keep personalized outputs and saved views out of search.

Public

This indexable tool page

Search engines and first-time visitors can understand the inputs, output shape, and the decision logic without needing a personal result page.

Public

Router pages and high-intent guides

Regional, authority, and selected decision pages remain the wide surface as long as they keep routing behavior ahead of long reading.

Private

Entry flows under /tool/*

The actual intake routes remain non-indexed so Google sees the product shape, but not user-specific form states as the main crawl surface.

Private

Saved results under /result/saved/*

Personalized output, saved views, and downloadable result artifacts stay out of search and out of the public content layer.

Start now

Use the narrow wedge directly

These routes go straight into the decision wedge. Use them when you already know which clue is strongest.

Start

Lab result entry

Best when you have one report line and want the next test or treatment hold decision fast.

 Start

Symptom entry

Best when the problem is visible or obvious but the lab data is partial, stale, or missing.

 Start

Recent change entry

Best when the event itself changed what should happen first, even before a new certified report is in hand.

 Route

State and home-sale path

Best when local requirements, program guidance, or real-estate timing should define the testing sequence.

Lead capture

Need help choosing the first tool path?

Leave an email if you have a vague clue, a home-sale situation, or a confusing report and want help choosing the right starting input.