Once a custom domain is verified, OmniCon automatically serves a sitemap.xml and robots.txt for that channel — nothing to configure beyond the domain verification itself.
sitemap.xml
https://yourdomain.com/sitemap.xml lists:
- The channel home page (
https://yourdomain.com/) - Every published article that's searchable and not archived or moved, as
https://yourdomain.com/d/{permaname}
Each entry's lastmod is the article's last update time, falling back to its publish date. The file is capped at 5,000 URLs per channel — well above anything OmniCon runs today.
robots.txt
https://yourdomain.com/robots.txt allows crawling everything and points at the sitemap above:
User-agent: * Allow: / Sitemap: https://yourdomain.com/sitemap.xml
Requirements
- The domain must be verified — see Verifying and troubleshooting.
- The channel must be public.
Requesting either file on omnicon.cloud itself — including omnicon.cloud/en/c/{channel}/sitemap.xml — returns a 404. Both files only resolve on the verified domain itself.
Without a custom domain
A channel served under the default omnicon.cloud/{culture}/c/{channel}/… URL has no per-channel sitemap. omnicon.cloud/sitemap.xml and omnicon.cloud/robots.txt are OmniCon's own platform files (marketing pages plus the Help and News sections) and don't list your articles. See Custom domains to set one up.
Caching
Both files are cached for 1 hour. A newly published or edited article can take up to that long to appear.
Community sitemap
If Community is enabled on the channel, its posts get their own sitemap at /community/sitemap.xml on the same domain, separate from the article sitemap above.
Submitting to Google Search Console
Once your domain is verified, submit https://yourdomain.com/sitemap.xml in Search Console to speed up indexing. See Optimizing your content for search for how to connect Search Console to a channel.