
Editorial Guidelines
Our mission is to share vehicle information, driver data, and thoughtful content with our audience. We strive for accuracy, with every piece based on in-depth research, official pressroom specs, market data, and driver surveys.
Writers & Drivers First
Like many brands that use AI to enhance their platforms, Very Driver employs advanced AI tools for research, drafting, and organization. We encourage writers to use them, but they do not replace the human behind the work. We are a research organization that values the drivers behind the vehicles and the writers and researchers behind the content. We aim to meet Google's E-E-A-T standard and keep our content genuinely helpful to readers.
Outside of the guidelines below, you have 100% editorial and creative freedom.
Written in Third Person, With Room for Commentary
❌ "We love the Durango SRT Hellcat because of its 710 horsepower."
✅ "The Durango SRT Hellcat makes 710 horsepower."
Listicle exception: "If you are hauling the family, the Explorer wins."
First-person exception: Additional commentary may be inserted into any of the articles, at which point you may write "I" in first person, then return to third. Ideally, limit commentary to the intro and outro sections of each piece.
Additional Voice & Writing Rules
- No em dashes. Ever. Break the sentence up or use a comma.
- No sentences starting with "That."
- No AI filler or fluff opener lines. First sentence states the news.
- No colons: inside sentences. (Fine in price lists like "LX: $39,190.")
- No caveats; if a claim cannot be verified from a reputable source, do not include it.
No from X to Y" and "whether X or Y"
❌ "From city streets to open highways, the Durango does it all."
✅ "The Durango SRT Hellcat makes 710 horsepower and tows up to 8,700 pounds."
❌ "Whether you are towing or commuting, this SUV has you covered."
✅ "The Telluride tows up to 5,000 pounds and returns 35 mpg combined as a hybrid."
❌ "When it comes to affordable EVs, Ford is making big moves."
✅ "Ford named its new midsize electric pickup the Fathom, starting at $28,350."
- When applicable, affiliate disclosures are pasted before purchase links verbitm
Structure
- Short declarative sentences. One fact each.
- Open with a 2 to 4 sentence lede that leads with the biggest fact: the price, the headline number, or the record.
- Keep paragraphs to 1 to 3 sentences.
- Explain jargon and names in plain terms.
Headers
- Single car (Overviews, Enthusiasts): short labels. "Powertrain," "Interior," "Safety." Use a hook header when a feature is the story ("No Start Button").
- Data pieces: full search term. "How Many Cars Are Scrapped Each Year in the US."
- Guides, Products: how-to phrasing, one action each. "What to Do When You Hydroplane."
- Industry: narrative for history ("Born on the Track," "V8 Era"), search-term for data.
Titles
Titles are short, usually no longer than 2 lines on the page. They should pull a click through the strength of the topic itself, not through hype or tricks. The best titles double as the exact phrase someone would type into Google or ask an AI.
❌ Too clickbait: "You'll Never Believe How Many Drivers Are Uninsured"
❌ Too complex: "Examining the Rising Share of Uninsured Motorists Across the United States"
✅ Just right: "How Many Drivers in the US Are Uninsured"
No colons in titles and Title Case.
Numbers & Units
Imperial first (mph, pounds, inches, miles). Keep metric only when it's the maker's native spec (kWh, kW, Nm, mm).
Write torque as "lb-ft." with the period.
Use "hp" lowercase in body, "HP" in titles.
Always use the % symbol, never "percent."
Examples: $43,675 / 15.4% / 60 mph / 6.2 seconds.
Sourcing
- Every stat ties to a named primary source, linked inline (NHTSA, IIHS, USGS, manufacturer newsrooms). No aggregators.
- Verify against the primary source before drafting. Always pull the newest year of the data.
- Attribute maker claims to the maker ("Ford says"), don't state them as fact.
- Caption every image: "Media: [Source]." Label AI images "AI Generated Media."
Photo Captions
Structure by type
- Vehicle overview: lede, then Powertrain, Range or Fuel Economy, Capability, Interior, Tech, Safety, Colors/Assembly, Trims and Pricing, closing debut or "what it means."
- Data piece: short, lead with the number, a few stat-driven H2s.
- Listicle: number each entry as an H2, add an Honorable Mention, close with "Which One to Buy" or the other side.
That's the whole thing as a page. Want it as an HTML file formatted for Ghost so you can drop it straight in?