Methodology

Our methodology is built around the reader's decision, not the product category. A good recommendation should make it clear who the gear is for, who should avoid it, what trade-offs matter, and what cheaper or simpler alternative may be enough.

How we choose topics

We start with keyword and SERP research, then filter for practical usefulness. A page must fit the site's vehicle-camping mission and help a real camper make a decision. If a keyword has weak data or significantly overlaps an existing page, it becomes a section inside a stronger hub or guide instead of a thin standalone article.

How we build buyer guides

• Decision framework first. Every guide opens with the buyer decision: who this product category is for, who should consider an alternative, and the two or three trade-offs that actually matter.
• Honest sourcing. When a recommendation is based on manufacturer specs, independent expert reviews, and verified owner feedback rather than our own use, we say so. Where we have personal experience with a category, we name the vehicles, conditions, and trips we drew on.
• System thinking. Shelter, sleep, power, cooking, heat, and storage affect each other. Guides cross-link to the adjacent decisions a reader is likely to hit next.

How a single claim moves through the pipeline

To make the abstract concrete: when a buying guide says "this fridge draws roughly X Ah per day in 30 C ambient," that claim is built from the manufacturer's rated draw at a stated ambient temperature, two or more independent test reports (when they exist) that publish their methodology and ambient conditions, and the pattern of owner reports in the forums and subreddits we monitor for that category. If those three sources disagree, the page either reports the range, picks the most conservative number, or drops the claim and explains why we won't commit. We do not publish a specific decibel reading, ice-retention hour count, BTU output, or runtime number when we cannot show our work.

How first-hand reviews will work

Review and roundup pages that present themselves as first-hand testing require documented test days, failure notes, and original images. That means a product guide cannot silently ship as a fake hands-on review. If we have not used a product, we say so on the page and avoid claims that imply ownership or testing. A first-hand sticker - when a future review carries one - will reference the specific dates, vehicles, and conditions the testing ran on, and it will only appear after a minimum of three trip-nights with the product.

How we treat synthesis vs. verified-owner sources

"Synthesis" content is built from manufacturer documentation, independent publications with named editors, and patterns we can verify across multiple owner threads with concrete details (vehicle, year, configuration, failure mode). "Verified owner feedback" means a specific named source - a published long-term review, a forum thread we can link to with a specific post number, or a written interview. We treat single anonymous comments as signal but never as a source on their own. The references block at the bottom of every guide lists the actual links we relied on for that page.

Evaluation criteria

• Fit for the vehicle camping use case
• Safety and installation risk
• Comfort, setup time, and daily usability
• Weight, packed size, and payload impact
• Power or fuel requirements
• Durability, serviceability, and common failure points
• Value compared with simpler alternatives

Editorial independence

Affiliate programs do not decide what we recommend. We disclose paid links, mark them with the appropriate sponsored and nofollow attributes, and keep each page useful even when a reader does not click a buying link. We do not accept payment for positive reviews, ranking placements, or guaranteed inclusion.

Corrections

If you spot an incorrect specification, an outdated safety note, a broken link, or a recommendation that no longer matches the evidence, email hello@vehiclecampingguide.com with the page URL and the section. We log corrections and update the last updated date at the top of the page when content changes substantively.