Seo Optimizer

# robots.txt template
# This file tells search engine crawlers which pages they can and cannot access

# Allow all crawlers to access all content by default
User-agent: *
Allow: /

# Disallow crawling of common administrative and system directories
Disallow: /admin/
Disallow: /private/
Disallow: /cgi-bin/
Disallow: /tmp/

# Disallow crawling of search results and dynamic pages (if applicable)
# Disallow: /search?
# Disallow: /?*

# Sitemap location (update with your actual sitemap URL)
Sitemap: https://example.com/sitemap.xml

# Common bot-specific rules (uncomment if needed)
# Block bad bots
# User-agent: BadBot
# Disallow: /

# Slow down aggressive crawlers
# User-agent: Googlebot
# Crawl-delay: 1


export default async function seo_optimizer(input) {
  console.log("🧠 Running skill: seo-optimizer");
  
  // TODO: implement actual logic for this skill
  return {
    message: "Skill 'seo-optimizer' executed successfully!",
    input
  };
}


{
  "name": "@ai-labs-claude-skills/seo-optimizer",
  "version": "1.0.0",
  "description": "Claude AI skill: seo-optimizer",
  "main": "index.js",
  "files": [
    "."
  ],
  "license": "MIT",
  "author": "AI Labs"
}

# Schema Markup Guide

Complete guide for implementing schema.org structured data on HTML websites.

## What is Schema Markup?

Schema markup (structured data) is code that helps search engines understand your content better and display rich results in search. It uses vocabulary from schema.org to provide context about your page content.

## Why Use Schema Markup?

1. **Rich Results**: Enhanced search listings with images, ratings, prices, etc.
2. **Better CTR**: Rich results stand out and get more clicks
3. **Voice Search**: Helps voice assistants understand and use your content
4. **Knowledge Graph**: Can appear in Google's Knowledge Graph
5. **Competitive Advantage**: Many sites don't use schema markup

## Implementation Formats

Schema markup can be implemented in three formats. **JSON-LD is recommended** by Google.

### 1. JSON-LD (Recommended)
```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title"
}
</script>
```

### 2. Microdata
```html
<div itemscope itemtype="https://schema.org/Article">
  <h1 itemprop="headline">Your Article Title</h1>
</div>
```

### 3. RDFa
```html
<div vocab="https://schema.org/" typeof="Article">
  <h1 property="headline">Your Article Title</h1>
</div>
```

## Common Schema Types for HTML Websites

### 1. Organization Schema

Use on your homepage or about page to define your organization.

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "description": "Brief description of your organization",
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-555-555-5555",
    "contactType": "Customer Service",
    "areaServed": "US",
    "availableLanguage": "English"
  },
  "sameAs": [
    "https://facebook.com/yourcompany",
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany"
  ]
}
</script>
```

### 2. LocalBusiness Schema

For businesses with physical locations.

```html
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "LocalBusiness",
  "name": "Your Business Name",
  "image": "https://example.com/business-photo.jpg",
  "@id": "https://example.com",
  "url": "https://example.com",
  "telephone": "+1-555-555-5555",
  "priceRange": "$$",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "City Name",
    "addressRegion": "State",
    "postalCode": "12345",
    "addressCountry": "US"
  },
  "geo": {
    "@type": "GeoCoordinates",
    "latitude": 40.7589,
    "longitude": -73.9851
  },
  "openingHoursSpecification": {
    "@type": "OpeningHoursSpecification",
    "dayOfWe