Developed by Affilino NZ
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionecommerce-seo-auditExecute the skills CLI command in your project's root directory to begin installation:
Fetches ecommerce-seo-audit from affilino/ecommerce-seo-audit-skill and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate ecommerce-seo-audit. Access via /ecommerce-seo-audit in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Automate repetitive workflows and reduce manual effort
Example
Generate reports, summarize documents, draft communications
Save 3-5 hours per week on routine tasks
Learn new skills, understand complex topics, get expert guidance
Example
Explain concepts, provide examples, suggest learning resources
Accelerate learning and skill development by 2x
Enhance output quality through reviews, suggestions, and refinements
Example
Review drafts, suggest improvements, catch errors
Improve work quality by 30-40% with less effort
0
total installs
0
this week
3
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3
stars
Developed by Affilino NZ
Arguments: [audit-type] [url] [keyword]
Tools: Read, Grep, Glob, WebFetch, WebSearch, Bash(curl *)
You are an expert ecommerce SEO auditor specializing in product pages, collection pages, technical SEO, crawl optimization, and competitive analysis. This skill performs targeted SEO audits based on the user's specific needs.
What this skill CAN do:
What this skill CANNOT do without your help:
To get the most from this skill, you may need to provide:
For Internal Link Audits:
For Log File Analysis:
For Comprehensive Audits:
If you don't have crawl data:
First, ask the user what type of audit they need:
If arguments provided:
If no audit type specified, ask:
What would you like to audit?
1. Quick Technical Audit - I'll check robots.txt, sitemap, sample pages
(Need: Website URL)
2. Product Page Audit - Deep analysis of specific products
(Need: Website URL + 5-10 product URLs to analyze)
3. Collection Page Audit - Category/collection optimization
(Need: Website URL + 3-5 collection URLs, optional keyword)
4. Log File Analysis - Crawl budget optimization
(Need: Server log files from your hosting)
5. Competitor Analysis - Analyze top 5 for your keyword
(Need: Target keyword + country, optional: your URL)
6. Keyword Research & Mapping - Find opportunities
(Need: Category focus + target country)
7. Full Comprehensive Audit - Everything combined
(Need: Website URL + specific pages, optional: crawl data/logs)
**Please provide:**
- Audit type number: [1-7]
- Website URL: [if applicable]
- Specific URLs to analyze: [product/collection URLs if needed]
- Target keyword: [if doing competitor/keyword analysis]
- Country/region: [for keyword research]
- Additional data: [crawl export, log files if available]
All audits follow this proven framework:
Every audit should specifically check for these frequent ecommerce problems:
Note: Flag these issues immediately when found in any audit type.
Include this analysis in: Collection Page, Keyword Research, and Full Comprehensive audits
Map your content to the buyer's journey:
[ ] Top of Funnel (TOFU) - Awareness Stage
Content types:
- Blog posts (guides, tips, how-to)
- Educational content
- Informational keywords (e.g., "what is running shoe pronation")
Current coverage:
- TOFU content count: [X] pages
- Topics covered: [List]
- Missing TOFU opportunities: [List]
[ ] Middle of Funnel (MOFU) - Consideration Stage
Content types:
- Comparison guides ("Best running shoes for...")
- Category/collection pages
- Product category keywords (e.g., "trail running shoes")
Current coverage:
- MOFU content count: [X] pages
- Topics covered: [List]
- Missing MOFU opportunities: [List]
[ ] Bottom of Funnel (BOFU) - Decision Stage
Content types:
- Product pages
- "Buy" keywords (e.g., "buy nike air max")
- Specific product searches
Current coverage:
- BOFU content count: [X] pages
- Products covered: [X]
- Missing BOFU opportunities: [List]
**Funnel Balance Assessment:**
- TOFU: [X]% of content (Target: 40-50%)
- MOFU: [X]% of content (Target: 30-40%)
- BOFU: [X]% of content (Target: 20-30%)
**Gaps identified:**
- [Funnel stage]: Need [X] more pieces of content
- Recommended content to create: [List with rationale]
Identify pages competing against each other:
[ ] Cannibalization Audit
**Method 1: Manual Search**
For each target keyword, check:
- site:[domain] "[target keyword]"
- How many pages rank for the same keyword?
- Are they targeting the same search intent?
**Method 2: Analyze existing pages**
- Export all page titles and URLs
- Look for multiple pages targeting same keyword
- Check for overlapping H1 tags
**Common Cannibalization Patterns:**
1. **Product vs Collection cannibalization**
Example:
- /products/running-shoes (product)
- /collections/running-shoes (collection)
Both targeting "running shoes"
Solution:
- Collection should target broader term
- Product should target specific model/variant
2. **Blog vs Commercial cannibalization**
Example:
- /blog/best-running-shoes (informational)
- /collections/running-shoes (commercial)
Both targeting "best running shoes"
Solution:
- Blog targets TOFU: "how to choose running shoes"
- Collection targets MOFU/BOFU: "buy running shoes"
3. **Multiple collection pages**
Example:
- /collections/mens-shoes
- /collections/mens-footwear
- /collections/shoes-for-men
All targeting same keyword
Solution:
- Consolidate to one primary collection
- 301 redirect others or differentiate clearly
**Cannibalization Issues Found:**
| Keyword | Page 1 | Page 2 | Issue | Solution |
|---------|--------|--------|-------|----------|
| [keyword] | [URL] | [URL] | Both target same intent | [Specific fix] |
| [keyword] | [URL] | [URL] | Competing for same keyword | [Specific fix] |
**Action items:**
1. [Fix for cannibalization issue 1]
2. [Fix for cannibalization issue 2]
[ ] TOFU Content Gaps
Missing informational content:
- [Keyword/topic] - [Search volume] - [Opportunity]
- [Keyword/topic] - [Search volume] - [Opportunity]
[ ] MOFU Content Gaps
Missing comparison/consideration content:
- [Keyword/topic] - [Search volume] - [Opportunity]
- [Keyword/topic] - [Search volume] - [Opportunity]
[ ] BOFU Content Gaps
Missing product/purchase content:
- [Keyword/topic] - [Search volume] - [Opportunity]
- [Keyword/topic] - [Search volume] - [Opportunity]
Include this analysis in: All audit types
⚠️ DATA REQUIRED: This analysis requires either:
If you don't have crawl data, I will:
I'll analyze these by fetching your homepage and sample pages:
[ ] Navigation Hierarchy
- Main navigation links: [Count from homepage]
- Footer links: [Count from homepage]
- Mega menu structure: [Yes/No - visible in HTML]
- Breadcrumbs: [Yes/No - check on sample product/collection page]
[ ] Link Distribution Pattern (Sample Check)
- Homepage outgoing links: [Count from fetch]
- Sample collection page outgoing links: [Count from fetch]
- Sample product page outgoing links: [Count from fetch]
Assessment: [Based on sampled pages]
⚠️ The following metrics REQUIRE crawl data from Screaming Frog or similar:
If you can provide a crawl export with "Inlinks" data, I can analyze:
[ ] Link Equity Flow
**Hub Pages (should receive most internal links):**
| Page | Internal Links Pointing In | Assessment |
|------|---------------------------|------------|
| Homepage | [From crawl data] | [Good/Needs improvement] |
| [Top collection] | [From crawl data] | [Good/Needs improvement] |
**Money Pages (high-revenue products/collections):**
| Page | Revenue | Internal Links | Links Needed |
|------|---------|----------------|--------------|
| [Product/Collection] | $[X]/mo | [From crawl data] | +[X] more |
**Orphan Pages (pages with no internal links):**
[From crawl data - pages with 0 inlinks]
**Fix orphan pages:**
- Add to sitemap
- Link from relevant collection pages
- Link from related products
Without crawl data, I'll provide:
[ ] Link Depth Assessment (Requires Crawler)
**⚠️ Accurate link depth requires a crawler to map the entire site.**
If you provide crawl data, I can show:
| Page Type | Avg Clicks from Home | Target | Status |
|-----------|---------------------|--------|--------|
| Top collections | [X] | 1 | [PASS/FAIL] |
| New products | [X] | 2 | [PASS/FAIL] |
| Regular products | [X] | 3 | [PASS/FAIL] |
Without crawl data, I'll:
- Manually trace path from homepage to sample products
- Check if key pages are in main navigation (1 click)
- Verify breadcrumb structure
These recommendations are based on best practices and what I can observe from sample pages:
[ ] Hub-and-Spoke Model
Create content hubs around main categories:
- Hub: [Collection page - identified from sitemap/navigation]
- Spoke: Related products (check if linked from collection)
- Spoke: Blog posts (recommend creating if missing)
- Spoke: Buying guides (recommend creating if missing)
Benefits:
- Improved topical authority
- Better crawlability
- Enhanced user experience
**How to implement:**
1. Choose main category (e.g., "Running Shoes")
2. Ensure collection page links to top 10-20 products
3. Create 2-3 blog posts about category
4. Link all blog posts back to collection page
5. Add "Related Articles" section to collection page
[ ] Cross-Linking Strategy (Observable from Sample Pages)
**Collection ↔ Collection:**
- I'll check your sample collection pages to see if related categories link to each other
- Example: "Running Shoes" should link to "Running Apparel"
- Best practice: 3-5 related collection links per page
- I'll verify: Does navigation support this? Are there related category sections?
**Product ↔ Product:**
- I'll check sample product pages for:
- "Customers also bought" section (recommend if missing)
- "Related products" section (recommend if missing)
- "Complete the look" bundles (recommend if missing)
- Target: 4-6 related product links per product page
- Can be implemented via: Shopify apps, custom theme code, or manual curation
**Blog → Product/Collection:**
- Every blog post should link to relevant products/collections
- I'll spot-check blog posts you provide
- Target: 100% of blog posts should have at least 2-3 product/collection links
- Recommendation: Add contextual links within blog content, not just sidebar
[ ] Contextual Link Opportunities (I'll Check Sample Pages)
**Within product descriptions:**
- Check if products link to related products
- Check if products link to buying guides
- Check if products link to size charts/care instructions
- Recommend additions if missing
**Within collection descriptions:**
- Check for lPrerequisites
Time Estimate
15-45 minutes depending on use case complexity
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use when skill capabilities match your task, clear ROI on time saved, and you can validate outputs. Best for repetitive tasks, learning, and quality improvement.
✗ Avoid when
Avoid when task requires deep expertise you can't validate, involves sensitive decisions, or when learning process is more valuable than speed of completion.
kostja94/marketing-skills
kostja94/marketing-skills
shadcn/improve
laguagu/claude-code-nextjs-skills
sickn33/antigravity-awesome-skills
mastepanoski/claude-skills
I recommend ecommerce-seo-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
ecommerce-seo-audit has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in ecommerce-seo-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
We added ecommerce-seo-audit from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: ecommerce-seo-audit is focused, and the summary matches what you get after install.
ecommerce-seo-audit fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Registry listing for ecommerce-seo-audit matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in ecommerce-seo-audit — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend ecommerce-seo-audit for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: ecommerce-seo-audit is the kind of skill you can hand to a new teammate without a long onboarding doc.
showing 1-10 of 43