“Include” and “add” feel interchangeable until a single misplaced keyword deflates your SEO, breaks your React build, or triggers a legal clause. The difference is not academic—it decides whether your code compiles, your page ranks, or your contract is enforceable.
Below is a field guide to the two verbs as they appear in programming, search optimization, product design, and legal drafting. Each section gives you live examples you can paste into your own work today.
Semantic Core: Why Google Hears “Include” as Open and “Add” as Closed
Google’s NLP model treats “include” as a non-exhaustive list signal and “add” as an explicit delta. When the query is “best foods that include magnesium,” the algorithm expects a sampling; when the query is “add magnesium to diet,” it expects a prescriptive step.
Place “include” in a heading and you silently tell the crawler that other items exist; use “add” and you imply the page will show the single, definitive method. This micro-distinction can push you from position #11 to #6 without a single extra backlink.
Test it yourself: search “include keyword” versus “add keyword” and notice how the SERP shifts from roundup articles to how-to tutorials.
Snippet Engineering: Crafting 155-Character Descriptions That Match Intent
For pages that “include” examples, write meta descriptions that hint at breadth: “7 vegan desserts that include hidden veggies—no one will guess.” For pages that “add” something, promise a transformation: “Add hidden veggies to any dessert in 3 minutes—kids approve.”
Keep the verb consistent between H1 and meta description; mixed signals lower CTR by up to 18 % in split tests.
JavaScript Imports: When import Adds and When include Would Crash
ES6 modules always add bindings to scope; they never merely include them for optional reference. Writing `import {a} from ‘./a’` creates a live link, not a loose association—tree-shaking relies on this hard fact.
Old-school `