kostja94/marketing-skills

open-graph

When the user wants to add, audit, implement, or optimize Open Graph metadata for social sharing, including og:title, og:description, og:image, og:url, Facebook previews, LinkedIn previews, or social share previews.

Voir la source

Mode d’emploi

  1. Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
  2. Consultez le document original pour les outils, identifiants et environnements requis.
  3. Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/kostja94/marketing-skills --skill open-graph

Avant de commencer

  • L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
  • Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original

Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.

SEO On-Page: Open Graph

Owns Open Graph writing and implementation rules for social previews. page-metadata owns the full-page lifecycle and release verification.

When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.

Scope (Social Sharing)

  • Open Graph: Facebook-originated protocol; controls preview card when links are shared on social platforms

The 4 Essential Tags

Every shareable page requires these minimum tags:

html
<meta property="og:title" content="Your Page Title">
<meta property="og:description" content="Your description">
<meta property="og:image" content="https://yourdomain.com/image.png">
<meta property="og:url" content="https://yourdomain.com/page">
TagGuideline
og:titleConcise and useful in a sharing context; same page identity as SEO title, not necessarily identical text
og:descriptionAccurate social summary; may differ from the meta description without changing the promise
og:imageAbsolute HTTPS URL; representative of the page; include dimensions when known
og:urlStable public page identity; normally the same URL declared canonical

Recommended Additional Tags

TagPurpose
og:typeContent type: website, article, video, product
og:site_nameWebsite name; displayed separately from title
og:image:width / og:image:heightImage dimensions (1200×630px)
og:image:altAlt text for accessibility
og:localeLanguage/territory (e.g., en_US); for multilingual sites

Image Best Practices

ItemGuideline
SizeUse a high-resolution image and verify the target platforms' current requirements; 1200×630 is a common cross-platform starting point
FormatUse a platform-supported web image format and verify the deployed response
URLAbsolute URL with https://; no relative paths
UniqueOne unique image per page when possible

Common Mistakes

  • Using relative image URLs instead of absolute https://
  • Images too small or wrong aspect ratio
  • Empty or placeholder values
  • Missing og:url (canonical)
  • Reusing a generic logo or unrelated image when a representative page image is available
  • Copying SEO title/description mechanically when the share context needs different wording

Implementation

Next.js (App Router)

tsx
export const metadata = {
  openGraph: {
    title: '...',
    description: '...',
    url: 'https://example.com/page',
    siteName: 'Example',
    images: [{ url: 'https://example.com/og.jpg', width: 1200, height: 630, alt: '...' }],
    locale: 'en_US',
    type: 'website',
  },
};

HTML (generic)

html
<meta property="og:title" content="Your Title">
<meta property="og:description" content="Your description">
<meta property="og:image" content="https://example.com/og.jpg">
<meta property="og:url" content="https://example.com/page">
<meta property="og:type" content="website">
<meta property="og:site_name" content="Your Site">
<meta property="og:image:width" content="1200">
<meta property="og:image:height" content="630">
<meta property="og:image:alt" content="Alt text">

Testing

Preview services cache metadata. Test the deployed absolute URL and refresh the cache when supported. Also inspect the raw initial HTML; a client-only tag insertion may not be available to every scraper.

Consistency boundary

Open Graph and SEO metadata may use different copy because search and social feeds are different contexts. They must still identify the same page, describe the same product or content, and avoid unsupported claims. Do not require string equality.

Related Skills

  • social-share-generator: Share buttons use OG tags for rich previews when users share; OG must be set for share buttons to show proper cards
  • article-page-generator: Use og:type article for article/post pages; article-specific tags (published_time, author)
  • page-metadata: Full lifecycle, source-of-truth implementation, and production validation
  • title-tag, meta-description: Search copy; may differ while preserving page identity
  • twitter-cards: Twitter uses OG as fallback; add Twitter-specific tags for best results
  • canonical-tag: og:url should match canonical URL
  • og-image-generator: Programmatic OG image generation — 6 visual styles (Terminal/CLI, Magazine Editorial, Swiss Minimal, Pixel Retro, Brutalist, Newspaper), Satori+resvg, Puppeteer, AI image generation tools, and Agent-Native content-aware workflow. This skill covers how to SET the image tag; og-image-generator covers how to CREATE the image.

Tâches connexes

du même dépôt

Autres Skills

Tous les Skills
kostja94
Communauté

google-search-console

When the user wants to analyze Google Search Console data, use the GSC API, or interpret search performance. Also use when the user mentions "GSC," "Search Console," "indexing report," "Core Web Vitals," "Enhancements," "Insights report," "search performance," "search queries," "search performance report," "URL inspection," "impressions," "CTR," "average position," "index coverage," "GSC data analysis," "Search Console API," or "searchanalytics.query." When the user wants to rewrite title tags (

installations
1
GitHub Stars
1,1 k
Mis à jour
6 oct.
kostja94
Communauté

indie-hacker-strategy

When the user wants indie hacker or bootstrapping founder strategy—growth, channels, Build in Public, or solo founder tactics. Also use when the user mentions "indie hacker," "indie developer," "bootstrapping," "bootstrapped founder," "solo founder," "Build in Public," "scratch your own itch," "Micro-SaaS," "first 100 users," or "solo company." For cold start, use cold-start-strategy.

installations
1
GitHub Stars
1,1 k
Mis à jour
6 oct.
kostja94
Communauté

google-ads

When the user wants to set up, optimize, or manage Google Ads campaigns. Also use when the user mentions "Google Ads," "Google Search Ads," "PPC," "SEM," "PMF testing with ads," "test product-market fit," "Responsive Search Ads," "RSA," "Performance Max," "Quality Score," "keyword bidding," or "Google Display/YouTube ads." For paid mix, use paid-ads-strategy.

installations
3
GitHub Stars
1,1 k
Mis à jour
6 oct.
kostja94
Communauté

growth-funnel

When the user wants to plan growth using the AARRR framework, diagnose growth bottlenecks, or map actions across the customer lifecycle. Also use when the user mentions "growth funnel," "AARRR," "pirate metrics," "acquisition activation retention," "customer lifecycle metrics," or "growth framework." For retention tactics, use retention-strategy.

installations
3
GitHub Stars
1,1 k
Mis à jour
6 oct.