Reach: ecosystem listings and launch channels (awesome lists, MCP directories, Show HN, releases)

[hexsecs]

Tracking issue for distribution work that isn't code. For a developer security tool, these channels likely matter more than classic search ranking.

Search engine submission (owner action — required for the sitemaps to be used at all)

GitHub project pages can't serve an authoritative robots.txt (crawlers only honor it at the host root, and hexsecs.github.io/robots.txt belongs to the user site, not this repo — see discussion on #485). So the sitemaps must be submitted directly:

• Verify the site in Google Search Console and submit https://hexsecs.github.io/canarchy/sitemap.xml and https://hexsecs.github.io/canarchy/docs/sitemap.xml
• Same in [Bing Webmaster Tools](https://www

[hexsecs]

Adding to the "Ongoing" list — surfaced during review of #485:

• Submit both sitemaps directly to search engines. On a GitHub project page the site is served from /canarchy/, so /canarchy/robots.txt is not at the host root and crawlers won't auto-discover its Sitemap: directives (Google treats subdirectory robots files as invalid). Submit https://hexsecs.github.io/canarchy/sitemap.xml and https://hexsecs.github.io/canarchy/docs/sitemap.xml to Google Search Console and Bing Webmaster Tools instead. (A custom domain served from the root would make robots.txt authoritative and remove this step.)

---

Generated by Claude Code