tag
seo
9 entries.
-
ssg 1.9: Share Cards, a Ceiling on Memory and Three Migration Fixes
ssg 1.9.0 draws a share card for every page, keeps a build inside a CPU and memory limit, splits a generated site's sitemap by source, and fixes three ways a migrated site could quietly ship the wrong thing.
-
Breadcrumbs, Honest Sitemap Dates and a Build Report
What changed in ssg 1.8.73 and 1.8.74: breadcrumbs that only link to pages that exist, a sitemap checked against Google's rules, dates in it that are true, the ssg version in templates, and a Go security fix.
-
Three Releases Without a Post: Structured Data, Languages and a Security Fix
What changed in ssg 1.8.70, 1.8.71 and 1.8.72: recipes and FAQs as structured data without a script, a CV page, a front page per language, a newsletter Worker, and a Go security release.
-
The Build Said Nothing
1.8.62 fixes fourteen things that never errored: pages dropped without a word, a 404 in the wrong language, a header that refused geolocation.
-
One Sitemap Per Site Does Not Scale to Forty Clients
An agency has a different relationship with sitemap.xml than a site owner. Split sitemaps answer 'is it indexed' per section, without forty dashboards.
-
The Build Was Green and the Site Was Wrong
Almost every fix in four releases came from one place: a third-party crawler, weeks after a build that reported success. What those failures had in common.
-
Migrating From WordPress Is Easy. Keeping Its URLs Is Not.
A WordPress migration must preserve more than posts: original URLs, category and date archives, menus, comments and language structure all affect old links.
-
Multilingual Without Losing Track of the Page
Translating the words is the easy half. The hard half is that /o-nas/ and /en/about/ are the same page, and nothing in a file tree says so.
-
Legible to Machines: What Landed in SSG 1.8.14
1.8.14 is about the readers you never see: social scrapers, AI agents and your own tooling. Structured data, social images that work, build-time contracts.