You hit publish. Everything after that is handled.
Share cards, search-engine pings, site search, other languages, HTTPS on your domain. The work that usually needs five separate services happens the moment a page goes live.
Everything that happens when you publish
One publish, several things at once
The moment you accept a draft, the page goes live and the rest fans out on its own.
What you would otherwise wire up yourself
| Publishing chore | Do it yourself | Giant Context |
|---|---|---|
Share images | An OG-image service, or a hand-made card for every page. | Rendered live from your branding on every publish. |
Search-engine indexing | Submit URLs by hand in a search console. | IndexNow pings fire automatically on publish. |
Site search | Add and index a third-party search like Algolia. | Built in, across pages, posts, and the knowledge base. |
Other languages | An i18n library, hreflang tags, and a translation pass. | Turn a language on. URLs, hreflang, and translation are handled. |
HTTPS and domain | Certificates and renewals to manage. | Point your domain. HTTPS is handled. |
Where indexing and translation stop
IndexNow reaches Bing, Yandex and the other engines that accept it directly. Google indexing on your own domain goes through your sitemap, not a direct ping. The direct line to Google is reserved for the platform's own domains, and your sitemap is how Google finds the rest.
Translation fills the missing languages when you save. If a translation pass fails, the page still saves in the language you wrote it in.
Publish once. It stays handled.
Every one of these runs again the next time you publish or update a page, including the share card, the pings, the sitemap, and the languages. You approve the change. The rest keeps up on its own.