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) - your site’s pages are listed in robots.txt and your sitemap, so search engines can crawl and index them.
  • Disabled - your site’s routes are excluded from robots.txt and sitemaps.
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.

​
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.

Related topics

IntegrationsDomain and URLSite Overview SettingsCommunity Site AnalyticsOverview