Multilingual SEO and AI search: what InsightSite does by default
Translating content is only the first step of a multilingual site. Search engines need to know which language versions exist and which one is the default; AI search needs to understand quickly what the site is about. Here is what InsightSite does out of the box.
URLs and languages
Each language has its own path prefix, such as /zh and /us. Content is stored per language and UI strings can be edited in the admin. Add more languages in the config; a live site already serves Finnish.
Signals for search engines
- hreflang and x-default on every page, linking its language versions.
- Per-language sitemaps that pick up new content as soon as it is published.
- Canonical URLs so the same content is not treated as duplicates.
- Structured data: Organization JSON-LD for the site and Article JSON-LD for posts.
- Instant indexing: IndexNow (Bing, Yandex and others) and Baidu submission on publish.
Entry points for AI search
- llms.txt: a short plain-text description of the site and its key pages for AI.
- An AI summary endpoint with a structured summary of the site's content.
- AI crawler rules in robots.txt: allow or block each AI crawler separately.
Per-post settings
Title, description, focus keyword, social image, canonical URL and robots directives can be set for each piece of content in the editor.
None of this needs an extra SEO plugin; it is there the day the site goes live.
Related articles
InsightSite 1.30–1.31: backups to object storage, multi-user with password reset, fleet checks
The latest release adds three practical things: send site backups straight to R2 / S3 / Alibaba OSS / Tencent COS, run the admin with several administrators and e-mail password reset, and check the health and AI-search readiness of every site in one command.
InsightSite 1.7–1.9: a safer admin, configurable bot protection and scheduling without cron
The last few releases focused on three things: a hardened admin, a choice of human check for every form, and scheduled content that goes live even on sites without a cron job.
Choosing a human check for your forms: built-in captcha, Turnstile or reCAPTCHA
Admin login, contact forms, comments and checkout all need protection from bots. The three options suit different sites; here is how to pick and configure one.