Skip to main content
One of the main reasons to run a community site is that it makes conversations in Slack findable on the web. These settings control whether that happens. Both live at Site > SEO & metadata in Studio.
Did you know you can change this with our MCP server too? Try asking your agent: “Turn on search engine indexing for our site.”
SEO and metadata settings in Studio

SEO and metadata settings in Studio

​
Search engine discoverability

The Discoverability setting opts your site in or out of being indexed by search engines.
  • Enabled (the default) - search engines can crawl and index your site’s public pages. Your sitemap at /sitemap.xml helps them discover content that is eligible to appear in search results.
  • Disabled - your site has no sitemap, every public page tells search engines not to index it (a noindex robots header), and robots.txt asks other crawlers, such as AI crawlers, not to crawl the site. Search engines may still revisit public pages to read noindex; existing results disappear as they recrawl.
Turning discoverability off is the right choice while you are still building the site, and the wrong choice once you have launched. A site excluded from sitemaps earns no search traffic, which removes most of the reason to have one.
Discoverability is separate from access control. A site set to Restricted access requires login regardless of this setting, so search engines cannot index its content either way.

​
What appears in your sitemap

/sitemap.xml is the main sitemap for your community site. Depending on the sections you have enabled, it helps search engines discover:
  • Standard site pages
  • Listed Feeds and their public posts
  • Active member profiles that have public activity
  • Events and Groups
  • Resource collections and Tags
Unlisted Feeds and their posts are not included. Bot profiles, deactivated members, and member profiles without public posts or replies are also left out. Those member pages remain available by direct link when your site’s access settings allow it, but they tell search engines not to index them. Tightknit refreshes sitemap data when public content changes. It also notifies supported search engines when a public post is created, updated, unpublished, or deleted. Search engines decide when to recrawl your site, so changes may not appear in search results immediately.

​
Page titles and metadata

Your site name is used as the title in your site header and in SEO metadata, and your site description and social media image are used when pages are shared. Set all three under Site > Overview.

​
Google Tag Manager

Add a Container ID in the format GTM-XXXXXXX to load your Google Tag Manager container on every page of your community site. Leave it blank to disable. Tag Manager lets you add your own analytics, advertising, and marketing tags without touching Tightknit. For the full setup walkthrough, including the events Tightknit emits that you can build triggers on, see Integrations.