[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NPK2312RQYN4K0PG6SPF2M":3,"skill-same:01M6NPK2312RQYN4K0PG6SPF2M":93},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":65,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6NPK2312RQYN4K0PG6SPF2M","seo-optimization",null,"SEO — on-page, technical, structured data, Core Web Vitals, and mobile-first indexing. Use when optimizing a website for search engines, adding meta tags or structured data, fixing Core Web Vitals, or auditing technical SEO.","projectious-work\u002Fprocesskit","projectious-work","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F263889726?v=4","01M6N97TJJ118WQ35CHRV8RD0E","projectious.work","01M6N97TPWJPF0BMKYQ4PBY5W8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdesign\u002Fseo-optimization\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"seo optimization","Optimization","seo","work","vitals","for","web vitals","tags","indexing","technical seo","use","technical","design","page","Meta Tags","first","Meta","search","core","structured data","2026-11-10 10:12:30",false,"---\nname: seo-optimization\ndescription: |\n  SEO — on-page, technical, structured data, Core Web Vitals, and mobile-first indexing. Use when optimizing a website for search engines, adding meta tags or structured data, fixing Core Web Vitals, or auditing technical SEO.\nmetadata:\n  processkit:\n    apiVersion: processkit.projectious.work\u002Fv2\n    id: SKILL-seo-optimization\n    version: \"1.1.0\"\n    created: 2026-04-06T00:00:00Z\n    category: design\n---\n\n# SEO Optimization\n\n## Intro\n\nSEO is two jobs: make the page understandable to crawlers (titles,\nheadings, structured data, sitemap, canonicals) and make it fast and\nusable for humans (Core Web Vitals, mobile, HTTPS). Both feed the\nsame ranking signals.\n\n## Overview\n\n### On-page SEO\n\n- **Title tags:** unique per page, 50–60 characters, primary\n  keyword near the start.\n- **Meta descriptions:** 120–160 characters, with a call to action,\n  unique per page.\n- **Headings:** one `\u003Ch1>` per page matching the topic; logical\n  `\u003Ch2>`–`\u003Ch6>` hierarchy without skipping levels.\n- **Alt text:** descriptive, concise (≤125 chars), keywords used\n  naturally. Decorative images use `alt=\"\"`.\n- **Internal links:** descriptive anchor text — never \"click here\".\n- **URLs:** short, lowercase, hyphen-separated, include the\n  primary keyword.\n- **Content:** answer the user's query comprehensively; use\n  related terms naturally rather than keyword-stuffing.\n\n### Crawling and indexing\n\n- **robots.txt** at the site root: allow important paths, block\n  admin and staging.\n- **XML sitemap** lists all indexable pages, excludes `noindex`\n  pages, submitted to Search Console.\n- **Canonicals** on every page (`\u003Clink rel=\"canonical\">`) to\n  prevent duplicate content.\n- **Hreflang** for multilingual sites\n  (`\u003Clink rel=\"alternate\" hreflang=\"en\">` per language) with a\n  self-referencing entry and `x-default`.\n- **HTTP status codes:** 200 for live, 301 for permanent redirects,\n  404 for gone. No soft 404s.\n- **Redirect chains:** at most one hop. Fix chains to point\n  directly to the final URL.\n- **Index control:** `\u003Cmeta name=\"robots\" content=\"noindex\">` on\n  pages that should not rank.\n\n### Structured data (JSON-LD)\n\n- Use JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">` in the\n  `\u003Chead>`. Prefer it over Microdata or RDFa.\n- Common types: `Article`, `Product`, `FAQPage`, `BreadcrumbList`,\n  `Organization`, `LocalBusiness`.\n- `@context: \"https:\u002F\u002Fschema.org\"` and the most specific `@type`\n  available.\n- Match structured data to visible page content — never add data\n  that is not shown on the page.\n- Validate with Google Rich Results Test before deploying.\n- Add `BreadcrumbList` for hierarchical navigation.\n\n### Core Web Vitals\n\n- **LCP (Largest Contentful Paint):** target \u003C 2.5s. Preload the\n  LCP image, use responsive `srcset`, inline critical CSS, defer\n  non-critical stylesheets.\n- **INP (Interaction to Next Paint):** target \u003C 200ms. Break up\n  long tasks (>50ms) with `requestIdleCallback` or\n  `scheduler.yield()`. Minimize main-thread work in interaction\n  handlers. Debounce rapid input events.\n- **CLS (Cumulative Layout Shift):** target \u003C 0.1. Set explicit\n  `width` and `height` on images and video. Reserve space for ads\n  and embeds. Avoid inserting content above the fold after initial\n  render. Use `font-display: swap` with preloaded fonts.\n\n### Page speed\n\n- Inline critical CSS and defer non-critical JS.\n- Compress images with WebP\u002FAVIF and provide fallbacks; lazy-load\n  below-fold images.\n- Enable HTTP\u002F2 or HTTP\u002F3 for multiplexed requests.\n- Serve static assets from a CDN to reduce TTFB.\n- Minify HTML\u002FCSS\u002FJS and enable Brotli or gzip.\n- Audit with Lighthouse: `npx lighthouse \u003Curl> --output=json`.\n\n### Mobile-first indexing\n\n- Google indexes the mobile version, so ensure content parity with\n  desktop.\n- Responsive design preferred: same URL, same HTML, CSS adapts.\n- Viewport tag:\n  `\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1\">`.\n- Base font size at least 16px so text is readable without zooming.\n- No horizontal scrolling at any viewport width.\n- Touch targets ≥ 48×48 CSS pixels with 8px spacing.\n- Verify with Chrome DevTools device emulation and Google's\n  Mobile-Friendly Test.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Writing generic or duplicate title tags across pages.** Title tags must be unique per page and lead with the primary keyword. Duplicate or generic titles (\"Home | Acme\" on every page) reduce click-through rate and confuse crawlers about which page to rank for a given query.\n- **Adding structured data that does not match visible page content.** A `Product` schema with a price not shown on the page, or an `Article` schema on a non-article page, fails Google's validation and may trigger manual actions. Structured data must reflect exactly what the user sees.\n- **Creating redirect chains longer than one hop.** Each additional hop adds latency and loses link equity. A chain A → B → C → D should be collapsed to a direct A → D redirect. Check for chains after any URL restructuring.\n- **Deploying pages without a canonical tag.** Without `\u003Clink rel=\"canonical\">`, a page accessible at multiple URLs (HTTP vs HTTPS, trailing slash, query parameters) fragments its link equity across variants. Every indexable page needs a self-referencing canonical even when there are no obvious duplicates.\n- **Optimizing for average load time instead of Core Web Vitals p75.** Google's ranking signals are p75 LCP, INP, and CLS — not average page load time. A fast average with a slow p75 LCP still ranks poorly. Measure and optimize the 75th-percentile field data, not only Lighthouse scores.\n- **Using `noindex` together with `Disallow` in robots.txt on the same URLs.** `Disallow` prevents crawling; if the page is also `noindex`, crawlers cannot discover the directive. Index control via `noindex` requires the page to remain crawlable. Use one or the other, not both.\n- **Shipping structured data changes without validating in the Rich Results Test.** Syntax errors in JSON-LD prevent rich results from appearing, but the page itself renders normally and the error is invisible without explicit testing. Always validate in the Rich Results Test before deploying.\n\n## Full reference\n\n### Internal linking\n\n- Link from high-authority pages to important pages that need\n  ranking signals.\n- Create content hubs: a pillar page links to cluster pages and\n  back.\n- Limit links per page to a reasonable number (under ~100).\n- Fix orphan pages — every indexable page should be reachable via\n  internal links.\n- Use breadcrumbs for hierarchical navigation and search engine\n  context.\n\n### Security and trust\n\n- Serve every page over HTTPS.\n- Set HSTS:\n  `Strict-Transport-Security: max-age=31536000; includeSubDomains`.\n- No mixed content (HTTP resources on HTTPS pages).\n- Set `X-Content-Type-Options: nosniff` and `X-Frame-Options`.\n- Configure a Content Security Policy.\n- Surface E-E-A-T signals: author bios, about pages, contact info,\n  reviews and certifications where relevant.\n\n### Technical SEO checklist\n\nA condensed actionable checklist (full version in\n`references\u002Ftechnical-seo-checklist.md`):\n\n**Crawling and indexing**\n\n- [ ] `robots.txt` exists; allows important paths, blocks admin\n- [ ] XML sitemap lists indexable pages and is submitted to\n  Search Console and Bing Webmaster Tools\n- [ ] No orphan pages\n- [ ] Redirect chains resolved (max 1 hop), no loops\n- [ ] 404s return real 404 status (not soft 404)\n- [ ] Removed pages return 410 or redirect to relevant content\n\n**Canonicals and duplicates**\n\n- [ ] Every page has a self-referencing or preferred canonical\n- [ ] Pagination uses sensible canonical strategy (not all to\n  page 1)\n- [ ] WWW vs non-WWW redirects configured to one canonical\n- [ ] Trailing-slash behavior consistent\n- [ ] HTTP redirects to HTTPS\n\n**Performance**\n\n- [ ] LCP \u003C 2.5s, INP \u003C 200ms, CLS \u003C 0.1\n- [ ] Images have explicit `width`\u002F`height`\n- [ ] Above-fold images preloaded; below-fold use `loading=\"lazy\"`\n- [ ] Fonts preloaded with `font-display: swap`\n- [ ] Critical CSS inlined; non-critical CSS deferred\n- [ ] JavaScript deferred or async where possible\n- [ ] Brotli\u002Fgzip enabled, static assets from CDN\n\n**Structured data**\n\n- [ ] JSON-LD format\n- [ ] `@context` is `https:\u002F\u002Fschema.org`\n- [ ] Most specific `@type` used\n- [ ] Fields match visible content\n- [ ] Validates clean in Google Rich Results Test\n- [ ] `BreadcrumbList` on hierarchical pages\n\n### JSON-LD examples\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Article Title\",\n  \"author\": { \"@type\": \"Person\", \"name\": \"Author Name\" },\n  \"datePublished\": \"2025-01-15\",\n  \"image\": \"https:\u002F\u002Fexample.com\u002Fimage.jpg\"\n}\n```\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Product\",\n  \"name\": \"Product Name\",\n  \"image\": \"https:\u002F\u002Fexample.com\u002Fproduct.jpg\",\n  \"description\": \"Product description\",\n  \"offers\": {\n    \"@type\": \"Offer\",\n    \"price\": \"29.99\",\n    \"priceCurrency\": \"USD\",\n    \"availability\": \"https:\u002F\u002Fschema.org\u002FInStock\"\n  }\n}\n```\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [{\n    \"@type\": \"Question\",\n    \"name\": \"What is the return policy?\",\n    \"acceptedAnswer\": {\n      \"@type\": \"Answer\",\n      \"text\": \"You can return items within 30 days.\"\n    }\n  }]\n}\n```\n\n### Anti-patterns\n\n- Stuffing keywords into titles, alt text, or body copy\n- Adding structured data that does not match visible content\n- Using \"click here\" or bare URLs as anchor text\n- Letting redirect chains accumulate over time\n- Lazy-loading the LCP image (defeats the preload)\n- Treating mobile as an afterthought when Google indexes mobile\n  first\n- Blocking CSS or JS in `robots.txt` — Googlebot needs them to\n  render\n\n### References\n\n- `references\u002Ftechnical-seo-checklist.md` — full checklist by\n  category\n- [Google Search Central](https:\u002F\u002Fdevelopers.google.com\u002Fsearch)\n- [web.dev Core Web Vitals](https:\u002F\u002Fweb.dev\u002Fvitals\u002F)\n","# SEO Optimization\n\n## Intro\n\nSEO is two jobs: make the page understandable to crawlers (titles,\nheadings, structured data, sitemap, canonicals) and make it fast and\nusable for humans (Core Web Vitals, mobile, HTTPS). Both feed the\nsame ranking signals.\n\n## Overview\n\n### On-page SEO\n\n- **Title tags:** unique per page, 50–60 characters, primary\n  keyword near the start.\n- **Meta descriptions:** 120–160 characters, with a call to action,\n  unique per page.\n- **Headings:** one `\u003Ch1>` per page matching the topic; logical\n  `\u003Ch2>`–`\u003Ch6>` hierarchy without skipping levels.\n- **Alt text:** descriptive, concise (≤125 chars), keywords used\n  naturally. Decorative images use `alt=\"\"`.\n- **Internal links:** descriptive anchor text — never \"click here\".\n- **URLs:** short, lowercase, hyphen-separated, include the\n  primary keyword.\n- **Content:** answer the user's query comprehensively; use\n  related terms naturally rather than keyword-stuffing.\n\n### Crawling and indexing\n\n- **robots.txt** at the site root: allow important paths, block\n  admin and staging.\n- **XML sitemap** lists all indexable pages, excludes `noindex`\n  pages, submitted to Search Console.\n- **Canonicals** on every page (`\u003Clink rel=\"canonical\">`) to\n  prevent duplicate content.\n- **Hreflang** for multilingual sites\n  (`\u003Clink rel=\"alternate\" hreflang=\"en\">` per language) with a\n  self-referencing entry and `x-default`.\n- **HTTP status codes:** 200 for live, 301 for permanent redirects,\n  404 for gone. No soft 404s.\n- **Redirect chains:** at most one hop. Fix chains to point\n  directly to the final URL.\n- **Index control:** `\u003Cmeta name=\"robots\" content=\"noindex\">` on\n  pages that should not rank.\n\n### Structured data (JSON-LD)\n\n- Use JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">` in the\n  `\u003Chead>`. Prefer it over Microdata or RDFa.\n- Common types: `Article`, `Product`, `FAQPage`, `BreadcrumbList`,\n  `Organization`, `LocalBusiness`.\n- `@context: \"https:\u002F\u002Fschema.org\"` and the most specific `@type`\n  available.\n- Match structured data to visible page content — never add data\n  that is not shown on the page.\n- Validate with Google Rich Results Test before deploying.\n- Add `BreadcrumbList` for hierarchical navigation.\n\n### Core Web Vitals\n\n- **LCP (Largest Contentful Paint):** target \u003C 2.5s. Preload the\n  LCP image, use responsive `srcset`, inline critical CSS, defer\n  non-critical stylesheets.\n- **INP (Interaction to Next Paint):** target \u003C 200ms. Break up\n  long tasks (>50ms) with `requestIdleCallback` or\n  `scheduler.yield()`. Minimize main-thread work in interaction\n  handlers. Debounce rapid input events.\n- **CLS (Cumulative Layout Shift):** target \u003C 0.1. Set explicit\n  `width` and `height` on images and video. Reserve space for ads\n  and embeds. Avoid inserting content above the fold after initial\n  render. Use `font-display: swap` with preloaded fonts.\n\n### Page speed\n\n- Inline critical CSS and defer non-critical JS.\n- Compress images with WebP\u002FAVIF and provide fallbacks; lazy-load\n  below-fold images.\n- Enable HTTP\u002F2 or HTTP\u002F3 for multiplexed requests.\n- Serve static assets from a CDN to reduce TTFB.\n- Minify HTML\u002FCSS\u002FJS and enable Brotli or gzip.\n- Audit with Lighthouse: `npx lighthouse \u003Curl> --output=json`.\n\n### Mobile-first indexing\n\n- Google indexes the mobile version, so ensure content parity with\n  desktop.\n- Responsive design preferred: same URL, same HTML, CSS adapts.\n- Viewport tag:\n  `\u003Cmeta name=\"viewport\" content=\"width=device-width, initial-scale=1\">`.\n- Base font size at least 16px so text is readable without zooming.\n- No horizontal scrolling at any viewport width.\n- Touch targets ≥ 48×48 CSS pixels with 8px spacing.\n- Verify with Chrome DevTools device emulation and Google's\n  Mobile-Friendly Test.\n\n## Gotchas\n\nAgent-specific failure modes — provider-neutral pause-and-self-check items:\n\n- **Writing generic or duplicate title tags across pages.** Title tags must be unique per page and lead with the primary keyword. Duplicate or generic titles (\"Home | Acme\" on every page) reduce click-through rate and confuse crawlers about which page to rank for a given query.\n- **Adding structured data that does not match visible page content.** A `Product` schema with a price not shown on the page, or an `Article` schema on a non-article page, fails Google's validation and may trigger manual actions. Structured data must reflect exactly what the user sees.\n- **Creating redirect chains longer than one hop.** Each additional hop adds latency and loses link equity. A chain A → B → C → D should be collapsed to a direct A → D redirect. Check for chains after any URL restructuring.\n- **Deploying pages without a canonical tag.** Without `\u003Clink rel=\"canonical\">`, a page accessible at multiple URLs (HTTP vs HTTPS, trailing slash, query parameters) fragments its link equity across variants. Every indexable page needs a self-referencing canonical even when there are no obvious duplicates.\n- **Optimizing for average load time instead of Core Web Vitals p75.** Google's ranking signals are p75 LCP, INP, and CLS — not average page load time. A fast average with a slow p75 LCP still ranks poorly. Measure and optimize the 75th-percentile field data, not only Lighthouse scores.\n- **Using `noindex` together with `Disallow` in robots.txt on the same URLs.** `Disallow` prevents crawling; if the page is also `noindex`, crawlers cannot discover the directive. Index control via `noindex` requires the page to remain crawlable. Use one or the other, not both.\n- **Shipping structured data changes without validating in the Rich Results Test.** Syntax errors in JSON-LD prevent rich results from appearing, but the page itself renders normally and the error is invisible without explicit testing. Always validate in the Rich Results Test before deploying.\n\n## Full reference\n\n### Internal linking\n\n- Link from high-authority pages to important pages that need\n  ranking signals.\n- Create content hubs: a pillar page links to cluster pages and\n  back.\n- Limit links per page to a reasonable number (under ~100).\n- Fix orphan pages — every indexable page should be reachable via\n  internal links.\n- Use breadcrumbs for hierarchical navigation and search engine\n  context.\n\n### Security and trust\n\n- Serve every page over HTTPS.\n- Set HSTS:\n  `Strict-Transport-Security: max-age=31536000; includeSubDomains`.\n- No mixed content (HTTP resources on HTTPS pages).\n- Set `X-Content-Type-Options: nosniff` and `X-Frame-Options`.\n- Configure a Content Security Policy.\n- Surface E-E-A-T signals: author bios, about pages, contact info,\n  reviews and certifications where relevant.\n\n### Technical SEO checklist\n\nA condensed actionable checklist (full version in\n`references\u002Ftechnical-seo-checklist.md`):\n\n**Crawling and indexing**\n\n- [ ] `robots.txt` exists; allows important paths, blocks admin\n- [ ] XML sitemap lists indexable pages and is submitted to\n  Search Console and Bing Webmaster Tools\n- [ ] No orphan pages\n- [ ] Redirect chains resolved (max 1 hop), no loops\n- [ ] 404s return real 404 status (not soft 404)\n- [ ] Removed pages return 410 or redirect to relevant content\n\n**Canonicals and duplicates**\n\n- [ ] Every page has a self-referencing or preferred canonical\n- [ ] Pagination uses sensible canonical strategy (not all to\n  page 1)\n- [ ] WWW vs non-WWW redirects configured to one canonical\n- [ ] Trailing-slash behavior consistent\n- [ ] HTTP redirects to HTTPS\n\n**Performance**\n\n- [ ] LCP \u003C 2.5s, INP \u003C 200ms, CLS \u003C 0.1\n- [ ] Images have explicit `width`\u002F`height`\n- [ ] Above-fold images preloaded; below-fold use `loading=\"lazy\"`\n- [ ] Fonts preloaded with `font-display: swap`\n- [ ] Critical CSS inlined; non-critical CSS deferred\n- [ ] JavaScript deferred or async where possible\n- [ ] Brotli\u002Fgzip enabled, static assets from CDN\n\n**Structured data**\n\n- [ ] JSON-LD format\n- [ ] `@context` is `https:\u002F\u002Fschema.org`\n- [ ] Most specific `@type` used\n- [ ] Fields match visible content\n- [ ] Validates clean in Google Rich Results Test\n- [ ] `BreadcrumbList` on hierarchical pages\n\n### JSON-LD examples\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"Article Title\",\n  \"author\": { \"@type\": \"Person\", \"name\": \"Author Name\" },\n  \"datePublished\": \"2025-01-15\",\n  \"image\": \"https:\u002F\u002Fexample.com\u002Fimage.jpg\"\n}\n```\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Product\",\n  \"name\": \"Product Name\",\n  \"image\": \"https:\u002F\u002Fexample.com\u002Fproduct.jpg\",\n  \"description\": \"Product description\",\n  \"offers\": {\n    \"@type\": \"Offer\",\n    \"price\": \"29.99\",\n    \"priceCurrency\": \"USD\",\n    \"availability\": \"https:\u002F\u002Fschema.org\u002FInStock\"\n  }\n}\n```\n\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [{\n    \"@type\": \"Question\",\n    \"name\": \"What is the return policy?\",\n    \"acceptedAnswer\": {\n      \"@type\": \"Answer\",\n      \"text\": \"You can return items within 30 days.\"\n    }\n  }]\n}\n```\n\n### Anti-patterns\n\n- Stuffing keywords into titles, alt text, or body copy\n- Adding structured data that does not match visible content\n- Using \"click here\" or bare URLs as anchor text\n- Letting redirect chains accumulate over time\n- Lazy-loading the LCP image (defeats the preload)\n- Treating mobile as an afterthought when Google indexes mobile\n  first\n- Blocking CSS or JS in `robots.txt` — Googlebot needs them to\n  render\n\n### References\n\n- `references\u002Ftechnical-seo-checklist.md` — full checklist by\n  category\n- [Google Search Central](https:\u002F\u002Fdevelopers.google.com\u002Fsearch)\n- [web.dev Core Web Vitals](https:\u002F\u002Fweb.dev\u002Fvitals\u002F)\n",{"name":5,"metadata":54,"description":60},{"processkit":55},{"id":56,"created":57,"version":58,"category":41,"apiVersion":59},"SKILL-seo-optimization",1775433600000,"1.1.0","processkit.projectious.work\u002Fv2","SEO — on-page, technical, structured data, Core Web Vitals, and mobile-first indexing. Use when optimizing a website for search engines, adding meta tags or structured data, fixing Core Web Vitals, or auditing technical SEO.\n","main","7231f100e266e30d2c1699ecde5c00602471dc3c","src\u002Fcontext\u002Fskills\u002Fdesign\u002Fseo-optimization","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit","https:\u002F\u002Fprojectious-work.github.io\u002Fprocesskit\u002F","https:\u002F\u002Fgithub.com\u002Fprojectious-work","2026-11-11 23:24:18",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add projectious-work\u002Fprocesskit --skill seo-optimization",{"tool":74,"command":75},"bunx","bunx skills add projectious-work\u002Fprocesskit --skill seo-optimization",{"tool":77,"command":78},"pnpm","pnpm dlx skills add projectious-work\u002Fprocesskit --skill seo-optimization","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdesign\u002Fseo-optimization\u002FSKILL.md",true,[82,88],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Ftechnical-seo-checklist.md","REFERENCE","参考文档",4219,"https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdesign\u002Fseo-optimization\u002Freferences\u002Ftechnical-seo-checklist.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":14,"sourceHtmlUrl":92},"scripts\u002F.gitkeep","SCRIPT","脚本","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fdesign\u002Fseo-optimization\u002Fscripts\u002F.gitkeep",[94,101,108,114,139,159],{"skillNo":95,"name":96,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":100},"01M7665G2ED3624R3X93304265","standard-ui-design","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-ui-design\u002FSKILL.md",[],[],"2026-11-12 13:55:43",{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":100},"01M76651QTC6W0HJ4AFW2MMR3V","standard-agent-use","Company standard for working with AI agents. Use when deciding what to delegate to agents, capturing open work, keeping agent memory or knowledge notes, improving an agent workflow, or introducing agent work in a team or for a client.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-use\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":100},"01M76650NN4T8P241021NBR64S","standard-agent-building","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fstandard-agent-building\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":123,"publishedAt":49},"01M6X5MTC89B4ZGXW3JVSQCPF8","skill-management","Manage Skill package manifests as v1 ontology entities.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fskill-management\u002FSKILL.md",[120],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[124,125,126,127,128,129,32,130,131,132,133,134,116,135,136,137,138],"management","skill management","ontology","v1","create","as","transition","get","manage","update","alpha","list","package","skill package","manifests",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":146,"publishedAt":49},"01M6X5MCV74NHW5MEDNHZRF2C8","schema-management","Manage generated processkit schema contracts through deterministic MCP rebuild and inspection workflows.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fschema-management\u002FSKILL.md",[145],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[147,148,124,149,150,151,152,153,154,155,156,157,32,131,132,134,158],"schema","schema management","contract","rebuild","contracts","workflows","wed","generated","MCP","validation","deterministic","mode",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":49},"01M6X5M5G6YJ96AMZGSCZJ1D13","proposition-management","Record claims, risks, beliefs, world facts, WSJF estimates, and assumptions through the Proposition interface.","https:\u002F\u002Fgithub.com\u002Fprojectious-work\u002Fprocesskit\u002Fblob\u002Fmain\u002Fsrc\u002Fcontext\u002Fskills\u002Fprocesskit\u002Fproposition-management\u002FSKILL.md",[],[166,124,167,168,128,169,170,171,32,131,172,173,133,174,134,175,176,177,178,179],"proposition management","proposition","interface","claims","record","world","creation","event","WSJF","index","updates","query","facts","log"]