technical-seo-engineering
v0.1.2Technical-SEO & search-engineering team — agents (seo-strategy-architect, seo-implementation-engineer) for the layer answering 'can search engines CRAWL, RENDER, INDEX, and UNDERSTAND this site, and will it RANK?': crawl-budget & log analysis, indexation control (robots.txt, meta robots, canonicalization, noindex), JS rendering (CSR/SSR/SSG, dynamic-rendering deprecation), structured data / schema.org (JSON-LD, rich-result eligibility), site architecture & internal linking, E-E-A-T, Core Web Vitals as a ranking factor (INP replaced FID in 2024), international SEO (hreflang), site migrations (redirect mapping, staging noindex), and topical authority. skills, a knowledge bank (strategy decision tree + 2026 patterns), and templates. Distinct from search-relevance-engineering (internal site-search relevance), web-design (the full website build & visual design), and marketing-operations (paid ads / campaign strategy) — this is the organic-search-engineering layer. Requires ravenclaude-core@>=0.7.0.
By Matt CorbettLicense: MIT7 GitHub starsUpdated last week
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 3 skill or MCP entries
- Source updated
- Sep 15, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install technical-seo-engineering for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install technical-seo-engineering@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/mcorbett51090/RavenClaudeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/technical-seo-engineering/.
Plugin files
├── .claude-plugin/plugin.json├── skills/choose-seo-strategy-and-priorities/SKILL.md├── skills/design-site-architecture-and-content-model/SKILL.md└── skills/implement-technical-seo-and-structured-data/SKILL.md
Included Skills3
Diagnose what to fix first for a described site by walking the SEO strategy decision tree (crawl → render → index → understand → rank), fixing the lowest broken rung first, then return the priority diagnosis, the indexation strategy, the E-E-A-T posture, and the conditions that would reorder the priorities. Reach for this when the user asks "our organic traffic is flat — where do we start?", "what should we fix first for SEO?", "which pages should we index or noindex?", or "how do we rank in a helpful-content world?". Used by `seo-strategy-architect` (primary).
From a site's target queries and page classes, design the crawl-efficient information architecture (flat depth, hub-and-spoke topic clusters), the internal-linking model that flows authority to the money pages, and the topical-authority / entity map that tells search engines what the site should own. Reach for this when the user asks "how should we structure the site and internal links?", "design our topic clusters / content model", or "what's our topical-authority / entity map?". Used by `seo-strategy-architect` (primary) and `seo-implementation-engineer`.
Implement and verify the technical-SEO layer for a site — crawlability (robots.txt, XML sitemaps, log-file analysis), rendering (CSR→SSR/SSG/prerender), indexation controls (canonical, meta-robots noindex, hreflang), JSON-LD schema.org structured data for rich-result eligibility, Core Web Vitals (INP/LCP/CLS on field data), and redirect-mapped site migrations — each checked against GSC / URL Inspection / the Rich Results Test / server logs. Reach for this when the user asks "fix our crawl/index", "our SPA doesn't rank — is it rendering?", "add schema markup", "improve Core Web Vitals", or "run our site migration without losing rankings". Used by `seo-implementation-engineer` (primary).
Plugin manifests1
{
"name": "technical-seo-engineering",
"version": "0.1.2",
"description": "Technical-SEO & search-engineering team — agents (seo-strategy-architect, seo-implementation-engineer) for the layer answering 'can search engines CRAWL, RENDER, INDEX, and UNDERSTAND this site, and will it RANK?': crawl-budget & log analysis, indexation control (robots.txt, meta robots, canonicalization, noindex), JS rendering (CSR/SSR/SSG, dynamic-rendering deprecation), structured data / schema.org (JSON-LD, rich-result eligibility), site architecture & internal linking, E-E-A-T, Core Web Vitals as a ranking factor (INP replaced FID in 2024), international SEO (hreflang), site migrations (redirect mapping, staging noindex), and topical authority. skills, a knowledge bank (strategy decision tree + 2026 patterns), and templates. Distinct from search-relevance-engineering (internal site-search relevance), web-design (the full website build & visual design), and marketing-operations (paid ads / campaign strategy) — this is the organic-search-engineering layer. Requires ravenclaude-core@>=0.7.0.",
"author": {
"name": "Matt Corbett"
},
"homepage": "https://github.com/mcorbett51090/RavenClaude",
"license": "MIT",
"keywords": [
"technical-seo",
"crawl-budget",
"indexation",
"structured-data",
"schema-org",
"core-web-vitals",
"hreflang",
"site-migration",
"internal-linking",
"e-e-a-t",
"search-console",
"topical-authority"
],
"requires": {
"plugins": [
"ravenclaude-core@>=0.7.0"
]
}
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[technical-seo-engineering on Agent Plugins Marketplace](https://pluginsmp.com/plugins/technical-seo-engineering)