seo-fundamentals
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.
What this skill does
# SEO Fundamentals > **Foundational principles for sustainable search visibility.** > This skill explains _how search engines evaluate quality_, not tactical shortcuts. --- ## 1. E-E-A-T (Quality Evaluation Framework) E-E-A-T is **not a direct ranking factor**. It is a framework used by search engines to **evaluate content quality**, especially for sensitive or high-impact topics. | Dimension | What It Represents | Common Signals | | --------------------- | ---------------------------------- | --------------------------------------------------- | | **Experience** | First-hand, real-world involvement | Original examples, lived experience, demonstrations | | **Expertise** | Subject-matter competence | Credentials, depth, accuracy | | **Authoritativeness** | Recognition by others | Mentions, citations, links | | **Trustworthiness** | Reliability and safety | HTTPS, transparency, accuracy | > Pages competing in the same space are often differentiated by **trust and experience**, not keywords. --- ## 2. Core Web Vitals (Page Experience Signals) Core Web Vitals measure **how users experience a page**, not whether it deserves to rank. | Metric | Target | What It Reflects | | ------- | ------- | ------------------- | | **LCP** | < 2.5s | Loading performance | | **INP** | < 200ms | Interactivity | | **CLS** | < 0.1 | Visual stability | **Important context:** - CWV rarely override poor content - They matter most when content quality is comparable - Failing CWV can _hold back_ otherwise good pages --- ## 3. Technical SEO Principles Technical SEO ensures pages are **accessible, understandable, and stable**. ### Crawl & Index Control | Element | Purpose | | ----------------- | ---------------------- | | XML sitemaps | Help discovery | | robots.txt | Control crawl access | | Canonical tags | Consolidate duplicates | | HTTP status codes | Communicate page state | | HTTPS | Security and trust | ### Performance & Accessibility | Factor | Why It Matters | | ---------------------- | ----------------------------- | | Page speed | User satisfaction | | Mobile-friendly design | Mobile-first indexing | | Clean URLs | Crawl clarity | | Semantic HTML | Accessibility & understanding | --- ## 4. Content SEO Principles ### Page-Level Elements | Element | Principle | | ---------------- | ---------------------------- | | Title tag | Clear topic + intent | | Meta description | Click relevance, not ranking | | H1 | Page’s primary subject | | Headings | Logical structure | | Alt text | Accessibility and context | ### Content Quality Signals | Dimension | What Search Engines Look For | | ----------- | ---------------------------- | | Depth | Fully answers the query | | Originality | Adds unique value | | Accuracy | Factually correct | | Clarity | Easy to understand | | Usefulness | Satisfies intent | --- ## 5. Structured Data (Schema) Structured data helps search engines **understand meaning**, not boost rankings directly. | Type | Purpose | | -------------- | ---------------------- | | Article | Content classification | | Organization | Entity identity | | Person | Author information | | FAQPage | Q&A clarity | | Product | Commerce details | | Review | Ratings context | | BreadcrumbList | Site structure | > Schema enables eligibility for rich results but does not guarantee them. --- ## 6. AI-Assisted Content Principles Search engines evaluate **output quality**, not authorship method. ### Effective Use - AI as a drafting or research assistant - Human review for accuracy and clarity - Original insights and synthesis - Clear accountability ### Risky Use - Publishing unedited AI output - Factual errors or hallucinations - Thin or duplicated content - Keyword-driven text with no value --- ## 7. Relative Importance of SEO Factors There is **no fixed ranking factor order**. However, when competing pages are similar, importance tends to follow this pattern: | Relative Weight | Factor | | --------------- | --------------------------- | | Highest | Content relevance & quality | | High | Authority & trust signals | | Medium | Page experience (CWV, UX) | | Medium | Mobile optimization | | Baseline | Technical accessibility | > Technical SEO enables ranking; content quality earns it. --- ## 8. Measurement & Evaluation SEO fundamentals should be validated using **multiple signals**, not single metrics. | Area | What to Observe | | ----------- | -------------------------- | | Visibility | Indexed pages, impressions | | Engagement | Click-through, dwell time | | Performance | CWV field data | | Coverage | Indexing status | | Authority | Mentions and links | --- > **Key Principle:** > Sustainable SEO is built on _useful content_, _technical clarity_, and _trust over time_. > There are no permanent shortcuts. ## When to Use This skill is applicable to execute the workflow or actions described in the overview. ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
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".