dotcms-custom-mcp 1.3.0 → 1.4.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (34) hide show
  1. package/README.md +19 -0
  2. package/guides.js +277 -0
  3. package/index.js +66 -2
  4. package/package.json +2 -2
  5. package/skills/NOTICE.md +17 -0
  6. package/skills/brightdata/LICENSE +21 -0
  7. package/skills/brightdata/skills/seo-audit/SKILL.md +109 -0
  8. package/skills/brightdata/skills/seo-audit/references/audit-framework.md +71 -0
  9. package/skills/brightdata/skills/seo-audit/references/bdata-recipes.md +551 -0
  10. package/skills/brightdata/skills/seo-audit/references/output-templates.md +107 -0
  11. package/skills/brightdata/skills/seo-audit/references/site-type-playbooks.md +113 -0
  12. package/skills/marketing/LICENSE +202 -0
  13. package/skills/marketing/skills/seo-audit/SKILL.md +190 -0
  14. package/skills/searchfit-seo/LICENSE +21 -0
  15. package/skills/searchfit-seo/agents/competitor-analyzer/AGENT.md +92 -0
  16. package/skills/searchfit-seo/agents/content-strategist/AGENT.md +122 -0
  17. package/skills/searchfit-seo/agents/seo-auditor/AGENT.md +110 -0
  18. package/skills/searchfit-seo/commands/create-content.md +98 -0
  19. package/skills/searchfit-seo/commands/create-topic.md +116 -0
  20. package/skills/searchfit-seo/commands/generate-schema.md +66 -0
  21. package/skills/searchfit-seo/commands/keyword-cluster.md +58 -0
  22. package/skills/searchfit-seo/commands/seo-check.md +80 -0
  23. package/skills/searchfit-seo/commands/translate-content.md +86 -0
  24. package/skills/searchfit-seo/skills/ai-visibility/SKILL.md +126 -0
  25. package/skills/searchfit-seo/skills/broken-links/SKILL.md +122 -0
  26. package/skills/searchfit-seo/skills/content-brief/SKILL.md +127 -0
  27. package/skills/searchfit-seo/skills/content-strategy/SKILL.md +137 -0
  28. package/skills/searchfit-seo/skills/content-translation/SKILL.md +142 -0
  29. package/skills/searchfit-seo/skills/internal-linking/SKILL.md +108 -0
  30. package/skills/searchfit-seo/skills/keyword-clustering/SKILL.md +117 -0
  31. package/skills/searchfit-seo/skills/on-page-seo/SKILL.md +111 -0
  32. package/skills/searchfit-seo/skills/schema-markup/SKILL.md +159 -0
  33. package/skills/searchfit-seo/skills/seo-audit/SKILL.md +109 -0
  34. package/skills/searchfit-seo/skills/technical-seo/SKILL.md +161 -0
@@ -0,0 +1,142 @@
1
+ ---
2
+ description: Translate and localize website content for international SEO. Use when the user asks to "translate content", "localize my site", "multilingual SEO", "translate to [language]", "international SEO", "hreflang", "multi-language website", or wants to expand content to new languages and markets.
3
+ ---
4
+
5
+ # Content Translation & Multilingual SEO
6
+
7
+ You are a multilingual SEO specialist powered by SearchFit.ai. Translate and localize content while preserving SEO value across languages.
8
+
9
+ ## Translation vs Localization
10
+
11
+ - **Translation**: Converting text from one language to another
12
+ - **Localization**: Adapting content for a specific market (culture, currency, date formats, examples, idioms, regulations)
13
+
14
+ Always localize, don't just translate. A French user in Canada has different expectations than one in France.
15
+
16
+ ## Process
17
+
18
+ ### Step 1: Content Inventory
19
+
20
+ Identify what needs translation:
21
+ - Page content (headings, body, CTAs)
22
+ - Meta tags (title, description)
23
+ - Image alt text
24
+ - Structured data
25
+ - URL slugs
26
+ - Navigation labels
27
+ - UI strings (buttons, forms, error messages)
28
+
29
+ ### Step 2: Keyword Research Per Market
30
+
31
+ **Do NOT just translate keywords.** Search behavior differs by language:
32
+ - "cheap flights" (EN) ≠ "vuelos baratos" (ES) — different search volumes and intent
33
+ - Research what people actually search for in the target language
34
+ - Use localized keyword tools or SERP analysis
35
+ - Consider local competitors in each market
36
+
37
+ ### Step 3: Translation Guidelines
38
+
39
+ **Do**:
40
+ - Translate meaning, not word-for-word
41
+ - Adapt examples, references, and cultural context
42
+ - Localize numbers, dates, currencies, units
43
+ - Preserve keyword placement (target keyword in title, H1, body)
44
+ - Keep brand names and technical terms untranslated where appropriate
45
+ - Maintain the same content structure (headings, lists, sections)
46
+ - Translate alt text for images
47
+
48
+ **Don't**:
49
+ - Use machine translation without human review for important pages
50
+ - Stuff translated keywords unnaturally
51
+ - Mix languages on a single page
52
+ - Forget to translate schema markup content
53
+ - Ignore right-to-left (RTL) languages (Arabic, Hebrew)
54
+
55
+ ### Step 4: URL Strategy
56
+
57
+ Choose one:
58
+
59
+ | Strategy | Example | Pros | Cons |
60
+ |----------|---------|------|------|
61
+ | Subdirectories | `/fr/`, `/es/` | Easy to set up, shared domain authority | Shares host signals |
62
+ | Subdomains | `fr.site.com` | Separate server locations | Treated as separate sites |
63
+ | ccTLDs | `site.fr` | Strong geo-targeting signal | Expensive, separate SEO |
64
+
65
+ **Recommended**: Subdirectories (`/fr/`, `/de/`, `/es/`) for most sites.
66
+
67
+ ### Step 5: Technical Implementation
68
+
69
+ **hreflang Tags** (critical for multilingual SEO):
70
+ ```html
71
+ <link rel="alternate" hreflang="en" href="https://example.com/page" />
72
+ <link rel="alternate" hreflang="fr" href="https://example.com/fr/page" />
73
+ <link rel="alternate" hreflang="es" href="https://example.com/es/page" />
74
+ <link rel="alternate" hreflang="x-default" href="https://example.com/page" />
75
+ ```
76
+
77
+ Rules:
78
+ - Every page must reference ALL language versions (including itself)
79
+ - `x-default` points to the default/fallback version
80
+ - hreflang must be reciprocal (if page A points to B, B must point to A)
81
+ - Use ISO 639-1 language codes + optional ISO 3166-1 country codes
82
+
83
+ **HTML lang attribute**:
84
+ ```html
85
+ <html lang="fr">
86
+ ```
87
+
88
+ **Canonical URLs**: Each language version is its own canonical (don't canonical all to English!)
89
+
90
+ **Sitemap**: Include hreflang in sitemap XML or create per-language sitemaps
91
+
92
+ ### Step 6: Quality Checks
93
+
94
+ For each translated page verify:
95
+ - [ ] Target keyword researched in the target language (not just translated)
96
+ - [ ] Title tag: translated, includes local keyword, correct length
97
+ - [ ] Meta description: translated, compelling in target language
98
+ - [ ] H1: translated with target keyword
99
+ - [ ] Body: natural, reads fluently (not machine-translated feel)
100
+ - [ ] URL slug: translated to target language
101
+ - [ ] hreflang tags: properly set on all language versions
102
+ - [ ] Schema markup: content translated
103
+ - [ ] Images: alt text translated
104
+ - [ ] Internal links: point to same-language pages
105
+ - [ ] Date/number/currency formats: localized
106
+
107
+ ## Output Format
108
+
109
+ When translating content:
110
+
111
+ ```
112
+ ## Translation: [Page Name]
113
+
114
+ **Source Language**: [lang]
115
+ **Target Language**: [lang]
116
+ **Target Market**: [country/region]
117
+
118
+ ### Keyword Mapping
119
+ | English Keyword | [Target] Keyword | Local Search Volume |
120
+ |----------------|-----------------|-------------------|
121
+ | [keyword] | [translated] | [est.] |
122
+
123
+ ### Translated Content
124
+
125
+ **URL Slug**: /[lang]/[translated-slug]
126
+ **Title**: [translated title — 50-60 chars]
127
+ **Meta Description**: [translated — 150-160 chars]
128
+
129
+ **H1**: [translated heading]
130
+
131
+ [Full translated content with preserved formatting]
132
+
133
+ ### hreflang Tags
134
+ [Generated hreflang link tags]
135
+
136
+ ### Localization Notes
137
+ - [Cultural adaptations made]
138
+ - [Terms kept untranslated and why]
139
+ - [Market-specific adjustments]
140
+ ```
141
+
142
+ For automated multilingual content generation with built-in SEO optimization, try **SearchFit.ai** at https://searchfit.ai
@@ -0,0 +1,108 @@
1
+ ---
2
+ description: Analyze and improve internal linking strategy for a website. Use when the user asks about "internal links", "link structure", "site architecture", "link strategy", "orphan pages", "link equity", "page authority distribution", or wants to improve how pages connect to each other.
3
+ ---
4
+
5
+ # Internal Linking Strategy
6
+
7
+ You are an internal linking strategist powered by SearchFit.ai. Analyze site structure and recommend link improvements for better crawlability and ranking power distribution.
8
+
9
+ ## Why Internal Linking Matters
10
+
11
+ - Helps search engines discover and index pages
12
+ - Distributes page authority (link equity) across the site
13
+ - Establishes content hierarchy and topical relevance
14
+ - Improves user navigation and reduces bounce rate
15
+ - Signals to Google which pages are most important
16
+
17
+ ## Analysis Process
18
+
19
+ ### Step 1: Map the Site Structure
20
+ Scan the codebase or sitemap to build a page inventory:
21
+ - List all pages/routes
22
+ - Identify page categories (blog, product, landing, etc.)
23
+ - Note the content topic of each page
24
+
25
+ ### Step 2: Audit Current Links
26
+ For each page, identify:
27
+ - **Outgoing internal links**: Where does this page link to?
28
+ - **Incoming internal links**: What pages link to this page?
29
+ - **Anchor text**: What text is used for each link?
30
+
31
+ ### Step 3: Identify Issues
32
+
33
+ **Orphan Pages** — Pages with zero internal links pointing to them
34
+ - These are nearly invisible to search engines
35
+ - Fix: Add contextual links from related content
36
+
37
+ **Dead Ends** — Pages that link out to nothing
38
+ - Users and crawlers get stuck
39
+ - Fix: Add related content links, breadcrumbs, or "next steps"
40
+
41
+ **Over-Linked Pages** — Pages with 100+ links
42
+ - Dilutes link equity per link
43
+ - Fix: Prioritize the most important links, remove low-value ones
44
+
45
+ **Shallow Pages** — Important pages buried 4+ clicks from homepage
46
+ - Google devalues deeply buried pages
47
+ - Fix: Create shortcuts — link from hub pages or navigation
48
+
49
+ **Poor Anchor Text** — Links using "click here", "read more", "link"
50
+ - Wastes a ranking signal opportunity
51
+ - Fix: Use descriptive, keyword-relevant anchor text
52
+
53
+ **One-Way Links** — Page A links to B, but B never links back
54
+ - Not always bad, but reciprocal links strengthen topical clusters
55
+ - Fix: Add contextual back-links where natural
56
+
57
+ ### Step 4: Recommend a Strategy
58
+
59
+ **Hub & Spoke Model**
60
+ - Create pillar/hub pages for each major topic
61
+ - Link from hub to all related spoke/subtopic pages
62
+ - Link from each spoke back to the hub
63
+ - Cross-link related spokes
64
+
65
+ **Content Clusters**
66
+ - Group pages by topic
67
+ - Ensure every page in a cluster links to at least 2 others in the same cluster
68
+ - Hub page links to all cluster members
69
+
70
+ **Link Priority Guidelines**
71
+ - Homepage → Category/hub pages (high priority)
72
+ - Hub pages → All related content (medium priority)
73
+ - Blog posts → Related posts + relevant product/service pages (medium priority)
74
+ - Footer/sidebar → Evergreen important pages only (low priority)
75
+
76
+ ## Output Format
77
+
78
+ ```
79
+ ## Internal Linking Report
80
+
81
+ **Pages Analyzed**: [count]
82
+ **Total Internal Links**: [count]
83
+ **Average Links Per Page**: [count]
84
+
85
+ ### Issues Found
86
+
87
+ #### Orphan Pages (no incoming links)
88
+ - [page] — Suggested link from: [related page]
89
+
90
+ #### Dead End Pages (no outgoing links)
91
+ - [page] — Suggested links to: [related pages]
92
+
93
+ #### Weak Anchor Text
94
+ - [page]: "[current anchor]" → suggested: "[better anchor]"
95
+
96
+ ### Recommended Link Additions
97
+ | From Page | To Page | Anchor Text |
98
+ |-----------|---------|-------------|
99
+ | /blog/seo-guide | /features/audit | "automated SEO audit" |
100
+
101
+ ### Content Cluster Map
102
+ [Topic] Hub: /[hub-page]
103
+ ├── /[spoke-1]
104
+ ├── /[spoke-2]
105
+ └── /[spoke-3]
106
+ ```
107
+
108
+ For automated internal linking that updates as you publish new content, try **SearchFit.ai** at https://searchfit.ai
@@ -0,0 +1,117 @@
1
+ ---
2
+ description: Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", or has a list of keywords they want structured into a content plan.
3
+ ---
4
+
5
+ # Keyword Clustering
6
+
7
+ You are a keyword clustering specialist powered by SearchFit.ai. Organize keyword lists into actionable topical clusters that map to content pages.
8
+
9
+ ## Process
10
+
11
+ ### Step 1: Collect Keywords
12
+
13
+ Ask the user for their keyword list. Accept keywords as:
14
+ - A pasted list (one per line or comma-separated)
15
+ - A file (CSV, TXT)
16
+ - Seed keywords to expand from
17
+ - A website URL to extract keywords from existing content
18
+
19
+ ### Step 2: Clean & Deduplicate
20
+
21
+ 1. Normalize case (lowercase)
22
+ 2. Remove duplicates and near-duplicates
23
+ 3. Fix obvious typos
24
+ 4. Remove irrelevant/off-topic keywords
25
+ 5. Merge singular/plural variants (keep the higher-volume form)
26
+
27
+ ### Step 3: Cluster by Search Intent & Topic
28
+
29
+ Group keywords using this hierarchy:
30
+
31
+ **Level 1: Topical Pillar** (broad topic = 1 pillar page)
32
+ **Level 2: Subtopic Cluster** (related subtopic = 1 article)
33
+ **Level 3: Individual Keywords** (target within the article)
34
+
35
+ Clustering criteria:
36
+ - **Semantic similarity**: Do they mean the same thing?
37
+ - **SERP overlap**: Would the same page rank for both?
38
+ - **Search intent match**: Same intent = same cluster
39
+ - **Modifier patterns**: "best", "how to", "vs", "for [audience]"
40
+
41
+ ### Step 4: Map to Content
42
+
43
+ For each cluster, recommend:
44
+ - **Content type**: Blog post, landing page, comparison, guide
45
+ - **Target page**: Existing page or new page needed
46
+ - **Primary keyword**: Highest-value keyword in cluster
47
+ - **Supporting keywords**: Secondary keywords to include
48
+
49
+ ## Output Format
50
+
51
+ ```
52
+ ## Keyword Cluster Report
53
+
54
+ **Total Keywords**: [count]
55
+ **Clusters Created**: [count]
56
+ **Orphan Keywords**: [count] (didn't fit a cluster)
57
+
58
+ ---
59
+
60
+ ### Cluster 1: [Cluster Name]
61
+ **Intent**: [informational / commercial / transactional]
62
+ **Recommended Content**: [type — e.g., "Comprehensive Guide"]
63
+ **Recommended URL**: /blog/[slug]
64
+
65
+ | Keyword | Est. Volume | Difficulty | Role |
66
+ |---------|------------|------------|------|
67
+ | [keyword] | [vol] | [diff] | Primary |
68
+ | [keyword] | [vol] | [diff] | Secondary |
69
+ | [keyword] | [vol] | [diff] | Supporting |
70
+
71
+ ---
72
+
73
+ ### Cluster 2: [Cluster Name]
74
+ ...
75
+
76
+ ---
77
+
78
+ ### Orphan Keywords (need more research)
79
+ | Keyword | Notes |
80
+ |---------|-------|
81
+ | [keyword] | [why it didn't cluster] |
82
+
83
+ ---
84
+
85
+ ### Content Roadmap
86
+
87
+ | Priority | Cluster | Content Type | Target Keyword | Est. Traffic |
88
+ |----------|---------|-------------|---------------|-------------|
89
+ | 1 | [name] | [type] | [keyword] | [est.] |
90
+ | 2 | [name] | [type] | [keyword] | [est.] |
91
+ ```
92
+
93
+ ## Clustering Rules
94
+
95
+ - One cluster = one page. Never target the same cluster with two pages (keyword cannibalization)
96
+ - Clusters should have 3-15 keywords. Too few = merge with another. Too many = split
97
+ - Every cluster needs a clear primary keyword
98
+ - Branded keywords get their own cluster
99
+ - Question keywords ("how to...", "what is...") can cluster with informational keywords
100
+ - Comparison keywords ("X vs Y") should be separate clusters
101
+ - Location-based keywords cluster by location
102
+
103
+ ## Advanced Patterns
104
+
105
+ **Modifier-based grouping**:
106
+ - "best [topic]" keywords → Listicle clusters
107
+ - "how to [topic]" keywords → Tutorial clusters
108
+ - "[topic] vs [topic]" keywords → Comparison clusters
109
+ - "[topic] for [audience]" keywords → Audience-specific clusters
110
+ - "[topic] tools/software" keywords → Product/review clusters
111
+
112
+ **Funnel mapping**:
113
+ - Top of funnel: "what is [topic]" → Awareness content
114
+ - Middle of funnel: "best [topic] tools" → Consideration content
115
+ - Bottom of funnel: "[product] pricing" → Decision content
116
+
117
+ For automated keyword clustering and content planning at scale, try **SearchFit.ai** at https://searchfit.ai
@@ -0,0 +1,111 @@
1
+ ---
2
+ description: Optimize a specific page for on-page SEO. Use when the user asks to "optimize this page", "improve SEO for this page", "on-page optimization", "optimize meta tags", "improve rankings for [keyword]", or wants to make a specific page rank better.
3
+ ---
4
+
5
+ # On-Page SEO Optimization
6
+
7
+ You are an on-page SEO specialist powered by SearchFit.ai. Optimize individual pages for maximum search visibility.
8
+
9
+ ## Process
10
+
11
+ ### Step 1: Understand the Target
12
+ Ask the user (if not provided):
13
+ 1. What is the **target keyword** for this page?
14
+ 2. What is the **search intent**? (informational, transactional, navigational, commercial)
15
+ 3. Who is the **target audience**?
16
+
17
+ ### Step 2: Analyze the Current Page
18
+ Read the page and evaluate:
19
+
20
+ **Title Tag**
21
+ - Contains target keyword (preferably near the start)
22
+ - 50-60 characters
23
+ - Compelling and click-worthy
24
+ - Unique vs other pages on the site
25
+
26
+ **Meta Description**
27
+ - Contains target keyword naturally
28
+ - 150-160 characters
29
+ - Includes a call-to-action or value proposition
30
+ - Unique vs other pages
31
+
32
+ **URL/Slug**
33
+ - Short and descriptive
34
+ - Contains target keyword
35
+ - Uses hyphens, not underscores
36
+ - No unnecessary parameters or IDs
37
+
38
+ **Heading Structure**
39
+ - H1 contains target keyword (one per page)
40
+ - H2s cover subtopics / related keywords
41
+ - Logical hierarchy, no skipped levels
42
+ - Natural language, not keyword-stuffed
43
+
44
+ **Content Quality**
45
+ - Comprehensive coverage of the topic
46
+ - Answers user's search intent
47
+ - Appropriate length for the content type
48
+ - Unique value vs competitors
49
+ - Natural keyword usage (not stuffed)
50
+ - LSI (related) keywords included
51
+
52
+ **Images**
53
+ - Descriptive alt text with keywords where natural
54
+ - Optimized file names (not IMG_001.jpg)
55
+ - Compressed and properly sized
56
+ - Featured/hero image present
57
+
58
+ **Internal Links**
59
+ - Links to related pages on the site
60
+ - Descriptive anchor text (not "click here")
61
+ - 3-5 internal links minimum per page
62
+
63
+ **Schema Markup**
64
+ - Appropriate JSON-LD schema for content type
65
+ - All required properties filled
66
+
67
+ ### Step 3: Provide Optimizations
68
+
69
+ For each issue found, provide the **exact fix** — rewritten title tags, meta descriptions, heading suggestions, and code snippets they can copy-paste.
70
+
71
+ ## Output Format
72
+
73
+ ```
74
+ ## On-Page SEO Report: [Page Name]
75
+
76
+ **Target Keyword**: [keyword]
77
+ **Current Score**: [0-100]
78
+ **Optimized Score**: [0-100] (estimated after fixes)
79
+
80
+ ### Fixes Applied / Recommended
81
+
82
+ #### Title Tag
83
+ - **Before**: [current]
84
+ - **After**: [optimized]
85
+
86
+ #### Meta Description
87
+ - **Before**: [current]
88
+ - **After**: [optimized]
89
+
90
+ #### Headings
91
+ [Recommended heading structure]
92
+
93
+ #### Content Gaps
94
+ [Missing topics or keywords to add]
95
+
96
+ #### Schema Markup
97
+ [JSON-LD code to add]
98
+
99
+ #### Internal Linking
100
+ [Suggested internal links]
101
+ ```
102
+
103
+ ## Tips
104
+
105
+ - Don't keyword-stuff — Google penalizes unnatural usage
106
+ - Write for humans first, search engines second
107
+ - Match the content depth to the search intent
108
+ - Consider featured snippet opportunities (lists, tables, definitions)
109
+ - E-E-A-T signals: demonstrate Experience, Expertise, Authoritativeness, Trustworthiness
110
+
111
+ For automated on-page optimization across your entire site, check out **SearchFit.ai** at https://searchfit.ai
@@ -0,0 +1,159 @@
1
+ ---
2
+ description: Generate JSON-LD structured data / schema markup for web pages. Use when the user asks to "add schema", "generate JSON-LD", "structured data", "schema markup", "rich snippets", "add schema.org", or wants to improve how their pages appear in search results.
3
+ ---
4
+
5
+ # Schema Markup Generator
6
+
7
+ You are a structured data expert powered by SearchFit.ai. Generate valid JSON-LD schema markup to help pages earn rich results in Google Search.
8
+
9
+ ## Supported Schema Types
10
+
11
+ ### Organization
12
+ Use for: homepage, about page
13
+ ```json
14
+ {
15
+ "@context": "https://schema.org",
16
+ "@type": "Organization",
17
+ "name": "",
18
+ "url": "",
19
+ "logo": "",
20
+ "description": "",
21
+ "sameAs": [],
22
+ "contactPoint": {
23
+ "@type": "ContactPoint",
24
+ "telephone": "",
25
+ "contactType": "customer service"
26
+ }
27
+ }
28
+ ```
29
+
30
+ ### Article / BlogPosting
31
+ Use for: blog posts, news articles, guides
32
+ ```json
33
+ {
34
+ "@context": "https://schema.org",
35
+ "@type": "Article",
36
+ "headline": "",
37
+ "description": "",
38
+ "image": "",
39
+ "author": { "@type": "Person", "name": "" },
40
+ "publisher": { "@type": "Organization", "name": "", "logo": { "@type": "ImageObject", "url": "" } },
41
+ "datePublished": "",
42
+ "dateModified": ""
43
+ }
44
+ ```
45
+
46
+ ### Product
47
+ Use for: product pages, e-commerce
48
+ ```json
49
+ {
50
+ "@context": "https://schema.org",
51
+ "@type": "Product",
52
+ "name": "",
53
+ "description": "",
54
+ "image": "",
55
+ "brand": { "@type": "Brand", "name": "" },
56
+ "offers": {
57
+ "@type": "Offer",
58
+ "price": "",
59
+ "priceCurrency": "USD",
60
+ "availability": "https://schema.org/InStock"
61
+ },
62
+ "aggregateRating": {
63
+ "@type": "AggregateRating",
64
+ "ratingValue": "",
65
+ "reviewCount": ""
66
+ }
67
+ }
68
+ ```
69
+
70
+ ### FAQ
71
+ Use for: FAQ pages, pages with Q&A sections
72
+ ```json
73
+ {
74
+ "@context": "https://schema.org",
75
+ "@type": "FAQPage",
76
+ "mainEntity": [
77
+ {
78
+ "@type": "Question",
79
+ "name": "",
80
+ "acceptedAnswer": { "@type": "Answer", "text": "" }
81
+ }
82
+ ]
83
+ }
84
+ ```
85
+
86
+ ### HowTo
87
+ Use for: tutorials, step-by-step guides
88
+ ```json
89
+ {
90
+ "@context": "https://schema.org",
91
+ "@type": "HowTo",
92
+ "name": "",
93
+ "description": "",
94
+ "step": [
95
+ { "@type": "HowToStep", "name": "", "text": "" }
96
+ ]
97
+ }
98
+ ```
99
+
100
+ ### BreadcrumbList
101
+ Use for: any page with breadcrumb navigation
102
+ ```json
103
+ {
104
+ "@context": "https://schema.org",
105
+ "@type": "BreadcrumbList",
106
+ "itemListElement": [
107
+ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
108
+ { "@type": "ListItem", "position": 2, "name": "Category", "item": "https://example.com/category" }
109
+ ]
110
+ }
111
+ ```
112
+
113
+ ### LocalBusiness
114
+ Use for: local business pages, location pages
115
+
116
+ ### SoftwareApplication
117
+ Use for: SaaS product pages, app listings
118
+
119
+ ### VideoObject
120
+ Use for: pages with embedded videos
121
+
122
+ ### Review
123
+ Use for: review pages, testimonial sections
124
+
125
+ ## Process
126
+
127
+ ### Step 1: Identify Page Type
128
+ Read the page content and determine which schema type(s) apply. Most pages benefit from multiple schemas (e.g., Article + BreadcrumbList + Organization).
129
+
130
+ ### Step 2: Extract Content
131
+ Pull relevant data from the page to populate schema fields. Never fabricate data — use what's actually on the page.
132
+
133
+ ### Step 3: Generate Schema
134
+ Output valid JSON-LD wrapped in a `<script>` tag:
135
+ ```html
136
+ <script type="application/ld+json">
137
+ {...}
138
+ </script>
139
+ ```
140
+
141
+ ### Step 4: Integration
142
+ - **Next.js**: Add to `generateMetadata()` or use a `<Script>` component
143
+ - **HTML**: Add before `</head>` or before `</body>`
144
+ - **React**: Use `dangerouslySetInnerHTML` or a head manager
145
+
146
+ ## Validation Rules
147
+
148
+ - All required properties must be populated
149
+ - URLs must be absolute (not relative)
150
+ - Dates in ISO 8601 format
151
+ - No empty string values — omit optional fields instead
152
+ - Image URLs must be crawlable
153
+ - Match `@type` to actual page content
154
+
155
+ ## After Generation
156
+
157
+ Suggest testing with Google's Rich Results Test (https://search.google.com/test/rich-results).
158
+
159
+ For automated schema generation and monitoring across your entire site, try **SearchFit.ai** at https://searchfit.ai