Add test coverage checklist, report template, and stack matrix for ecommerce project

- Created a test coverage checklist to ensure comprehensive testing of backend and frontend components. - Added a test report template to standardize reporting on test execution results and gaps. - Introduced a test stack matrix to guide the selection of testing tools and frameworks for backend and frontend. - Established a skill for repairing failing tests, including a failure triage checklist and a test repair template. - Documented recommended MCP stack for ecommerce development with FastAPI and React/Next.js. - Developed a detailed README outlining the project structure, agent capabilities, and recommended workflows. - Compiled a comprehensive workflow guide detailing step-by-step commands for project setup, testing, and SEO implementation.
2026-05-20 18:09:24 +03:00
parent 5699670ea0
commit 2817cf8dc6
96 changed files with 2987 additions and 2888 deletions
@@ -0,0 +1,53 @@
+---
+name: ecommerce-seo-strategy
+description: 'Plan and improve ecommerce SEO across technical SEO, information architecture, category strategy, product pages, schema markup, metadata, internal linking, Core Web Vitals, and measurement. Use for SEO audits, SEO planning, and organic growth work on online stores.'
+argument-hint: 'Describe the store, market, target pages, and whether this is a new build or an existing site'
+---
+# Ecommerce SEO Strategy
+
+## When to use
+- Planning SEO for a new ecommerce site before build.
+- Auditing an existing storefront that needs stronger organic visibility.
+- Defining technical SEO, content architecture, schema, metadata, and internal linking.
+- Improving category, product, brand, collection, blog, and help content for search intent.
+
+## Goal
+- Maximize sustainable organic visibility for the site.
+- Produce implementation-ready SEO decisions instead of vague advice.
+- Create or update .ai/SEO-PLAN.md when the task is substantial.
+
+## Important constraint
+- Do not promise a number one ranking. Search performance depends on competition, domain authority, backlinks, history, and market conditions.
+- Optimize for the strongest possible technical and content foundation, measurable growth, and durable search coverage.
+
+## Required workflow
+1. Read .ai/STORE-BRIEF.md if it exists. If not, gather enough business and market context from the user or repository.
+2. Determine the market, audience, geography, revenue model, and search intent mix.
+3. Build a keyword and intent map using [keyword intent framework](./assets/keyword-intent-framework.md).
+4. Define search landing pages and information architecture for home, categories, subcategories, collections, brands, products, guides, FAQs, and support content.
+5. Review or propose technical SEO using [technical SEO checklist](./assets/technical-seo-checklist.md).
+6. Review or propose structured data using [schema markup map](./assets/schema-markup-map.md).
+7. Review or propose internal linking using [internal linking playbook](./assets/internal-linking-playbook.md).
+8. Define measurement using [SEO measurement framework](./assets/seo-measurement-framework.md).
+9. Create or update .ai/SEO-PLAN.md using [SEO plan template](./assets/seo-plan-template.md) when the work is broad enough.
+10. Prioritize recommendations into quick wins, medium lifts, and structural work.
+
+## Coverage expectations
+- Technical SEO: crawlability, indexability, canonicals, noindex strategy, redirects, sitemaps, robots, rendering, structured data, image SEO, faceted navigation, pagination behavior, hreflang when needed, page speed and Core Web Vitals.
+- Commercial SEO: category taxonomy, filter landing page policy, product detail optimization, collection and brand pages, price and availability signals, review strategy, seasonal and campaign landing pages.
+- Content SEO: metadata, headings, copy structure, FAQs, guides, comparison pages, supporting content clusters, entity coverage, and user intent alignment.
+- UX signals that affect SEO: mobile-first layouts, performance, layout stability, media optimization, readable content hierarchy, and clean navigation.
+- Measurement: rankings are not enough; include index coverage, impressions, CTR, non-brand traffic, landing page performance, conversions, and page group health.
+
+## Outputs
+- .ai/SEO-PLAN.md for broad SEO work.
+- Specific code or content implementation tasks when the user wants execution.
+- Clear prioritization by business impact and engineering cost.
+
+## References
+- [SEO plan template](./assets/seo-plan-template.md)
+- [keyword intent framework](./assets/keyword-intent-framework.md)
+- [technical SEO checklist](./assets/technical-seo-checklist.md)
+- [schema markup map](./assets/schema-markup-map.md)
+- [internal linking playbook](./assets/internal-linking-playbook.md)
+- [SEO measurement framework](./assets/seo-measurement-framework.md)
@@ -0,0 +1,18 @@
+# Internal Linking Playbook
+
+## Core principles
+- Link from high-authority pages to priority commercial pages.
+- Use consistent anchor language tied to real user phrasing.
+- Keep internal links helpful for users, not mechanically stuffed.
+
+## Required link systems
+- Global navigation to top categories and collections.
+- Breadcrumbs on category, collection, brand, and product pages.
+- Related products and related categories modules.
+- Editorial links from guides, FAQs, and comparison content to money pages.
+- Cross-links between complementary categories when intent overlaps.
+
+## Priority rules
+- Important categories should be reachable in few clicks.
+- New seasonal or campaign pages need fast internal linking support.
+- Orphan pages are not acceptable for strategic landing pages.
@@ -0,0 +1,27 @@
+# Keyword Intent Framework
+
+## Intent buckets
+- Transactional: buy-now, price, delivery, in-stock, order intent.
+- Commercial investigation: best, compare, review, top, versus, alternatives.
+- Informational: how to choose, how to use, care guides, ingredient guides, compatibility guides.
+- Navigational and brand: brand, collection, store name, product line, branded queries.
+
+## Mapping rules
+- Homepage should target broad category and brand-level demand, not all keywords.
+- Category and subcategory pages should target the highest-volume commercial and transactional themes.
+- Product pages should target explicit product, variant, model, SKU, brand, and long-tail modifiers.
+- Guide and FAQ pages should support commercial pages and capture informational demand.
+
+## Output fields
+- Keyword theme
+- Primary intent
+- Suggested landing page type
+- Funnel stage
+- Priority
+- Required content blocks
+- Internal link targets
+
+## Ecommerce caution points
+- Do not create indexable pages for every low-value filter combination.
+- Avoid cannibalization between category pages, collection pages, and blog content.
+- Prefer strong category and brand hubs over thin near-duplicate pages.
@@ -0,0 +1,19 @@
+# Schema Markup Map
+
+## By page type
+- Homepage: Organization, WebSite, SearchAction when appropriate.
+- Category or collection pages: ItemList and BreadcrumbList when the page meaningfully lists products.
+- Product pages: Product, Offer, AggregateRating, Review when the data is real and visible.
+- FAQ sections: FAQPage only when the content is actually presented to users.
+- Editorial pages: Article or BlogPosting where appropriate.
+- Store or contact pages: LocalBusiness when location data exists and is accurate.
+
+## Requirements
+- Only mark up data that is visible and truthful.
+- Keep price, availability, brand, SKU, and rating data synchronized with visible content.
+- Validate JSON-LD output after implementation.
+
+## Ecommerce cautions
+- Do not fabricate ratings or reviews.
+- Do not mark every accordion as FAQPage unless it truly qualifies.
+- Keep structured data aligned with canonical URLs and page intent.
@@ -0,0 +1,25 @@
+# SEO Measurement Framework
+
+## Primary KPIs
+- Non-brand clicks and impressions.
+- Organic sessions by landing page group.
+- Organic conversion rate.
+- Revenue or lead value from organic traffic.
+- Indexed page quality by page type.
+
+## Secondary KPIs
+- CTR on major page templates.
+- Average position for priority keyword groups.
+- Core Web Vitals on category and product pages.
+- Share of traffic landing on strategic commercial pages versus weak informational pages.
+
+## Monitoring dimensions
+- By page type: homepage, category, collection, brand, product, content, help.
+- By market or locale.
+- By device.
+- By branded versus non-branded traffic.
+
+## Reporting approach
+- Separate quick wins from structural improvements.
+- Measure before and after major releases.
+- Track technical fixes, content launches, and internal linking changes as distinct interventions.
@@ -0,0 +1,84 @@
+# SEO-PLAN.md Template
+
+## 1. Business Context
+- Site or brand name
+- Market and geography
+- Audience segments
+- Revenue model and priority categories
+
+## 2. SEO Objectives
+- Primary growth goals
+- Non-brand traffic goals
+- Conversion goals from organic traffic
+- Constraints and dependencies
+
+## 3. Search Intent Model
+- Transactional intents
+- Commercial investigation intents
+- Informational intents
+- Brand and navigational intents
+
+## 4. Keyword and Page Mapping
+- Homepage target themes
+- Category pages
+- Subcategory or collection pages
+- Brand pages
+- Product pages
+- Editorial or guide pages
+- FAQ and support pages
+
+## 5. Information Architecture
+- Planned taxonomy
+- URL rules
+- Faceted navigation policy
+- Canonicalization rules
+- Pagination or infinite scroll handling
+
+## 6. On-Page SEO Requirements
+- Title patterns
+- Meta description patterns
+- Heading rules
+- Intro copy rules for category pages
+- Product page content blocks
+- FAQ and support content rules
+
+## 7. Structured Data Plan
+- Required schema types by page type
+- Required properties
+- Validation notes
+
+## 8. Technical SEO Plan
+- Indexing and crawl rules
+- Robots and sitemaps
+- Redirect policy
+- Performance and Core Web Vitals goals
+- Image optimization rules
+- Renderability and JavaScript considerations
+
+## 9. Internal Linking Strategy
+- Global navigation
+- Breadcrumbs
+- Related products
+- Category cross-links
+- Editorial to commercial links
+
+## 10. Content Expansion Plan
+- High-priority landing pages
+- Cluster content ideas
+- Seasonal and campaign opportunities
+
+## 11. Measurement and Reporting
+- KPIs
+- Dashboard inputs
+- Search Console tracking
+- Analytics events or goals
+
+## 12. Priority Roadmap
+- Quick wins
+- Medium lifts
+- Structural work
+
+## 13. Risks and Assumptions
+- Market competition risks
+- Platform constraints
+- Content or asset gaps
@@ -0,0 +1,32 @@
+# Technical SEO Checklist
+
+## Crawl and indexation
+- Confirm indexable money pages and noindex low-value or duplicate pages.
+- Define robots policy for search, cart, account, internal filters, and thin utility pages.
+- Ensure XML sitemaps exist for key page groups and exclude noindex URLs.
+
+## Canonicalization and duplication
+- Define canonicals for categories, filtered states, sorting states, pagination, and product variants.
+- Prevent duplicate content across collection pages, brand pages, and promotional landings.
+
+## Rendering and architecture
+- Ensure key content is available in server-rendered or reliably rendered HTML.
+- Confirm crawlers can see titles, headings, main content, structured data, and internal links.
+
+## Performance and Core Web Vitals
+- Optimize LCP, INP, and CLS on category and product pages.
+- Control image size, font loading, script weight, and third-party bloat.
+- Avoid layout shifts from banners, lazy media, and client-only widgets.
+
+## Media and assets
+- Use descriptive image filenames where practical.
+- Provide alt text with functional accuracy, not keyword stuffing.
+- Generate responsive image variants and preload only what is truly critical.
+
+## Navigation and page discovery
+- Ensure deep categories and products are reachable through internal links.
+- Use breadcrumbs and clear taxonomy-based navigation.
+
+## International and local SEO when relevant
+- Use hreflang carefully only when multiple locales truly exist.
+- Align locale routing, canonicals, translated metadata, and sitemap structure.