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.
Best use case
seo-fundamentals is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.
Teams using seo-fundamentals should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/seo-fundamentals/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How seo-fundamentals Compares
| Feature / Agent | seo-fundamentals | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Core principles of SEO including E-E-A-T, Core Web Vitals, technical foundations, content quality, and how modern search engines evaluate pages.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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 Skills
threejs-fundamentals
Three.js scene setup, cameras, renderer, Object3D hierarchy, coordinate systems. Use when setting up 3D scenes, creating cameras, configuring renderers, managing object hierarchies, or working with transforms.
geo-fundamentals
Generative Engine Optimization for AI search engines (ChatGPT, Claude, Perplexity).
context-fundamentals
Context is the complete state available to a language model at inference time. It includes everything the model can attend to when generating responses: system instructions, tool definitions, retrieved documents, message history, and tool outputs.
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
vercel-cli-with-tokens
Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".
vercel-react-view-transitions
Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.
vercel-react-native-skills
React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.
deploy-to-vercel
Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".
vercel-composition-patterns
React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
ckm:ui-styling
Create beautiful, accessible user interfaces with shadcn/ui components (built on Radix UI + Tailwind), Tailwind CSS utility-first styling, and canvas-based visual designs. Use when building user interfaces, implementing design systems, creating responsive layouts, adding accessible components (dialogs, dropdowns, forms, tables), customizing themes and colors, implementing dark mode, generating visual designs and posters, or establishing consistent styling patterns across applications.
ckm:design
Comprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG, Gemini 3.1 Pro), social photos (HTML→screenshot, multi-platform). Actions: design logo, create CIP, generate mockups, build slides, design banner, generate icon, create social photos, social media images, brand identity, design system. Platforms: Facebook, Twitter, LinkedIn, YouTube, Instagram, Pinterest, TikTok, Threads, Google Ads.