Find Sitemap URLs (Utility)
Find → Find Sitemap URLs (Utility)
/v1/find-sitemap-urls-texau{ "domain": "https://acme.com" }
{ "ok": true, "data": { "domain": "https://acme.com", "filtered_url_count": "https://acme.com", "sitemap_url": "https://acme.com", "total_urls_count": "https://acme.com", "url": "https://acme.com" } }
Extracts all URLs from a website's sitemap.xml for SEO analysis and site auditing.
Install
Add find sitemap urls (utility) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__find-sitemap-urls-texau
When to use this.
The "Find Sitemap URLs" action is designed to extract all URLs from a website's sitemap.xml, facilitating SEO analysis and site auditing. By inputting the root domain (e.g., https://example.com), users can efficiently gather essential data for optimizing their online presence. The action outputs key information, including the domain (companyDomain), the total count of discovered URLs (total_urls_count), the count of filtered URLs (filtered_urls_count), and the actual sitemap URLs (sitemap_urls) along with a list of all discovered URLs (urls). This action is particularly useful for digital marketers, SEO professionals, and web developers seeking to enhance website performance and visibility in search engines, making it a vital tool in the enrichment category.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Find Sitemap URLs (Utility)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
domainDomaintextfiltered_url_countFiltered Url Countnullablenumbersitemap_urlSitemap Urlarraytotal_urls_countTotal Urls CountnumberurlUrlnullablearray
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/find-sitemap-urls-texau. Auth: x-api-key.
/v1/find-sitemap-urls-texaucurl -X POST 'https://v3-api.texau.com/api/v1/find-sitemap-urls-texau' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"domain":"https://acme.com"}'
{ "ok": true, "data": { "domain": "https://acme.com", "filtered_url_count": "https://acme.com", "sitemap_url": "https://acme.com", "total_urls_count": "https://acme.com", "url": "https://acme.com" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → find sitemap urls (utility) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
Reliability
Rate limits & reliability.
- Per-minute limit300 / min
- Per-day limit10,000 / day
- RetriesAutomatic w/ backoff
- ModeSync
Errors
HTTP status codes.
What each response means and what to do about it.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
FAQ.
Is this real-time?
Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).
Do I get charged on failure?
No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.
Does it work with Claude / Cursor via MCP?
Yes. Add the texau MCP server to your client config, then call `texau__find-...` directly.
What CRMs can I push results to?
HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.
Run Find Sitemap URLs (Utility) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.