[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7FBFMYCJDVHMB37FAF5XCKX":3,"skill-same:01M7FBFMYCJDVHMB37FAF5XCKX":53},{"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":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7FBFMYCJDVHMB37FAF5XCKX","seo-strategy",null,"Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.","siddu1004\u002FSFP","siddu1004","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260113491?v=4","01M7F8W1SAJAR49097VRTE1TW5","Siddhardh Vanguri","01M7F8W1SYGY7JE15AHAECCT9R",5,"MIT","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fseo-strategy\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: seo-strategy\ndescription: Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured data, or prioritize which SEO fixes are worth doing.\n---\n\n# SEO strategy\n\n## Diagnose in this order\n\nSkipping to content when the problem is technical wastes months. Work down; stop when you find the\nbreak.\n\n1. **Can it be crawled?** Robots directives, noindex left on after a launch, blocked resources,\n   crawl budget wasted on parameter and filter URLs.\n2. **Can it be indexed?** Check what is actually in the index versus what should be. Canonicals\n   pointing at the wrong page and unintended duplicates are the two usual causes.\n3. **Does the page deserve to rank?** Search intent match first. A page can be technically perfect\n   and still lose because it answers a different question than the query asks.\n4. **Does the site have the authority to rank for it?** Some terms are out of reach for now.\n   Targeting them is a decision to spend without return.\n\n## Architecture\n\nStructure follows how people look for things, not how the company is organized.\n\n- Anything important reachable within three clicks of the home page.\n- Group related pages so internal linking is natural, not retrofitted.\n- One URL per thing. Parameters, trailing-slash variants, and case differences that all resolve are\n  duplicate content in the crawler's eyes.\n- URLs readable and stable. Changing them costs equity even done correctly.\n\nInternal linking is the most underused lever available: it is fully within your control, and it\ndirects authority to the pages you actually care about. Link with descriptive anchor text from your\nstrongest pages to the ones that need help.\n\n## Performance and mobile\n\nSpeed and mobile usability are ranking inputs and, more importantly, conversion inputs. Audit them\nas part of every SEO review rather than treating them as an engineering concern.\n\nMeasure on **field data** from real users where available, not only lab tools. Lab scores on a fast\nconnection routinely miss what mobile users experience.\n\nThe three that matter:\n\n- **Loading** — how long until the largest visible element renders. Usually fixed by image sizing\n  and format, render-blocking resources, and slow server response.\n- **Interaction responsiveness** — how long the page takes to react to a tap or click. Usually\n  fixed by reducing main-thread JavaScript work.\n- **Layout stability** — how much content shifts while loading. Almost always fixed by reserving\n  space for images, ads, and embeds before they load.\n\nMobile is the version that gets indexed. Check that mobile serves the same content as desktop —\ncontent hidden or dropped on mobile is content that does not exist for ranking — and that tap\ntargets, font sizes, and viewport configuration do not make the page unusable.\n\nPrioritize performance work by pages with traffic, not by worst score. A terrible score on a page\nnobody visits is not a finding.\n\n## Structured data\n\nMark up what genuinely exists on the page — the entity, its attributes, the relationships. It\nclarifies meaning to the crawler and can earn richer results.\n\nUse JSON-LD in the page head rather than inline microdata — it is easier to maintain and validate,\nand it does not entangle markup with content.\n\nThe types worth implementing, in rough order of return: organization and site identity, breadcrumbs,\narticles, products with offers and availability, frequently asked questions, events, local business\ndetails, and job postings. Implement the properties each type actually requires plus the recommended\nones you can populate honestly; partial markup with missing required fields is usually ignored\nentirely.\n\nValidate after every template change. Structured data breaks silently when a template is edited, and\nnothing tells you.\n\nNever mark up content that is not visible on the page, and never mark up ratings, prices, or events\nthat are not real. Both are policy violations with penalties attached.\n\n## Prioritizing\n\nRank fixes by traffic at risk against effort. In practice the order is almost always: indexation\nproblems, then intent mismatch on high-value pages, then internal linking, then structured data,\nthen everything else.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Chase rankings for a term the page cannot satisfy. The click arrives, bounces, and teaches the engine the page was wrong.\n- Restructure a site without a redirect map. Lost link equity does not come back on its own.\n- Judge a change in the first fortnight. Search feedback is slow enough that early movement is usually noise.\n\n## Return contract\n\nFindings by severity with the evidence for each, the sequenced fix list, expected impact and when it\nshould be visible, and what you are choosing not to fix.\n","# SEO strategy\n\n## Diagnose in this order\n\nSkipping to content when the problem is technical wastes months. Work down; stop when you find the\nbreak.\n\n1. **Can it be crawled?** Robots directives, noindex left on after a launch, blocked resources,\n   crawl budget wasted on parameter and filter URLs.\n2. **Can it be indexed?** Check what is actually in the index versus what should be. Canonicals\n   pointing at the wrong page and unintended duplicates are the two usual causes.\n3. **Does the page deserve to rank?** Search intent match first. A page can be technically perfect\n   and still lose because it answers a different question than the query asks.\n4. **Does the site have the authority to rank for it?** Some terms are out of reach for now.\n   Targeting them is a decision to spend without return.\n\n## Architecture\n\nStructure follows how people look for things, not how the company is organized.\n\n- Anything important reachable within three clicks of the home page.\n- Group related pages so internal linking is natural, not retrofitted.\n- One URL per thing. Parameters, trailing-slash variants, and case differences that all resolve are\n  duplicate content in the crawler's eyes.\n- URLs readable and stable. Changing them costs equity even done correctly.\n\nInternal linking is the most underused lever available: it is fully within your control, and it\ndirects authority to the pages you actually care about. Link with descriptive anchor text from your\nstrongest pages to the ones that need help.\n\n## Performance and mobile\n\nSpeed and mobile usability are ranking inputs and, more importantly, conversion inputs. Audit them\nas part of every SEO review rather than treating them as an engineering concern.\n\nMeasure on **field data** from real users where available, not only lab tools. Lab scores on a fast\nconnection routinely miss what mobile users experience.\n\nThe three that matter:\n\n- **Loading** — how long until the largest visible element renders. Usually fixed by image sizing\n  and format, render-blocking resources, and slow server response.\n- **Interaction responsiveness** — how long the page takes to react to a tap or click. Usually\n  fixed by reducing main-thread JavaScript work.\n- **Layout stability** — how much content shifts while loading. Almost always fixed by reserving\n  space for images, ads, and embeds before they load.\n\nMobile is the version that gets indexed. Check that mobile serves the same content as desktop —\ncontent hidden or dropped on mobile is content that does not exist for ranking — and that tap\ntargets, font sizes, and viewport configuration do not make the page unusable.\n\nPrioritize performance work by pages with traffic, not by worst score. A terrible score on a page\nnobody visits is not a finding.\n\n## Structured data\n\nMark up what genuinely exists on the page — the entity, its attributes, the relationships. It\nclarifies meaning to the crawler and can earn richer results.\n\nUse JSON-LD in the page head rather than inline microdata — it is easier to maintain and validate,\nand it does not entangle markup with content.\n\nThe types worth implementing, in rough order of return: organization and site identity, breadcrumbs,\narticles, products with offers and availability, frequently asked questions, events, local business\ndetails, and job postings. Implement the properties each type actually requires plus the recommended\nones you can populate honestly; partial markup with missing required fields is usually ignored\nentirely.\n\nValidate after every template change. Structured data breaks silently when a template is edited, and\nnothing tells you.\n\nNever mark up content that is not visible on the page, and never mark up ratings, prices, or events\nthat are not real. Both are policy violations with penalties attached.\n\n## Prioritizing\n\nRank fixes by traffic at risk against effort. In practice the order is almost always: indexation\nproblems, then intent mismatch on high-value pages, then internal linking, then structured data,\nthen everything else.\n\n## Sources\n\n`references\u002Fsources.md` in this skill lists the outside authorities that settle the questions\nhere — what each one is authoritative for, and what you may do with it. Check them before\nanswering on anything they cover, and cite what you used. Most are free to read and not free\nto reproduce; the use note on each is binding.\n\n## Never\n\n- Chase rankings for a term the page cannot satisfy. The click arrives, bounces, and teaches the engine the page was wrong.\n- Restructure a site without a redirect map. Lost link equity does not come back on its own.\n- Judge a change in the first fortnight. Search feedback is slow enough that early movement is usually noise.\n\n## Return contract\n\nFindings by severity with the evidence for each, the sequenced fix list, expected impact and when it\nshould be visible, and what you are choosing not to fix.\n",{"name":5,"description":7},"main","15fa5201935d2b1d172b4e61c2360c908d876d20","plugins\u002Fbusiness-ops\u002Fskills\u002Fseo-strategy",0,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP","https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002Fsfp-hive","https:\u002F\u002Fgithub.com\u002Fsiddu1004","I am a student at Amrita Vishwa Vidyapeetham pursuing my BTECH degree in Electronics and Electrical Engineering (2024-2028).","2026-11-09 16:04:40",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add siddu1004\u002FSFP --skill seo-strategy",{"tool":39,"command":40},"bunx","bunx skills add siddu1004\u002FSFP --skill seo-strategy",{"tool":42,"command":43},"pnpm","pnpm dlx skills add siddu1004\u002FSFP --skill seo-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fseo-strategy\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fsources.md","REFERENCE","参考文档",2631,"https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fbusiness-ops\u002Fskills\u002Fseo-strategy\u002Freferences\u002Fsources.md",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M7FEEDADZBNBVY19H3XZKCBQ","scientific-schematics","Generates scientific diagram drafts using Nano Banana 2 AI with smart iterative refinement. Uses Gemini 3.7 Flash for quality review. Refines when the review requests improvement, with at most two generations. Specialized in neural network architectures, system diagrams, flowcharts, biological pathways, and complex scientific visualizations.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fscientific-schematics\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M7FEE0JS04FE58MST48D0MMC","polyhaven-texture-apply","Apply realistic PBR textures from PolyHaven to any Blender object. Supports metals, wood, concrete, fabric, and more. Trigger when asked to texture an object, apply a material from PolyHaven, make something look like metal\u002Fwood\u002Fmarble, or change object surface.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-texture-apply\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M7FEDJRWV194TY411WVRS84W","polyhaven-studio-setup","Set up a professional product photography studio in Blender using PolyHaven HDRIs and PBR ground materials. Trigger when asked to create a studio setup, add HDRI lighting, set up product photography, or create a showroom scene.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-studio-setup\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M7FED5H2FGS50XGETMGSM0RV","polyhaven-scene-builder","Build complete product scenes using PolyHaven assets — HDRI environment, textured ground\u002Fpedestal, and optional props from the 3D model library. Trigger when asked to build a product scene, create a showcase setup, add a pedestal, or compose a product shot.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-scene-builder\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M7FECSNZ2CJA7Z8TPE5R844R","polyhaven-material-swap","Cycle through multiple PolyHaven materials on a product and render each variant. Great for showing color\u002Ffinish options. Trigger when asked to show material variants, swap textures, create color options, show finish comparisons, or render product in different materials.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-material-swap\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M7FECBPQ6YWH48PYAMS0C5CE","polyhaven-hdri-showcase","Render the same product across multiple HDRI environments and output a comparison grid. Trigger when asked to compare lighting setups, test different environments, show product in multiple settings, or create an HDRI comparison.","https:\u002F\u002Fgithub.com\u002Fsiddu1004\u002FSFP\u002Fblob\u002Fmain\u002Fplugins\u002Fscience-hardware\u002Fskills\u002Fpolyhaven-hdri-showcase\u002FSKILL.md",[],[]]