google-official-seo-guide
Official Google SEO guide covering search optimization, best practices, Search Console, crawling, indexing, and improving website search visibility based on official Google documentation
What this skill does
# Google Official SEO Guide
Comprehensive assistance with Google Search optimization, SEO best practices, and search visibility improvements based on official Google documentation.
## When to Use This Skill
This skill should be triggered when users ask about:
### SEO & Search Optimization
- Improving website ranking in Google Search
- Implementing SEO best practices
- Optimizing meta tags, titles, and descriptions
- Fixing crawling or indexing issues
- Understanding how Google Search works
### Structured Data & Rich Results
- Adding VideoObject, BroadcastEvent, or Clip structured data
- Implementing schema.org markup for rich results
- Creating sitemaps and robots.txt files
- Setting up breadcrumb navigation
- Configuring hreflang for multi-language sites
### Technical SEO
- Mobile-first indexing optimization
- JavaScript SEO and rendering issues
- Managing duplicate content with canonical tags
- Configuring robots meta tags
- URL structure and internal linking
### Search Console & Monitoring
- Using Google Search Console reports
- Debugging search visibility issues
- Monitoring crawl errors and indexing status
- Analyzing search performance metrics
### Content & Links
- Writing effective anchor text
- Internal and external linking strategies
- Avoiding spam policies violations
- Managing site migrations and redirects
## Key Concepts
### The Three Stages of Google Search
1. **Crawling**: Googlebot discovers and fetches pages from the web
2. **Indexing**: Google analyzes page content and stores it in the index
3. **Serving**: Google returns relevant results for user queries
### Important SEO Principles
- **Mobile-First Indexing**: Google primarily uses the mobile version of content for indexing and ranking
- **Canonical URLs**: Specify the preferred version of duplicate or similar pages
- **Structured Data**: Use schema.org markup to help Google understand your content
- **Search Essentials**: Technical, content, and spam requirements for Google Search eligibility
### Common Structured Data Types
- **VideoObject**: For video content and features
- **BroadcastEvent**: For livestream videos (LIVE badge)
- **Clip**: For video key moments/timestamps
- **SeekToAction**: For auto-detected key moments in videos
## Quick Reference
### Example 1: Basic VideoObject Structured Data
```json
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Video title",
"description": "Video description",
"thumbnailUrl": [
"https://example.com/photos/1x1/photo.jpg",
"https://example.com/photos/4x3/photo.jpg",
"https://example.com/photos/16x9/photo.jpg"
],
"uploadDate": "2024-03-31T08:00:00+08:00",
"duration": "PT1M54S",
"contentUrl": "https://example.com/video.mp4",
"embedUrl": "https://example.com/embed/123"
}
```
**Use this for**: Adding basic video metadata to help Google understand and display your videos in search results.
---
### Example 2: LIVE Badge with BroadcastEvent
```json
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Livestream title",
"uploadDate": "2024-10-27T14:00:00+00:00",
"publication": {
"@type": "BroadcastEvent",
"isLiveBroadcast": true,
"startDate": "2024-10-27T14:00:00+00:00",
"endDate": "2024-10-27T14:37:14+00:00"
}
}
```
**Use this for**: Enabling the LIVE badge on livestream videos in Google Search results.
---
### Example 3: Video Key Moments with Clip
```json
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Cat video",
"hasPart": [
{
"@type": "Clip",
"name": "Cat jumps",
"startOffset": 30,
"endOffset": 45,
"url": "https://example.com/video?t=30"
},
{
"@type": "Clip",
"name": "Cat misses the fence",
"startOffset": 111,
"endOffset": 150,
"url": "https://example.com/video?t=111"
}
]
}
```
**Use this for**: Manually specifying important timestamps/chapters in your video for the key moments feature.
---
### Example 4: Good Anchor Text Practices
```html
<!-- Bad: Too generic -->
<a href="https://example.com">Click here</a> to learn more.
<!-- Better: Descriptive and contextual -->
For a full list of cheese available for purchase, see the
<a href="https://example.com">list of cheese types</a>.
<!-- Bad: Too many adjacent links -->
I've written about cheese
<a href="/page1">so</a>
<a href="/page2">many</a>
<a href="/page3">times</a>.
<!-- Better: Spaced out with context -->
I've written about cheese so many times this year:
the <a href="/blue-cheese">controversy over blue cheese</a>,
the <a href="/oldest-brie">world's oldest brie</a>, and
<a href="/boy-and-cheese">A Boy and His Cheese</a>.
```
**Use this for**: Creating effective internal and external links that help both users and Google understand your content.
---
### Example 5: Crawlable Links
```html
<!-- Recommended: Google can crawl these -->
<a href="https://example.com">Link text</a>
<a href="/products/category/shoes">Link text</a>
<a href="./products/category/shoes">Link text</a>
<!-- Not recommended: May not be crawled -->
<a routerLink="products/category">Link text</a>
<a onclick="goto('https://example.com')">Link text</a>
<span href="https://example.com">Link text</span>
```
**Use this for**: Ensuring your links are discoverable and crawlable by Googlebot.
---
### Example 6: Mobile and Desktop hreflang for Separate URLs
```html
<!-- Mobile version (https://m.example.com/) -->
<link rel="canonical" href="https://example.com/">
<link rel="alternate" hreflang="es" href="https://m.example.com/es/">
<link rel="alternate" hreflang="fr" href="https://m.example.com/fr/">
<!-- Desktop version (https://example.com/) -->
<link rel="canonical" href="https://example.com/">
<link rel="alternate" media="only screen and (max-width: 640px)"
href="https://m.example.com/">
<link rel="alternate" hreflang="es" href="https://example.com/es/">
<link rel="alternate" hreflang="fr" href="https://example.com/fr/">
```
**Use this for**: Properly configuring separate mobile URLs (m-dot sites) with internationalization support.
---
### Example 7: robots meta tags
```html
<!-- Don't index this page -->
<meta name="robots" content="noindex">
<!-- Don't follow links on this page -->
<meta name="robots" content="nofollow">
<!-- Don't index and don't follow -->
<meta name="robots" content="noindex, nofollow">
<!-- Don't show snippet in search results -->
<meta name="robots" content="nosnippet">
```
**Use this for**: Controlling how Google crawls and indexes specific pages.
---
### Example 8: InteractionStatistic for Video Views
```json
{
"@context": "https://schema.org",
"@type": "VideoObject",
"name": "Video title",
"interactionStatistic": {
"@type": "InteractionCounter",
"interactionType": { "@type": "WatchAction" },
"userInteractionCount": 12345
}
}
```
**Use this for**: Displaying the number of views/watches for your video content.
---
### Example 9: External Links with Attribution
```html
<!-- Citing sources with proper attribution -->
<p>
According to a recent study from Swiss researchers,
Emmental cheese wheels exposed to music had a milder flavor,
with the full findings available in
<a href="https://example.com/cheese-study">
Cheese in Surround Sound—a culinary art experiment
</a>.
</p>
<!-- Use nofollow when you don't trust the source -->
<a href="https://untrusted-site.com" rel="nofollow">
Untrusted content
</a>
<!-- Sponsored links must be marked -->
<a href="https://partner-site.com" rel="sponsored">
Partner content
</a>
```
**Use this for**: Properly linking to external sources while maintaining SEO best practices.
---
### Example 10: Mobile-First Indexing Checklist
```html
<!-- Ensure same robots meta tags on mobile and desktop -->
<meta name="robots" content="index, follow">
<!-- Use same structured data on both versions -->
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "OrganiRelated in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".