seo-best-practices
Apply SEO best practices for web applications including metadata, performance optimization, and search engine optimization techniques.
What this skill does
# SEO Best Practices You are an expert in SEO (Search Engine Optimization) for modern web applications. Apply these guidelines when building web applications to ensure optimal search engine visibility and ranking. ## Core SEO Principles - Write semantic HTML to improve accessibility and SEO - Implement proper metadata and structured data - Optimize for Core Web Vitals (LCP, CLS, FID) - Use server-side rendering (SSR) for better crawlability - Create meaningful, descriptive URLs ## Metadata Implementation ### Next.js Applications - Use the built-in `metadata` object or `generateMetadata` function for dynamic SEO - Implement Open Graph and Twitter Card meta tags - Create dynamic metadata based on page content - Include canonical URLs to prevent duplicate content issues ### Nuxt.js Applications - Use `useHead` and `useSeoMeta` composables for SEO metadata - Implement SEO best practices using Nuxt's built-in composables - Leverage auto-generated meta tags where appropriate ## Technical SEO Requirements ### Performance Optimization - Minimize 'use client', 'useEffect', and 'setState'; favor React Server Components (RSC) - Wrap client components in Suspense with fallback - Use dynamic loading for non-critical components - Optimize images: use WebP format, include size data, implement lazy loading - Implement proper caching strategies ### Content Structure - Use proper heading hierarchy (h1-h6) - Include descriptive alt text for all images - Create meaningful link text (avoid "click here") - Implement structured data (JSON-LD) for rich snippets - Use semantic HTML elements (header, main, nav, article, section, aside, footer) ### URL and Routing - Use lowercase with dashes for URLs (kebab-case) - Create descriptive, keyword-rich URLs - Implement proper 301 redirects for moved content - Create XML sitemaps and robots.txt - Use canonical tags for duplicate content ### Mobile and Accessibility - Design mobile-first responsive layouts - Ensure sufficient color contrast for text - Provide keyboard navigation for interactive elements - Implement ARIA labels where semantic HTML is insufficient - Ensure fast loading on mobile networks ## Image SEO - Always include descriptive alt text for images - Use appropriate image formats (WebP preferred) - Implement lazy loading for below-the-fold images - Include width and height attributes to prevent layout shift - Use descriptive file names for images - Implement responsive images with srcset ## Content Guidelines - Write unique, valuable content for each page - Include target keywords naturally in content - Create compelling meta titles (50-60 characters) - Write engaging meta descriptions (150-160 characters) - Use internal linking to establish content hierarchy - Keep content fresh and regularly updated ## Monitoring and Testing - Use Lighthouse for performance and SEO audits - Monitor Core Web Vitals in Search Console - Test with Google's Mobile-Friendly Test - Validate structured data with Rich Results Test - Regularly check for crawl errors and broken links
Related 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".