mirror of
https://github.com/Screenly/Anthias.git
synced 2026-07-30 17:25:50 -04:00
248af07a54
Two things, both found while looking at why the old product name
converts so badly in Search Console.
1. Every JSON-LD string value is wrapped in literal quote characters.
Go's html/template applies contextual auto-escaping inside <script>,
so `{{ .Title | jsonify }}` gets escaped a second time as a JS
string. The emitted value is "\"Installation Options\"" rather than
"Installation Options". The JSON stays valid, which is why this went
unnoticed, but every headline, description and FAQ question carries
stray quotes into Google's rich results.
19 affected values: TechArticle headline + description on all 9 docs
pages, the site description, and all 29 FAQ questions and answers.
Fixed by adding `| safeJS` after `jsonify` at all five call sites —
jsonify already produces correctly escaped JSON, so the second pass
was pure corruption. All 11 ld+json blocks now parse clean with zero
stray-quote values.
2. The site never mentioned "Screenly OSE" — its own former name.
Search Console, last 90 days: 23 old-name queries, 1,962 impressions,
43 clicks (2.19% CTR). "screenly ose" alone is 1,253 impressions at
position 6.8 for 17 clicks; "screenly ose pi3" and "screenly ose
pi 3" are 429 impressions for zero clicks.
Where the two names appear together, the same searchers convert an
order of magnitude better: "anthias (screenly ose)" is 16 clicks from
31 impressions (51.6%) and "anthias screenly ose" 9 from 20 (45%).
People looking for the old name do want this project — the site just
never confirms they are in the right place.
Adds an FAQ entry (inherits the existing FAQPage schema, so it is
eligible as a rich result) citing the December 2022 announcement
linked from the repo README, plus one line under the homepage hero.
hugo 0.157.0 (the version pinned in deploy-website.yaml) builds clean.
Co-authored-by: Cyborg Viktor <307551610+vpetersson-bot@users.noreply.github.com>