← All use cases

Gist replacement

Replace GitHub Gist embeds in your tutorial blog with self-hosted pastes

Self-hosted Gist replacement for blog tutorials. Embeds render inline, code is on your domain, Google indexes the code WITH your post.

What you are building

A WordPress blog where every code example in a tutorial post lives in a SnipShare paste, embedded inline. Visually identical to a GitHub Gist embed - syntax-highlighted, copyable, with a clean header. But the code is yours: on your domain, indexed under your blog’s authority, never disappearing because someone else’s GitHub account closed.

Why move off Gist embeds

GitHub Gist embeds are the default for WordPress tutorial bloggers in 2026. They work. But every embed has costs:

  • A third-party <script> tag runs on every page view (Gist’s embed.js)
  • Your code is indexed by Google under gist.github.com, not your domain - the Stack Overflow + Gist combo dominates search where you wanted to rank
  • Gist URL changes when GitHub renames repos or your account changes - your tutorial breaks
  • Tracking pixels fire on every page view that includes an embed
  • No revision history visible to your reader - they cannot see how the snippet evolved
  • You cannot customize the styling - it looks like Gist, not like your blog

For a serious technical blog, code embedded on your own domain ranks for your domain, looks like your brand, and survives independently of GitHub’s roadmap.

What SnipShare delivers as a Gist replacement

  • oEmbed support - paste a SnipShare URL on its own line in a Gutenberg post; renders as inline preview
  • Shortcode - [snipshare id="abc"] for explicit embedding
  • Multi-file pastes render with file tabs (same UX as Gist)
  • 20+ language syntax themes - match your blog’s design with custom theme
  • Code stays on your domain - /paste/<hash>/ URL pattern
  • No third-party scripts - the embed is server-rendered HTML + minimal client JS
  • Customizable styling - override the embed CSS in your blog theme

The reader experience is the same. The technical posture is dramatically better.

The migration from Gist to SnipShare

If you have a blog with 50+ Gist embeds, batch migrate over a quiet week:

  1. Install SnipShare + Pro license (Pro adds the rich oEmbed + collections).
  2. Audit existing Gist embeds - WP-CLI: 
    wp post list --format=ids | xargs -I {} sh -c 'wp post get {} --field=content | grep -l "gist.github.com" && echo {}'
    gives you the list of posts to update.
  3. For each Gist URL, fetch the raw content from GitHub: 
    curl https://gist.githubusercontent.com/USER/HASH/raw > snippet.txt
  4. Create a matching SnipShare paste via the REST API: 
    curl -X POST https://yourblog.com/wp-json/snipshare/v1/pastes \
  -H "Authorization: Bearer ${WP_TOKEN}" \
  -d "title=Tutorial%20snippet%20X&language=php&code=$(cat snippet.txt)"
  5. Replace the Gist URL in the post with the new SnipShare URL.
  6. Verify the rendering matches what readers saw before. The shape should be familiar.

For 5-10 embeds, do it manually. For 50+, the WP-CLI script + curl loop runs in under an hour.

SEO gain you do not get with Gist

When your tutorial embeds a Gist, Google sees:

Your blog post (gets some ranking signal)
+ iframe to gist.github.com (gets the ranking signal for the code)

Google ranks gist.github.com for the code content because that is where the indexable HTML lives. Your tutorial gets credit for the prose around the code, but not the code itself.

With SnipShare, the code IS in the rendered HTML of your post. Google indexes your tutorial AS the place that has the code. You compete with Gist + Stack Overflow on equal footing.

For a niche tutorial site that depends on long-tail technical searches (“how to do X in Y”), this changes which results dominate the SERP.

Blog-specific configuration

Some settings worth flipping if SnipShare is for a blog (not a community):

  • Default visibility: Public - blog tutorials need pastes public so they index
  • Public archive: enabled - /pastes/ becomes a “code library” sub-section of your blog
  • Tag-based browse: enabled - readers find related snippets via tag
  • Revision history: enabled - readers can see code evolution if they care
  • Forking: enabled if you have community - readers can fork your snippets into their own accounts; not relevant if your site is read-only
  • Comments: optional - some blogs want code-level discussion; others keep comments off

Collections (Pro) as series-organization

If your blog has multi-part tutorials, Collections (Pro) become a useful organization layer.

Example: a 12-part series on “Building a SaaS dashboard with WordPress + Astro”. Each part has 2-3 pastes. Create one Collection per series, add the pastes. Readers can browse the whole series’s code at once via /pastes/collection/<slug>/.

This also gives you a content asset to promote independently: “the full code library for the dashboard series” as a single shareable URL.

Common pitfalls

  • Migrating only some embeds - readers find the old Gist links, click through, find your blog feels inconsistent. Migrate all in one pass, not piecemeal.
  • Setting tutorial pastes Private - they have to be Public for SEO + reader access. Override the role default if you set Default Visibility to Private for non-blog contexts.
  • Forgetting to redirect old Gist URLs - if your blog post directly linked to gist.github.com (not embedded), set up a Cloudflare Worker or .htaccess rule to redirect to the SnipShare equivalent. Otherwise old backlinks 404.
  • Not customizing embed CSS - default SnipShare embed styling is fine, but your blog probably has different fonts + spacing. 30 minutes of CSS override makes it feel native.

Ship checklist

  • Plugin installed + Pro license active (for oEmbed + Collections)
  • Default visibility set to Public for blog context
  • Tutorial-relevant settings flipped (revision history on, forking optional)
  • oEmbed verified in a test post (paste URL → renders as embed)
  • Migration script ready for batch Gist → SnipShare conversion
  • Embed CSS overridden to match blog typography
  • Site search tested - readers can find pastes via the blog’s search

Then publish your next tutorial with SnipShare embeds. Track Google Search Console - within 60 days you should see your tutorial pages ranking for code-specific queries they previously did not.