adynato-seo
Handles SEO requirements for all web content including blogs, landing pages, and documentation. Covers LD+JSON schema.org structured data, internal backlinks strategy, further reading sections, meta tags, and Open Graph. Use when creating or editing any public-facing web content, blog posts, or pages that need search visibility.
Handles SEO requirements for all web content including blogs, landing pages, and documentation. Covers LD+JSON schema.org structured data, internal backlinks strategy, further reading sections, meta tags, and Open Graph. Use when creating or editing any public-facing web content, blog posts, or pages that need search visibility.
SEO Skill
Use this skill when creating or modifying any public-facing web content for Adynato projects.
Requirements Checklist
Every public page MUST include:
- LD+JSON Structured Data - schema.org markup in
<script type="application/ld+json"> - Internal Backlinks - Links to related Adynato projects/pages
- Further Reading Section - At the end of content, link to related resources
- Meta Tags - title, description, keywords
- Open Graph Tags - og:title, og:description, og:image, og:url
LD+JSON Schema.org
Always include structured data. See references/SCHEMAS.md for templates.
Required Schemas by Content Type
| Content Type | Required Schemas |
|---|---|
| Blog Post | Article, BreadcrumbList, Organization |
| Landing Page | WebPage, Organization, optional Product/Service |
| Documentation | TechArticle, BreadcrumbList |
| Product Page | Product, BreadcrumbList, Organization |
Implementation
Place LD+JSON in the <head> or before closing </body>:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
...
}
</script>
For multiple schemas, use @graph:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{ "@type": "Article", ... },
{ "@type": "BreadcrumbList", ... },
{ "@type": "Organization", ... }
]
}
</script>
Internal Backlinks
Every piece of content must link to related Adynato projects and pages.
Rules
- Minimum 2-3 internal links per page/post
- Link naturally within content, not just in footer sections
- Use descriptive anchor text - not "click here" or "read more"
- Cross-link related projects - if mentioning image optimization, link to img4web
Example
When optimizing images for your project, use [img4web](https://github.com/adynato/img4web)
to automatically compress and convert assets to modern formats like WebP and AVIF.
Further Reading Section
Every blog post and documentation page must end with a "Further Reading" section.
Format
## Further Reading
- [Related Post Title](/blog/related-post) - Brief description of what reader will learn
- [Another Project](https://github.com/adynato/project) - How it relates to current topic
- [External Resource](https://example.com) - Why this external link is valuable
Rules
- Minimum 3 links in Further Reading
- At least 1 internal link to Adynato content
- Include brief descriptions explaining relevance
- Mix of internal and external resources when appropriate
Meta Tags
Required Meta Tags
<meta name="title" content="Page Title - Adynato">
<meta name="description" content="Concise description under 160 characters">
<meta name="keywords" content="relevant, keywords, comma, separated">
<meta name="author" content="Adynato">
Open Graph (Required)
<meta property="og:type" content="article">
<meta property="og:url" content="https://adynato.com/blog/post-slug">
<meta property="og:title" content="Post Title">
<meta property="og:description" content="Description for social sharing">
<meta property="og:image" content="https://adynato.com/images/og/post-slug.png">
<meta property="og:site_name" content="Adynato">
Twitter Cards
<meta name="twitter:card" content="summary_large_image">
<meta name="twitter:title" content="Post Title">
<meta name="twitter:description" content="Description for Twitter">
<meta name="twitter:image" content="https://adynato.com/images/og/post-slug.png">
Blog Post Frontmatter
For MDX/Markdown blogs, include this frontmatter:
---
title: "Post Title"
description: "Meta description under 160 characters"
date: "2026-01-17"
author: "Author Name"
tags: ["tag1", "tag2"]
image: "/images/blog/post-slug/cover.png"
ogImage: "/images/og/post-slug.png"
schema:
type: "Article"
datePublished: "2026-01-17"
dateModified: "2026-01-17"
---
Validation
Before publishing, verify:
- [ ] LD+JSON validates at https://validator.schema.org/
- [ ] Meta description is under 160 characters
- [ ] OG image exists and is correct dimensions (1200x630)
- [ ] At least 2 internal backlinks present
- [ ] Further Reading section has 3+ links
- [ ] All links are working (no 404s)
You Might Also Like
Related Skills
cache-components
Expert guidance for Next.js Cache Components and Partial Prerendering (PPR). **PROACTIVE ACTIVATION**: Use this skill automatically when working in Next.js projects that have `cacheComponents: true` in their next.config.ts/next.config.js. When this config is detected, proactively apply Cache Components patterns and best practices to all React Server Component implementations. **DETECTION**: At the start of a session in a Next.js project, check for `cacheComponents: true` in next.config. If enabled, this skill's patterns should guide all component authoring, data fetching, and caching decisions. **USE CASES**: Implementing 'use cache' directive, configuring cache lifetimes with cacheLife(), tagging cached data with cacheTag(), invalidating caches with updateTag()/revalidateTag(), optimizing static vs dynamic content boundaries, debugging cache issues, and reviewing Cache Component implementations.
vercel
component-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
langgenius
web-artifacts-builder
Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.
anthropicsfrontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
anthropics
react-modernization
Upgrade React applications to latest versions, migrate from class components to hooks, and adopt concurrent features. Use when modernizing React codebases, migrating to React Hooks, or upgrading to latest React versions.
wshobsontailwind-design-system
Build scalable design systems with Tailwind CSS v4, design tokens, component libraries, and responsive patterns. Use when creating component libraries, implementing design systems, or standardizing UI patterns.
wshobson