seo-weblyfe

seo-weblyfe is a skill for Claude Code, Codex from S3YED/appie-kit. It costs 52 tokens per session (1,030 once invoked), scanned A, original, MIT.

An SEO planning and auditing guide for Weblyfe sites, covering search terms, page improvements, technical checks, links, and content structure.

In plain words
What is it for?
Use it to plan SEO, improve pages, check indexing and site speed, build internal links, and plan relevant backlinks.
Why use it?
It gives SEO work a consistent order, from choosing search targets to checking how Google crawls the site and reviewing results.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to plan SEO, improve pages, check indexing and site speed, build internal links, and plan relevant backlinks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/s3yed/appie-kit/seo-weblyfe
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add S3YED/appie-kit --skill seo-weblyfe
Clone the repo
git clone --depth 1 https://github.com/S3YED/appie-kit

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for seo-weblyfe

README.md
[![agentmods](https://agentmods.dev/badge/skills/s3yed/appie-kit/seo-weblyfe/github.svg)](https://agentmods.dev/skills/s3yed/appie-kit/seo-weblyfe)
Your own site
<a href="https://agentmods.dev/skills/s3yed/appie-kit/seo-weblyfe"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/seo-weblyfe/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for seo-weblyfe

Your own site · 80×15
<a href="https://agentmods.dev/skills/s3yed/appie-kit/seo-weblyfe"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/seo-weblyfe.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,030 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01030
Opus 5 $0.00026 $0.00515
Sonnet 5 $0.00010 $0.00206
Haiku 4.5 $0.00005 $0.00103

Measured 9d ago against content hash 696161074fa3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

seo-weblyfe scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/content/seo-weblyfe/SKILL.md · 86 lines

How it starts

The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Weblyfe SEO

Umbrella skill for the Weblyfe SEO curriculum. Prefer this over one-module-per-skill micro entries.

Canonical workflow

  1. Start with the ranking model and site goal.
  2. Choose target keywords and map one primary keyword per URL.
  3. Apply the on-page checklist.
  4. Confirm technical crawl/index health.
  5. Build internal-link architecture and content clusters.
  6. Grow authority with relevant backlinks.
  7. Re-audit based on Search Console, rankings, and CTR changes.

Module map

Foundation

  • Why SEO matters
  • The six Google signals: relevance, popularity, uniqueness, freshness, quality, readability
  • SEO as both traffic acquisition and reputation management

Keyword strategy

  • Long-tail preference
  • Search-volume validation before writing
  • One primary keyword per page
  • Early placement in title, H1, intro, headings, URL, meta, and alt text

On-page checklist

  • Title tag, meta description, slug, H1, first paragraph, heading placement
  • Image filenames and alt tags
  • Breadcrumbs and media enrichment

Technical SEO

  • Sitemap submission
  • Search Console coverage monitoring
  • mobile-first rendering
  • speed, schema/JSON-LD, canonicals, plugin/app hygiene

Smart content architecture

  • Pillar + supporting article clusters
  • Internal links as a deliberate authority network
  • Retargeting and conversion instrumentation on content assets
  • Favor 2 posts per week when the cluster map is active, rather than publishing isolated one-offs
  • Use the blog as a support system for conversion pages, not just a publishing feed
  • Build posts from market research plus internal learnings, not from a pre-made calendar.
  • Match Seyed's voice: direct, authentic, no corporate fluff.
  • Avoid em dashes.
  • Use good sources and backlinks.
  • Current Weblyfe blog operating mode: 2 posts per week, written from market research plus internal learnings, with a decision-stage bias when the cluster supports it.
  • Live publication standard: every published Weblyfe blog must include a branded cover image and set both CMS image fields (main-image and thumbnail-image). Use references/weblyfe-blog-publish-and-cover-checklist.md.
  • Blog drafts are not "done" until the article is placed in the Weblyfe CMS, not just saved as markdown.
  • When the user explicitly asks to push live, publish in Webflow CMS immediately, then verify the public URL (HTTP 200 + correct title/snippet) before confirming.
  • When repurposing the same idea for LinkedIn, Dutch is acceptable if requested.
  • See references/weblyfe-editorial-system-2026.md for the current cluster-based publishing rhythm and topic directions.
  • See references/weblyfe-content-consistency-operating-system-2026.md for the weekly operating cadence that connects 2 blogs/week, LinkedIn drafts, repurposing, and review loops.
  • See references/weblyfe-webflow-blog-publish-runbook.md for the Webflow CMS go-live sequence and verification checklist.
  • See references/weblyfe-editorial-voice-and-cadence-2026.md for the current voice, cadence, and LinkedIn language preference.

Read the full file on GitHub · 86 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 86 lines · 52 tokens per session scan A 696161074fa3

Subscribe to this mod's changes

seo-weblyfe is a skill published in the GitHub repository S3YED/appie-kit (9 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 1,030 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

browser-edge-cases

SOP for debugging browser automation failures on complex websites. Use when browser tools fail on specific sites like LinkedIn, Twitter/X, SPAs, or sites with Shadow DOM.

aden-hive/hive · 40 tokens

aws-patterns

Lambda best practices, S3 event patterns, SQS/SNS fanout, and DynamoDB access patterns for serverless AWS architectures.

vibeeval/vibecosystem · 31 tokens

review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use…

stevesolun/ctx · 95 tokens

agents-md-protocol

Create or review an AGENTS.md file so coding agents get stable repo-local instructions: environment setup, testing, style, security boundaries, PR policy, and handoff rules. Use when a repo lacks durable agent guidance or when a custom harness needs a predictable context file.

stevesolun/ctx · 59 tokens

investment-memo-generator

Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.

travisjneuman/.claude · 37 tokens

python-memory-safe-scripts

Memory-safe Python script patterns for long-running processes under systemd MemoryMax constraints. Covers allocator purge (mimalloc/glibc malloctrim), HTTP response lifecycle, DataFrame cleanup, thread-local connection reuse, and periodic GC cadence. Battle-tested through 5 OOM optimization cycles on production GPU…

terrylica/cc-skills · 197 tokens