SEO
Two optional fields override what search engines and social platforms show for a release’s detail page.
| Field | Used for |
|---|---|
| SEO title | The clickable headline in search results and the title on a shared link. |
| SEO description | The snippet underneath it. |
Leave them blank and the release’s Title and Description are used instead. For most releases that is the right answer — set these only when you want something different.
When it’s worth overriding
Section titled “When it’s worth overriding”Your headline is stylised. A title like “Onwards.” works on your press page and is meaningless in a search result. An SEO title of “GISL announces expansion into three new markets” is what someone searching would actually click.
Your headline is long. Search results truncate. A shorter SEO title keeps the important half visible.
Your description assumes context. The card sits among your other releases; a search result sits among strangers. The SEO description can restate what the card takes for granted.
Practical lengths
Section titled “Practical lengths”Guidance rather than limits — nothing is rejected for being long, it is just cut off in the result:
- SEO title: roughly 60 characters.
- SEO description: roughly 155 characters.
Front-load both. The beginning survives truncation; the end may not.
What the app does not do
Section titled “What the app does not do”- No keyword analysis or scoring. These are two override fields, not an SEO tool.
- No sitemap of its own. Detail pages are served through the app proxy under your own domain, so they are part of your store rather than a separate site.
- No control over indexing. Whether a page is indexed is between the search engine and your store’s settings.
A note on redirects
Section titled “A note on redirects”If Redirect to source is ticked, visitors — and crawlers — are sent to the external URL, so your SEO fields do little. See Linking to an external source.