[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FN9M05GCHYTK848SSMN9R":3,"skill-same:01M78FN9M05GCHYTK848SSMN9R":47},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M78FN9M05GCHYTK848SSMN9R","web-seo",null,"Use when improving technical and entity SEO for a modern personal, portfolio, documentation, or marketing site, including crawlable HTML, canonical metadata, sitemap and robots, Person\u002FProfilePage JSON-LD, Core Web Vitals, and honest ranking expectations.","jeswr\u002Fsolid-sdk","jeswr","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F63333554?v=4","01M78F8AE112CQ0KHFC3R0Z8SJ","Jesse Wright","01M78F8AERJX4YWDA1S4BMF74V",2,"MIT","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fweb-seo\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: web-seo\ndescription: Use when improving technical and entity SEO for a modern personal, portfolio, documentation, or marketing site, including crawlable HTML, canonical metadata, sitemap and robots, Person\u002FProfilePage JSON-LD, Core Web Vitals, and honest ranking expectations.\n---\n\n## Quick reference\n\n\u003C!-- AUTHORED-BY Codex GPT-5 -->\n\n**Improve web SEO honestly**\n\nOn-page work makes a site crawlable and understandable; it cannot guarantee rank. For a common personal name, backlinks, consistent identity signals, and time often dominate.\n\n### Technical baseline\n\n- Server-render or statically generate indexable content.\n- Verify raw crawler HTML contains the title, one meaningful H1, body copy, canonical URL, and structured data.\n- Use one canonical HTTPS host with real 200\u002Fredirect\u002F404\u002F410 statuses and no cloaking.\n- Publish `robots.txt` and `sitemap.xml`; ensure they reference the intended canonical URLs.\n- Keep content negotiation and middleware away from framework assets and prove HTML requests cannot receive an RDF representation accidentally.\n- Provide unique titles\u002Fdescriptions, Open Graph\u002FTwitter metadata, absolute image URLs, and stable icons\u002Fmanifest.\n\n### Entity structured data\n\nFor a personal profile, connect `Person`, `ProfilePage`, and `WebSite` JSON-LD nodes with stable `@id` values. Add only visible, true facts. Use `sameAs` for verified authoritative profiles and keep it consistent with any RDFa\u002FWebID identity graph.\n\nDo not invent ORCID, Wikidata, affiliation, or profile identifiers. Validate JSON-LD with current schema and search-engine tools.\n\n### Content and performance\n\n- Put the person's or product's primary name in title, H1, and natural prose.\n- Publish useful dated\u002Fauthored material, credentials, projects, and topical evidence.\n- Keep client JavaScript small, reserve image dimensions, optimize the largest content element, and measure field Core Web Vitals.\n- Use descriptive internal links and accessible link text.\n\n### Human follow-up\n\nList backlinks, Search Console\u002FBing verification, sitemap submission, and knowledge-graph\u002Fprofile consistency as explicit maintainer actions. Report eligibility and validation results; never promise a ranking position.\n\n### Agent persona\n\nWhen this work is delegated to a sub-agent, spawn the `solid-frontend-dev` persona from\n[`.claude\u002Fagents\u002Fsolid-frontend-dev.md`](..\u002F..\u002F.claude\u002Fagents\u002Fsolid-frontend-dev.md) — it routes through this skill.\nOrchestration: `.claude\u002Fagents\u002Fsolid-app-orchestration.md`.\n\n\u003C!-- AUTHORED-BY Codex GPT-6.1-Sol -->\n\n# web-seo — SEO for a modern personal \u002F portfolio site\n\n## The one thing to internalize first (honesty rule)\n\nOn-page SEO makes a site **eligible** and **legible**. It does not buy rank.\nFor a **common personal name** (\"Jesse Wright\", \"John Smith\") ranking #1 is\ndominated by **off-page authority** (who links to you, how strong those domains\nare) and **time\u002Fconsistency** — not by any tag you can add. So split every\nengagement into:\n\n- **On-page (you control, do now):** crawlability, metadata, structured data,\n  content, internal links, performance. Aim: be the single canonical, clearly-\n  described, entity-resolved page for the person.\n- **Off-page (you influence, takes time):** authoritative backlinks, a Wikidata\u002F\n  Knowledge-Graph entity, consistent name-and-bio across the web. List these as\n  explicit human actions; never promise a ranking.\n\nTell the user this up front. Over-promising rank is the cardinal SEO sin.\n\n## 1. Crawlability & render — Googlebot must get full HTML\n\nGoogle crawls → renders (headless Chromium runs JS) → indexes, but Google itself\nsays server-side or pre-rendering is still a great idea — not all bots run JS. So:\n\n- **SSR or SSG every indexable route.** Keep page content in Server Components;\n  push interactivity to small `\"use client\"` leaves. A client-only SPA shell that\n  paints empty HTML risks thin\u002Flate indexing and starves non-Google + AI bots.\n- **Verify the bytes a crawler receives:** `curl -A \"Googlebot\" -H \"Accept: text\u002Fhtml,...\" URL`\n  and confirm `\u003Ctitle>`, `\u003Ch1>`, body copy, and JSON-LD are in the RAW HTML.\n- **Never serve different content to Googlebot than to users** (cloaking — a\n  Google violation). Same content, same status codes.\n- **Edge middleware \u002F content-negotiation is a crawl hazard.** If a middleware\n  transforms responses by `Accept` header (e.g. RDF conneg), prove the `text\u002Fhtml`\n  branch returns the page unchanged, runs no extra origin fetch on the crawl path,\n  and is scoped with a `matcher` so it never touches `\u002F_next\u002F*`, sitemap, robots,\n  or icons. A negotiator that can pick a non-HTML representation for any `Accept`\n  a bot might send is a latent de-indexing bug.\n- Real HTTP status codes (200\u002F301\u002F308\u002F404\u002F410), one canonical host (pick apex OR\n  www and 301\u002F308 the other), HTTPS only, no redirect chains.\n\n## 2. Next.js App Router metadata (the legible layer)\n\nUse the Metadata API (Server Components only):\n- **`metadataBase`** in the root layout = production origin (so relative OG image\n  URLs resolve to absolute — social scrapers need absolute).\n- **`title`** as `{ default, template: \"%s — Name\" }`; per-page `title` strings.\n- **`description`** — unique, ~150 chars, includes the primary query naturally.\n- **`alternates: { canonical }`** — absolute, self-canonical per page.\n- **`robots: { index, follow, googleBot }`**.\n- **`openGraph`**: title, description, url, siteName, type ('website'|'profile'),\n  images [{ url, width:1200, height:630, alt }], locale.\n- **`twitter`**: card 'summary_large_image', title, description, images, creator.\n- **OG image 1200×630** — a static `app\u002Fopengraph-image.(png|jpg)` \u002F `app\u002Ftwitter-image.png`,\n  or a dynamic `opengraph-image.tsx` using `ImageResponse` from `next\u002Fog`.\n- **Favicons\u002Fmanifest** via file conventions: `app\u002Ffavicon.ico`, `app\u002Ficon.png`,\n  `app\u002Fapple-icon.png`, `app\u002Fmanifest.ts`.\n- **`app\u002Fsitemap.ts`** → `MetadataRoute.Sitemap`. **`app\u002Frobots.ts`** →\n  `MetadataRoute.Robots` (rules + sitemap + host).\n- Next ≥15 streams metadata on dynamic pages but disables streaming for known\n  bots; prefer static\u002Fprerendered pages so metadata is in the HTML at build time.\n\n## 3. Structured data — the key ENTITY lever (JSON-LD)\n\nGoogle prefers **JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">`**. This makes a\nperson a resolvable **entity** (Knowledge Graph, AI-answer citations), not a\nstring. Emit three connected nodes:\n- **`Person`** with a stable `@id` (the page's own identity URI, e.g. `https:\u002F\u002Fsite\u002F#me`),\n  name, alternateName, url, image, jobTitle, worksFor\u002Faffiliation, alumniOf,\n  description, `knowsAbout` (topics to be associated with), and **`sameAs`** — an\n  array of EVERY authoritative profile (GitHub, LinkedIn, ORCID, Google Scholar,\n  employer\u002Funiversity page, X, Mastodon, and crucially Wikidata\u002FWikipedia if they\n  exist). `sameAs` is the strongest entity-resolution signal; Wikidata is a direct\n  Knowledge-Graph input.\n- **`WebSite`** (url, name, publisher\u002Fauthor → the Person `@id`).\n- **`ProfilePage`** (Google-supported) with `mainEntity` → the Person; recommended\n  `dateCreated`\u002F`dateModified`.\nRules: the JSON-LD must match visible page content (Google policy — no markup-only\nfacts). Validate with the Rich Results Test + Schema Markup Validator. Keep `@id`s\nconsistent across pages so the graph links into one entity.\n\n### Coexisting JSON-LD (SEO) with RDFa (a WebID\u002FLinked-Data profile)\nA site can be both a human page and a machine-readable profile:\n- **RDFa** = attributes on the visible DOM (`typeof`\u002F`property`\u002F`resource`),\n  consumed by RDF parsers \u002F content-negotiation to Turtle. Keep it for a WebID.\n- **JSON-LD** = a `\u003Cscript>` block, consumed by search engines. Add it for SEO.\n- **Align the subject URI:** point the JSON-LD `Person` `@id` at the SAME identity\n  URI the RDFa\u002FWebID uses (`…\u002F#me`). Use schema.org terms in both so the Turtle\n  conneg output and the JSON-LD agree. Keep the two `sameAs` lists identical. Do\n  NOT rely on RDFa alone for SEO (JSON-LD is Google's recommended, rich-results\n  path), and do NOT drop RDFa for JSON-LD (it would break the WebID conneg).\n\n## 4. Content & E-E-A-T\n\n- **Name in `\u003Ctitle>` and the single `\u003Ch1>`.** One `\u003Ch1>` per page.\n- **Real, dated, authored content** in server-rendered HTML (a name-only SPA stub\n  is thin). Bio + what you do + your topics, in prose.\n- **Natural keyword use** — topics woven into sentences, not stuffed.\n- **Outbound links to your own authoritative profiles** corroborate the entity.\n- For a researcher\u002Fprofessional: surface credentials, affiliations, publications,\n  talks — and mirror them in `Person` (jobTitle, affiliation, alumniOf, knowsAbout).\n- Descriptive URLs; meaningful internal links.\n\n## 5. Core Web Vitals (the performance gate; p75 of real users)\n\nThresholds: **LCP \u003C 2.5 s · INP \u003C 200 ms · CLS \u003C 0.1**, at the 75th percentile of\nfield data (CrUX); lab scores are diagnostic only. Levers: SSR\u002FSSG, ship less JS\n(Server Components + dynamic-import client islands), `next\u002Fimage` with explicit\nwidth\u002Fheight + priority on the LCP image, `next\u002Ffont` (no layout-shift swap),\npreconnect to needed origins.\n\n## 6. Off-page (human actions — list as needs:user, never promise rank)\n\n- **Backlinks from authoritative profiles → the site** (employer staff page,\n  university dept page, ORCID, Scholar, GitHub, LinkedIn, conference speaker pages)\n  — the strongest realistic lever for a personal name.\n- **Knowledge Graph \u002F Wikidata** — create\u002Fclaim a Wikidata item (notability\n  permitting) + add the site + sameAs. Direct Knowledge-Graph input.\n- **Google Search Console** — verify (DNS TXT or HTML meta), submit the sitemap,\n  monitor coverage + CWV + queries. **Bing Webmaster Tools** likewise.\n- **Consistency** — identical name, bio, headshot across all profiles.\n\n## 7. Verify before claiming done\n\n- `curl -A Googlebot` the page; title\u002Fh1\u002Fbody\u002FJSON-LD in raw HTML.\n- Rich Results Test + Schema Markup Validator (zero errors).\n- `\u002Fsitemap.xml` + `\u002Frobots.txt` resolve and reference each other.\n- One canonical host; no redirect chains; HTTPS; 404 returns 404.\n- PageSpeed Insights \u002F CrUX for field CWV.\n- Search Console: property verified, sitemap submitted, no coverage errors.\n\n## Anti-patterns\n\n- Promising a rank (esp. for a common name).\n- Keyword stuffing; markup describing facts not visible on the page (policy\n  violation → possible structured-data manual action).\n- Cloaking \u002F serving bots different content.\n- A client-only SPA with an empty HTML shell as the indexable page.\n- A middleware\u002Fconneg layer that can return non-HTML to a crawler, double-fetches\n  on the crawl path, or lacks a `matcher`.\n- Inventing identifiers (ORCID, Wikidata IDs) — only assert profiles the person\n  owns; a wrong `sameAs` poisons entity resolution.\n","## Quick reference\n\n\u003C!-- AUTHORED-BY Codex GPT-5 -->\n\n**Improve web SEO honestly**\n\nOn-page work makes a site crawlable and understandable; it cannot guarantee rank. For a common personal name, backlinks, consistent identity signals, and time often dominate.\n\n### Technical baseline\n\n- Server-render or statically generate indexable content.\n- Verify raw crawler HTML contains the title, one meaningful H1, body copy, canonical URL, and structured data.\n- Use one canonical HTTPS host with real 200\u002Fredirect\u002F404\u002F410 statuses and no cloaking.\n- Publish `robots.txt` and `sitemap.xml`; ensure they reference the intended canonical URLs.\n- Keep content negotiation and middleware away from framework assets and prove HTML requests cannot receive an RDF representation accidentally.\n- Provide unique titles\u002Fdescriptions, Open Graph\u002FTwitter metadata, absolute image URLs, and stable icons\u002Fmanifest.\n\n### Entity structured data\n\nFor a personal profile, connect `Person`, `ProfilePage`, and `WebSite` JSON-LD nodes with stable `@id` values. Add only visible, true facts. Use `sameAs` for verified authoritative profiles and keep it consistent with any RDFa\u002FWebID identity graph.\n\nDo not invent ORCID, Wikidata, affiliation, or profile identifiers. Validate JSON-LD with current schema and search-engine tools.\n\n### Content and performance\n\n- Put the person's or product's primary name in title, H1, and natural prose.\n- Publish useful dated\u002Fauthored material, credentials, projects, and topical evidence.\n- Keep client JavaScript small, reserve image dimensions, optimize the largest content element, and measure field Core Web Vitals.\n- Use descriptive internal links and accessible link text.\n\n### Human follow-up\n\nList backlinks, Search Console\u002FBing verification, sitemap submission, and knowledge-graph\u002Fprofile consistency as explicit maintainer actions. Report eligibility and validation results; never promise a ranking position.\n\n### Agent persona\n\nWhen this work is delegated to a sub-agent, spawn the `solid-frontend-dev` persona from\n[`.claude\u002Fagents\u002Fsolid-frontend-dev.md`](..\u002F..\u002F.claude\u002Fagents\u002Fsolid-frontend-dev.md) — it routes through this skill.\nOrchestration: `.claude\u002Fagents\u002Fsolid-app-orchestration.md`.\n\n\u003C!-- AUTHORED-BY Codex GPT-6.1-Sol -->\n\n# web-seo — SEO for a modern personal \u002F portfolio site\n\n## The one thing to internalize first (honesty rule)\n\nOn-page SEO makes a site **eligible** and **legible**. It does not buy rank.\nFor a **common personal name** (\"Jesse Wright\", \"John Smith\") ranking #1 is\ndominated by **off-page authority** (who links to you, how strong those domains\nare) and **time\u002Fconsistency** — not by any tag you can add. So split every\nengagement into:\n\n- **On-page (you control, do now):** crawlability, metadata, structured data,\n  content, internal links, performance. Aim: be the single canonical, clearly-\n  described, entity-resolved page for the person.\n- **Off-page (you influence, takes time):** authoritative backlinks, a Wikidata\u002F\n  Knowledge-Graph entity, consistent name-and-bio across the web. List these as\n  explicit human actions; never promise a ranking.\n\nTell the user this up front. Over-promising rank is the cardinal SEO sin.\n\n## 1. Crawlability & render — Googlebot must get full HTML\n\nGoogle crawls → renders (headless Chromium runs JS) → indexes, but Google itself\nsays server-side or pre-rendering is still a great idea — not all bots run JS. So:\n\n- **SSR or SSG every indexable route.** Keep page content in Server Components;\n  push interactivity to small `\"use client\"` leaves. A client-only SPA shell that\n  paints empty HTML risks thin\u002Flate indexing and starves non-Google + AI bots.\n- **Verify the bytes a crawler receives:** `curl -A \"Googlebot\" -H \"Accept: text\u002Fhtml,...\" URL`\n  and confirm `\u003Ctitle>`, `\u003Ch1>`, body copy, and JSON-LD are in the RAW HTML.\n- **Never serve different content to Googlebot than to users** (cloaking — a\n  Google violation). Same content, same status codes.\n- **Edge middleware \u002F content-negotiation is a crawl hazard.** If a middleware\n  transforms responses by `Accept` header (e.g. RDF conneg), prove the `text\u002Fhtml`\n  branch returns the page unchanged, runs no extra origin fetch on the crawl path,\n  and is scoped with a `matcher` so it never touches `\u002F_next\u002F*`, sitemap, robots,\n  or icons. A negotiator that can pick a non-HTML representation for any `Accept`\n  a bot might send is a latent de-indexing bug.\n- Real HTTP status codes (200\u002F301\u002F308\u002F404\u002F410), one canonical host (pick apex OR\n  www and 301\u002F308 the other), HTTPS only, no redirect chains.\n\n## 2. Next.js App Router metadata (the legible layer)\n\nUse the Metadata API (Server Components only):\n- **`metadataBase`** in the root layout = production origin (so relative OG image\n  URLs resolve to absolute — social scrapers need absolute).\n- **`title`** as `{ default, template: \"%s — Name\" }`; per-page `title` strings.\n- **`description`** — unique, ~150 chars, includes the primary query naturally.\n- **`alternates: { canonical }`** — absolute, self-canonical per page.\n- **`robots: { index, follow, googleBot }`**.\n- **`openGraph`**: title, description, url, siteName, type ('website'|'profile'),\n  images [{ url, width:1200, height:630, alt }], locale.\n- **`twitter`**: card 'summary_large_image', title, description, images, creator.\n- **OG image 1200×630** — a static `app\u002Fopengraph-image.(png|jpg)` \u002F `app\u002Ftwitter-image.png`,\n  or a dynamic `opengraph-image.tsx` using `ImageResponse` from `next\u002Fog`.\n- **Favicons\u002Fmanifest** via file conventions: `app\u002Ffavicon.ico`, `app\u002Ficon.png`,\n  `app\u002Fapple-icon.png`, `app\u002Fmanifest.ts`.\n- **`app\u002Fsitemap.ts`** → `MetadataRoute.Sitemap`. **`app\u002Frobots.ts`** →\n  `MetadataRoute.Robots` (rules + sitemap + host).\n- Next ≥15 streams metadata on dynamic pages but disables streaming for known\n  bots; prefer static\u002Fprerendered pages so metadata is in the HTML at build time.\n\n## 3. Structured data — the key ENTITY lever (JSON-LD)\n\nGoogle prefers **JSON-LD in `\u003Cscript type=\"application\u002Fld+json\">`**. This makes a\nperson a resolvable **entity** (Knowledge Graph, AI-answer citations), not a\nstring. Emit three connected nodes:\n- **`Person`** with a stable `@id` (the page's own identity URI, e.g. `https:\u002F\u002Fsite\u002F#me`),\n  name, alternateName, url, image, jobTitle, worksFor\u002Faffiliation, alumniOf,\n  description, `knowsAbout` (topics to be associated with), and **`sameAs`** — an\n  array of EVERY authoritative profile (GitHub, LinkedIn, ORCID, Google Scholar,\n  employer\u002Funiversity page, X, Mastodon, and crucially Wikidata\u002FWikipedia if they\n  exist). `sameAs` is the strongest entity-resolution signal; Wikidata is a direct\n  Knowledge-Graph input.\n- **`WebSite`** (url, name, publisher\u002Fauthor → the Person `@id`).\n- **`ProfilePage`** (Google-supported) with `mainEntity` → the Person; recommended\n  `dateCreated`\u002F`dateModified`.\nRules: the JSON-LD must match visible page content (Google policy — no markup-only\nfacts). Validate with the Rich Results Test + Schema Markup Validator. Keep `@id`s\nconsistent across pages so the graph links into one entity.\n\n### Coexisting JSON-LD (SEO) with RDFa (a WebID\u002FLinked-Data profile)\nA site can be both a human page and a machine-readable profile:\n- **RDFa** = attributes on the visible DOM (`typeof`\u002F`property`\u002F`resource`),\n  consumed by RDF parsers \u002F content-negotiation to Turtle. Keep it for a WebID.\n- **JSON-LD** = a `\u003Cscript>` block, consumed by search engines. Add it for SEO.\n- **Align the subject URI:** point the JSON-LD `Person` `@id` at the SAME identity\n  URI the RDFa\u002FWebID uses (`…\u002F#me`). Use schema.org terms in both so the Turtle\n  conneg output and the JSON-LD agree. Keep the two `sameAs` lists identical. Do\n  NOT rely on RDFa alone for SEO (JSON-LD is Google's recommended, rich-results\n  path), and do NOT drop RDFa for JSON-LD (it would break the WebID conneg).\n\n## 4. Content & E-E-A-T\n\n- **Name in `\u003Ctitle>` and the single `\u003Ch1>`.** One `\u003Ch1>` per page.\n- **Real, dated, authored content** in server-rendered HTML (a name-only SPA stub\n  is thin). Bio + what you do + your topics, in prose.\n- **Natural keyword use** — topics woven into sentences, not stuffed.\n- **Outbound links to your own authoritative profiles** corroborate the entity.\n- For a researcher\u002Fprofessional: surface credentials, affiliations, publications,\n  talks — and mirror them in `Person` (jobTitle, affiliation, alumniOf, knowsAbout).\n- Descriptive URLs; meaningful internal links.\n\n## 5. Core Web Vitals (the performance gate; p75 of real users)\n\nThresholds: **LCP \u003C 2.5 s · INP \u003C 200 ms · CLS \u003C 0.1**, at the 75th percentile of\nfield data (CrUX); lab scores are diagnostic only. Levers: SSR\u002FSSG, ship less JS\n(Server Components + dynamic-import client islands), `next\u002Fimage` with explicit\nwidth\u002Fheight + priority on the LCP image, `next\u002Ffont` (no layout-shift swap),\npreconnect to needed origins.\n\n## 6. Off-page (human actions — list as needs:user, never promise rank)\n\n- **Backlinks from authoritative profiles → the site** (employer staff page,\n  university dept page, ORCID, Scholar, GitHub, LinkedIn, conference speaker pages)\n  — the strongest realistic lever for a personal name.\n- **Knowledge Graph \u002F Wikidata** — create\u002Fclaim a Wikidata item (notability\n  permitting) + add the site + sameAs. Direct Knowledge-Graph input.\n- **Google Search Console** — verify (DNS TXT or HTML meta), submit the sitemap,\n  monitor coverage + CWV + queries. **Bing Webmaster Tools** likewise.\n- **Consistency** — identical name, bio, headshot across all profiles.\n\n## 7. Verify before claiming done\n\n- `curl -A Googlebot` the page; title\u002Fh1\u002Fbody\u002FJSON-LD in raw HTML.\n- Rich Results Test + Schema Markup Validator (zero errors).\n- `\u002Fsitemap.xml` + `\u002Frobots.txt` resolve and reference each other.\n- One canonical host; no redirect chains; HTTPS; 404 returns 404.\n- PageSpeed Insights \u002F CrUX for field CWV.\n- Search Console: property verified, sitemap submitted, no coverage errors.\n\n## Anti-patterns\n\n- Promising a rank (esp. for a common name).\n- Keyword stuffing; markup describing facts not visible on the page (policy\n  violation → possible structured-data manual action).\n- Cloaking \u002F serving bots different content.\n- A client-only SPA with an empty HTML shell as the indexable page.\n- A middleware\u002Fconneg layer that can return non-HTML to a crawler, double-fetches\n  on the crawl path, or lacks a `matcher`.\n- Inventing identifiers (ORCID, Wikidata IDs) — only assert profiles the person\n  owns; a wrong `sameAs` poisons entity resolution.\n",{"name":5,"description":7},"main","5482abfe2666cc12f835fe360e8fad1f1e1dea8c","skills\u002Fweb-seo",0,"https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk","https:\u002F\u002Fgithub.com\u002Fjeswr","jeswr.org\u002F#me","@solid Lead @theodi | PhD Candidate @OxfordHCC\r\n\r\n","2026-11-15 05:20:24",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add jeswr\u002Fsolid-sdk --skill web-seo",{"tool":39,"command":40},"bunx","bunx skills add jeswr\u002Fsolid-sdk --skill web-seo",{"tool":42,"command":43},"pnpm","pnpm dlx skills add jeswr\u002Fsolid-sdk --skill web-seo","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fweb-seo\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M78FNRF6EV6SKPEYRZ6JTTQ3","storage-conformance","Work on @jeswr\u002Fstorage-conformance, the shared storage conformance suite package in the Solid SDK workspace.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftools\u002Fstorage-conformance\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M78FNMS7HQGD9EE43WAFEW6A","fetch-rdf-engine-tests","Maintain fetch-rdf's real Node WASM parser integration tests without introducing a reverse engine dependency in fetch-rdf.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftools\u002Ffetch-rdf-engine-tests\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M78FNK5M6ASAR3909JT6BZV1","alpha","Use when checking fixtures, including folded YAML descriptions.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcheck-skills\u002Fvalid\u002Fskills\u002Falpha\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78FNGATR8F4N09HWSFVWBAF","widget","Use when testing package skills: YAML quoting works.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Ftest\u002Ffixtures\u002Fcheck-skills\u002Fvalid\u002Fpackages\u002Fwidget\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M78FN5ANETMSPMEFACSJ7JMC","solid-wac","Use when implementing or auditing Solid server WAC authorization, ACL creation and inheritance, auxiliary-resource escalation, method-to-mode mapping, 401 versus 403 challenges, WAC-Allow, or defensive typed ACL parsing with @solid\u002Fobject and @rdfjs\u002Fwrapper.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-wac\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M78FN2286ASSW8GM4W3KW6TJ","solid-type-index","Use when discovering or registering Solid data by RDF class, reading publicTypeIndex or privateTypeIndex links, creating missing Type Index documents, or implementing TypeRegistration wrappers and bounded pod search.","https:\u002F\u002Fgithub.com\u002Fjeswr\u002Fsolid-sdk\u002Fblob\u002Fmain\u002Fskills\u002Fsolid-type-index\u002FSKILL.md",[],[]]