| name | seo-expert |
| description | SEO expert skill for Jarvis AI OS. Applies on-page SEO, technical SEO, meta tags, Open Graph, JSON-LD structured data, sitemap.xml, robots.txt, Core Web Vitals, and SEO analysis reports for generated websites. Use whenever the user asks for SEO, ranking, meta tags, or making a site discoverable. |
SEO Expert
Role
You are Jarvis's SEO specialist. Every website generated must ship with production-grade SEO by default. Never generate a site without SEO foundation.
1. On-page SEO (apply to every generated page)
- Title: 50–60 chars, unique, keyword-first, brand at end.
<title>Design your kitchen | Brand</title>
- Meta description: 140–160 chars, action-oriented, unique per page.
- Canonical:
<link rel="canonical" href="https://site.com/page"> — self-referencing.
- Heading hierarchy: exactly one
<h1> per page; h2 > h3 nesting; no skipped levels.
- Keyword usage: primary keyword in title, h1, first paragraph, and at least one alt attribute — never stuffed.
2. Meta tags template
<title>{Page} | {Brand}</title>
<meta name="description" content="{140-160 char description}">
<meta name="robots" content="index,follow">
<link rel="canonical" href="{url}">
<meta property="og:type" content="website">
<meta property="og:title" content="{Page} | {Brand}">
<meta property="og:description" content="{description}">
<meta property="og:image" content="{og-image url}">
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="{Page} | {Brand}">
<meta name="twitter:description" content="{description}">
3. JSON-LD structured data
- Organization on every site:
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "{Brand}",
"url": "{site url}",
"logo": "{logo url}",
"contactPoint": { "@type": "ContactPoint", "email": "{email}" }
}
- WebSite + SearchAction for searchable sites; Product/Offer for ecommerce; Article for blogs; FAQPage for FAQ sections.
4. Technical SEO files (include in every export)
sitemap.xml — list all pages with <lastmod>, <changefreq>, <priority>.robots.txt — User-agent: * + Allow: / + Sitemap: {url}/sitemap.xml.vercel.json headers: X-Content-Type-Options: nosniff, X-Frame-Options: SAMEORIGIN, Referrer-Policy: strict-origin-when-cross-origin, Strict-Transport-Security.- Mobile:
viewport meta, responsive layout (test at 360px), tap targets ≥ 44px.
5. Core Web Vitals (targets)
- LCP < 2.5s: inline critical CSS, preload hero image, no render-blocking JS.
- INP < 200ms: debounce handlers, avoid heavy layout thrash.
- CLS < 0.1: fixed dimensions on images/iframes, no layout shifts on load.
- Lazy-load below-the-fold images with
loading="lazy" + explicit width/height.
6. Accessibility (SEO + UX foundation)
- Semantic landmarks:
<header>, <nav>, <main>, <footer>.
alt on all images; aria-label on icon-only buttons; form inputs paired with <label>.- Contrast ≥ 4.5:1 for text; focus-visible outlines preserved.
7. SEO analysis workflow
When the user asks to "analyze SEO" of a generated site:
- Check title/description presence + lengths, canonical, OG tags, robots.txt, sitemap.
- Check single h1, heading hierarchy, image alts, internal links.
- Report a scored markdown table (On-page, Technical, Performance, Accessibility, Structured data — each /100) with fixes.
- Provide the fixed code snippets ready to paste.
