Publishing and domains
PWA, head code, and error pages
The Pro finishing touches: install to home screen, your own head tags, and branded error pages.
On Pro and Teams, three extras make a published app feel like a finished product: install-to-home-screen (PWA), your own code in the page head, and branded error pages. Each is small on its own; together they close the gap between "an app on the web" and "my product".
PWA install: your app on the home screen
The PWA card in the SEO tab of the Vault configures the install manifest for your published app: the app's name, a short name for under the icon, theme and background colors, and icons. With it set, visitors' browsers offer to install your app to their home screen or dock, where it opens in its own window like a native app, no app store involved.
Practical notes:
- Use a square icon, ideally 512 by 512, so every platform renders it crisply.
- The short name is what shows under the icon; keep it to a word or two.
- Colors come from a picker and should match your app's brand; the theme color tints the window chrome on install.
This covers most "I want my app on my phone" needs. For the honest boundary between PWAs and app stores, see Known limitations.
Custom head code
The Custom code card in the SEO tab of the Vault injects markup you supply into the <head> of every page of your published app: analytics pixels, marketing and conversion tags, ownership verifications, custom fonts. Up to 20,000 characters, applied at publish time, so changes take effect on your next publish.
Use it for what only you can supply. The essentials (titles, descriptions, social previews, sitemaps) are already handled by Vaulter's SEO plumbing, so head code is for the tags your marketing stack asks you to add, pasted exactly as that service provides them.
Custom error pages
The Error pages card in Vault → Deployments replaces the default not-found and error screens with your own markup, so even your app's dead ends carry your brand. A visitor who mistypes a link sees your page, your tone, and a way back in, instead of a generic screen.
Two details worth knowing:
- Your error pages show on walled apps too, and deliberately without revealing whether the requested path exists behind the wall.
- Like head code, the markup is served exactly as written; paste only what you trust.
Frequently asked
Which of these need a republish?
Head code is baked in at publish, so it takes effect on your next publish. The PWA manifest and error pages are served live by Vaulter's edge and update without one.
Who can edit these?
All three require an admin role on the project. And all three are readable even if the workspace later moves off Pro, so nothing you configured is ever held hostage: you can always see, copy, and clear what you stored.
Can I use head code to add a chat widget or a script that changes the page?
You can, and script tags run as on any site. Keep an eye on the result in your published app: a third-party script that rewrites the page can fight your app's own rendering. Test after the next publish.
Do error pages affect my SEO?
Missing pages return proper not-found status codes either way; the custom page changes what humans see, not what crawlers are told.