ВяткинАртём
2817cf8dc6
- 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.
19 lines
923 B
Markdown
19 lines
923 B
Markdown
# 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. |