Sitemap URL Health Checker (via Apify MCP)

io.github.lineagersiui-boop由 GitHub 帳號 lineagersiui-boop 發布v1.0.0更新於 Oct 30, 2026

Check sitemap URLs for 404s, redirects and noindex. One Apify Actor via Apify's hosted MCP server.

發布方自己的服務:Apify MCP Server

已驗證Streamable HTTP可網頁執行網頁搜尋與抓取安全與監控

概覽

AI 產生的概覽

由 Apify 託管的 MCP 工具,檢查網站 XML 網站地圖中每個 URL 是否有 404、重新導向、HTTPS 降級與 noindex 標頭。

可以做什麼
  • 依網域透過 robots.txt 或 /sitemap.xml 尋找網站地圖,也可直接提供網站地圖、索引、.xml.gz 或純文字清單 URL。
  • 逐一請求列出的 URL,回報狀態碼、重新導向、重新導向鏈、最終 URL 與標記。
  • 標記 404/4xx/5xx、重新導向過多、https 轉為 http 以及 X-Robots-Tag noindex 等問題。
  • 每個 URL 輸出一筆資料集項目,並在 SUMMARY 記錄中彙總找到、已檢查、計費、有問題、被 robots 阻擋與出錯的 URL 數量。
適用情境
適合在網站搬遷、更換網域或大量修改內容後,確認網站地圖中的 URL 仍可存取且可被索引。也適合對你有權測試的網站做定期 SEO 健檢。
執行需求
使用 Apify 託管的遠端 MCP 端點,並以 tools 參數只載入此 Actor。需要自己的 Apify 帳號與 API 權杖,以 Authorization Bearer 標頭傳送,或在支援時使用 OAuth 登入。本機 npx 方式使用 APIFY_TOKEN 環境變數。非示範執行需將 confirmPermission 設為 true。
安裝前請注意
執行費用計入你的 Apify 帳號,每個檢查的 URL 收費 0.0005 美元,另加 Apify 平台用量;被 onlyProblems 過濾掉的 URL 仍會計費。此清單作者維護該 Actor 並從中收取費用,端點由 Apify 而非作者營運。只檢查網站地圖列出的 URL,不爬取頁面內連結。你必須有權檢查目標網站。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Sitemap URL Health Checker (via Apify MCP),將其新增到工作區。
  2. 連接 所需的 憑證。它們會被私密儲存,絕不會在公開頁面上展示。
  3. 為需要使用其工具的對話啟用該服務。

Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。

交給代理程式安裝

把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。

閱讀 https://sourceweft.com/mcp/io.github.lineagersiui-boop%2Fsitemap-url-health-checker/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。

檢視代理程式所依據的安裝指南

其他 MCP 客戶端

把它新增到你客戶端的 mcpServers 設定中。 客戶端會在首次連接時完成 OAuth 登入。

{
  "mcpServers": {
    "sitemap-url-health-checker-via-apify": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker"
    }
  }
}

README

Sitemap URL Health Checker: MCP server (via Apify)

Check every URL listed in a website's XML sitemap for 404s, server errors, redirects, redirect chains, https-to-http downgrades and X-Robots-Tag: noindex headers, from any MCP client.

Disclosure: we built and maintain the Apify Actor lineagersiui/sitemap-url-health-checker and earn its pay-per-event fees. This listing is not affiliated with or endorsed by Apify or the Model Context Protocol project. The MCP endpoint is Apify's hosted MCP server (mcp.apify.com), run by Apify, not by us. This listing only preselects our Actor as the single tool. Drafted with AI tools under the author's direction.

Registry name: io.github.lineagersiui-boop/sitemap-url-health-checker

What it does

  • Finds the sitemap from a site address (via robots.txt or /sitemap.xml), or takes direct sitemap, sitemap-index, .xml.gz or plain-text list URLs.
  • Requests each listed URL and reports its status, redirects, final URL and flags.
  • Checks only URLs listed in the sitemap. It does not crawl links inside pages.

Requirements

  • Your own Apify account and API token. Get the token in Apify Console → Settings → API & Integrations. Runs are billed to your Apify account, not ours.
  • Permission to check the site. The Actor refuses non-demo runs unless confirmPermission is true.

Pricing

  • $0.0005 per URL checked (one event per URL that returns an HTTP status). 1,000 URLs cost $0.50, plus Apify platform usage.
  • Not billed: URLs skipped by robots.txt, timeouts and network errors.
  • Free demo: run with empty input to check 20 URLs of apify.com, not billed.

Connect

Endpoint (Streamable HTTP):

https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker

The tools parameter makes Apify's server load only this Actor. Without it, Apify's server loads its default tool set instead.

Bearer token (most clients):

json
{  "mcpServers": {    "sitemap-url-health-checker": {      "url": "https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker",      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }    }  }}

Apify's server also supports OAuth sign-in, without a token in the config, for clients that support it. See Apify's MCP documentation.

Local stdio, for clients without remote support. This runs Apify's own open-source package, not ours:

json
{  "mcpServers": {    "sitemap-url-health-checker": {      "command": "npx",      "args": ["-y", "@apify/actors-mcp-server", "--tools", "lineagersiui/sitemap-url-health-checker"],      "env": { "APIFY_TOKEN": "<YOUR_APIFY_TOKEN>" }    }  }}

Input

FieldTypeNotes
siteUrlsarray of stringsSite addresses, e.g. example.com. Up to 10
sitemapUrlsarray of stringsDirect sitemap, sitemap-index, .xml.gz or plain-text list URLs. Up to 10
confirmPermissionbooleanDefault false. Must be true for non-demo runs
maxUrlsintegerDefault 500, range 1 to 5,000. Hard cap per run
onlyProblemsbooleanDefault false. Leaves out 2xx URLs with no redirect (they are still billed)
timeLimitSecsintegerDefault 1,500, range 60 to 3,600. No new checks start after this

Output

One dataset item per URL: url, status, flags, redirects, redirectStatuses, finalUrl, lastmod, sitemap. The key-value store record SUMMARY holds the counts: urlsFound, checked, billed, problems, blockedByRobots, errors.

FlagMeaning
not_found, client_error, server_error404/410, another 4xx, or 5xx
redirected, redirect_chain, too_many_redirectsOne redirect, more than one, or more than 5
https_downgradeAn https URL redirects to http
noindex_headerSends X-Robots-Tag: noindex
blocked_by_robotsDisallowed by robots.txt; skipped, not billed
timeout, network_error, blocked_private_addressCouldn't be checked; not billed
ok2xx, no redirect

Example prompts

  • "Check the sitemap of example.com for broken links and redirects. I own the site."
  • "Which URLs in https://example.com/sitemap_index.xml return 404 or redirect after our migration?"
  • "Which pages in our sitemap send a noindex header?"

Support

Open an issue in this repository. The Actor is maintained by its author on the Apify Store.

License

This README and server.json are MIT-licensed. The Actor and Apify's MCP server have their own terms.

來源:mcp/sitemap-url-health-checker/README.md,提交 a7bc96e

工具

0
該伺服器需要登入,因此 SourceWeft 無法在沒有帳號的情況下讀取其工具,也未收錄。已連接帳號所能看到的內容可能因帳號及其權限而異。

版本歷史

1
  1. v1.0.0最新Oct 30, 2026

評分

已滿足適用檢查項的 85%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通必需25 分
  • 已宣告認證方式必需10 分
  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

其他 Apify 整合