format: apply repo prettier (3.8.1) to the folded skills tree
963 markdown files reformatted with the repository's pinned prettier so pnpm format:check covers the folded tree like every other repo file. The formatter's embedded-language pass also normalized code fences (TS semicolons, closed HTML tags in examples, lowercased CSS hex colors, one renumbered list that skipped an index). Alphanumeric token deltas vs the fold commit were audited file-by-file; all are formatter-equivalent markup normalizations plus the four sanitized skills.
This commit is contained in:
@@ -26,21 +26,25 @@ Before implementing schema, understand:
|
||||
## Core Principles
|
||||
|
||||
### 1. Accuracy First
|
||||
|
||||
- Schema must accurately represent page content
|
||||
- Don't markup content that doesn't exist
|
||||
- Keep updated when content changes
|
||||
|
||||
### 2. Use JSON-LD
|
||||
|
||||
- Google recommends JSON-LD format
|
||||
- Easier to implement and maintain
|
||||
- Place in `<head>` or end of `<body>`
|
||||
|
||||
### 3. Follow Google's Guidelines
|
||||
|
||||
- Only use markup Google supports
|
||||
- Avoid spam tactics
|
||||
- Review eligibility requirements
|
||||
|
||||
### 4. Validate Everything
|
||||
|
||||
- Test before deploying
|
||||
- Monitor Search Console
|
||||
- Fix errors promptly
|
||||
@@ -49,18 +53,18 @@ Before implementing schema, understand:
|
||||
|
||||
## Common Schema Types
|
||||
|
||||
| Type | Use For | Required Properties |
|
||||
|------|---------|-------------------|
|
||||
| Organization | Company homepage/about | name, url |
|
||||
| WebSite | Homepage (search box) | name, url |
|
||||
| Article | Blog posts, news | headline, image, datePublished, author |
|
||||
| Product | Product pages | name, image, offers |
|
||||
| SoftwareApplication | SaaS/app pages | name, offers |
|
||||
| FAQPage | FAQ content | mainEntity (Q&A array) |
|
||||
| HowTo | Tutorials | name, step |
|
||||
| BreadcrumbList | Any page with breadcrumbs | itemListElement |
|
||||
| LocalBusiness | Local business pages | name, address |
|
||||
| Event | Events, webinars | name, startDate, location |
|
||||
| Type | Use For | Required Properties |
|
||||
| ------------------- | ------------------------- | -------------------------------------- |
|
||||
| Organization | Company homepage/about | name, url |
|
||||
| WebSite | Homepage (search box) | name, url |
|
||||
| Article | Blog posts, news | headline, image, datePublished, author |
|
||||
| Product | Product pages | name, image, offers |
|
||||
| SoftwareApplication | SaaS/app pages | name, offers |
|
||||
| FAQPage | FAQ content | mainEntity (Q&A array) |
|
||||
| HowTo | Tutorials | name, step |
|
||||
| BreadcrumbList | Any page with breadcrumbs | itemListElement |
|
||||
| LocalBusiness | Local business pages | name, address |
|
||||
| Event | Events, webinars | name, startDate, location |
|
||||
|
||||
**For complete JSON-LD examples**: See [references/schema-examples.md](references/schema-examples.md)
|
||||
|
||||
@@ -69,21 +73,26 @@ Before implementing schema, understand:
|
||||
## Quick Reference
|
||||
|
||||
### Organization (Company Page)
|
||||
|
||||
Required: name, url
|
||||
Recommended: logo, sameAs (social profiles), contactPoint
|
||||
|
||||
### Article/BlogPosting
|
||||
|
||||
Required: headline, image, datePublished, author
|
||||
Recommended: dateModified, publisher, description
|
||||
|
||||
### Product
|
||||
|
||||
Required: name, image, offers (price + availability)
|
||||
Recommended: sku, brand, aggregateRating, review
|
||||
|
||||
### FAQPage
|
||||
|
||||
Required: mainEntity (array of Question/Answer pairs)
|
||||
|
||||
### BreadcrumbList
|
||||
|
||||
Required: itemListElement (array with position, name, item)
|
||||
|
||||
---
|
||||
@@ -108,6 +117,7 @@ You can combine multiple schema types on one page using `@graph`:
|
||||
## Validation and Testing
|
||||
|
||||
### Tools
|
||||
|
||||
- **Google Rich Results Test**: https://search.google.com/test/rich-results
|
||||
- **Schema.org Validator**: https://validator.schema.org/
|
||||
- **Search Console**: Enhancements reports
|
||||
@@ -125,15 +135,18 @@ You can combine multiple schema types on one page using `@graph`:
|
||||
## Implementation
|
||||
|
||||
### Static Sites
|
||||
|
||||
- Add JSON-LD directly in HTML template
|
||||
- Use includes/partials for reusable schema
|
||||
|
||||
### Dynamic Sites (React, Next.js)
|
||||
|
||||
- Component that renders schema
|
||||
- Server-side rendered for SEO
|
||||
- Serialize data to JSON-LD
|
||||
|
||||
### CMS / WordPress
|
||||
|
||||
- Plugins (Yoast, Rank Math, Schema Pro)
|
||||
- Theme modifications
|
||||
- Custom fields to structured data
|
||||
@@ -143,16 +156,18 @@ You can combine multiple schema types on one page using `@graph`:
|
||||
## Output Format
|
||||
|
||||
### Schema Implementation
|
||||
|
||||
```json
|
||||
// Full JSON-LD code block
|
||||
{
|
||||
"@context": "https://schema.org",
|
||||
"@type": "...",
|
||||
"@type": "..."
|
||||
// Complete markup
|
||||
}
|
||||
```
|
||||
|
||||
### Testing Checklist
|
||||
|
||||
- [ ] Validates in Rich Results Test
|
||||
- [ ] No errors or warnings
|
||||
- [ ] Matches page content
|
||||
|
||||
@@ -363,8 +363,8 @@ Combine multiple schema types using @graph.
|
||||
```jsx
|
||||
export default function ProductPage({ product }) {
|
||||
const schema = {
|
||||
"@context": "https://schema.org",
|
||||
"@type": "Product",
|
||||
'@context': 'https://schema.org',
|
||||
'@type': 'Product',
|
||||
name: product.name,
|
||||
// ... other properties
|
||||
};
|
||||
|
||||
Reference in New Issue
Block a user