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.
This commit is contained in:
ВяткинАртём
+18
@@ -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.
|
||||
+27
@@ -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.
|
||||
+19
@@ -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.
|
||||
+25
@@ -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.
|
||||
+84
@@ -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
|
||||
+32
@@ -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.
|
||||
Reference in New Issue
Block a user