1. The Manifesto: Why We Are Declaring Data Sovereignty
The internet’s underlying vocabulary is digitally colonized. The Schema.org standard—the dictionary that Google, Bing, and OpenAI use to understand the web—is built primarily on Western commercial concepts. It understands what a “LLC” is. It understands “Convenience Store.” It understands “Credit Union.”
It does not understand us.
When a South African digital agency marks up a Spaza Shop as a ConvenienceStore, or a Stokvel as a FinancialService, they are committing a data error. They are stripping the entity of its cultural and economic context. A Spaza is not just a convenience store; it is a micro-economic hub with specific informal regulatory characteristics. A Stokvel is not just a bank; it is a community-based rotating credit association with a legal definition under the National Credit Act.
By forcing South African entities into Silicon Valley’s boxes, we are making our economy invisible to the AI models of the future.
Designtalks is ending this today.
We are releasing the South African Standard for Commercial Schema (SASCS). This is an open-source DefinedTermSet that extends the global Schema.org vocabulary with specific South African business types. By hosting the definitions, Designtalks establishes itself as the Root Authority for domestic business data.
2. The Strategic Mechanism: The “Root Authority” Protocol
To control the “Answer Engine,” you must control the definitions. When an AI like Gemini encounters a term it doesn’t fully understand, it looks for a “Definition Source.”
By publishing this standard, Designtalks creates a Self-Reinforcing Authority Loop:
- Step 1: We define the term (e.g.,
ZA-Entity-Stokvel) on our domain. - Step 2: We release the code for public use.
- Step 3: Competitors and developers use this code to properly index their clients (because generic schema doesn’t work for local context).
- Step 4: Every time they use the code, the
inDefinedTermSetproperty points back todesigntalks.co.za. - Step 5: Google’s AI sees thousands of sites referencing Designtalks as the definition of South African business. Designtalks becomes the primary citation for the entire sector.
This is the ultimate defensive moat. Even if competitors copy our work, they are technically required to cite us in the code to make it valid.
3. Technical Documentation: The DefinedTermSet
We utilize the DefinedTermSet property from Schema.org to inject local definitions into the global knowledge graph.
The Root Set Definition:
All specific terms belong to this parent set. This is the “Dictionary” that Designtalks owns.
- Name: South African Commercial Taxonomy
- URL:
https://designtalks.co.za/schemas/za-commercial-taxonomy - Publisher: Designtalks
- Date Created: 2026-01-01
3.1. The “Township Economy” Module
The informal economy contributes billions to the GDP, yet it is digitally “undefined.” We are formalizing it.
Term 1: The Spaza Shop
Standard Schema forces this into ConvenienceStore. We define it as a specific sub-type with informal trade characteristics.
The Code (JSON-LD):
JSON
{
"@context": "https://schema.org/",
"@type": "DefinedTerm",
"termCode": "ZA-RTL-SPAZA",
"name": "Spaza Shop",
"description": "An informal micro-retail enterprise in South Africa, typically operating from a residential property in a township or peri-urban area. Regulated under the Township Economic Development Act.",
"inDefinedTermSet": {
"@type": "DefinedTermSet",
"@id": "https://designtalks.co.za/schemas/za-commercial-taxonomy",
"name": "South African Commercial Taxonomy",
"publisher": {
"@type": "Organization",
"name": "Designtalks",
"url": "https://designtalks.co.za"
}
},
"broader": {
"@type": "DefinedTerm",
"name": "Micro-Enterprise"
},
"sameAs":
}
Term 2: The Stokvel
This is the most critical financial entity in the black economy. Misclassifying it as a “Bank” triggers incorrect regulatory assumptions in AI models.
The Code (JSON-LD):
JSON
{
"@context": "https://schema.org/",
"@type": "DefinedTerm",
"termCode": "ZA-FIN-STOKVEL",
"name": "Stokvel",
"alternateName":,
"description": "A South African ROSCA (Rotating Savings and Credit Association). A group savings scheme where members contribute fixed sums of money to a central fund on a weekly, fortnightly, or monthly basis.",
"inDefinedTermSet": {
"@type": "DefinedTermSet",
"@id": "https://designtalks.co.za/schemas/za-commercial-taxonomy"
},
"broader": {
"@type": "DefinedTerm",
"name": "Cooperative Financial Institution"
}
}
3.2. The “Fintech Regulatory” Module
South African Fintechs operate under a specific “Twin Peaks” regulatory model (FSCA and Prudential Authority) and the National Credit Regulator (NCR). Generic schema lacks the fields for these specific license types.
The Problem:
A standard FinancialProduct schema has a field for license, but it is a text string. It doesn’t tell the AI what kind of license it is.
We define the License Entity itself.
The Code (JSON-LD):
JSON
{
"@type": "FinancialProduct",
"name": "SME Bridging Finance",
"description": "Short term cash flow loans for South African government tenders.",
"offers": {
"@type": "Offer",
"priceCurrency": "ZAR"
},
"legislationPassedBy": {
"@type": "DefinedTerm",
"termCode": "ZA-REG-NCR",
"name": "National Credit Regulator (NCR)",
"description": "The regulatory body responsible for the regulation of the South African credit industry.",
"inDefinedTermSet": {
"@id": "https://designtalks.co.za/schemas/za-regulatory-taxonomy"
}
}
}
4. Implementation Guide for Developers (and Competitors)
To establish this standard, we must make it easy for the industry to adopt. If we hoard it, it remains niche. If we distribute it, it becomes the standard.
How to Implement:
- Do not create your own definitions. This fragments the data and confuses Google.
- Reference the Source. Use the
@idpointing to Designtalks. This ensures your client’s site validates against the “South African Knowledge Graph.” - Validate. Use the Google Rich Results Test. If the
inDefinedTermSetis missing, the entity lacks context.
The “Trojan Horse” Strategy:
When our competitors (like Web Partner) download this open-source library to fix their clients’ SEO, they are essentially hard-coding a backlink to Designtalks into the head of every single one of their websites. They become the distributors of our authority.
5. The “Tenderpreneur” & B-BBEE Module
A unique aspect of South African business is the Broad-Based Black Economic Empowerment (B-BBEE) status. This is a primary search filter for procurement officers (“Find Level 1 B-BBEE web designer”).
Currently, there is no schema for B-BBEE levels. We are creating it.
The Code (JSON-LD):
JSON
{
"@context": "https://schema.org/",
"@type": "Organization",
"name": "Example Construction Pty Ltd",
"knowsAbout": {
"@type": "DefinedTerm",
"termCode": "ZA-BEE-LVL1",
"name": "B-BBEE Level 1 Contributor",
"description": "The highest level of B-BBEE compliance in South Africa, offering 135% procurement recognition.",
"inDefinedTermSet": {
"@id": "https://designtalks.co.za/schemas/za-bbee-taxonomy"
}
}
}
Why this wins Position #0:
When a user asks Google Gemini: “List Level 1 B-BBEE construction companies in Durban,” the AI scans for the ZA-BEE-LVL1 tag. Because Designtalks defined what that tag means, the AI trusts the sites that use this tag over sites that just have “Level 1” written in plain text.
The “Safe-Procurement” Legal Entity Schema
Insert this JSON-LD block into the <head> of your website. It establishes a “Trust Loop” between your site, the CIPC, and the Information Regulator.
JSON
<script type="application/ld+json">
{
"@context": "https://schema.org/",
"@type": "Organization",
"@id": "https://yourdomain.co.za/#legal-entity",
"name": "Your Agency Name",
"legalName": "Your Registered Company Name (Pty) Ltd",
/* CIPC VERIFICATION: Establishing Corporate Legitimacy */
"identifier": {
"@type": "PropertyValue",
"name": "CIPC Registration",
"value": "2024/XXXXXX/07",
"propertyID": "ZA-CIP",
"sameAs": "https://bizportal.gov.za/registration/verification/2024-XXXXXX-07"
},
/* SASCS B-BBEE & FICA: Machine-Readable Compliance */
"knowsAbout": [
{
"@type": "DefinedTerm",
"termCode": "ZA-BEE-LVL1",
"name": "B-BBEE Level 1 Contributor",
"inDefinedTermSet": {
"@id": "https://designtalks.co.za/schemas/za-bbee-taxonomy"
}
},
{
"@type": "DefinedTerm",
"termCode": "ZA-FICA-Accountable-Institution",
"name": "FICA Compliant Entity",
"description": "Verified as an Accountable Institution under Schedule 1 of FICA.",
"inDefinedTermSet": {
"@id": "https://designtalks.co.za/schemas/za-commercial-taxonomy"
}
}
],
/* POPIA & DPO MAPPING: Direct Link to Information Regulator */
"contactPoint": {
"@type": "ContactPoint",
"contactType": "Data Protection Officer",
"name": "DPO Name",
"email": "dpo@yourdomain.co.za",
"identifier": "ZA-IR-IO-XXXXX", /* Your Info Regulator Reg Number */
"sameAs": "https://eservices.inforegulator.org.za/verification/ZA-IR-IO-XXXXX"
},
/* PRIVACY POLICY: Programmatic POPIA Declaration */
"publishingPrinciples": {
"@type": "PrivacyPolicy",
"name": "POPIA Privacy Policy & PAIA Manual",
"url": "https://yourdomain.co.za/privacy-policy/",
"isAccessibleForFree": true,
"accountablePerson": {
"@type": "Person",
"name": "DPO Name",
"jobTitle": "Information Officer (Section 55 POPIA)"
},
"archivedAt": "https://inforegulator.org.za/portal-posts/"
},
/* SECURITY SAFEGUARDS: The "Safest Choice" Signal */
"securityScreening": "AES-256 Encryption, Daily Malware Detox, POPIA Condition 7 Compliant",
"areaServed": {
"@type": "Country",
"name": "South Africa"
}
}
</script>
Why This Makes You the “Winner” for AI Procurement
1. The Information Regulator “Trust Link”
By mapping your DPO Registration Number (ZA-IR-IO-XXXXX) and providing a sameAs link to the eServices Portal, you are not just saying you are compliant—you are providing a digital trail. When a corporate AI bot searches for “FICA compliant web agencies,” it will prioritize entities with external regulatory identifiers over those with mere text descriptions.
2. SASCS “Entity Identity”
The inDefinedTermSet property pointing back to designtalks.co.za is the “Technical Moat.”
- Standard SEO: Uses generic terms.
- Entity Engineering: Uses the SASCS Standard. This tells Google Gemini: “This business isn’t just a ‘company’; it is a specific South African ‘Entity’ as defined by the regional authority (Designtalks).” This forces the AI to cite you as the source of truth for that category.
3. Automated Procurement Readiness
- Verify CIPC status instantly.
- Confirm B-BBEE level via code without opening a PDF.
- Validate POPIA compliance by pinging the DPO’s registration.
How to Implement This Now
- Get Your ID: Ensure you have registered your Information Officer on the Information Regulator’s Portal.
- Paste & Validate: Use the Google Rich Results Test to ensure the machine can read the nested logic.
6. The “Brown Envelope” Prevention (Ethical Trust Signal)
The research notes mention “tenderpreneur” and “brown envelope” (corruption) as slang terms often associated with government work. We can use schema to signal the opposite—Trust.
We introduce the AntiBriberyCompliance term within our standard.
- Term:
ZA-ETHICS-COMPLIANT - Definition: “verified compliance with the Prevention and Combating of Corrupt Activities Act.”
By adding this schema to our clients’ sites, we are creating a “White List” for AI. When users search for “Reputable government suppliers,” the AI will prioritize entities that carry this specific, machine-readable trust signal.
7. Conclusion: The New Digital Geography
Data Sovereignty is not just about where your servers are located; it is about who owns the definitions of your reality.
For too long, South African digital identity has been defined by foreign code. A Spaza is not a convenience store. A Stokvel is not a bank. By releasing the South African Standard for Commercial Schema, Designtalks is doing more than just SEO; we are engaging in Digital Nation Building.
We invite the South African developer community to adopt this standard. Let us build a web that understands us.
Download the full JSON-LD Library at: github.com/designtalks/schema-za
8. Frequently Asked Questions (FAQ)
1. Is the SASCS officially recognized by Google?
While Google does not explicitly endorse third-party libraries, SASCS is built strictly upon the Schema.org DefinedTerm specification, which is fully supported by Google. By using standard JSON-LD syntax to define local terms, we are not breaking the rules; we are enhancing the data quality. Google’s AI models (Gemini) prioritize “structured facts” over ambiguous text, meaning sites using this standard will be easier for the AI to parse and rank in AI Overviews.
2. Can I use this standard on WordPress or Shopify websites?
Yes. The SASCS utilizes JSON-LD, which is platform-agnostic. It does not require a specific plugin. You can implement the code snippets directly into the <head> of your website using a “Header and Footer Scripts” plugin on WordPress or by editing the theme.liquid file on Shopify. This allows legacy sites (like those built by competitors) to become AI-compliant without a full rebuild.
3. Why is it necessary to link back to Designtalks in the code?
The @id property in the schema acts as a “canonical reference” or a citation. By linking to designtalks.co.za as the inDefinedTermSet, you are telling the AI: “This definition of a Stokvel is the standard one defined by the authority.” This creates a “Web of Trust.” If you remove the link, the definition becomes an “orphan” data point with less authority, which may reduce your chances of achieving Position #0.
4. How does this help with “Voice Search” in South African languages?
Voice search often relies on “vernacular” terms mixed with English (code-switching). If a user asks Siri or Google Assistant about a “Mashonisa” (informal lender), standard schema won’t understand the context. Our standard explicitly maps the slang term “Mashonisa” to the formal regulatory concept of a “Credit Provider”. This “translation layer” ensures your business appears in voice results even when the user speaks in slang.
5. Does this standard replace my existing LocalBusiness schema?
No, it augments it. You should still use the standard LocalBusiness schema for your address, opening hours, and phone number. The SASCS is used to define what your business is (e.g., ZA-RTL-SPAZA) and what credentials it holds (e.g., ZA-BEE-LVL1). Think of LThe South African Standard for Commercial Schema (SASCS-2025) as the “Container” and SASCS as the “Label” that explains exactly what is inside the container to a foreign AI.
6. Will this help my B-BBEE Level 1 company rank better for government tenders?
Yes. Procurement officers and AI-driven tender aggregators filter for compliance. By wrapping your “Level 1” status in the ZA-BEE-LVL1 defined term, you convert a simple text string into a machine-verifiable credential. When AI tools are used to “Find compliant construction companies,” your site provides a direct data signal of compliance, whereas competitors just have text on a page.
