1 · Define the job
Each page begins with the user’s actual task—amount, deadline, credit constraint, income setup, repayment horizon or product structure—so separate URLs do not exist only for wording variations.
Every product page is built around the decision a user is trying to make: amount, timing, eligibility, state rules, total cost, repayment and provider responsibility.
We separate product labels from actual user needs such as urgent cash, a fixed amount, a payment schedule or a credit-profile constraint.
Where possible, calculators show payment, finance charge, APR-equivalent, total repayment, fees or net proceeds in the same decision.
State-sensitive products use location as an input. Cross-checked regulator data is distinguished from broader legal summaries.
The identified provider's disclosure controls final pricing, approval, funding, repayment and servicing.
Pages show review dates and contextual source links near the block they support. If a law or provider term can change materially, the page should not present an old figure as a guaranteed current offer.
Editorial standards →Each page begins with the user’s actual task—amount, deadline, credit constraint, income setup, repayment horizon or product structure—so separate URLs do not exist only for wording variations.
Regulators, statutes, provider disclosures and primary historical records are prioritized. Secondary sources are used for discovery or context and should not override a current primary source.
Calculators expose the variables that materially change the outcome: amount, term, APR/fee, dates, state rules, income, DTI, funding rail, inquiry method or product type.
The team checks the page for intent coverage, mathematical consistency, state/source status, trust language, usability, internal linking, metadata/schema and whether the request flow preserves the selected context.