How we work

How We Research and Verify

Every page starts from a real gardening question, then gets built from relevant horticultural evidence and practical context. Here is our process.

Last updated
Status
Editorial information

Our method begins with the decision a gardener must make. We define the plant, setting, risk, and likely failure mechanism before research, then trace each material recommendation to evidence that fits those conditions.

1. Frame the Decision

Research cannot start from a question as broad as “how do I care for this plant?”

We break it into decisions about identifying suitable light, judging when soil moisture calls for water, knowing which temperature marks real risk, placing a plant for its mature size, and reading the visible clues that separate two likely problems. We also state whether the plant is indoors, in a container, in a bed, or in a landscape, because those settings change root temperature, drainage, exposure, and recovery.

Before drafting, the page needs a specific distinction from its nearest siblings and a primary failure mechanism.

A succulent that stores water in its leaves should not inherit the same watering explanation as a thin-leaved tropical. A young tree with circling container roots needs different establishment priorities from a bare-root whip.

That framing is what stops a category template from replacing plant behavior.

Method in practice: a recommendation is ready only when the evidence supports the wording, the reader can identify the controlling condition, and the page names a safer next step when observation alone cannot settle the question. A long bibliography cannot repair a claim that lost its species, dose, climate, or risk boundary.

We also record negative findings and rejected sources. A study may use a different plant, greenhouse setting, concentration, or measured outcome, and a regional calendar may not transfer across climates.

Keeping the reason for a rejection stops a later draft from restoring an attractive but inapplicable number.

Where indirect evidence is the best support available, the prose names the inference instead of presenting it as a universal tested instruction.

Search visibility does not determine truth. Queries tell us the language and decisions readers bring to a page, while the source hierarchy controls the factual conclusions.

That separation lets a page answer the real question without copying the oversimplification that made the query popular.

2. Use a Source Ladder

No source type wins every question.

A current pesticide label owns permitted use and safety directions. A botanical institution can settle accepted identity and native range.

University extension guidance connects research to home landscapes and regional conditions. Peer-reviewed literature can explain physiology or compare a treatment, though a narrow experiment may not justify a universal home-garden instruction.

Source groupBest used forCheck before relying on it
Government and product labelsRegulation, hazards, invasive status, permitted product useJurisdiction, effective date, crop or site, and current label
University extensionRegional cultivation, diagnosis, integrated pest managementClimate, publication date, named plant, and intended audience
Scientific literatureMechanisms, measured effects, treatment comparisonsSpecies, sample, method, setting, and limits of the result
Botanical institutionsIdentity, taxonomy, distribution, established cultivationAccepted name, regional scope, and whether advice is collection-specific
Experienced horticultural referencesTechnique, workflow, and useful field observationsWhether material claims can be confirmed independently

3. Build an Evidence Trail

Research notes connect each consequential claim to the source that supports it. We capture the plant or treatment studied, the conditions, the measured outcome, and any boundary the final sentence must keep.

Sources are not decoration added after a draft, because they decide what the draft is allowed to say.

  • The source discusses the named plant, a clearly stated group, or an explicitly limited analogy.
  • The claim keeps the source’s climate, site, life stage, dose, timing, and uncertainty where those details matter.
  • A recommendation distinguishes evidence from our practical inference.
  • Links point to the useful source page or document, not an unrelated organization homepage.
  • A reader can understand the instruction without treating a citation count as proof by itself.

We also use internal links as decision paths. A link should help the reader identify a plant, compare alternatives, understand a method, or investigate a symptom.

We do not add a link only to raise the count.

4. Reconcile conflicting guidance

Two reputable sources can recommend different watering intervals, planting dates, or pruning windows and both can be reasonable within their settings. We compare species, cultivar, climate, production system, soil, container size, plant maturity, experimental method, and the outcome each source was trying to improve.

When the difference can be explained

We state the conditions behind each recommendation and give the reader an observable way to choose. A cool-climate planting window, for example, may not transfer to a hot region where root establishment follows a different seasonal pattern.

When uncertainty remains

We narrow the claim, use a defensible range, or say that evidence is mixed. We do not average incompatible numbers or present the most precise figure as the most reliable one.

5. Draft around plant behavior

Each major section should open with the behavior or diagnostic that makes the named subject different.

The care principle is explained fully once, in the section that owns it. Later sections can point back to it without repeating the same warning in new words.

  1. Name the mechanism. Explain what roots, leaves, buds, stems, soil, weather, or a pest are doing.
  2. Translate it into an observation. Tell the reader what they can inspect without specialized equipment.
  3. Connect the action. State what to change and how the observed condition controls timing or amount.
  4. Set a reassessment point. Describe the response to expect and what would justify a different diagnosis.

That sequence is what prevents unsupported certainty.

A symptom such as yellow leaves is not a diagnosis, because it can follow root oxygen loss, drought, nutrient limits, normal aging, cold injury, or pest damage. The draft has to use pattern, location, timing, and recent changes to narrow the possibilities.

6. Apply Risk-Based Checks

Advice about ingestion, toxicity, pesticides, fertilizers, chainsaws, ladders, structural trees, fire, utilities, wildlife, and invasive plants requires stronger boundaries than a styling suggestion. We check current labels and local authority where relevant, keep doses and safety language tied to their source, and tell the reader when an in-person professional must own the decision.

We do not diagnose a medical or veterinary emergency, certify that a plant is safe to eat, or confirm that a tree is structurally sound from a web description.

When an error could injure a person, animal, plant, or property, uncertainty must remain visible.

7. Check the page as a decision tool

Claim check

Does the wording go farther than the cited evidence?

Context check

Are climate, setting, stage, and important exceptions present?

Structure check

Does each section own one job without repeated advice?

Action check

Can a reader observe, act, and reassess safely?

We also validate page structure, links, tables, headings, accessible labels, and mobile layout. Automated tools may help organize research and drafting, but their output is not evidence.

The Editorial Policy describes that separation in more detail.

8. Follow Update Signals

A new source, changed label, revised regulation, broken link, reader report, or material site change can trigger review.

We first identify whether the problem belongs to the factual claim, editorial standard, content contract, page renderer, or generation process. The clean fix goes at that owner layer, so the same mistake does not survive somewhere else.

Confirmed factual errors are corrected on the affected page. Significant revisions update the displayed date.

A reader can report the page URL, disputed passage, and supporting source through the correction route.

We cannot promise that every suggestion changes a page, but specific evidence gives us a clear path to investigate.