Seo Visibility Expert

SEO & Visibility Expert

Get your web projects discovered by both traditional search engines AND AI systems.

Quick Start

1. Create llms.txt at site root → AI crawlers find your content 2. Add JSON-LD schema → Rich snippets in search results 3. Verify robots.txt → Allow good bots, block bad ones 4. Generate sitemap.xml → Help crawlers index everything 5. Check Core Web Vitals → PageSpeed Insights score >90 6. Add Open Graph tags → Beautiful social previews

When to Use

Use for:

• Technical SEO audits and fixes
• llms.txt for AI crawlers
• Schema.org/JSON-LD structured data
• Launch strategies (Product Hunt, HN, Reddit)
• Core Web Vitals optimization

NOT for:

• Paid advertising/PPC campaigns
• Social media content creation
• Email marketing campaigns

The Modern Discovery Stack

┌─────────────────────────────────────────────┐
│          AI ANSWER ENGINES                  │
│  ChatGPT, Claude, Perplexity, Google AI     │
│  → llms.txt, structured data, AEO           │
├─────────────────────────────────────────────┤
│          TRADITIONAL SEARCH                 │
│  Google, Bing, DuckDuckGo                   │
│  → Technical SEO, content, backlinks        │
├─────────────────────────────────────────────┤
│          SOCIAL DISCOVERY                   │
│  Product Hunt, HN, Reddit, Twitter/X        │
│  → Launch timing, community, narratives     │
└─────────────────────────────────────────────┘

Technical SEO Essentials

Metadata Must-Haves

<!-- Every page needs these -->
<title>Primary Keyword | Brand Name</title>
<meta name="description" content="150-160 chars with keywords">
<link rel="canonical" href="https://yoursite.com/page">

<!-- Open Graph for social -->
<meta property="og:title" content="Title for social shares">
<meta property="og:image" content="https://yoursite.com/og-image.png">

URL Rules

• Lowercase, hyphen-separated
• Include primary keyword
• Keep under 60 characters
• No query parameters for content pages

AI Crawler Optimization (AEO)

llms.txt Quick Template

# Your Site Name

> Brief tagline describing what you do

## Overview
2-3 sentences for AI systems.

## Key Features
- Feature 1: Description
- Feature 2: Description

## Documentation
- [Getting Started](/docs/getting-started)
- [API Reference](/docs/api)

robots.txt for AI Era

# AI Crawlers - Allow them!
User-agent: GPTBot
Allow: /

User-agent: Claude-Web
Allow: /

User-agent: PerplexityBot
Allow: /

# Sitemaps
Sitemap: https://yoursite.com/sitemap.xml

Decision tree:

• Want AI to reference your content? → Allow GPTBot, Claude-Web
• Training data concerns? → Disallow Google-Extended

Social Launch Quick Guide

Product Hunt

• Launch at 12:01 AM PST exactly
• Best days: Tuesday, Wednesday, Thursday
• Never ask for upvotes directly → "Would love your feedback!"
• See references/launch-checklists.md for full checklist

Hacker News

• Post 6-8 AM PST, Tuesday-Thursday
• Title: Show HN: [Tool] – [Plain English description]
• Be technical, humble, genuine
• Respond to every comment

Reddit

• Participate before promoting (90/10 rule)
• Find niche subreddits for your domain
• r/SideProject, r/webdev, r/InternetIsBeautiful

Core Web Vitals Targets

Quick fixes: Optimize images (LCP), minimize JS (INP), set explicit dimensions (CLS)

Anti-Patterns

1. "Build It and They Will Come"

Symptom: Great product, zero traffic Fix: Spend 50% of time on marketing/distribution

2. Ignoring AI Crawlers

Symptom: No llms.txt, blocking AI user agents Fix: Create llms.txt, allow AI crawlers in robots.txt

3. Keyword Stuffing

Symptom: Unnatural keyword repetition Fix: Write for humans first, keywords naturally

4. Launch and Abandon

Symptom: Big launch, then silence Fix: Build in public, regular updates, consistent presence

5. No Schema Markup

Symptom: Plain search results, no rich snippets Fix: Add JSON-LD for your content type (see references)

6. Ignoring Mobile

Symptom: Desktop-only testing Fix: Mobile-first indexing is default. Test on devices.

Measurement

Free tools:

• Google Search Console - Search performance
• PageSpeed Insights - Core Web Vitals
• Schema Validator - Structured data testing

Track these: 1. Organic search impressions/clicks 2. Referral traffic from social launches 3. Core Web Vitals scores 4. AI citations (search your brand in ChatGPT/Claude)

Reference Files

---

Covers: Technical SEO | AI Crawler Optimization | Social Launch Strategy | Core Web Vitals | Schema Markup

Use with: content-marketer (content strategy) | web-design-expert (landing pages) | indie-monetization-strategist (conversion)

Changelog

All notable changes to the seo-visibility-expert skill will be documented in this file.

[2.0.0] - 2024-12-13

Changed

• BREAKING: Restructured SKILL.md from 399 lines to ~180 lines for progressive disclosure
• Moved detailed examples and templates to ./references/ directory
• Expanded anti-patterns section to 6 patterns

Added

• references/llms-txt-examples.md - Complete llms.txt examples for different site types (SaaS, docs, OSS, blog, e-commerce)
• references/schema-templates.md - JSON-LD structured data templates for all common types
• references/launch-checklists.md - Detailed checklists for Product Hunt, Hacker News, and Reddit launches
• Version field in frontmatter for skill tracking

Improved

• Modern Discovery Stack diagram (AI Engines, Traditional Search, Social)
• AI Crawler Optimization section with decision tree
• Quick wins checklist for immediate actions
• Framework-specific implementations kept concise with references to detailed templates

[1.0.0] - 2024-11-30

Added

• Initial seo-visibility-expert skill
• Modern Discovery Stack concept
• Technical SEO essentials (metadata, URL structure, JSON-LD)
• AI Crawler Optimization with llms.txt and robots.txt
• Social launch strategies (Product Hunt, HN, Reddit)
• Core Web Vitals optimization
• Framework-specific implementations (Next.js, Docusaurus)
• Measurement and iteration guidance

Launch Checklists

Detailed checklists for Product Hunt, Hacker News, and Reddit launches.

---

Product Hunt Launch

4 Weeks Before

Build Your Network

• [ ] Follow 50+ active PH users in your space
• [ ] Comment genuinely on 2-3 products daily
• [ ] Identify potential hunters (look for those who've hunted similar products)
• [ ] Reach out to 3-5 potential hunters with personalized messages
• [ ] Join maker communities (Indie Hackers, Twitter indie dev circles)

Prepare Assets

• [ ] Logo: 240×240px PNG with transparent background
• [ ] Gallery images: 1270×760px (up to 8 images)
• [ ] Video: 1-2 min demo (optional but recommended)
• [ ] GIF: Animated preview (optional)
• [ ] Thumbnail: 240×240px

Write Copy

• [ ] Tagline: Under 60 characters (this is critical!)
• [ ] Description: 260 characters max
• [ ] Maker comment: Your story, why you built it
• [ ] First comment: Thank hunters, explain vision

1 Week Before

Technical Prep

• [ ] Create dedicated /producthunt landing page (optional)
• [ ] Set up analytics to track PH traffic
• [ ] Prepare discount code (e.g., PRODUCTHUNT for 20% off)
• [ ] Test signup/onboarding flow extensively
• [ ] Ensure site can handle traffic spike

Communication Prep

• [ ] Draft launch day email to existing users
• [ ] Prepare Twitter/X thread announcing launch
• [ ] Create Slack/Discord message for communities
• [ ] Line up 10-20 supporters for launch day
• [ ] Brief your team on launch day responsibilities

Day Before

• [ ] Submit product (but don't schedule—let hunter control)
• [ ] Finalize all assets in PH dashboard
• [ ] Set up PH notifications on mobile
• [ ] Clear calendar for launch day
• [ ] Get good sleep!

Launch Day Schedule

12:01 AM PST - Product goes live
12:02 AM - Your personal upvote + first comment
12:05 AM - Notify inner circle (10-20 people)
           "We launched! Would love your honest feedback"
           (NEVER ask for upvotes explicitly)

6:00 AM PST - Second wave
           - Tweet thread goes live
           - Email to existing users
           - Post in relevant Slack/Discord communities

9:00 AM PST - Check ranking, respond to ALL comments
           - Thank every commenter personally
           - Answer questions in detail

12:00 PM PST - Third wave push
           - LinkedIn post
           - Additional community posts

3:00 PM PST - Continue engagement
           - Respond to new comments
           - Share interesting feedback publicly

6:00 PM PST - Final push if competing for top 5
           - DM people who said they'd support
           - Share current ranking to create urgency

11:59 PM PST - Voting ends

Post-Launch

• [ ] Thank everyone who supported (public tweet/post)
• [ ] Send follow-up email to new signups
• [ ] Write retrospective on what worked
• [ ] Collect testimonials from comments
• [ ] Update product based on feedback received

What NOT to Do

❌ Never say: "Please upvote us!" ❌ Never: Share direct upvote links ❌ Never: Use upvote pods or services ❌ Never: Create fake accounts to upvote ❌ Never: Spam the same message everywhere

✅ Instead say: "We launched on Product Hunt - would love your feedback!" ✅ Share: Your product URL, not the upvote URL ✅ Focus on: Genuine engagement and responding to comments

---

Hacker News Launch

Before Posting

Content Prep

• [ ] Write genuine Show HN post (not marketing fluff)
• [ ] Focus on technical interesting bits
• [ ] Have a "why I built this" story ready
• [ ] Prepare honest answers for tough questions
• [ ] Read HN guidelines thoroughly

Title Formulas That Work

Show HN: [Tool Name] – [Plain English description]
Example: Show HN: Vite – A faster alternative to Webpack

Show HN: I built [X] to solve [problem I had]
Example: Show HN: I built a CLI to manage my dotfiles across machines

[Interesting technical finding] (with data/results)
Example: We analyzed 1M npm packages and found 23% have CVEs

What NOT to Write

❌ "Revolutionary AI-powered solution..."
❌ "The Uber of X..."
❌ "Disrupting the Y industry..."
❌ Any marketing-speak
❌ Buzzword salads

Posting Strategy

Timing

• Best: 6-8 AM PST, Tuesday-Thursday
• Good: Weekday mornings PST
• Avoid: Weekends (lower engagement for technical content)
• Avoid: Major news days

The Post

Title: Show HN: [Your Tool] – [What it does simply]

Body (as first comment, not in submission):
- What it is (1-2 sentences)
- Why you built it (personal story)
- Technical approach (what makes it interesting)
- What you learned
- What's next
- Honest limitations

Keep it under 300 words. Be humble.

During the Post

In the first 30 minutes:

• [ ] Respond to every comment
• [ ] Be genuinely helpful
• [ ] Answer technical questions thoroughly
• [ ] Acknowledge valid criticisms
• [ ] Don't be defensive

Throughout the day:

• [ ] Keep checking for new comments
• [ ] Engage thoughtfully (not just "thanks!")
• [ ] Share additional technical details when asked
• [ ] Be honest about limitations and roadmap

HN Survival Tips

When criticized:

• Acknowledge valid points
• Explain your reasoning without being defensive
• Thank people for feedback
• Don't argue—discuss

Common criticisms and responses:

"Why not just use X?"
→ "Great question! I actually started with X but found [specific limitation]. Here's what I tried..."

"This has been done before"
→ "Totally! I was inspired by [previous work]. The main difference is [specific technical choice]..."

"Who is this for?"
→ "[Specific user type] who are dealing with [specific problem]. Here's an example..."

Post-Submission

• [ ] Write blog post about what you learned
• [ ] Save interesting technical discussions
• [ ] Follow up with people who showed interest
• [ ] Track referral traffic in analytics

---

Reddit Launch

Finding Your Subreddits

General Launch Subs

• r/SideProject - Show your side projects
• r/indiehackers - Indie business/product discussion
• r/InternetIsBeautiful - Beautiful/useful web tools
• r/Startup_Ideas - Early stage feedback

Developer Focused

• r/webdev - Web development
• r/programming - General programming
• r/javascript, r/reactjs, r/python, etc. - Language specific
• r/selfhosted - Self-hostable tools

Niche Subreddits

• Find subreddits specific to your product domain
• Check each sub's rules before posting
• Some require karma/age minimums

Before You Post

Build credibility first (2-4 weeks)

• [ ] Comment helpfully on other posts (not promotion)
• [ ] Answer questions in your area of expertise
• [ ] Follow 90/10 rule: 90% helpful, 10% self-promotion
• [ ] Read each subreddit's specific rules

Check subreddit rules

• [ ] Self-promotion allowed?
• [ ] Specific days for promotion? (e.g., "Share Saturday")
• [ ] Flair requirements?
• [ ] Link vs text post requirements?

Posting Strategy

Title Format by Subreddit Type

r/SideProject:
"I built [X] - [what it does] [optional: results/timeframe]"
Example: "I built a CLI tool that generates changelogs from git commits"

r/webdev, r/programming:
"[Project type] [What it does] - feedback welcome"
Example: "Open source alternative to [X] - looking for feedback"

r/InternetIsBeautiful:
Focus on the cool factor, not the tech
Example: "A tool that visualizes your Spotify listening history"

Post Body Structure

# What I built
[Brief description - what it does, not how]

# Why I built it
[Personal story - the problem you had]

# Tech stack (if relevant to sub)
[Keep brief unless asked]

# What I'm looking for
[Be specific: feedback on X, beta testers, etc.]

# Links
- [Live demo/site]
- [GitHub if open source]

Happy to answer any questions!

Engagement Rules

DO

• Respond to every comment
• Answer questions thoroughly
• Be grateful for feedback (even harsh)
• Share your process and learnings
• Upvote helpful comments on your post

DON'T

• Cross-post the same content to many subs
• Post and disappear
• Be defensive about criticism
• Argue with commenters
• Delete and repost if it doesn't get traction

Timing

• Best: Tuesday-Thursday
• Post time: 9-11 AM EST (peak Reddit activity)
• Avoid: Weekends (lower professional audience)
• Avoid: Major news/event days

Tracking

• [ ] Use UTM parameters for Reddit traffic

  ?utm_source=reddit&utm_medium=social&utm_campaign=launch

• [ ] Track which subreddits drive signups
• [ ] Note which post formats work best
• [ ] Save feedback for product improvements

---

Launch Day Communication Templates

Email to Existing Users

Subject: We're live on Product Hunt! 🚀

Hey [Name],

Big news - [Product] just launched on Product Hunt!

[Link to Product Hunt page]

We've been building [product] for [time period], and today we're
sharing it with the world.

If you have a minute, we'd love for you to:
1. Check out our page
2. Leave honest feedback
3. Share with anyone who might find it useful

Thanks for being an early supporter. Means the world.

[Your name]

Tweet/X Thread

Thread 1/5:
🚀 We just launched [Product] on Product Hunt!

[Brief description of what it does]

Here's the story 🧵

2/5:
The problem: [Pain point you're solving]

I was dealing with this at [company/project] and couldn't find
a good solution.

So I built one.

3/5:
What makes [Product] different:

• [Key differentiator 1]
• [Key differentiator 2]
• [Key differentiator 3]

4/5:
Building this taught me:

• [Learning 1]
• [Learning 2]
• [Learning 3]

5/5:
If you're interested, check us out:

🔗 [Product Hunt link]
🔗 [Direct link]

Would love your honest feedback!

RT appreciated if you think others would find this useful 🙏

Slack/Discord Community Post

Hey everyone! 👋

Just launched my side project on Product Hunt - would love your feedback!

[Product Name]: [One-line description]

🔗 [Link]

Built it because [brief personal story].

Happy to answer any questions here!

---

Post-Launch Analysis

Metrics to Track

Product Hunt

• [ ] Final ranking
• [ ] Total upvotes
• [ ] Comments received
• [ ] Traffic from PH (in analytics)
• [ ] Signups/conversions from PH traffic
• [ ] Email list growth

Hacker News

• [ ] Points received
• [ ] Comments
• [ ] Time on front page
• [ ] Traffic spike
• [ ] Signups during peak

Reddit

• [ ] Upvote ratio
• [ ] Comments
• [ ] Traffic from each subreddit
• [ ] Cross-posts (if any)

Retrospective Questions

1. What worked better than expected? 2. What didn't work as planned? 3. Which platform drove best quality traffic? 4. What feedback will you act on? 5. Would you launch this way again?

llms.txt Examples

Complete examples for different project types. Copy, customize, deploy to your site root.

What is llms.txt?

llms.txt is a markdown file at your site root that helps AI systems (ChatGPT, Claude, Perplexity, etc.) understand your content. It's the "robots.txt for AI" - providing structured, machine-readable information about your site.

Location: https://yoursite.com/llms.txt

Developer Tool / SaaS

# DevSync

> Real-time code collaboration for distributed teams

## Overview
DevSync provides real-time collaborative coding with conflict resolution, voice chat, and integrated debugging. Built for teams working across time zones who need to pair program without latency.

## Key Features
- Real-time cursor tracking and code sync (<50ms latency)
- Intelligent conflict resolution using CRDT
- Integrated voice/video with screen sharing
- Git integration with branch visualization
- Works with VS Code, JetBrains, and Vim

## Technical Specs
- Language: TypeScript/Rust
- Protocol: WebSocket with CRDT sync
- Deployment: Self-hosted or cloud
- Security: E2E encryption, SOC2 compliant

## Pricing
- Free: 2 users, 1 workspace
- Pro: $12/user/month - unlimited workspaces
- Enterprise: Custom - SSO, SLA, dedicated support

## Documentation
- \[Getting Started\](/docs/quickstart)
- \[API Reference\](/docs/api)
- \[Self-Hosting Guide\](/docs/self-host)
- \[Security Whitepaper\](/docs/security)

## Use Cases
1. Remote pair programming sessions
2. Code review with live discussion
3. Onboarding new team members
4. Teaching and mentorship

## Links
- Website: https://devsync.io
- GitHub: https://github.com/devsync/devsync
- Discord: https://discord.gg/devsync
- Status: https://status.devsync.io

Documentation Site

# FastAPI Documentation

> Modern, fast web framework for building APIs with Python

## Overview
FastAPI is a modern, fast (high-performance) web framework for building APIs with Python 3.8+ based on standard Python type hints. Automatic OpenAPI documentation, async support, and dependency injection out of the box.

## Core Concepts
- **Path Operations**: Define API endpoints with decorators
- **Type Hints**: Automatic validation and serialization
- **Dependency Injection**: Reusable components and auth
- **Async Support**: Native async/await for high performance

## Quick Start

from fastapi import FastAPI app = FastAPI()

@app.get("/") def read_root(): return {"Hello": "World"}

## Documentation Structure
- \[Tutorial\](/tutorial) - Step-by-step guide for beginners
- \[Advanced Guide\](/advanced) - Complex patterns and optimization
- \[API Reference\](/reference) - Complete API documentation
- \[Deployment\](/deployment) - Production deployment guides

## Common Tasks
- \[CRUD Operations\](/tutorial/crud)
- \[Authentication\](/tutorial/security)
- \[Database Integration\](/tutorial/sql-databases)
- \[Testing\](/tutorial/testing)
- \[WebSockets\](/advanced/websockets)

## Comparisons
- vs Flask: Faster, type hints, async native
- vs Django REST: Lighter, modern, auto-docs
- vs Express: Python ecosystem, type safety

## Links
- GitHub: https://github.com/tiangolo/fastapi
- PyPI: https://pypi.org/project/fastapi/
- Discord: https://discord.gg/fastapi

Open Source Library

# Zod

> TypeScript-first schema validation with static type inference

## Overview
Zod is a TypeScript-first schema declaration and validation library. Define a schema once and Zod will automatically infer the static TypeScript type. Zero dependencies.

## Why Zod
- TypeScript-first: Infers types from schemas
- Zero dependencies: Small bundle size
- Composable: Build complex schemas from simple ones
- Ecosystem: Works with React Hook Form, tRPC, Prisma

## Installation

npm install zod

## Basic Usage

import { z } from "zod";

const UserSchema = z.object({ name: z.string(), email: z.string().email(), age: z.number().min(0).optional(), });

type User = z.infer<typeof UserSchema>; // { name: string; email: string; age?: number }

## Schema Types
- Primitives: string, number, boolean, date
- Objects: object, array, tuple, record
- Advanced: union, intersection, discriminatedUnion
- Modifiers: optional, nullable, default

## Documentation
- \[Introduction\](/docs)
- \[Basic Usage\](/docs/basic-usage)
- \[Primitives\](/docs/primitives)
- \[Objects\](/docs/objects)
- \[Error Handling\](/docs/error-handling)

## Integrations
- React Hook Form: @hookform/resolvers
- tRPC: Built-in support
- Prisma: prisma-zod-generator

## Links
- GitHub: https://github.com/colinhacks/zod
- npm: https://www.npmjs.com/package/zod
- Docs: https://zod.dev

Content/Blog Site

# The Pragmatic Engineer

> Software engineering insights for senior+ engineers

## Overview
In-depth articles and analysis on software engineering, tech leadership, and the industry. Written by Gergely Orosz, formerly at Uber, Microsoft, and Skyscanner.

## Content Categories

### Engineering
- System Design and Architecture
- Code Quality and Best Practices
- Performance Optimization
- Incident Management

### Career
- Staff+ Engineering Career Paths
- Salary and Compensation Trends
- Interview Preparation
- Job Market Analysis

### Leadership
- Engineering Management
- Tech Lead Responsibilities
- Team Building
- Project Management

## Popular Articles
- \[The Trimodal Nature of Tech Compensation\](/blog/trimodal-compensation)
- \[System Design Interview Guide\](/blog/system-design-interview)
- \[What TPMs Do\](/blog/what-tpms-do)
- \[The Developer Experience\](/blog/developer-experience)

## Newsletter
- Weekly: Deep dives on engineering topics
- 500,000+ subscribers
- Paid tier for full access

## About the Author
Gergely Orosz - 15+ years in software engineering at Uber, Microsoft, Skyscanner, and Skype. Author of "The Software Engineer's Guidebook."

## Links
- Newsletter: https://newsletter.pragmaticengineer.com
- Twitter: https://twitter.com/gergelyorosz
- Book: https://www.engguidebook.com

E-commerce / Product

# Notion

> All-in-one workspace for notes, docs, wikis, and project management

## Overview
Notion is an all-in-one workspace combining notes, documents, wikis, and project management. Teams use it for documentation, knowledge bases, roadmaps, and task tracking.

## Core Features
- **Pages & Blocks**: Modular content with 50+ block types
- **Databases**: Tables, boards, calendars, galleries
- **Templates**: Pre-built workflows for common use cases
- **AI**: Built-in AI for writing, summarizing, translating
- **Collaboration**: Real-time editing, comments, mentions

## Use Cases
1. Team wikis and documentation
2. Project and task management
3. Personal note-taking and journaling
4. Product roadmaps and planning
5. Meeting notes and decisions

## Pricing
- Free: Personal use, limited blocks
- Plus: $10/user/month - unlimited blocks
- Business: $18/user/month - advanced permissions
- Enterprise: Custom - SSO, audit logs, dedicated support

## Integrations
- Slack, Google Drive, GitHub
- Figma, Jira, Asana
- 100+ integrations via API

## Resources
- \[Getting Started Guide\](https://notion.so/help/getting-started)
- \[Template Gallery\](https://notion.so/templates)
- \[API Documentation\](https://developers.notion.com)
- \[Community\](https://notion.so/community)

## Links
- Website: https://notion.so
- Help Center: https://notion.so/help
- API: https://developers.notion.com
- Status: https://status.notion.so

Best Practices

DO

• Use clear, factual language
• Structure with headers and lists
• Include version/date information
• Link to canonical documentation
• Focus on what AI systems need to answer user questions

DON'T

• Include marketing hyperbole ("revolutionary", "game-changing")
• Repeat keywords unnaturally
• Include huge code blocks (link instead)
• Omit pricing/key information
• Use vague descriptions

Maintenance

• Update when features change
• Review quarterly for accuracy
• Test by asking AI systems about your product
• Track AI citation rates

JSON-LD Schema Templates

Copy-paste JSON-LD structured data for different content types. Place in <script type="application/ld+json"> tags.

Software Application

{
  "@context": "https://schema.org",
  "@type": "SoftwareApplication",
  "name": "Your App Name",
  "description": "Clear description of what your software does",
  "applicationCategory": "DeveloperApplication",
  "operatingSystem": "Web, macOS, Windows, Linux",
  "url": "https://yourapp.com",
  "downloadUrl": "https://yourapp.com/download",
  "screenshot": "https://yourapp.com/screenshot.png",
  "softwareVersion": "2.0.0",
  "datePublished": "2024-01-15",
  "author": {
    "@type": "Organization",
    "name": "Your Company",
    "url": "https://yourcompany.com"
  },
  "offers": {
    "@type": "Offer",
    "price": "29.00",
    "priceCurrency": "USD",
    "priceValidUntil": "2025-12-31"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.8",
    "ratingCount": "1250"
  }
}

Application categories:

• DeveloperApplication
• DesignApplication
• BusinessApplication
• ProductivityApplication
• UtilitiesApplication
• SecurityApplication

Organization / Company

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company Name",
  "alternateName": "Short Name",
  "url": "https://yourcompany.com",
  "logo": "https://yourcompany.com/logo.png",
  "description": "What your company does",
  "foundingDate": "2020-01-01",
  "founders": [
    {
      "@type": "Person",
      "name": "Founder Name"
    }
  ],
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "123 Main St",
    "addressLocality": "San Francisco",
    "addressRegion": "CA",
    "postalCode": "94102",
    "addressCountry": "US"
  },
  "contactPoint": {
    "@type": "ContactPoint",
    "contactType": "customer support",
    "email": "support@yourcompany.com",
    "url": "https://yourcompany.com/contact"
  },
  "sameAs": [
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany",
    "https://github.com/yourcompany"
  ]
}

Article / Blog Post

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "Your Article Title",
  "description": "Article description for search results",
  "image": "https://yoursite.com/article-image.jpg",
  "datePublished": "2024-01-15T08:00:00+00:00",
  "dateModified": "2024-01-20T10:30:00+00:00",
  "author": {
    "@type": "Person",
    "name": "Author Name",
    "url": "https://yoursite.com/author/name"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Your Site Name",
    "logo": {
      "@type": "ImageObject",
      "url": "https://yoursite.com/logo.png"
    }
  },
  "mainEntityOfPage": {
    "@type": "WebPage",
    "@id": "https://yoursite.com/blog/article-slug"
  }
}

For technical articles, add:

{
  "articleSection": "Tutorials",
  "wordCount": 2500,
  "about": {
    "@type": "Thing",
    "name": "React Hooks"
  }
}

FAQ Page

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is your product?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Our product is a tool that helps developers..."
      }
    },
    {
      "@type": "Question",
      "name": "How much does it cost?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "We offer a free tier for individuals. Paid plans start at $29/month."
      }
    },
    {
      "@type": "Question",
      "name": "Is there a free trial?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, all paid plans include a 14-day free trial. No credit card required."
      }
    }
  ]
}

How-To Guide

{
  "@context": "https://schema.org",
  "@type": "HowTo",
  "name": "How to Set Up Your Development Environment",
  "description": "Step-by-step guide to setting up a modern development environment",
  "image": "https://yoursite.com/howto-image.jpg",
  "totalTime": "PT30M",
  "estimatedCost": {
    "@type": "MonetaryAmount",
    "currency": "USD",
    "value": "0"
  },
  "supply": [
    {
      "@type": "HowToSupply",
      "name": "VS Code"
    },
    {
      "@type": "HowToSupply",
      "name": "Node.js 20+"
    }
  ],
  "tool": [
    {
      "@type": "HowToTool",
      "name": "Terminal"
    }
  ],
  "step": [
    {
      "@type": "HowToStep",
      "name": "Install Node.js",
      "text": "Download and install Node.js from nodejs.org",
      "url": "https://yoursite.com/guide#step1",
      "image": "https://yoursite.com/step1.jpg"
    },
    {
      "@type": "HowToStep",
      "name": "Install VS Code",
      "text": "Download VS Code from code.visualstudio.com",
      "url": "https://yoursite.com/guide#step2",
      "image": "https://yoursite.com/step2.jpg"
    }
  ]
}

Course / Learning Resource

{
  "@context": "https://schema.org",
  "@type": "Course",
  "name": "Complete React Developer Course",
  "description": "Learn React from scratch and build production apps",
  "provider": {
    "@type": "Organization",
    "name": "Your Academy",
    "sameAs": "https://youracademy.com"
  },
  "educationalLevel": "Intermediate",
  "courseCode": "REACT-101",
  "numberOfCredits": 0,
  "hasCourseInstance": {
    "@type": "CourseInstance",
    "courseMode": "online",
    "courseWorkload": "PT40H"
  },
  "offers": {
    "@type": "Offer",
    "price": "99.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.9",
    "reviewCount": "523"
  }
}

Product (Physical or Digital)

{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Product Name",
  "description": "Product description",
  "image": [
    "https://yoursite.com/product-1.jpg",
    "https://yoursite.com/product-2.jpg"
  ],
  "brand": {
    "@type": "Brand",
    "name": "Your Brand"
  },
  "sku": "PROD-001",
  "mpn": "12345678",
  "offers": {
    "@type": "Offer",
    "url": "https://yoursite.com/product",
    "price": "49.99",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock",
    "priceValidUntil": "2025-12-31",
    "seller": {
      "@type": "Organization",
      "name": "Your Store"
    }
  },
  "aggregateRating": {
    "@type": "AggregateRating",
    "ratingValue": "4.7",
    "reviewCount": "89"
  },
  "review": [
    {
      "@type": "Review",
      "reviewRating": {
        "@type": "Rating",
        "ratingValue": "5"
      },
      "author": {
        "@type": "Person",
        "name": "Happy Customer"
      },
      "reviewBody": "This product changed my workflow completely!"
    }
  ]
}

Breadcrumb Navigation

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {
      "@type": "ListItem",
      "position": 1,
      "name": "Home",
      "item": "https://yoursite.com"
    },
    {
      "@type": "ListItem",
      "position": 2,
      "name": "Documentation",
      "item": "https://yoursite.com/docs"
    },
    {
      "@type": "ListItem",
      "position": 3,
      "name": "Getting Started",
      "item": "https://yoursite.com/docs/getting-started"
    }
  ]
}

Website (Search Box)

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "name": "Your Site Name",
  "url": "https://yoursite.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": {
      "@type": "EntryPoint",
      "urlTemplate": "https://yoursite.com/search?q={search_term_string}"
    },
    "query-input": "required name=search_term_string"
  }
}

Video

{
  "@context": "https://schema.org",
  "@type": "VideoObject",
  "name": "Video Title",
  "description": "Video description",
  "thumbnailUrl": "https://yoursite.com/video-thumbnail.jpg",
  "uploadDate": "2024-01-15T08:00:00+00:00",
  "duration": "PT10M30S",
  "contentUrl": "https://yoursite.com/video.mp4",
  "embedUrl": "https://www.youtube.com/embed/VIDEO_ID",
  "author": {
    "@type": "Person",
    "name": "Creator Name"
  }
}

Implementation in React/Next.js

// components/StructuredData.tsx
export function StructuredData({ data }: { data: object }) {
  return (
    <script
      type="application/ld+json"
      dangerouslySetInnerHTML={{ __html: JSON.stringify(data) }}
    />
  );
}

// Usage in page
import { StructuredData } from '@/components/StructuredData';

export default function ProductPage() {
  const productSchema = {
    "@context": "https://schema.org",
    "@type": "Product",
    // ... schema data
  };

  return (
    <>
      <StructuredData data={productSchema} />
      {/* Page content */}
    </>
  );
}

Validation Tools

• Google Rich Results Test: https://search.google.com/test/rich-results
• Schema.org Validator: https://validator.schema.org/
• JSON-LD Playground: https://json-ld.org/playground/

Common Mistakes

1. Invalid JSON - Always validate before deploying 2. Missing required fields - Check schema.org documentation 3. Wrong @type - Use exact schema.org type names 4. Fake ratings - Only use real aggregate ratings 5. Outdated dates - Keep dateModified current