Trust
Editorial policy
This editorial policy explains how Vehicle Plainly researches topics, uses verified sources, writes with limits, handles corrections, and keeps commercial relationships separate from educational claims.
Editorial mission
Vehicle Plainly publishes cautious, useful guides about vehicle research. Accuracy and reader safety matter more than aggressive SEO claims.
Vehicle Plainly is an independent informational publisher. We explain VIN lookup, vehicle history, title brands, recalls, and used-car research with limits-first language. We are not a government agency, DMV, vehicle history report provider, insurer, lender, dealer, or Consumer Reporting Agency.
Source hierarchy
When making factual claims, we follow this order:
- Official government or agency sources with verified registry entries
- Verified educational guidance tied to allowed claims in the source registry
- General limits language when a specific claim is not source-backed
- Commercial provider mentions only with independence and without rankings unless methodology is published
Verified source registry
Production guides should cite sourceIds from the verified registry in frontmatter and align body claims to allowedClaims for those sources.
NEEDS_REVIEW and HOLD sources are not used for production claims until separately verified.
Government and official sources
Examples include NHTSA VIN decoder and recall lookup tools, NMVTIS educational pages about report indicators, and FTC used-car buying guidance.
We describe what these sources say they provide. We do not imply government endorsement of Vehicle Plainly.
Commercial data providers
Vehicle history reports may include NMVTIS information when obtained through approved providers. We may explain that context without recommending a specific vendor.
Any future affiliate or commercial link must be disclosed and must not change factual claims.
Why we write with limits
Vehicle data is incomplete by nature. Limits-first writing prevents readers from treating a lookup as proof of a clean history, safe condition, or owner identity.
Claim discipline rules
Authors and editors should avoid unsupported certainty.
- Prefer may show, can help explain, and records can be incomplete
- Do not use guarantee, prove, full event-by-event history claims, or every record
- Do not publish owner lookup or private registration access
- Do not claim Vehicle Plainly accesses NMVTIS or DMV directly
- Do not provide legal, insurance, lending, or mechanical diagnosis
Safety and privacy boundaries
We do not publish people-search-style content, license plate owner lookup, or private DMV record access guides.
High-risk topics remain in hold until source packs and safety review support publication.
Batch production
Guides are prepared in batches of related routes so keyword overlap, internal links, and source maps stay coherent.
Prompt packs, import QA, and content-quality verifiers reduce claim drift between related pages.
Draft, preview, and index posture
New guides start as draft MDX with noindex posture. Internal preview may render drafts for editorial review.
Public linking and indexing happen only after explicit approval. Sitemap inclusion and index flags remain locked until a separate launch decision.
Human and automated QA
Batch verifiers check sourceIds, forbidden phrases, internal links, MDX shape, and safety patterns.
QA findings are fixed with surgical edits rather than full rewrites when the base draft is already sound.
Internal linking policy
Guides link to related routes in the same cluster and to trust pages where boundaries need reinforcement.
We do not link to owner lookup, held routes, or comparison/review URLs without a published methodology.
Corrections policy
Report corrections to contact@vehicleplainly.com with the URL, issue, and source if available. Material factual corrections are prioritized. Typographic or clarity fixes may ship with routine updates.
Update policy
Guides include last-updated metadata through route definitions. Substantive source or claim changes trigger a review pass and may update the lastModified date.
Affiliate and commercial independence
Editorial content is independent from commercial relationships. Future affiliate links, if any, require disclosure and must not imply official endorsement or provider ranking.
When sources are missing
If a route lacks verified sources, it stays in prompt hold or draft hold rather than publishing unsupported claims.
We soften or remove claims rather than invent facts.
Frequently asked questions
- Does Vehicle Plainly use AI to write guides?
- Guides may be drafted with assisted workflows, but publication requires human QA, source maps, and automated verification. Unsupported claims are removed or softened before draft import.
- Can I request a new topic?
- You may send suggestions through contact. We prioritize topics with verified sources and clear reader utility within our risk taxonomy.
- How do you handle conflicting sources?
- We describe the conflict, cite the verified source scope, and avoid false certainty. Readers are directed to official channels for binding decisions.
Related pages
Last updated: