Skip to content

SEO and Social Cards for Your Micropage Site

Getting a page indexed and looking good when it’s shared shouldn’t require a plugin, a checklist, and an afternoon. Micropage emits a full set of SEO and social-sharing tags on every published page — meta description, Open Graph, Twitter Card, canonical, theme-color, JSON-LD — and serves sitemap.xml and robots.txt for you.

Most of it works with no configuration. The rest is a handful of keys in your [site] block.

Site-wide defaults

Add these directly inside [site]. They apply to every page and are the defaults you’ll override per page when you need to.

[site]
title: Acme Widgets
description: Beautifully simple widgets for makers.
keywords: widgets, gadgets, makers
og_image: <- /assets/social-card.png
og_type: website
twitter_handle: @acmewidgets
theme_color: #5c6fff
lang: en

The two that matter most:

  • description — your default meta description, reused for og:description and the Twitter card. Keep it between 50 and 160 characters; search engines truncate longer ones.
  • og_image — the image shown when someone shares your link. Use a 1200×630 PNG or JPG. Upload it as a project file and reference it with <-, just like any other image.

If you don’t set og_image, Micropage falls back to your logo, so even an unconfigured site gets a sensible social card.

Per-page overrides

Any page can override the site defaults with an indented meta: block. It has to come before the page’s first /// section.

[page -> /blog/launch]
meta:
  description: We're launching Acme Widgets v2 — here's what changed.
  og_image: <- /assets/launch-card.png
  og_type: article
  canonical: https://acmewidgets.com/blog/launch

# Launching v2

Today we shipped a complete redesign...

Useful keys here: description, keywords, og_image, og_type, and canonical. Set canonical (an absolute https:// URL) when you’re reposting content that lives on another site, so you don’t compete with the original.

What you get without doing anything

Every published site automatically exposes:

  • /sitemap.xml — one entry per page, with the absolute URL (from your custom domain, or the default *.micropage.sh host) and the deploy timestamp. Nothing to configure.
  • /robots.txt — allows crawling and points at your sitemap.
  • Open Graph and Twitter Card tags on every page, so links unfurl properly in Slack, iMessage, X, and LinkedIn.
  • A JSON-LD WebSite schema block with your site name, URL, and description.

Keeping pages out of the index

Use noindex: true for pages that shouldn’t rank — thank-you confirmations, staging pages, utility routes:

[page -> /thanks]
meta:
  noindex: true

# Thanks!

We got your message.

A noindex page is dropped from sitemap.xml and gets a noindex, nofollow robots tag. Set noindex: true at the [site] level to take an entire site out of the index while it’s under construction.

Where Micropage stops

Two things it won’t generate for you:

  • JSON-LD is WebSite only. Richer schemas (Article, FAQPage, Product) aren’t emitted — embed them with a raw HTML block if you need them.
  • No custom robots.txt rules beyond the site-wide noindex flag. Hide individual pages with per-page noindex instead.

Next steps