Push new and changed listings to search engines, and add a sitemap - #46
Merged
Merged
Conversation
The registry's 34,000 server pages had no sitemap and no feed, so crawlers found them by chance. Search engines now hear about each change as it lands. - Serve a sitemap index, 10,000 listings per file, named in a rendered robots.txt - Publish an Atom feed of the newest listings that declares Google's WebSub hub - After each sync, send new, removed and changed URLs to IndexNow, which shares them with Bing, Yandex, Naver, Seznam and Yep, and ping the hub on additions - Batch approvals, API publishes and saved articles into one push a minute - Serve the IndexNow key, derived from SECRET_KEY_BASE so deploys need no new setting, and add bin/announce for a one-off backfill Closes #45 --- Pages affected: - [MCP Registry](https://ai.mcpharbor.dev/) — directory home, now advertising the new-servers feed. - [MCP server directory](https://ai.mcpharbor.dev/servers) — every listing reachable through the sitemap. - [Context7 MCP server](https://ai.mcpharbor.dev/servers/io.github.upstash/context7) — a listing page pushed on change. - [XML sitemap](https://ai.mcpharbor.dev/sitemap.xml) — index of all active MCP servers. - [MCP servers Atom feed](https://ai.mcpharbor.dev/feed.xml) — newest listings, pushed through WebSub. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
About 34,000 server pages had no sitemap and no feed.
/sitemap.xml301'd to the home page androbots.txtnamed nothing, so new listings from each six-hourly sync waited for a crawler to stumble on them. This pushes every change to the discovery channels search engines listen to, and gives crawlers a map of the rest./sitemap.xmlindexes/sitemaps/pages.xmland/sitemaps/servers-N.xml, 10,000 active listings each withlastmod.robots.txtis now rendered so it can name the sitemap./feed.xmlis an Atom feed of the newest 50 listings that declares Google's hub. Pinging the hub is how Google's Feedfetcher hears about a new listing, since Google takes neither IndexNow nor sitemap pings.api.indexnow.org, which shares them with Bing, Yandex, Naver, Seznam and Yep. Approvals, API publishes and saved articles are batched into one request a minute. A 429 is never retried.SECRET_KEY_BASEand served at/<key>.txt. Pushing is on in prod (DISCOVERY_PUSH=falseturns it off) and off in dev and test.After deploy, run
bin/announceonce to backfill all listings.The 17 new tests pass. The 3 failures in
mix testalso fail onmain: the local test database holds leftover seed rows.Closes #45
Pages affected:
🤖 Generated with Claude Code