dependencies

dependencies · Not mentioned by Google

Appears in

• TechArticle

What is it?

dependencies lists the prerequisites a reader needs before following the steps in a technical article. It tells search engines and AI systems what software, hardware, libraries, or knowledge the reader must have installed or understood before the article content applies.

Why this matters for AEO

When a user asks "what do I need before setting up a CI/CD pipeline?" an AI answer engine can pull the dependencies field from the TechArticle markup to list exact prerequisites (Node.js 18+, npm, Git) without parsing the article body. This surfaces precise setup requirements in conversational answers.

What the specs say

Schema.org: Text. Prerequisites needed to fulfill steps in article. schema.org/dependencies

Google: Not mentioned. No dedicated Google structured data page exists for TechArticle. Google does not document rich result support for this property.

How to find your value

• Article body — "Prerequisites" or "Requirements" section
• README file — "Getting Started" or "Installation" section
• Package manifest — package.json, requirements.txt, Gemfile
• Tutorial intro — First paragraph listing what the reader needs

List each dependency as a comma-separated string. Include version numbers when relevant.

Format and code

Type: Text (free-form string, typically comma-separated)

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "How to Set Up a CI/CD Pipeline",
  "dependencies": "Node.js 18+, npm, Git",
  "proficiencyLevel": "Intermediate"
}

Formatting conventions:

• Comma-separated — "Node.js 18+, npm, Git"
• With versions — "Python 3.10+, pip, Docker 24.0"
• Single dependency — "Arduino IDE"

Keep the string concise. Long dependency lists work better as comma-separated values rather than paragraph-style prose.

Webflow implementation

Static pages

Add the JSON-LD block in Page Settings > Custom Code > Footer Code:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "How to Set Up a CI/CD Pipeline",
  "dependencies": "Node.js 18+, npm, Git",
  "proficiencyLevel": "Intermediate"
}
</script>

CMS template pages

Create a Plain Text field in your CMS collection (e.g., prerequisites). Reference it in the template embed:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "{{wf {"path":"name","type":"PlainText"} }}",
  "dependencies": "{{wf {"path":"prerequisites","type":"PlainText"} }}"
}
</script>

In Schema HQ

Your CMS text field to dependencies and outputs it as a properly escaped string in published JSON-LD. is mapped automatically

Real examples

jsonld-examples.com (source):

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "dependencies": "Node.js 18+, npm, Git",
  "proficiencyLevel": "Intermediate",
  "headline": "How to Set Up a CI/CD Pipeline"
}

Schemantra (source):

{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "dependencies": "all, dependencies, needed",
  "proficiencyLevel": "Advanced",
  "headline": "Arduino LED Tutorial"
}

Related fields

• proficiencyLevel — skill level required to follow the article
• headline — title of the technical article
• description — summary of the article content

FAQ

Can dependencies list non-software prerequisites?

Yes. The field accepts any text describing prerequisites. Hardware requirements ("Arduino Uno board"), accounts ("AWS account with IAM permissions"), or knowledge prerequisites ("familiarity with REST APIs") all qualify.

Should dependencies duplicate what the article body already says?

The field should mirror the article's prerequisites section in condensed form. AI engines use the structured field for direct answers, but the article body provides the full context and installation instructions.