XooCode(){

TechArticle Schema Generator

Fill out a form. Get valid TechArticle JSON-LD.

A form-driven builder for schema.org TechArticle markup with a live JSON-LD preview that updates as you type. TechArticle extends Article with two properties that matter for technical content: proficiencyLevel (Beginner or Expert) and dependencies (prerequisites the reader needs before starting). The generator ships with a seed example based on the XooStructured integration guide. Switch to Full coverage mode for the complete property vocabulary, including paywall metadata and @id author references. Everything runs in your browser, nothing is sent to XooCode.

TechArticle form

Title of the tech article. Google truncates at 110 characters. 51/110

Summary of the tech article. Google truncates at ~160 chars in the SERP.

Images (three aspect ratios)

Google's Article rich result requires images in three aspect ratios: 1:1 (1200x1200), 4:3 (1200x900), and 16:9 (1200x675). All three are recommended for full rich result eligibility.

Square. Minimum 1200x1200px.

Landscape. Minimum 1200x900px.

Widescreen. Minimum 1200x675px.

Canonical URL of the article page.

When the article was first published.

When the article was last updated.

Emits as nested Person. In Full mode you can use @id instead.

Emits as nested Organization.

Live JSON-LD output

schema.org/TechArticle
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "TechArticle",
  "headline": "Integrating XooStructured Markup: A Developer Guide",
  "description": "Step-by-step guide to adding XooStructured JSON-LD markup to your site. Covers installation, configuration, and testing with Google's Rich Results Test.",
  "image": [
    "https://xoocode.com/docs/images/xoostructured-guide-1x1.jpg",
    "https://xoocode.com/docs/images/xoostructured-guide-4x3.jpg",
    "https://xoocode.com/docs/images/xoostructured-guide-16x9.jpg"
  ],
  "url": "https://xoocode.com/docs/xoostructured-integration",
  "datePublished": "2026-01-10",
  "dateModified": "2026-03-22",
  "author": {
    "@type": "Person",
    "name": "XooCode Docs Team"
  },
  "publisher": {
    "@type": "Organization",
    "name": "XooCode Docs"
  }
}
</script>

Updates as you type. Empty fields are omitted from the output. Click the copy icon above to copy the full <script> tag ready for pasting into your HTML head.

How to use the generator

The tool is a two-pane split: a form on the left, a live JSON-LD preview on the right. Type into any field and the preview updates immediately. When you’re done, click the copy icon in the preview header and paste the <script> block into your page’s <head> tag. That’s the whole workflow.

  1. 1

    Start from the seed

    Click Load example above the form. It populates the fields with the XooStructured integration guide: a developer-facing tutorial with headline, description, three image URLs, dates, author, and publisher pre-filled. Use it to see what a fully-populated TechArticle looks like, then clear and start with your own content.
  2. 2

    Pick coverage mode

    The Coverage dropdown has two settings. Essential shows the minimum viable fields: headline, description, image triple, URL, dates, author, publisher. Full keeps all of that and adds proficiencyLevel, dependencies, @id author toggle, paywall metadata, articleBody, wordCount, inLanguage, and more.
  3. 3

    Fill in the image triple

    Google’s Article rich result requires images in three aspect ratios: 1:1 (1200x1200), 4:3 (1200x900), and 16:9 (1200x675). All three fields accept a URL. The output emits a single string when only one is provided and an array when two or more are filled.
  4. 4

    Copy the output

    The preview pane shows the full <script type="application/ld+json"> wrapper with syntax highlighting. Click the copy icon to grab it and paste into your page head. Test with Google’s Rich Results Test before publishing.

proficiencyLevel and why it matters

proficiencyLevel is the one property that makes TechArticle worth using over plain Article. It accepts "Beginner" or "Expert" as values. Google uses this to match technical content to the right audience. A beginner searching “how to deploy a Node.js app” should not see an article about Kubernetes cluster autoscaling. TechArticle with proficiencyLevel helps Google make that distinction.

Without the type and the property, Google has to guess from the content complexity, which it does less reliably. The signal is especially useful for documentation sites that publish both introductory tutorials and advanced reference material under the same domain. When every tutorial page carries proficiencyLevel: "Beginner" and every reference page carries proficiencyLevel: "Expert", Google can rank the right page for the right query without having to infer difficulty from vocabulary and sentence structure alone.

Dependencies and prerequisites

The dependencies property lists what the reader needs before starting. Free text, not structured. Write it the way you would write a “Prerequisites” section at the top of a tutorial: “Node.js 18+, npm, a schema.org account.” Google doesn’t render this in a rich result, but AI crawlers (ChatGPT, Perplexity, Claude) use it to decide whether to recommend the article to someone who asks about a technology stack they haven’t set up yet.

Keep the value short and concrete. List the tools, libraries, and accounts the reader will need, in the order they’ll need them. If a prerequisite has a minimum version, include it. If a prerequisite is optional (nice to have but not required), leave it out of dependencies and mention it in prose instead. The property is meant to answer one question: “Can I follow this guide right now with what I already have installed?”

Dates for technical content

Article markup supports three date properties: datePublished, dateModified, and (in Full mode) dateCreated. For technical documentation, dateModified is the most important of the three. Outdated technical docs are worse than no docs. When you update a guide for a new API version, update dateModified. Google shows “Updated:” in the SERP, which tells developers the guide covers the current version before they click.

datePublished records the original publish date and rarely needs changing. dateCreated captures the internal draft date (useful for editorial workflows where a doc sits in review for weeks before publishing). All three accept ISO 8601 date strings. The generator uses date pickers that emit YYYY-MM-DD format, which is the safest choice for cross-browser and cross-crawler compatibility.

What this generator isn't

The TechArticle Schema Generator is a tightly-scoped authoring tool. Knowing what it doesn’t try to do will save you time hunting for features that were never supposed to exist.

It IS a TechArticle builder

Full TechArticle vocabulary: headline, description, image triple, dates, author, publisher, proficiencyLevel, dependencies, paywall, and every inherited Article property in Full mode.

It is NOT an Article builder

Article, NewsArticle, and BlogPosting each have their own generator. Use the Article generator for non-technical content.

It IS proficiencyLevel aware

The generator exposes proficiencyLevel as a dropdown restricted to the two values Google actually reads: Beginner and Expert. Pick one and the property emits in the output.

It is NOT a code documentation generator

TechArticle describes a written tutorial or guide, not API reference docs or code comments. For auto-generated API documentation, consider tools like TypeDoc or JSDoc instead.

It IS Essential/Full aware

Essential mode shows only the minimum viable fields. Full mode exposes proficiencyLevel, dependencies, @id author, paywall, articleBody, wordCount, inLanguage, and every other inherited property.

It is NOT a Rich Results Test

Run the JSON-LD through Google's Rich Results Test afterwards to catch value-level mistakes the form can't see (broken URLs, invalid dates, etc).

Authoritative sources behind the TechArticle vocabulary

The generator’s behaviour is sourced from primary documentation. These are the documents to consult when you need to verify anything the tool produces.

  • schema.org/TechArticle. The canonical vocabulary definition. TechArticle inherits from Article which inherits from CreativeWork which inherits from Thing, so the full property list is much longer than the TechArticle-specific section.
  • Google Article structured data documentation. The current required and recommended property lists for all Article subtypes, including TechArticle. Google’s image requirements (three aspect ratios) and headline truncation rules are documented here.
  • Google Rich Results Test. Run your generator output through this to confirm the markup is valid and eligible for the Article rich result.