adynato-seo
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)
More from adynato/skills
adynato-mobile
Mobile app development conventions for Adynato projects using React Native and Expo. Covers navigation patterns, native APIs, performance optimization, and platform-specific considerations. Use when building or modifying mobile applications.
14adynato-vercel
Vercel deployment and configuration for Adynato projects. Covers environment variables, vercel.json, project linking, common errors like VERCEL_ORG_ID/VERCEL_PROJECT_ID, and CI/CD setup. Use when deploying to Vercel, configuring builds, or troubleshooting deployment issues.
11adynato-web
Web development conventions for Adynato projects. Covers image optimization with img4web, asset management, component patterns, styling, and performance best practices. Use when building or modifying web applications, adding images/assets, or creating UI components.
11adynato-web-api
Web API development conventions for Adynato projects. Covers API routes, middleware, authentication, error handling, validation, and response formats for Next.js and Node.js backends. Use when building or modifying API endpoints, server actions, or backend logic.
10adynato-github
GitHub workflow conventions for Adynato projects. Covers creating PRs with gh CLI, writing thorough descriptions, and using stacked PRs for large deliverables. Use when creating pull requests, managing branches, or breaking down large features.
10adynato-cloudflare
Cloudflare Workers and Pages deployment for Adynato projects. Covers wrangler CLI, reading logs for debugging, KV/D1/R2 storage, environment variables, and common errors. Use when deploying to Cloudflare, debugging workers, or configuring edge functions.
10