Help, search engines and AI crawlers
Editing help pages, the site description, the AI-crawler setting, and the static robots.txt, sitemap.xml and llms.txt files.
Super → Help & SEO controls how the public side of the platform presents itself.
Search and social#
- Site description — shown under the landing page in search results, in link previews and at the top of
llms.txt. - AI crawlers — Allow lets assistants such as ChatGPT, Claude and Perplexity read the public pages; Block tells their crawlers (GPTBot, ClaudeBot, Google-Extended, CCBot and others) to stay away. Search engines are not affected either way.
What every public page carries#
- a title, a description and a canonical address;
- Open Graph and Twitter tags with a generated 1200×630 image (the product, its price and the workspace's accent colour);
- structured data (JSON-LD): Organization and WebSite on the landing page, Product with an Offer per plan and breadcrumbs on product pages, FAQPage and HowTo on help pages where they apply.
Private pages — account, receipts, checkout hand-off, payment links, staff screens — are marked noindex and listed as disallowed in robots.txt.
The static files#
robots.txt, sitemap.xml, llms.txt, llms-full.txt and site.webmanifest are regenerated every hour by the seo.publish job and written into the webroot, so a plain PHP vhost serves them at the usual addresses. Publish now runs it immediately.
If the webroot belongs to root (the recommended layout), give the PHP user just these five files once:
cd /var/www/encrypted.com/public
sudo touch robots.txt sitemap.xml llms.txt llms-full.txt site.webmanifest
sudo chown www-data:www-data robots.txt sitemap.xml llms.txt llms-full.txt site.webmanifest
Until then, the routes answer at the same addresses wherever Nginx passes unknown paths to the application, and the self-check shows a warning.
Editing help pages#
Every help page ships with the release. Edit next to a page opens the editor:
- change the title, the description and the text (Markdown: headings, lists, tables,
**bold**, `code,> Note:callouts, links such astext, and diagrams with{{diagram:name}}`); - Preview shows the page as visitors will see it; Save publishes it; Revert to shipped text removes your edit.
Edits are kept in the database, so upgrades never overwrite them. When an upgrade changes the shipped version of a page you edited, the editor warns you so that you can merge the changes. Every save and revert is recorded in the audit log. HTML in the text is shown as text, never run.