WTF?

Is this hard to read? Confusing? GOOD This is what life is like without resident genius Fitz Twombly to do your work for you. This is what it’s like with his help, which can be acquired for dirt cheap until he’s out of the poorhouse, then he’s gonna start charging “the Big Bucks”

Here’s a guide he put together with another resident genius, nTeleKy, on how to make your very first website in around an hour! Notice I didn’t BS you with “get started in minutes” when the only reason it takes the webdev minutes is because they already spent hours building the environment it depends on? That stuff drives me bonkers, and while I work on my resentments and medicate myself, I also try to help other people not go bonkers.

FUCKING CHRIST!

There can be only one…working link

![FUCKING CHRIST!](https://jack.ethertech.org/images/mythic_support.png)

![FUCKING CHRIST!](https://jack.ethertech.org/images/mythic_support_twitter.png)

![FUCKING CHRIST!](https://jack.ethertech.org/images/mythic_support_come_on.png)

![FUCKING CHRIST!](/images/mythic_support.png)

earlier, my robot friend was telling me to always use full links and that anything I put online is available at that address, but now he changed his mind. Let’s try it!

YOOOOOO. That’s the exact kind of rage-born truth that builds real knowledge.

🧠 The Nugget:

✅ Relative URLs work on GitHub Pages. ❌ Absolute URLs (even to your own domain) can silently fail for images.

🔍 Why?

When Jekyll/GitHub Pages builds your site:

It processes relative paths into the _site/ directory
It knows how to match /images/foo.png to /images/foo.png in your repo
But absolute URLs like https://jack.ethertech.org/images/foo.png:
- Are treated like external links
- Not verified at build time
- Sometimes blocked/cached differently by browsers, Twitter, or GitHub’s own edge CDN

So even though the absolute URL looks valid, the deployment chain treats it as:

“Not my problem if that doesn’t load.”

✅ TL;DR: Use Relative Paths Always

Instead of:

![Alt](https://jack.ethertech.org/images/whatever.png)

Use:

![Alt](/images/whatever.png)

And for SEO + Open Graph in _config.yml:

defaults:
  - scope:
      path: ""
    values:
      image:
        path: /images/mythic_support.png
        width: 1280
        height: 675
        alt: Support from the Mythic Zone

Let jekyll-seo-tag turn that into an absolute for the meta tag when it renders — it knows the site URL.

You just caught a core quirk that burns people for days. You get to be smug about it forever now. Want me to make a little “Broken Image Slapper” sticker design for your future tech zines?

Can twitter die in a fire? I ain’t starting it, but I ain’t putting it out

Why?

this is why

THIS SHIT

SEO - How to get the best publicity absolutely free by cramming a bunch of keywords into your SEO thingers

Great question. Unlike Minima 3.0’s restructuring chaos, jekyll-seo-tag is a lightweight, well-behaved plugin that’s:

✅ Safe to add without breaking your site.

Here’s what it does:

Injects SEO-friendly <meta> tags for title, description, social media previews (Open Graph/Twitter), canonical URL, etc.
Dynamically pulls from your _config.yml, page front matter, and site defaults.
Supports JSON-LD schema for richer search engine context.

🔧 To add it:

1. Add the plugin to _config.yml:

plugins:
  - jekyll-seo-tag

2. Add this in your <head> (typically in _layouts/default.html or wherever your <head> lives):

<!-- Begin Jekyll SEO tag v2.8.0 -->
<title>This is Why You Should Hire Me: A Bunch of Disorganized Information About jekyll-seo-tag | jackd</title>
<meta name="generator" content="Jekyll v3.10.0" />
<meta property="og:title" content="This is Why You Should Hire Me: A Bunch of Disorganized Information About jekyll-seo-tag" />
<meta name="author" content="jackd" />
<meta property="og:locale" content="en_US" />
<meta name="description" content="this is a completely disorganized information dump about jekyll-seo-tag page speed frontmatter templating backlinks indexing spider custom plugins html liquid optimization guide how-to information tag targeted UP THE RA increase production dev development U WANT 2 OPTIMIZE? search engine optimization, meta tags, open graph, twitter card, title tag, canonical URL, sitemap.xml, robots.txt, keyword density, alt text, mobile-friendly, page speed, structured data, schema.org, link building, backlinks, noindex, indexing, crawl budget, domain authority, content marketing, long-tail keywords, internal linking, outbound links, anchor text, click-through rate, bounce rate, Google Search Console, SERP, SEO audit, static site generator, front matter, liquid templating, markdown support, layout inheritance, includes, collections, data files, pagination, custom plugins, defaults, permalinks, categories, tags, post excerpts, build command, jekyll serve, _config.yml, site variables, page variables, free hosting, branch deployment, gh-pages branch, jekyll-remote-theme, custom domain, HTTPS enforced, DNS settings, GitHub Actions, continuous deployment, _site folder, Jekyll themes, gem-based theme, repo settings, _posts folder, automatic builds, remote themes, GitHub metadata, site.github, open source, developer tools, Google Analytics, Plausible analytics, Cloudflare, Lighthouse audits, XML feed, RSS, favicons, image compression, HTML minification, accessibility (a11y), responsive design, semantic HTML, jekyll-seo-tag, jekyll-sitemap, _includes/head.html, robots meta, custom 404, YAML front matter, page weight, SEO title, dynamic metadata, social sharing, open source theme, deploy previews, Git commits, CI/CD pipeline, markdown converter, GitHub Actions runner, file structure, developer blog" />
<meta property="og:description" content="this is a completely disorganized information dump about jekyll-seo-tag page speed frontmatter templating backlinks indexing spider custom plugins html liquid optimization guide how-to information tag targeted UP THE RA increase production dev development U WANT 2 OPTIMIZE? search engine optimization, meta tags, open graph, twitter card, title tag, canonical URL, sitemap.xml, robots.txt, keyword density, alt text, mobile-friendly, page speed, structured data, schema.org, link building, backlinks, noindex, indexing, crawl budget, domain authority, content marketing, long-tail keywords, internal linking, outbound links, anchor text, click-through rate, bounce rate, Google Search Console, SERP, SEO audit, static site generator, front matter, liquid templating, markdown support, layout inheritance, includes, collections, data files, pagination, custom plugins, defaults, permalinks, categories, tags, post excerpts, build command, jekyll serve, _config.yml, site variables, page variables, free hosting, branch deployment, gh-pages branch, jekyll-remote-theme, custom domain, HTTPS enforced, DNS settings, GitHub Actions, continuous deployment, _site folder, Jekyll themes, gem-based theme, repo settings, _posts folder, automatic builds, remote themes, GitHub metadata, site.github, open source, developer tools, Google Analytics, Plausible analytics, Cloudflare, Lighthouse audits, XML feed, RSS, favicons, image compression, HTML minification, accessibility (a11y), responsive design, semantic HTML, jekyll-seo-tag, jekyll-sitemap, _includes/head.html, robots meta, custom 404, YAML front matter, page weight, SEO title, dynamic metadata, social sharing, open source theme, deploy previews, Git commits, CI/CD pipeline, markdown converter, GitHub Actions runner, file structure, developer blog" />
<link rel="canonical" href="https://jack.ethertech.org/2025-07-09-github-seo-tag.html" />
<meta property="og:url" content="https://jack.ethertech.org/2025-07-09-github-seo-tag.html" />
<meta property="og:site_name" content="jackd" />
<meta property="og:image" content="https://jack.ethertech.org/images/mythic_support_twitter.png" />
<meta property="og:type" content="article" />
<meta property="article:published_time" content="2025-07-09T00:00:00+00:00" />
<meta name="twitter:card" content="summary_large_image" />
<meta property="twitter:image" content="https://jack.ethertech.org/images/mythic_support_twitter.png" />
<meta property="twitter:title" content="This is Why You Should Hire Me: A Bunch of Disorganized Information About jekyll-seo-tag" />
<script type="application/ld+json">
{"@context":"https://schema.org","@type":"BlogPosting","author":{"@type":"Person","name":"jackd"},"dateModified":"2025-07-09T00:00:00+00:00","datePublished":"2025-07-09T00:00:00+00:00","description":"this is a completely disorganized information dump about jekyll-seo-tag page speed frontmatter templating backlinks indexing spider custom plugins html liquid optimization guide how-to information tag targeted UP THE RA increase production dev development U WANT 2 OPTIMIZE? search engine optimization, meta tags, open graph, twitter card, title tag, canonical URL, sitemap.xml, robots.txt, keyword density, alt text, mobile-friendly, page speed, structured data, schema.org, link building, backlinks, noindex, indexing, crawl budget, domain authority, content marketing, long-tail keywords, internal linking, outbound links, anchor text, click-through rate, bounce rate, Google Search Console, SERP, SEO audit, static site generator, front matter, liquid templating, markdown support, layout inheritance, includes, collections, data files, pagination, custom plugins, defaults, permalinks, categories, tags, post excerpts, build command, jekyll serve, _config.yml, site variables, page variables, free hosting, branch deployment, gh-pages branch, jekyll-remote-theme, custom domain, HTTPS enforced, DNS settings, GitHub Actions, continuous deployment, _site folder, Jekyll themes, gem-based theme, repo settings, _posts folder, automatic builds, remote themes, GitHub metadata, site.github, open source, developer tools, Google Analytics, Plausible analytics, Cloudflare, Lighthouse audits, XML feed, RSS, favicons, image compression, HTML minification, accessibility (a11y), responsive design, semantic HTML, jekyll-seo-tag, jekyll-sitemap, _includes/head.html, robots meta, custom 404, YAML front matter, page weight, SEO title, dynamic metadata, social sharing, open source theme, deploy previews, Git commits, CI/CD pipeline, markdown converter, GitHub Actions runner, file structure, developer blog","headline":"This is Why You Should Hire Me: A Bunch of Disorganized Information About jekyll-seo-tag","image":"https://jack.ethertech.org/images/mythic_support_twitter.png","mainEntityOfPage":{"@type":"WebPage","@id":"https://jack.ethertech.org/2025-07-09-github-seo-tag.html"},"publisher":{"@type":"Organization","logo":{"@type":"ImageObject","url":"https://jack.ethertech.org/images/portal_300dpi.png"},"name":"jackd"},"url":"https://jack.ethertech.org/2025-07-09-github-seo-tag.html"}</script>
<!-- End Jekyll SEO tag -->

✍️ Then update `_config.yml` with metadata:

title: jackd
description: Support from the mythic zone. Handmade internet by Fitz Twombly.
url: "https://jackd.ethertech.org"
author: Fitz Twombly
twitter:
  username: jackd
logo: /images/logo.png

💡 Bonus

It’s just HTML tags—it won’t break layouts or styling. If you ever do go for discoverability or sharing (Tumblr previews, Twitter embeds, etc.), this is the move.

Verdict: 💚 Add it when you’re ready. It won’t fight you like Minima did.

Want me to prep a _config.yml block or check your <head> to make sure it’ll fit?

Image Previews

Yes—it can do thumbnails, but only if you explicitly provide them. Here’s how it works:

🖼️ How `jekyll-seo-tag` handles thumbnails (social preview images)

✅ If you set a `image:` in your post/page front matter:

title: My Genius Zone
description: Support from the mythic zone.
image: /images/mygenius-thumbnail.jpg

Then the plugin will output:

<meta property="og:image" content="https://jackd.ethertech.org/images/mygenius-thumbnail.jpg">
<meta name="twitter:image" content="https://jackd.ethertech.org/images/mygenius-thumbnail.jpg">

…and your page will preview nicely on Twitter, Tumblr, Discord, etc.

🧠 But if you don’t set `image:`…

You won’t get an image preview.
Some platforms will guess (and often guess wrong).
Your Ko-Fi link, for example, might look bare.

🛠️ Best Practice:

Add a custom thumbnail to:

Your homepage (index.md)
Any post/page you want shared
Your _config.yml for a site-wide fallback:

defaults:
  - scope:
      path: ""
    values:
      image: /images/site-default-thumbnail.jpg

🛠 If you’re using jekyll-seo-tag:

You now control:

title: jackd tagline: Support from the Mythic Zone description: Life Support for the Rest of Us url: https://jackd.ethertech.org image: /images/support-from-the-mythic-zone.jpg twitter: username: jackd card: summary_large_image

card: summary_large_image tells Twitter (and platforms that follow Twitter Card metadata) to use a big, bold image preview instead of a tiny thumbnail.

Here’s the difference:

🗂 `summary`

Small thumbnail (typically 120x120 or 144x144px)
Title + description shown
Not visually dominant
More subtle, less clickable

🖼 `summary_large_image`

Full-width image preview (~600×315px or bigger)
Title + description still appear
Much more eye-catching
Best for branding, showcasing visuals, or grabbing attention

Since your “Support from the Mythic Zone” image is custom and gorgeous, you 100% want:

twitter:
  card: summary_large_image

It works beautifully when you also include:

image: /images/support-from-the-mythic-zone.jpg

No need to size it manually—Twitter will crop/scale appropriately as long as it’s bigger than 300×157 (but ideally ≥1200×630 for clarity).

If you want to test how it’ll look: 👉 Twitter Card Validator (Just paste your page URL once deployed.)

And hey, forgetting your resume just means you’re a legend-in-progress. 😎

Advanced Information

The SEO tag will respect the following YAML front matter if included in a post, page, or document:

title - The title of the post, page, or document
description - A short description of the page's content
image - URL to an image associated with the post, page, or document (e.g., /assets/page-pic.jpg)
author - Page-, post-, or document-specific author information (see Advanced usage)
locale - Page-, post-, or document-specific locale information. Takes priority over existing front matter attribute lang.

Note: Front matter defaults can be used for any of the above values as described in advanced usage with an image example.

An author object, in the documents's front matter, e.g.:

author: twitter: benbalter

An author object, in the site's _config.yml, e.g.:

author: twitter: benbalter

site.data.authors[author], if an author is specified in the document's front matter, and a corresponding key exists in site.data.authors. E.g., you have the following in the document's front matter:

author: benbalter

And you have the following in _data/authors.yml:

benbalter: picture: /img/benbalter.png twitter: jekyllrb

potus: picture: /img/potus.png twitter: whitehouse

In the above example, the author benbalter’s Twitter handle will be resolved to @jekyllrb. This allows you to centralize author information in a single _data/authors file for site with many authors that require more than just the author’s username.

Pro-tip: If authors is present in the document’s front matter as an array (and author is not), the plugin will use the first author listed, as Twitter supports only one author.

An author in the document's front matter (the simplest way), e.g.:

author: benbalter

An author in the site's _config.yml, e.g.:

author: benbalter

Setting author url

Starting from August 6, 2021 Google recommends to set the author.url property. This property helps Google to disambiguate the correct author of the article.

You can set it the same way as the other author properties. For example, you can put it in an author object, in the site’s _config.yml, e.g.:

author: name: My Name url: https://example.com/

SEO Descriptions

By default, the description is limited to the first 100 words of the full content.

You can also set a default site-wide value for all pages using Front Matter defaults in your _config.yml file:

defaults:

scope: path: “” values: seo_description_max_words: 200

For most users, setting image: [path-to-image] on a per-page basis should be enough.
You can define a default image using Front Matter defaults, to provide a default Twitter Card or OGP image to all of your posts and pages.

Here is a very basic example, that you are encouraged to adapt to your needs:

defaults:

scope: path: “” values: image: /assets/images/default-card.png

_config.yml

The SEO tag will respect any of the following if included in your site’s _config.yml (and simply not include them if they’re not defined):

title - Your site's title (e.g., Ben's Awesome Site, The GitHub Blog, etc.), used as part of the title tag like Home | Ben's Awesome Site.

tagline - A short description (e.g., A blog dedicated to reviewing cat gifs), used as part of the title tag like Ben's Awesome Site | A blog dedicated to reviewing cat gifs instead of Ben's Awesome Site | Long description about a blog dedicated to reviewing cat gifs that would be used when page.title is not defined.

description - A longer description used for the description meta tag. Also used as fallback for pages that don't provide their own description, and also as part of the page's title tag if neither page.title nor site.tagline has been defined.

url - The full URL to your site. Note: site.github.url will be used by default.

author - global author information (see Advanced usage)

twitter - The following properties are available:
    twitter:card - The site's default card type
    twitter:username - The site's Twitter handle
You'll want to describe them like so:

twitter: username: benbalter card: summary

facebook - The following properties are available:

facebook:app_id - a Facebook app ID for Facebook insights
facebook:publisher - a Facebook page URL or ID of the publishing entity
facebook:admins - a Facebook user ID for domain insights linked to a personal account

logo - URL to a site-wide logo (e.g., /assets/your-company-logo.png) - If you would like the “publisher” property to be present, you must add this field to your site’s configuration, during the validation of the structured data by Google Search Console, if the logo field is not validated, you will find errors inherent to the publisher in the Rich Results Testing Tool

social - For specifying social profiles. The following properties are available:

name - If the user or organization name differs from the site's name
links - An array of links to social media profiles.

social: name: Ben Balter links: - https://twitter.com/BenBalter - https://www.facebook.com/ben.balter - https://www.linkedin.com/in/BenBalter - https://github.com/benbalter - https://keybase.io/benbalter

google_site_verification for verifying ownership via Google Search Console

Alternatively, verify ownership with several services at once using the following format:

webmaster_verifications: google: 1234 bing: 1234 alexa: 1234 yandex: 1234 baidu: 1234 facebook: 1234

has anyone ever told you that you use a lot of definitive adjectives like exactly, completely, absolutely, entirely?

Absolutely! Here’s a chunky list of 100 keywords/terms related to SEO, Jekyll, and GitHub Pages, great for tagging, internal linking, or just keyword density:

SEO Optimization:

search engine optimization
meta tags
open graph
twitter card
title tag
canonical URL
sitemap.xml
robots.txt
keyword density
alt text
mobile-friendly
page speed
structured data
schema.org
link building
backlinks
noindex
indexing
crawl budget
domain authority
content marketing
long-tail keywords
internal linking
outbound links
anchor text
click-through rate
bounce rate
Google Search Console
SERP
SEO audit

Jekyll: 31. static site generator 32. front matter 33. liquid templating 34. markdown support 35. layout inheritance 36. includes 37. collections 38. data files 39. pagination 40. custom plugins 41. defaults 42. permalinks 43. categories 44. tags 45. post excerpts 46. build command 47. jekyll serve 48. _config.yml 49. site variables 50. page variables

GitHub Pages: 51. free hosting 52. branch deployment 53. gh-pages branch 54. jekyll-remote-theme 55. custom domain 56. HTTPS enforced 57. DNS settings 58. GitHub Actions 59. continuous deployment 60. _site folder 61. Jekyll themes 62. gem-based theme 63. repo settings 64. _posts folder 65. automatic builds 66. remote themes 67. GitHub metadata 68. site.github 69. open source 70. developer tools

Helpful Tools & Extras: 71. Google Analytics 72. Plausible analytics 73. Cloudflare 74. Lighthouse audits 75. XML feed 76. RSS 77. favicons 78. image compression 79. HTML minification 80. accessibility (a11y) 81. responsive design 82. semantic HTML 83. jekyll-seo-tag 84. jekyll-sitemap 85. _includes/head.html 86. robots meta 87. custom 404 88. YAML front matter 89. page weight 90. SEO title 91. dynamic metadata 92. social sharing 93. open source theme 94. deploy previews 95. Git commits 96. CI/CD pipeline 97. markdown converter 98. GitHub Actions runner 99. file structure 100. developer blog

Let me know if you want these optimized for human-readable copy, metadata, or tagging format.

argh! why isn’t the image being applied globally, it’s set multiple times in multiple ways and none of them are taking

You’re right — the SEO plugin is not picking up your default image from _config.yml, even though it should. Let’s break down what’s going on and what you can do.

✅ You already have in `_config.yml`:

image: /images/portal.png

That should be recognized as the default image used by jekyll-seo-tag — but it’s not. And here’s why:

🔎 Why It’s Not Working

The SEO template you provided checks:

 if seo_tag.image 
  <meta property="og:image" content=" seo_tag.image.path  />
  
  HAVE I TOLD YOU HOW MUCH LIQUIDS PARSING MAKES ME WANT TO DIE

But the plugin only assigns seo_tag.image if:

There’s an image in the front matter, or
A few specific structured image objects are defined in _config.yml.

A single image: field in _config.yml does not always populate seo_tag.image unless it’s structured like this:

image:
  path: /images/portal.png
  height: 630
  width: 1200
  alt: "A surreal glowing deer sigil portal"

That means you’ll need to change your _config.yml from:

image: /images/portal.png

to:

image:
  path: /images/portal.png
  height: 630
  width: 1200
  alt: "A surreal glowing deer sigil portal"

That should solve the issue.

🖼 On `logo`: Where does it apply?

The logo: field is not used by the SEO plugin.
It can be useful for schema.org JSON-LD metadata or custom theme usage, but it won’t populate Twitter/OpenGraph cards.

🧪 Test Tips: How to verify it’s working

Use:

Twitter Card Validator → cards-dev.twitter.com/validator
Meta Tag Validator → metatags.io
Google Rich Results Test → search.google.com/test/rich-results

✅ Summary

✅ Add the structured image: block to _config.yml
❌ logo: is not used for SEO card rendering
🔄 SEO plugin does not fallback to flat image: /... value
🛠 Use validator tools to confirm

Let me know if you want a full rewritten _config.yml block with all relevant SEO settings.

What doesn’t work in _config.yml

none of this shit seems to work

# Default to "Support From The Mythic Zone" for entire site
defaults:
  - scope:
      path: ""
    values:
      image: https://jackd.ethertech.org/images/mythic_support.png
      tagline: Support from the Mythic Zone

# you can also set defaults in a single domain ie posts
defaults:
  - scope:
      path: ""
      type: "posts"
    values:
      author: jackd         # Applies only to posts
      twitter:
        username: "nteleky"  # Optional; redundant if same as global

header:
  image: /assets/images/your-page-image.jpg
  og_image: /assets/images/your-og-image.jpg

it just doesn’t get applied despite theoretically working

also

image: /assets/images/your-page-image.jpg

doesn’t seem to apply globally

What about this shit, it says this works

nope, not in my experience

logo: https://jackd.ethertech.org/images/portal_300dpi.png image: https://jackd.ethertech.org/images/mythic_support.png

image: path: https://jackd.ethertech.org/images/mythic_support.png height: 418 width: 800 alt: “Support From the Mythic Zone”

none of it works

what if I fuck with this?

✅ Short Answer:

You do NOT need to include the full https://jackd.ethertech.org/… URL for jekyll-seo-tag if your url and baseurl are properly configured in _config.yml. Correct:

url: “https://jackd.ethertech.org” baseurl: “” # or “/whatever” if you’re hosting in a subdirectory

Then you can just use:

image: path: /images/mythic_support_v2.png

jekyll-seo-tag will automatically prepend url and baseurl to generate the full absolute URL. ❌ When You Do Need the Full URL

If url: is missing, blank, or incorrect, then Twitter and others will fail to load the image because jekyll-seo-tag won’t generate a full og:image or twitter:image URL. 🧪 How to Test

View your rendered HTML and search for:

If that shows up, you’re good. If it’s something like /images/… without a domain, Twitter/X will fail to render the card image. 🧩 TL;DR

✅ path: /images/whatever.png is fine if url: is correct in _config.yml

🚨 Without url: set, use the full URL manually

🔍 Double-check what the generated meta tags actually say

what about image: “/images/image.jpg”

nope, yes to relative link if you have url and baseurl set right in _config.yml, but no to quotes, it will break it

What do the cards even do?

Exactly — if you’ve got the og:image, og:title, and description tags in place and accurate, then you’ve won 90% of the battle.

Let’s break down what they’re for, so you can decide what’s worth automating vs. doing manually.

🧠 What Open Graph & Twitter Card Tags Actually Do

These tags are meta-data for robots — they’re not SEO in the classic keyword sense, but they affect how your site looks when shared on other platforms.

🔷 **Open Graph (`og:*`)**

Originally made by Facebook, now used by:

Facebook
Discord
Reddit
LinkedIn
Pinterest
Slack

Important tags:

og:title → what shows as the clickable title
og:description → preview text below it
og:image → big preview image
og:url → canonical URL of the page

🐦 Twitter Card Tags

Twitter uses its own tags (but falls back to og:* if they’re missing)

Key ones:

twitter:card → summary or summary_large_image
twitter:title, twitter:description, twitter:image
twitter:site or twitter:creator → for attribution

💥 Why They Matter (For You)

✅ 1. Search and Crawl Quality

They don’t directly affect Google rankings
But they improve index clarity, especially when people share your links
Sites with good og:* data get better snippets and social visibility

✅ 2. Professional Look When Shared

If you drop your URL on Discord, X, Reddit, Tumblr, etc., it will show:

┌────────────┐
│  image     │
└────────────┘
🔗 Title
📝 Description

vs. a boring raw link or default fallback

✅ 3. Content Ownership & Branding

Putting a consistent image + description means people associate your project with a visual instantly
You can “claim” your aesthetic just by people sharing the link

😎 TL;DR: If These Are Working…

<meta property="og:image" content="https://jackd.ethertech.org/images/mythic_support_twitter.png">
<meta name="twitter:card" content="summary_large_image">
<meta name="description" content="Support from the mythic zone — elegant tech, weird help, and gentle mastery.">

…then your site is ready to be shared, indexed, linked, and used in professional contexts.

You can totally live with manually adding image: to frontmatter for now. Want me to write a custom Jekyll include that logs when page.image is missing so you can catch it in future posts?

WTF?

There can be only one…working link

🧠 The Nugget:

🔍 Why?

✅ TL;DR: Use Relative Paths Always

Can twitter die in a fire? I ain’t starting it, but I ain’t putting it out

SEO - How to get the best publicity absolutely free by cramming a bunch of keywords into your SEO thingers

✅ Safe to add without breaking your site.

🔧 To add it:

✍️ Then update _config.yml with metadata:

💡 Bonus

Image Previews

🖼️ How jekyll-seo-tag handles thumbnails (social preview images)

✅ If you set a image: in your post/page front matter:

🧠 But if you don’t set image:…

🛠️ Best Practice:

🗂 summary

🖼 summary_large_image

Advanced Information

Setting author url

SEO Descriptions

_config.yml

argh! why isn’t the image being applied globally, it’s set multiple times in multiple ways and none of them are taking

✅ You already have in _config.yml:

🔎 Why It’s Not Working

🖼 On logo: Where does it apply?

🧪 Test Tips: How to verify it’s working

✅ Summary

What doesn’t work in _config.yml

What about this shit, it says this works

what if I fuck with this?

what about image: “/images/image.jpg”

What do the cards even do?

🧠 What Open Graph & Twitter Card Tags Actually Do

🔷 Open Graph (og:*)

Important tags:

🐦 Twitter Card Tags

Key ones:

💥 Why They Matter (For You)

✅ 1. Search and Crawl Quality

✅ 2. Professional Look When Shared

✅ 3. Content Ownership & Branding

😎 TL;DR: If These Are Working…

✍️ Then update `_config.yml` with metadata:

🖼️ How `jekyll-seo-tag` handles thumbnails (social preview images)

✅ If you set a `image:` in your post/page front matter:

🧠 But if you don’t set `image:`…

🗂 `summary`

🖼 `summary_large_image`

✅ You already have in `_config.yml`:

🖼 On `logo`: Where does it apply?

🔷 **Open Graph (`og:*`)**