SEO & Search Visibility
Control whether a campaign's pages are indexed by search engines, plus the sitemap, robots.txt, llms.txt, and structured data PurposeTech generates.
Overview
Every campaign site gets the technical groundwork search engines look for: a robots.txt, a sitemap.xml, an llms.txt, and event structured data on the home page. Whether any of it leads to your pages being indexed depends on three things: whether the site is public, whether it has its own custom domain, and an indexing opt-in.
Indexing is off by default
Campaign sites tell search engines not to index them (a noindex tag on every page), even when the site is public. Campaigns are often time-bound, invite-only, or not ready to appear in search results, so this is the safe starting point.
Turning indexing on is a site setting called seoIndexable. It is not a switch in the admin portal. Contact support when you are ready for a campaign to be found in search and we will switch it on.
robots.txt
Every campaign has a robots.txt, generated from the campaign's domain and privacy settings:
| Campaign | robots.txt |
|---|---|
| Private (password-protected) | Blocks all crawling |
Public, on a PurposeTech address (your-org.purposetech.io or a campaign subdomain) | Blocks all crawling |
| Public, on its own custom domain | Allows crawling, blocks the sign-in, registration, My Shifts, My Details and roster pages, and includes a Sitemap: line pointing at sitemap.xml |
In practice, a campaign needs a custom domain, a public website and the indexing opt-in before search engines will list it. You don't maintain robots.txt yourself.
Sitemap and llms.txt
Public campaigns have a sitemap.xml and an llms.txt. Both list the campaign home page, the Find shifts (/events) page and the campaign's published CMS pages. Pages marked as hidden are left out. Private campaigns return nothing for either file.
The lists are built from your current pages and cached for up to an hour, so a new page may take a little while to appear.
llms.txt is an emerging convention that gives AI tools a short, plain list of your public pages and how volunteering works, the same idea as a sitemap aimed at a different reader.
Structured data
A campaign's home page includes Event structured data (JSON-LD) whenever the campaign has dates. It carries the campaign name and description, the first and last campaign dates, the organiser name and the site address. The location is given as "Nationwide, NZ", so it is a general description rather than a venue, and individual sites and shifts are not listed in it.
Image optimisation
Images that come from the content system behind your CMS pages are requested at a suitable width and in WebP, so pages load quickly whatever size the original was. There is nothing to configure.
Next steps
- Campaign Pages & Templates – page templates and CMS sections
- Custom Domains & Branding – domains, branding and site privacy
- Organisation Setup – tenant and campaign configuration