# Schema Markup Templates Available in Geo-SEO-Claude: A Complete Guide

> Discover the six Schema Markup templates in Geo-SEO-Claude: Website SearchAction, Software, Product, Organization, Local Business, and Article Author for enhanced search visibility. Get rich snippets easily.

- Repository: [Zubair Trabzada/geo-seo-claude](https://github.com/zubair-trabzada/geo-seo-claude)
- Tags: api-reference
- Published: 2026-09-08

---

**The Geo-SEO-Claude repository ships six production-ready JSON-LD Schema Markup templates—Website SearchAction, Software SaaS, Product Ecommerce, Organization, Local Business, and Article Author—that enable rich snippets and enhanced search visibility when embedded in web pages.**

Schema Markup templates provide the structured data foundation modern SEO requires. The `zubair-trabzada/geo-seo-claude` project maintains a curated collection of schema.org-compliant JSON files designed for immediate integration into any web property. These templates reside in the `schema/` directory and conform to Google’s structured data guidelines, allowing developers to inject valid structured data without crafting schemas from scratch.

## Available Schema Markup Templates

The repository organizes its Schema Markup templates by business use case, each targeting specific rich result types in search engines.

### Website SearchAction

The **Website SearchAction** template enables the coveted "Sitelinks Searchbox" rich result. It defines a `WebSite` entity with a nested `SearchAction` that tells search engines how to query your internal search engine. According to the source code, this template is defined in [`schema/website-searchaction.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/website-searchaction.json) and requires configuration of the base URL and search query parameter pattern.

### Software SaaS

For SaaS products, the **Software SaaS** template implements the `SoftwareApplication` schema type with `applicationCategory` set to "SaaS". Stored in [`schema/software-saas.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/software-saas.json), this markup captures pricing through nested `Offer` entities, product descriptions, and provider information—critical for software marketplaces and product listing pages.

### Product Ecommerce

The **Product Ecommerce** template in [`schema/product-ecommerce.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/product-ecommerce.json) defines the `Product` schema with complete commercial metadata. It includes fields for SKU, price, currency, availability status, and product imagery. This template generates rich product snippets that display price and stock status directly in search results.

### Organization

Found in [`schema/organization.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/organization.json), the **Organization** template establishes brand identity through structured data. It captures the organization name, official URL, logo asset, and customer service contact points using the `Organization` type with embedded `ContactPoint` entities.

### Local Business

The **Local Business** template provides comprehensive location markup via [`schema/local-business.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/local-business.json). It combines `LocalBusiness` type definitions with `PostalAddress` and `GeoCoordinates` to satisfy Google’s local pack requirements, including opening hours specification and geographic coordinates for map integration.

### Article Author

For content publishers, the **Article Author** template in [`schema/article-author.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/article-author.json) implements the `Person` schema. It supports affiliation linkage to `Organization` entities and `sameAs` properties for social profile verification, establishing author authority and enabling byline rich results.

## Implementation Examples

Each Schema Markup template uses standard JSON-LD syntax and connects to schema.org contexts. Implement these by embedding the scripts in your HTML `<head>` or injecting them server-side, replacing placeholder values with production data.

### Website SearchAction Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "url": "{{SITE_URL}}",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "{{SITE_URL}}/search?q={search_term_string}",
    "query-input": "required name=search_term_string"
  }
}
</script>

```

### Software SaaS Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "{{PRODUCT_NAME}}",
  "description": "{{PRODUCT_DESCRIPTION}}",
  "url": "{{PRODUCT_URL}}",
  "applicationCategory": "SaaS",
  "offers": {
    "@type": "Offer",
    "price": "{{PRICE}}",
    "priceCurrency": "USD"
  }
}
</script>

```

### Product Ecommerce Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "{{PRODUCT_NAME}}",
  "image": "{{IMAGE_URL}}",
  "description": "{{DESCRIPTION}}",
  "sku": "{{SKU}}",
  "offers": {
    "@type": "Offer",
    "price": "{{PRICE}}",
    "priceCurrency": "USD",
    "availability": "https://schema.org/{{AVAILABILITY}}"
  }
}
</script>

```

### Organization Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "{{ORG_NAME}}",
  "url": "{{ORG_URL}}",
  "logo": "{{LOGO_URL}}",
  "contactPoint": [{
    "@type": "ContactPoint",
    "telephone": "{{PHONE}}",
    "contactType": "customer service"
  }]
}
</script>

```

### Local Business Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "{{BUSINESS_NAME}}",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "{{STREET}}",
    "addressLocality": "{{CITY}}",
    "addressRegion": "{{STATE}}",
    "postalCode": "{{ZIP}}",
    "addressCountry": "{{COUNTRY}}"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": "{{LAT}}",
    "longitude": "{{LON}}"
  },
  "openingHours": "{{OPENING_HOURS}}"
}
</script>

```

### Article Author Implementation

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Person",
  "name": "{{AUTHOR_NAME}}",
  "url": "{{AUTHOR_URL}}",
  "affiliation": {
    "@type": "Organization",
    "name": "{{AFFILIATION}}"
  },
  "sameAs": [
    "{{SOCIAL_PROFILE_1}}",
    "{{SOCIAL_PROFILE_2}}"
  ]
}
</script>

```

## Summary

- The Geo-SEO-Claude repository maintains **six specialized Schema Markup templates** in the `schema/` directory covering common SEO use cases.
- **Website SearchAction** ([`schema/website-searchaction.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/website-searchaction.json)) enables internal search functionality in search results.
- **Software SaaS** ([`schema/software-saas.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/software-saas.json)) and **Product Ecommerce** ([`schema/product-ecommerce.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/product-ecommerce.json)) support commercial entity markup with pricing structures.
- **Local Business** ([`schema/local-business.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/local-business.json)) provides geographic and operational metadata for physical locations.
- **Organization** ([`schema/organization.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/organization.json)) and **Article Author** ([`schema/article-author.json`](https://github.com/zubair-trabzada/geo-seo-claude/blob/main/schema/article-author.json)) establish brand and author authority signals.
- All templates use **JSON-LD syntax** compatible with schema.org standards and Google’s rich results requirements.

## Frequently Asked Questions

### What format do the Geo-SEO-Claude Schema Markup templates use?

The templates use **JSON-LD** (JavaScript Object Notation for Linked Data) wrapped in HTML script tags with `type="application/ld+json"`. This format is the preferred method for structured data according to Google’s Search Central documentation, as it keeps the markup separate from visible HTML content while remaining easily parseable by search engine crawlers.

### How do I customize the Schema Markup templates for my website?

Replace the double-bracketed placeholders (e.g., `{{SITE_URL}}`, `{{PRODUCT_NAME}}`) with your actual data values. For dynamic sites, inject these values server-side before page render, or use a static site generator to substitute variables at build time. Each template in `schema/*.json` follows consistent naming conventions for easier programmatic substitution.

### Can I use multiple Schema Markup templates on the same page?

Yes, you can embed multiple JSON-LD scripts on a single page when the schemas describe different entities. For example, an e-commerce product page might include both the **Product Ecommerce** template and the **Organization** template to establish seller credibility. Ensure each script tag contains only one top-level `@type` entity unless using explicit `@graph` notation.

### Where should I place the Schema Markup in my HTML?

Place the JSON-LD script tags within the `<head>` section of your HTML document. This placement ensures search engine crawlers encounter the structured data immediately when parsing the page. Alternatively, you can inject the markup before the closing `</body>` tag, though `<head>` placement remains the standard recommendation for optimal crawler detection.