TechArticle schema
A technical article: documentation, a how-to guide, a reference chapter.
Where to use it
Developer documentation and technical reference content.
A complete example
Valid as written, with every required property and the recommended ones that carry real information.
{
"@context": "https://schema.org",
"@type": "TechArticle",
"headline": "A headline under 110 characters, because Google truncates past that",
"datePublished": "2026-07-27T00:00:00.000Z",
"dependencies": "Next.js 16 or later",
"proficiencyLevel": "Expert",
"author": {
"@type": "Person",
"name": "A Real Person",
"url": "https://www.seoforsolos.com/about"
},
"publisher": {
"@id": "https://www.seoforsolos.com/#organization"
},
"wordCount": 2400
}Properties
| Property | Status |
|---|---|
headline | Required |
datePublished | Required |
dependencies | Recommended |
proficiencyLevel | Recommended |
author | Recommended |
publisher | Recommended |
wordCount | Recommended |
The three mistakes this type attracts
- 01Ignoring proficiencyLevel, which is one of the few fields unique to this type.
- 02Using it for marketing content that merely mentions technology.
- 03Omitting dependencies on a page that assumes a specific stack.
Related types
Where this appears in the playbook
- Structured data: what each type is for and which ones earned their place.
- The schema graph: composing types into one graph with stable identifiers.
- One JSON-LD script per page, holding one @graph
- Stable @id anchors that cross-reference rather than duplicate
- Optional fields are omitted, never emitted as empty strings
Questions
What is the TechArticle schema type for?
A technical article: documentation, a how-to guide, a reference chapter. Use it on: developer documentation and technical reference content.
Which TechArticle properties are required?
TechArticle requires 2 properties: headline, datePublished. It also recommends 5: dependencies, proficiencyLevel, author, publisher, wordCount.
Does TechArticle produce a rich result?
TechArticle is eligible for a Google rich result when its required properties are present and valid. A validation error therefore has a visible cost in the search result itself.
What is the most common TechArticle mistake?
The most common TechArticle mistake is: Ignoring proficiencyLevel, which is one of the few fields unique to this type.