Editorial Standards
FitAppliance is a small tool site, so its editorial standard has to be simple enough to maintain and strict enough to protect users. We publish fit guidance only when it can be tied back to project data, public source material, or visible code. When a value is unknown, the better answer is to say less rather than fill the gap with confident copy.
Our claims policy
In April 2026, FitAppliance audited public claims across the homepage, generated pages, documentation and
promotional drafts. The audit is recorded in docs/claims-audit.md. The purpose was to remove
unsupported promises and keep the site aligned with what the tool actually does. Claims about appliance fit,
brand-specific clearance rules, doorway checks and energy star fields stayed because those features exist in the
code and data. Claims about rebate calculations, current stock and current prices were removed or weakened because
the site does not maintain those systems as public features.
The rule going forward is conservative: if a claim cannot be checked in the repository or in a cited public source, it should not appear as a user-facing promise. This applies to page titles, trust strips, schema fields, FAQs, promotional drafts and generated copy. It also applies to words that sound legal or official. FitAppliance can publish clear affiliate disclosure; it should not use broad legal conclusions as marketing language.
How we handle affiliate links
Some outgoing retailer links may be affiliate links. Where affiliate rendering is generated by project code,
links use attributes such as rel="sponsored nofollow noopener" or equivalent sponsored disclosure
patterns. The site also maintains an affiliate disclosure page so users can
see how commissions work.
The current affiliate partners referenced by FitAppliance are JB Hi-Fi, Harvey Norman, The Good Guys,
Appliances Online and Bing Lee. Commission can help pay for hosting and maintenance, but it does not change the
dimensional fit calculation. A product cannot buy its way past the cavity math in
public/scripts/search-core.js. If a retailer link is available for a product, that may make the card
more useful, but it should not be confused with an editorial endorsement.
How we choose what to recommend
FitAppliance is not a review publication. It does not choose a single "best" fridge or dishwasher for everyone. The search result starts with the measured cavity and category. The fit pipeline checks dimensions and clearances, then the user can refine with facets and sort options. The default ranking favours exact physical fit before it considers other signals.
The "Popular in AU" badge is based on project scoring fields such as priorityScore. It is not a
paid placement label. Brand canonicalisation comes from data/brand-canon.json, which normalises
spelling and casing collisions so generated pages do not split the same brand into avoidable variants. That file
currently keeps drop decisions empty; brand removal was deferred so the project does not hide catalogue entries
without enough evidence.
Data accuracy commitments
Appliance data can be wrong for ordinary reasons: source feeds change, model names are inconsistent, dimensions are revised, or a retailer link disappears. FitAppliance treats errors as fixable data issues, not as something to hide. Users can report problems by opening a GitHub issue at https://github.com/fitappliance/fitappliance/issues/new. The public repository is https://github.com/fitappliance/fitappliance.
When a clear data error is reported, the goal is to acknowledge it within 7 days and correct it in the relevant source file or generation script. The correction should leave a trace in GitHub history. If the error affects public pages, the pages should be regenerated rather than hand-edited in one place and forgotten.
Conflict of interest disclosure
FitAppliance may earn commission from retailer links, including links to JB Hi-Fi, Harvey Norman, The Good Guys, Appliances Online and Bing Lee. It does not accept paid brand ranking, paid product reviews, or paid clearance rules. A brand can appear in results because it has catalogue entries and the product fits the user's dimensions. A brand cannot pay to make a product physically fit.
If a commercial relationship is added later and it changes how results are displayed, that change should be disclosed before users rely on it. The safer editorial choice is to separate fit calculation, retailer availability and advertising disclosure instead of blending them into one vague recommendation.
Corrections policy
Corrections should be specific. A useful report includes the product model, the page URL, the incorrect field,
and the source that shows the better value. If the report relates to door swing inference, the relevant code path
is scripts/infer-door-swing.js. If it relates to search behaviour, the relevant path is usually
public/scripts/search-core.js. If it relates to generated brand naming, the relevant path may be
data/brand-canon.json.
Where a correction is accepted, FitAppliance should update the source data or generator, run the test suite, regenerate affected pages and keep the commit history visible. If a correction is not accepted because the evidence is unclear, the response should explain what is missing.
Generated copy review
Many FitAppliance pages are generated from templates because the site covers hundreds of brand, cavity, doorway, comparison and guide routes. Generated pages still need editorial rules. The copy audit checks for risky phrases, unsupported claims and repeated boilerplate. Schema tests check that structured data is valid JSON and avoids fake ratings or fake review counts. Sitemap and link-graph tests check that pages are reachable after generation.
Templates should not add claims merely because they sound helpful. A template may say that a page uses brand-specific clearance rules if the page is generated from the clearance data. It should not say a product is recommended by experts, approved by a government body, or available at a current price unless that evidence exists in the repository. The same rule applies to small UI labels as much as long guide pages.
Open source review
The repository is public at https://github.com/fitappliance/fitappliance. Public source does not guarantee perfect data, but it lets users and reviewers inspect the system rather than trust a black box.
Last reviewed
This page was last reviewed on 26 April 2026. Material policy changes should be visible in the GitHub commit history.