Outverse workspaces are optimized for SEO. Unless you're migrating your docs from another platform, you don't need to do anything to help search engines index your content.

Custom domains

You can host Outverse on your own domain or subdomain.

SEO-friendly content

  • HTML titles and H1 tags are generated based on the document or thread title

  • Each page has a self-referencing canonical tag to prevent duplicate content

  • Outverse content is rendered server-side so it can be crawled and indexed by search engines

  • You can set custom alt text for images

Structured data: forum markup

  • In forums with thread resolutions enabled, threads use QAPage structured data

  • In all other forums, threads use DiscussionForumPosting structured data

Open Graph and social sharing

  • Open Graph titles are based on the document or thread title

  • You can set a custom Open Graph image for your Outverse space

XML sitemap

You can find your XML sitemap by appending /sitemap.xml to the Outverse root directory. This could look something like:



You can submit this to Google Search Console to view additional information on indexing.

Speeding up indexing

It can take some time for search engines to pick up new content, especially if it exists on a new domain or new subdomain. To speed up this process:

  • Link to your Outverse space from webpages that have already been indexed, e.g. your main website

  • Submit your sitemap to Google Search Console and manually request indexing for specific pages

Migrating your docs to Outverse

If you're migrating from another knowledge base platform to Outverse, we recommend redirecting your old knowledge base to avoid duplicate content issues and to make sure your Outverse content is picked up by Google.

Redirecting each URL to its corresponding Outverse URL means:

  • Google will recognize your Outverse content as the new version, and index it accordingly (vs viewing your new docs as duplicate content)

  • Customers who have bookmarked your old articles will be redirected to the doc's new location

  • Any link equity from existing backlinks will be passed on, and not lost during the migration