コレクション

ブログ公開ツールキット

ブログ記事向けのSNSプレビュー、クリーンなHTMLマークアップ、Canonical URL、構造化データ、レスポンシブ画像のツール。

利用できるツール

今すぐ使えるブログ公開ツールキット

このカテゴリでできること

ブログ記事には繰り返し発生するメタデータのニーズがあります:SNSプレビュータグ、Canonical URL、リンク関係、画像マークアップ、構造化データ。これらの詳細は定期的な公開の中で見落とされがちです。

向いている作業

  • ブログ記事のSNSシェアプレビューを準備する。
  • Canonical URLとリンクタグを記事テンプレート間で一貫させる。
  • コンテンツの多いページに構造化データと画像マークアップを追加する。

Workflow steps

  1. Write and finalize your post content: Complete your article text, headline, excerpt, and featured image before generating metadata. Final content ensures your social preview text, structured data, and canonical URL reflect the published version.
  2. Create social preview tags: Use the OG and Twitter Card builder to generate Open Graph and Twitter Card tags with your post title, description, URL, and image. These tags control how your post appears when shared on social platforms.
  3. Set the canonical URL: Generate a canonical link tag that points to the published URL of the post. This prevents duplicate content issues if the post appears on multiple paths, such as category and tag archive pages.
  4. Add structured data: Use the JSON-LD starter builder to generate Article schema with your post headline, publication date, author, and featured image. Structured data helps search engines display rich results for your content.
  5. Configure link relationships: Generate link rel tags for pagination, alternate formats, and related content. Include prev and next tags for multi-page articles and alternate tags for translated versions if applicable.
  6. Prepare responsive images: Generate responsive image markup with multiple source sizes and formats for your featured and inline images. Use srcset and picture elements to serve the appropriate image size for each viewport.

Prerequisites

  • A blog or article page with finalized headline, excerpt, and featured image file.
  • A publishing platform or static site generator that supports custom head markup per page.
  • Access to your site template or CMS custom fields to insert generated meta tags and structured data.
  • A content workflow that tracks the canonical URL and publication date for each post.

Publishing checklist

  • Each post has unique og:title and og:description that match the post content, not a site-wide default.
  • Canonical URL is set to the final published URL and matches any URL parameters or trailing slash conventions used on the site.
  • JSON-LD structured data includes required Article properties: headline, datePublished, author, and image.
  • Link rel prev and next tags only appear on paginated post series, not on individual single-page posts.
  • Responsive image srcset includes at least two source sizes with the correct ordering from smallest to largest.
  • Social preview image URL is absolute or resolves correctly when shared outside the site context.

Related collections

多言語サイト設定, GitHub Pages公開ワークフロー

FAQ

ブログ公開ツールキットのFAQ

Should I use the same social preview image for every blog post?

A shared default image is acceptable for small blogs, but unique images per post produce richer previews on social platforms and give readers context before they click. Create at least a post-specific og:title when a custom image is not available.

Do I need JSON-LD structured data for every post?

Article structured data helps search engines understand your content type and can enable rich results in search. It is useful for any blog that wants better search visibility, though it is not required for indexing or ranking.

Should I set a canonical URL on a post that is only published once?

Yes. If the post might appear on category, tag, author, or archive pages, those URLs could be treated as duplicate content. Setting a canonical on the main post URL keeps the signal clear.

How do responsive images affect blog performance?

Responsive images reduce unnecessary data transfer by serving smaller files to smaller screens. This improves load time on mobile devices and reduces bandwidth usage without sacrificing image quality on larger displays.