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:
+40
@@ -0,0 +1,40 @@
|
||||
# SEO Review Checklist
|
||||
|
||||
## Metadata
|
||||
- Titles are unique on strategic page types.
|
||||
- Meta descriptions are present where useful and not duplicated at scale.
|
||||
- Open Graph and social metadata are present for key public pages.
|
||||
|
||||
## Crawl and indexation
|
||||
- Canonicals exist where duplication risk is real.
|
||||
- Noindex is applied to low-value routes such as cart, account, internal search, and thin utility pages when appropriate.
|
||||
- Filter, sort, and pagination behavior aligns with the SEO plan.
|
||||
- Sitemap generation excludes noindex and low-value URLs.
|
||||
- robots.txt does not accidentally block important content.
|
||||
|
||||
## Structured data
|
||||
- JSON-LD exists where intended.
|
||||
- Schema matches visible content.
|
||||
- Product, offer, breadcrumb, article, FAQ, and organization schema are used correctly.
|
||||
- There are no fake reviews, misleading offers, or invalid structured data assumptions.
|
||||
|
||||
## Page templates
|
||||
- Category and collection templates support unique SEO fields and meaningful content.
|
||||
- Product templates support strong metadata, support content, and structured data.
|
||||
- Brand and editorial pages have distinct intent and do not cannibalize key landing pages.
|
||||
|
||||
## Internal linking
|
||||
- Breadcrumbs exist where expected.
|
||||
- Important categories are linked from strong pages.
|
||||
- Product and editorial pages support relevant internal links.
|
||||
- Strategic landing pages are not orphaned.
|
||||
|
||||
## Performance-sensitive SEO
|
||||
- Key pages are not overloaded with client-only SEO logic.
|
||||
- There are obvious protections against large layout shifts and heavy above-the-fold payloads.
|
||||
- Media and fonts do not create avoidable search-quality regressions.
|
||||
|
||||
## Unknowns to flag
|
||||
- Runtime rendering behavior.
|
||||
- Search Console or analytics data not visible in code.
|
||||
- Production-only redirects, robots headers, CDN behavior, and sitemap deployment details.
|
||||
Reference in New Issue
Block a user