Wien.gv.at Schema.org Analysis

Complete Deep-Dive: What's Really in the Structured Data?

Analysis Date: January 25, 2026 | Sample: 200 URLs | Live Data Fetch

100%
Schema.org Adoption
11
Schema Types Used
37.5%
Organization Uniqueness
Contents

1. Executive Summary

Key Finding: Organization Schema is Pseudo-Unique

While every Organization schema has a unique @id (100%), the actual content is only 37.5% unique. The same organization name like "MA 10 - Informationsplattform" appears on 35 different pages!

200/200
Pages with Schema.org
11
Different Schema Types
110
Duplicate Organization Content

The Bottom Line

❌ What Looks Unique But Isn't

  • Organization schema: 176 total, only 66 truly unique
  • Same "MA 10" content repeated 35+ times
  • Only differs by @id and dates

✓ What's Actually Unique

  • WebPage: 114/114 unique (100%)
  • Preschool: 35/35 unique (100%)
  • NewsArticle, Event, Project: All unique

2. Schema Types Found on Wien.gv.at

Wien.gv.at uses 11 different schema.org types across its pages:

Organization
176
WebPage
114
ImageObject
52
Preschool
35
CollectionPage
18
Project
11
NewsArticle
7
Event
6
CivicStructure
5
GovernmentOffice
2

Red = Low uniqueness | Green = High uniqueness | Blue = Supporting type

3. Schema Combinations Per Page

Most pages have 2-3 schema types combined:

Schemas Per Page Number of Pages Percentage
1 schema 12 24%
2 schemas 27 54%
3 schemas 11 22%

Most Common Combinations

Schema Combination Pages Example Use
Organization WebPage
21 Standard content pages
CollectionPage
11 Category/overview pages
Organization Preschool
3 Kindergarten pages
Organization ImageObject WebPage
3 Pages with featured images
Organization ImageObject Project
3 Urban development projects

4. Uniqueness Analysis: The Core Finding

Question: Is the schema.org data on wien.gv.at actually unique per page, or is it the same boilerplate repeated?

Method: Two Hash Comparisons

Full Hash (includes everything)

Includes @id, dateModified, datePublished, url

→ Makes every schema look unique

Content Hash (meaningful data only)

Excludes @id, dates, URLs - only actual content

→ Reveals true uniqueness

Results Per Schema Type

Schema Type Total Unique (Full) Unique (Content) Verdict
Organization 176 176 (100%) 66 (37.5%) PSEUDO-UNIQUE
WebPage 114 114 (100%) 114 (100%) TRULY UNIQUE
ImageObject 52 52 (100%) 51 (98%) TRULY UNIQUE
Preschool 35 35 (100%) 35 (100%) TRULY UNIQUE
CollectionPage 18 18 (100%) 18 (100%) TRULY UNIQUE
Project 11 11 (100%) 11 (100%) TRULY UNIQUE
NewsArticle 7 7 (100%) 7 (100%) TRULY UNIQUE
Event 6 6 (100%) 6 (100%) TRULY UNIQUE

5. Organization Schema Deep-Dive

The Problem with Organization Schema

110 out of 176 Organization schemas have duplicate content. They only appear unique because each has a different @id and timestamp.

Most Repeated Organization Names

Organization Name Occurrences % of Total What It Means
"MA 10 - Informationsplattform" 35 19.9% Wiener Kindergärten (Kindergartens)
"MA 21" 13 7.4% Stadtteilplanung (District Planning)
"MA 10" 7 4.0% Wiener Kindergärten
"BV 23" 1 0.6% Bezirksvorstehung Liesing
"BV 14" 1 0.6% Bezirksvorstehung Penzing

What's Actually IN an Organization Schema

// Real example from a kindergarten page { "@context": "https://schema.org", // always the same "@type": "Organization", // always the same "@id": "...#Organization-9364c", // unique (URL-based) "dateModified": "2024-02-01...", // varies "datePublished": "2024-02-01...", // varies "inLanguage": "de-DE", // always the same "name": "MA 10 - Informationsplattform" // REPEATED on 35 pages! }

What's Missing (Would Be Useful for AI)

// Fields that EXIST: ✓ @context ✓ @type ✓ @id ✓ dateModified ✓ datePublished ✓ inLanguage ✓ name // often just "MA XX"
// Fields that are MISSING: ✗ address ✗ telephone ✗ email ✗ contactPoint ✗ description ✗ openingHours ✗ areaServed ✗ parentOrganization ✗ department

6. Real Examples: Same Content, Different Pages

Example: Two Different Kindergartens, Same Organization Schema

Page 1: Kindergarten Teddybär
wien.gv.at/bildung/schadinagasse-9-teddybaer
{ "@type": "Organization", "@id": "...teddybaer#Organization-9364c", "name": "MA 10 - Informationsplattform" }
Page 2: Kindergarten Tabarak
wien.gv.at/bildung/lobmeyrgasse-5-7-kindergarten-tabarak
{ "@type": "Organization", "@id": "...tabarak#Organization-9364c", "name": "MA 10 - Informationsplattform" }
The Problem

Both kindergartens have the exact same Organization content: "MA 10 - Informationsplattform".

An AI reading this cannot tell which kindergarten is which, or get any contact details.

Example: WebPage Schema (Actually Unique!)

Page: Stadtplanung
wien.gv.at/stadtentwicklung/
{ "@type": "CollectionPage", "name": "Stadtplanung", "description": "Themen der Stadtplanung und Stadtentwicklung, Vorhaben..." }
Page: Wohnen
wien.gv.at/wohnen/
{ "@type": "CollectionPage", "name": "Wohnen", "description": "Übersicht über Themen und Beratungsangebote aus dem Bereich..." }
This is Good!

Each CollectionPage has a unique name and description. An AI can understand what each page is about.

7. What Wien.gv.at Does Well

100%
Schema.org Adoption Rate
JSON-LD
Modern Format (Google Recommended)

Positive Findings

8. What Could Be Improved for AI/GEO

Current Gaps

Issue Impact Example
Cryptic abbreviations AI can't understand "MA 10" "MA 10" should be "Wiener Kindergärten"
No contact details AI can't provide phone/email Missing: telephone, email, contactPoint
No address data AI can't locate services Missing: PostalAddress for each location
Repeated Organization content No per-page differentiation 35 kindergartens all show "MA 10"
No service descriptions AI can't describe what services do Missing: GovernmentService schema
No FAQs in schema AI can't extract Q&As Missing: FAQPage for help content

What an AI Sees vs What It Needs

❌ Current: What AI Sees

{ "name": "MA 10 - Informationsplattform", "dateModified": "2024-02-01...", "inLanguage": "de-DE" } AI thinks: "This is about MA 10, some kind of information platform, in German. That's all I know."

✓ Ideal: What AI Could See

{ "name": "Kindergarten Teddybär", "parentOrganization": "Wiener Kindergärten", "address": "Schadinagasse 9, 1110 Wien", "telephone": "+43 1 4000-90123", "openingHours": "Mo-Fr 06:30-17:30" } AI thinks: "This is kindergarten Teddybär at Schadinagasse 9, call +43 1..."

9. Recommendations for GEO Optimization

1. Enrich Organization Schema

{ "@type": "Organization", "name": "Kindergarten Teddybär", // Specific name! "alternateName": "Städtischer Kindergarten", "description": "Städtischer Kindergarten für Kinder von 0-6 Jahren", "address": { "@type": "PostalAddress", "streetAddress": "Schadinagasse 9", "postalCode": "1110", "addressLocality": "Wien" }, "telephone": "+43 1 4000-90123", "email": "kindergarten@ma10.wien.gv.at", "parentOrganization": { "@type": "GovernmentOrganization", "name": "MA 10 - Wiener Kindergärten" } }

2. Use Full Names Instead of Abbreviations

Current → Recommended
"MA 10" → "MA 10 - Wiener Kindergärten"
"MA 21" → "MA 21 - Stadtteilplanung und Flächennutzung"
"BV 23" → "Bezirksvorstehung 23. Bezirk - Liesing"

3. Add GovernmentService for Service Pages

{ "@type": "GovernmentService", "name": "Kindergarten-Anmeldung", "description": "Online-Anmeldung für städtische Kindergärten in Wien", "serviceType": "Kinderbetreuung", "provider": { "@type": "GovernmentOrganization", "name": "Stadt Wien" }, "areaServed": { "@type": "City", "name": "Wien" } }

4. Add FAQPage for Help Content

{ "@type": "FAQPage", "mainEntity": [{ "@type": "Question", "name": "Wie melde ich mein Kind im Kindergarten an?", "acceptedAnswer": { "@type": "Answer", "text": "Die Anmeldung erfolgt online über..." } }] }

Conclusion

Summary for GEO Strategy

Wien.gv.at has excellent schema.org coverage (100%) with modern JSON-LD implementation.

However, Organization schema is pseudo-unique: It looks different per page (unique @id) but the actual content ("MA 10 - Informationsplattform") is repeated 35 times. AI cannot extract meaningful organizational differences.

Good news: WebPage, Preschool, Project, NewsArticle, and Event schemas are truly unique with page-specific content.

Recommendation: Enrich Organization with contact details, full names (not abbreviations), and per-location information. Add GovernmentService and FAQPage schemas for service-oriented content.