SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillspublish-checklist

publish-checklist

Frontend & websites

View repository

Updated 10-16 05:04

About this skill

Publish Checklist

A checklist that is automatically applied to every new site/landing/deliverable page. Before calling a page "complete", the template in this file must be filled in. The same criteria are used when auditing existing sites (seo-setup G0).

1. Copy-paste template (<head>)

Use it as-is, changing only the placeholders. All URLs are absolute paths.

<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<title>{Primary Keyword} — {Brand}</title>
<meta name="description" content="{150자 내외, 구체적 베네핏 + 행동 유도}">
<link rel="canonical" href="https://{domain}/{path}">

<html lang="ko"> (or the corresponding language).

2. Rules

Title

  • Unique per page. Pattern: internal pages {키워드} — {Brand}, home is {Brand} — {한 줄 가치제안}.
  • 50–60 characters (EN) / ~30 characters (KR) — if it overflows, it gets truncated in search results. Naver is especially strict about title rules (ENGINES.md §2).

Description

  • Unique per page, 150–160 characters (EN) / 70–80 characters (KR). Write a reason to click, not a list of keywords.

OG image

  • Fixed at 1200×630, one per page, on-brand (logo + title text within the safe area's central 1000×524). Text should be 40px+ so it is readable even on mobile cards.
  • Absolute URL required — relative paths break in KakaoTalk/Slack previews.
  • If there isn't one, make one and include it. A page without OG looks like a dead link the moment it is shared.

Favicon

  • Minimum set of 4: favicon.ico(32), icon.svg(dark mode support possible), apple-touch-icon.png(180×180, opaque background with padding), icon-192/512.png+manifest.
  • If there is no brand symbol, use wordmark initials at least — no default globe/blank favicon.

Korean page typography

  • word-break: keep-all to body/headline — prevents line breaks in the middle of words.
  • Check headline overflow in the mobile viewport.

3. Verification (immediately after deployment)

  1. Paste the URL into KakaoTalk/Slack → check the card preview (image + title + description). If the cache remains: re-scrape with Facebook Sharing Debugger (developers.facebook.com/tools/debug).
  2. Check the favicon set in the browser tab + when added to the mobile home screen.
  3. view-source:Check that og:image is an absolute URL and that canonical is the final domain (it is common for the staging domain to be left in and deployed).
  4. Pick 2–3 pages at random and check that title/description differ from each other — the same title on every page is the most common mistake.