Syenite serves a sitemap and robots.txt so crawlers can discover and index the site. You can verify ownership in Google Search Console (GSC) using an environment variable. For an overview of how Syenite is discoverable by AI agents and MCP clients, see MCP server DeFi and crypto discovery.
GET https://syenite.ai/sitemap.xml returns an XML sitemap of the homepage, docs index, and all doc articles — including the MCP Server DeFi Tools Reference and the Build a DeFi AI Agent guide. Updated when new docs are added. Cache-Control: 1 hour. Submit this URL in GSC under Sitemaps after verifying the property.
GET https://syenite.ai/robots.txt allows crawlers for / and /docs, disallows /dashboard and /metrics, and references the sitemap. Cache-Control: 24 hours.
Add the property at search.google.com/search-console with URL prefix https://syenite.ai. To verify ownership, use one of the following.
In GSC choose “HTML tag” and copy the content value from the meta tag. Set it in your deployment environment:
GOOGLE_SITE_VERIFICATION=your-token-from-gscSyenite injects <meta name=”google-site-verification” content=”...”> into the landing page head when this variable is set. Redeploy, then click Verify in GSC.
If you prefer the file method, use the same token. GSC will ask you to place a file named google<token>.html. Syenite serves that URL with the required content when GOOGLE_SITE_VERIFICATION is set. Request https://syenite.ai/google<token>.html after deploying; then verify in GSC.
Submit the sitemap URL in GSC (Sitemaps → Add a new sitemap → sitemap.xml). Use the URL Inspection tool to request indexing for important URLs. Key pages to prioritize include Why agentic DeFi, the MCP Server DeFi Tools Reference, and the agent quickstart. Indexing can take a few days for new or updated pages.