enuno/claude-command-and-control/google-seo

Google SEO Best Practices

Description

This skill provides comprehensive guidance for optimizing web content and documentation for search engine discoverability based on Google's official SEO Starter Guide. Use this skill when creating new web content, reviewing existing pages for SEO compliance, or documenting best practices for web-based projects. The skill ensures content follows Google's people-first approach while implementing technical optimizations that improve search visibility.

When to Use This Skill

• When creating new web pages, documentation sites, or online content
• When reviewing existing web content for search optimization
• When generating HTML documentation that needs to be discoverable
• When implementing metadata (titles, descriptions, alt text) for web content
• When structuring URLs, navigation, or site architecture
• When providing guidance on content quality and organization

When NOT to Use This Skill

• For content not intended for search engines (internal tools, private documentation)
• For API-only services without web interfaces
• When SEO considerations conflict with user experience (prioritize UX)
• For content behind authentication walls where search indexing is inappropriate

Prerequisites

• Access to web content, documentation, or HTML files
• Understanding of basic HTML structure (<title>, <meta>, <img> tags)
• Familiarity with web architecture (URLs, directories, linking)
• Context about target audience and search vocabulary

Workflow

Phase 1: Content Discovery & Indexability

Purpose: Ensure Google can find and access your content

Step 1.1: Verify Indexing

Check if Google has already indexed your content:

# Use site: search operator in Google
site:example.com/your-page

Expected Output: Verification of whether page is indexed

Step 1.2: Enable Crawl Access

Ensure Google can access critical resources:

• [ ] CSS files are accessible (not blocked by robots.txt)
• [ ] JavaScript files are accessible
• [ ] Images are accessible
• [ ] Page renders properly in URL Inspection Tool

Decision Point:

• IF content is new → Submit sitemap (optional but helpful)
• IF content is established → Monitor via Search Console
• IF critical resources blocked → Update robots.txt

Expected Output: Confirmation that Googlebot can fully render page

Step 1.3: Establish Link Structure

Enable natural discovery through links:

• Ensure new pages are linked from existing indexed pages
• Create logical navigation hierarchy
• Implement breadcrumb navigation for deep content

Expected Output: Clear path for crawlers to discover content

Phase 2: URL Structure Optimization

Purpose: Create descriptive, organized URLs that enhance search results

Step 2.1: Design Descriptive URLs

Best Practices: ✅ Use meaningful words: example.com/pets/cats.html ❌ Avoid random IDs: example.com/2/6772756D707920636174

Implementation:

# Good URL structure
https://example.com/docs/api/authentication
https://example.com/products/laptops/gaming
 
# Poor URL structure
https://example.com/page?id=12345
https://example.com/p/a/b/c/xyz

Validation:

• [ ] URLs contain meaningful words
• [ ] URL segments reflect content hierarchy
• [ ] URLs are concise but descriptive

Step 2.2: Organize Directory Structure

Group similar content logically:

/policies/          # Infrequently updated content
/blog/              # Frequently updated content
/docs/getting-started/
/docs/api-reference/
/products/category/

Expected Output: Hierarchical URL structure that communicates update frequency and content grouping

Step 2.3: Manage Duplicate Content

Implement canonicalization:

<!-- In <head> of duplicate/alternate pages -->
<link rel="canonical" href="https://example.com/preferred-url" />

Or use 301 redirects:

# .htaccess example
Redirect 301 /old-page.html https://example.com/new-page.html

Expected Output: Each content piece accessible via one primary URL

Phase 3: Metadata Optimization

Purpose: Create compelling titles and descriptions that appear in search results

Step 3.1: Craft Unique Titles

Write clear, concise <title> elements:

<!-- Good examples -->
<title>API Authentication Guide | Example Docs</title>
<title>Gaming Laptops - High Performance | Example Store</title>
 
<!-- Poor examples -->
<title>Page 1</title>
<title>Home - Home - Home - Example</title>
<title>Buy cheap laptops gaming computers best deals discount sale</title>

Guidelines:

• Keep unique per page
• Include business name or key identifier
• Accurately describe page content
• Avoid keyword stuffing

Expected Output: Unique, descriptive titles for each page

Step 3.2: Write Meta Descriptions

Create 1-2 sentence summaries:

<!-- Good example -->
<meta name="description" content="Learn how to implement OAuth 2.0 authentication in our API with step-by-step code examples for Node.js, Python, and Ruby." />
 
<!-- Poor example -->
<meta name="description" content="API docs page authentication login security OAuth token password credential user access." />

Guidelines:

• One unique description per page
• Highlight most relevant information
• Keep succinct (1-2 sentences)
• Write naturally, not keyword-stuffed

Expected Output: Unique meta descriptions that accurately summarize page content

Phase 4: Image Optimization

Purpose: Make images discoverable and accessible

Step 4.1: Use High-Quality Images

Best Practices:

• Use sharp, clear images
• Place images near relevant text
• Ensure surrounding text explains image content

Step 4.2: Write Descriptive Alt Text

Implement proper alt attributes:

<!-- Good examples -->
<img src="golden-retriever-playing-fetch.jpg"
     alt="Golden retriever catching red frisbee in park" />
 
<img src="api-authentication-flow.png"
     alt="Diagram showing OAuth 2.0 authentication flow from client to server" />
 
<!-- Poor examples -->
<img src="img123.jpg" alt="image" />
<img src="photo.jpg" alt="" />
<img src="product.jpg" alt="buy now click here cheap discount sale" />

Guidelines:

• Keep short but descriptive
• Explain image-content relationship
• Avoid keyword stuffing
• Provide context for accessibility

Expected Output: All images have meaningful alt text

Phase 5: Content Quality & Link Strategy

Purpose: Create people-first content with proper link practices

Step 5.1: Ensure Content Quality

Core Attributes Checklist:

• [ ] Text is easy-to-read and well organized
• [ ] Content is unique (not copied from other sources)
• [ ] Information is current and updated
• [ ] Content is helpful, reliable, and people-first
• [ ] Expertise/authority is demonstrated
• [ ] No keyword stuffing (write naturally)

Organization:

• Break long content into paragraphs
• Use clear section headings
• Create logical navigation structure

Expected Output: High-quality, original, well-organized content

Step 5.2: Implement Link Best Practices

Anchor Text:

<!-- Good examples -->
<a href="/api/authentication">Learn about API authentication</a>
<a href="/products/gaming-laptops">Browse gaming laptops</a>
 
<!-- Poor examples -->
<a href="/page">click here</a>
<a href="/info">read more</a>

Outbound Links:

• Link to trusted resources that corroborate content
• Add rel="nofollow" to untrusted sources

<!-- Trusted resource -->
<a href="https://oauth.net/2/">OAuth 2.0 specification</a>
 
<!-- User-generated or untrusted content -->
<a href="https://unknown-site.com" rel="nofollow">User submitted link</a>

Expected Output: Descriptive anchor text and properly qualified outbound links

Phase 6: Technical Implementation & Structured Data

Purpose: Implement technical SEO features

Step 6.1: Implement Structured Data

Add schema.org markup for rich results:

<!-- Breadcrumb example -->
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [{
    "@type": "ListItem",
    "position": 1,
    "name": "Docs",
    "item": "https://example.com/docs"
  },{
    "@type": "ListItem",
    "position": 2,
    "name": "API Reference",
    "item": "https://example.com/docs/api"
  }]
}
</script>

Step 6.2: Create and Submit Sitemap

Generate XML sitemap for content management:

<?xml version="1.0" encoding="UTF-8"?>
<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
  <url>
    <loc>https://example.com/docs/getting-started</loc>
    <lastmod>2026-01-22</lastmod>
    <changefreq>monthly</changefreq>
    <priority>0.8</priority>
  </url>
</urlset>

Expected Output: Sitemap submitted to Search Console

Step 6.3: Configure Robots Meta Tags

Control crawl/index behavior when needed:

<!-- Prevent indexing of test pages -->
<meta name="robots" content="noindex, nofollow" />
 
<!-- Allow indexing, prevent link following -->
<meta name="robots" content="index, nofollow" />

Expected Output: Appropriate robots directives on all pages

Examples

Example 1: Optimizing Documentation Site

Context: Creating new API documentation site with 50+ pages

Input:

Project: API Documentation
Pages: Authentication, Endpoints, Examples, Guides
Current state: Basic HTML with generic titles

Execution Flow:

1. Phase 1: Verify localhost isn't blocking CSS/JS → Create sitemap
2. Phase 2: Restructure URLs from /page1.html to /docs/authentication
3. Phase 3: Write unique titles:

• <title>API Authentication - OAuth 2.0 Guide | Example API</title>
• <title>POST /users Endpoint Reference | Example API</title>

1. Phase 4: Add alt text to all code diagram images
2. Phase 5: Add descriptive anchor text to cross-references
3. Phase 6: Implement breadcrumb structured data

Expected Output:

• 50 pages with unique, descriptive titles and meta descriptions
• Logical URL hierarchy (/docs/authentication, /docs/endpoints/users)
• All images with proper alt text
• Breadcrumb navigation with schema.org markup
• Sitemap submitted to Search Console

Rationale: Documentation sites benefit greatly from SEO as users primarily discover APIs through search

Example 2: Content Quality Review

Context: Existing blog with poor search performance

Input:

Current issues:
-Generic titles ("Blog Post 1", "Blog Post 2")
-No meta descriptions
-Short, thin content (<200 words)
-Heavy keyword stuffing
-No internal linking structure

Execution Flow:

1. Quality Audit: Identify thin content for expansion or deletion
2. Title Rewrite: "Blog Post 1" → "How to Implement OAuth 2.0 in Node.js"
3. Meta Description: Add unique 1-2 sentence summary per post
4. Content Enhancement: Expand thin posts with unique insights
5. Link Structure: Add descriptive internal links between related posts
6. Keyword Review: Remove keyword stuffing, write naturally

Expected Output:

<!-- Before -->
<title>Blog Post 1</title>
<!-- No meta description -->
<p>OAuth security authentication login API security token...</p>
 
<!-- After -->
<title>How to Implement OAuth 2.0 in Node.js | Example Blog</title>
<meta name="description" content="Learn how to add OAuth 2.0 authentication to your Node.js application with this step-by-step tutorial including code examples." />
<p>OAuth 2.0 provides a secure authentication framework for web applications. This guide walks through implementing OAuth in a Node.js Express application...</p>

Rationale: Demonstrates transformation from SEO anti-patterns to best practices

Example 3: E-commerce Product Pages

Context: 500 product pages with duplicate content issues