Seven x2y tools remain free. Code Leak Detector is $29 as a one-time purchase.

View products

Professional Sitemap Generator & SEO Crawler

SiteDirective

v2.0.0

A professional-grade desktop application for web developers, SEO specialists, and digital marketers. Built as a high-performance crawling engine, it automates website structure discovery to generate search engine-compliant XML, HTML, JSON, and TXT sitemaps.

WINDOWSJS RENDERING100% LOCALZERO TELEMETRY

Free — no account, no cloud processing, no telemetry. Every crawl runs entirely on your machine.

At a glance

  • Versionv2.0.0
  • PlatformWindows 10 / 11
  • RenderingFull JS engine, SPA-aware
  • SitemapsXML · HTML · JSON · TXT
  • Crawl depth1–10 levels
  • PriceFree · 0 bytes out

Crawls, renders and audits run on your machine. Results export as sitemaps and CSV — nothing is sent to a vendor.

Core features

A crawling engine built for real-world websites

Full website crawling with JS rendering

Most crawlers see only static HTML. SiteDirective uses a real browser rendering engine to execute JavaScript, wait for dynamic content to load, and discover URLs that only appear after client-side hydration. Single-page applications, React, Vue, Angular — all fully indexed.

XML, HTML, JSON, TXT sitemap generation

Export sitemaps in every format search engines accept. XML for Google and Bing submission, HTML for human-readable site maps, JSON for API-driven workflows, and plain TXT for lightweight indexing. All generated locally from live crawl data.

Robots.txt Architect with custom rules

Build, preview and validate robots.txt files with a visual rule editor. Define user-agent directives, allow/disallow patterns, crawl-delay values and sitemap references. Test rules against your crawled URL set before deploying.

Crawl Depth Control (1–10 levels)

Set exactly how deep the crawler goes — from a single landing page (depth 1) to a full site traversal (depth 10). Combine with URL pattern filters to scope crawls precisely. Throttle request rate to respect server resources and avoid rate limiting.

SEO analysis

Audit every page before search engines do

Broken Link Detection (404 errors)

Every internal and external link is checked during the crawl. Dead links are flagged with their source page, anchor text and HTTP status code. Export the full report to prioritise fixes before they hurt your search rankings.

Metadata Audit (missing titles and descriptions)

Scan every crawled page for missing, duplicate or truncated title tags and meta descriptions. Identify pages with no H1 heading, multiple H1s, or missing canonical URLs. Colour-coded severity makes triage fast.

Performance Flagging (heavy pages)

Pages with excessive response times, oversized payloads or slow server responses are flagged automatically. Identify the pages dragging down your Core Web Vitals before Google does it for you.

100% local processing, zero telemetry

Every crawl runs on your machine. Crawled data, sitemaps, audit reports and robots.txt files are stored locally and never transmitted. No analytics, no crash reports, no cloud relay. Verify with any network monitor.

Specifications

Technical details

SiteDirective specifications
ProductSiteDirective
Versionv2.0.0
PlatformWindows
RenderingFull JavaScript engine (SPA-aware)
Sitemap formatsXML, HTML, JSON, TXT
Crawl depth1–10 levels configurable
Robots.txtVisual architect with rule testing
Broken linksInternal + external 404 detection
Metadata auditTitles, descriptions, H1, canonicals
PerformanceResponse time and payload flagging
Rate controlConfigurable request throttle
URL filteringInclude/exclude patterns
ExportSitemaps, CSV audit reports
Processing100% local — no cloud relay
Telemetry0 bytes — verified continuously
Account requiredNone — ever
PriceFree
Developerx2y Devs Tools Ltd, Nairobi, Kenya

Quick start

From install to first sitemap in four steps

  1. 01

    Install

    Download from Microsoft Store or itch.io. Run the installer — no administrator privileges required for standard installs. No account creation, no activation key.

  2. 02

    Configure the crawl

    Enter the root URL. Set crawl depth (1–10), enable or disable JS rendering, configure request throttle and add URL include/exclude patterns to scope the crawl.

  3. 03

    Crawl and analyse

    SiteDirective discovers URLs, renders JavaScript, checks every link and audits metadata. Review the results table — status codes, response times, titles, SEO flags — all in real time.

  4. 04

    Export and deploy

    Generate sitemaps in XML, HTML, JSON or TXT. Build a robots.txt with the visual architect. Export audit reports as CSV. Everything saves locally — upload to your server when ready.

JS rendering note. Enabling JavaScript rendering uses a bundled browser engine and increases memory usage during the crawl. For large sites, start with a shallow depth (2–3) and increase once you have confirmed the crawl scope is correct.

Downloads

Get SiteDirective v2.0.0

Verify before installing. Every release is signed. Compare the published checksum on the release page against your downloaded file before running the installer.

Changelog

Release history

2026v2.0.0

Major release. Full JavaScript rendering engine for SPA-aware crawling. Robots.txt Architect with visual rule editor and testing. Multi-format sitemap export (XML, HTML, JSON, TXT). Broken link detection for internal and external URLs. Metadata audit covering titles, descriptions, H1 and canonicals. Performance flagging for heavy pages. Crawl depth control (1–10 levels). Configurable request throttling and URL pattern filtering.

2025v1.x

Initial release. Basic sitemap generation from static HTML crawling. XML export. Simple URL discovery without JavaScript rendering.

Security model

Your crawl data never leaves your machine

Data policy. Telemetry: 0 bytes collected. Account required: none, ever. Crawl data: stored locally only. Sitemaps and reports: saved to your filesystem, never transmitted. Cloud processing: none — the crawl engine runs entirely on your hardware. Licence: free.

SiteDirective makes outbound HTTP requests to the websites you choose to crawl — that is its function. It makes zero other network connections. No analytics endpoint, no crash reporter, no licence verification server, no "improve this product" telemetry. The crawled data, generated sitemaps, audit reports and robots.txt files are written to your local filesystem and exist nowhere else. Verify with Wireshark, Fiddler, GlassWire or your firewall logs.

Security manifest
Telemetry0 bytes collected
AccountNone required — ever
Crawl dataStored locally only
SitemapsSaved to filesystem, never transmitted
Cloud processingNone — engine runs on your hardware
Outbound trafficOnly to crawled target sites
VerificationAny network monitor

Crawling properly

The difference between a URL list and an understanding of a site

Rendering is the whole game

A static fetch sees the HTML shell of a client-rendered application: nav links that exist only after hydration, routes that never appear in markup, and menus built by a router. Crawl that and you conclude a site is a fraction the size it is.

SiteDirective drives a full JavaScript engine, so it sees what a browser sees — including content injected after load — and records the status code and payload that a real visitor would. Depth control (1 to 10 levels) and include/exclude URL patterns keep large sites tractable without giving up rendering.

Throttling is courtesy, and it is configurable

A crawler without a throttle is a denial-of-service test on your own staging box. Request throttling, depth limits and pattern filters exist so a crawl is sized to what the server can take, and so the results describe your site rather than the artefacts of a hammered environment.

This is also the right way to treat robots.txt: read it, respect it, and use the built-in architect to author rules you have actually tested before you deploy them.

Four sitemap formats, chosen on purpose

XML is what search engines consume, so it is the default export. HTML sitemaps serve people and give crawlers a link graph that does not depend on a file path. JSON suits programmatic pipelines and static-site generators; TXT is the quick inventory for a review or a handover.

Because they come from the same crawl, the four cannot drift out of sync with each other — the failure mode of hand-maintained sitemap files. That single-source behaviour is most of the value of the tool.

The audit is a checklist you can prove

Broken-link detection covers internal and external 404s; the metadata audit flags missing or duplicate titles and descriptions, absent H1s and canonical mismatches; performance flagging identifies heavy pages by response time and payload.

These are the same checks we run against this site before a release. An offline crawler is not a Search Console replacement — it has no idea what a search engine decided to index — but it is the cheapest way to catch a broken template, a missing canonical or an orphaned route before anybody else does.

Where crawl data goes: nowhere

Crawled URLs, response bodies, audit findings and exports stay on the machine that ran the crawl. There is no vendor cloud receiving your pre-launch site, your staging credentials or your client's structure.

For agencies, that is a contractual point as much as a privacy one: the crawl of a client's unreleased site is confidential data, and a hosted SEO platform stores it somewhere you did not choose.

How it works

Configure a crawl, get publishable artefacts

01

Point at a root URL

Set the start address, choose a crawl depth between 1 and 10 and add include or exclude patterns so a marketing site is not swallowed by its own documentation subfolder.

02

Crawl and render

The engine fetches each URL, renders JavaScript, records status codes and response times, and builds the link graph. Throttle to protect the target while it works.

03

Audit what it found

Review broken internal and external links, metadata gaps, canonical mismatches and heavy pages from the same crawl — no second pass, no re-fetch.

04

Export and deploy

Write the XML, HTML, JSON or TXT sitemap plus a CSV audit report. Validate against a live search-console submission once deployed; a local crawl proves structure, not index coverage.

Technical summary
RenderingFull JavaScript engine, SPA routes included
Crawl scopeDepth 1–10, include and exclude patterns
EtiquetteConfigurable request throttling
robots.txtVisual architect with rule testing
AuditsLinks, metadata, canonicals, performance
ExportsXML · HTML · JSON · TXT sitemaps, CSV reports
Test a staging site, keep the robots rules honest. Run SiteDirective against an environment that blocks crawlers with noindex and a restrictive robots.txt, confirm the crawl respects both, and only then point it at production. A crawler that cannot be tamed by those files will annoy every server it ever touches.

Who it is for

Crawl jobs that need to stay on your machine

SEO specialists and agencies

Audit a client site before and after a migration, and hand over the CSV report without the crawl itself living on a vendor's server.

Front-end and platform teams

Catch orphaned routes, broken internal links and missing metadata in a SPA build before it ships.

Marketing teams on static hosts

Generate the XML and HTML sitemaps your host expects, from a local crawl, with no third-party account in the loop.

Documentation and knowledge bases

Large doc trees are exactly where depth limits and URL filters pay for themselves — and where hand-maintained sitemaps drift.

Pre-launch QA

Verify canonicals, titles, H1s and status codes on staging, while the site is still nobody's problem but yours.

Performance triage

Heavy-page flagging and response times from the same crawl point at the templates worth optimising, without installing an agent.

Prerequisites

Crawl sizing, etiquette and environment

SiteDirective prerequisites and crawl sizing
RequirementMinimumRecommended
Operating systemWindows 10Windows 11
Target accessA URL the machine can reachInclude staging hosts that resolve only on your network or VPN
Crawl budgetDepth 1–2 for a quick inventoryDepth 3–5 with include and exclude patterns for a real audit
ThrottlingAny value above the default concurrencyThrottle down for staging, small VPS or shared servers
RenderingOn for static HTML sites too, to confirm parityAlways on for SPAs and any client-rendered route
OutputLocal disk for sitemaps and CSV exportsVersion the generated XML in your repository so it is reviewable
PrivilegesStandard user accountNo service, scheduler or background agent is installed
A crawl is a request load. Size depth and throttle to the server you are hitting, respect robots.txt, and never crawl a production site you do not own without permission. The tool gives you the controls; the judgement stays with the operator.

Context

Desktop crawler versus hosted SEO platforms and curl scripts

Comparison of local, hosted and scripted crawling
ConcernSiteDirectiveHosted SEO platformAd-hoc script
Where crawl data sitsYour machineVendor cloud, per retention policyYour terminal scrollback
CostFreeMonthly per-project subscriptionEngineering hours
JavaScript renderingFull engine, SPA-awareUsually included in higher tiersYou build it
Works against staging or offlineYes, including localhostOften blocked by plan tier or public-URL requirementYes, if you write it
robots.txt authoringBuilt-in architect with rule testingReport-only in most toolsYou parse it
SchedulingOn demand from the desktop appRecurring crawlsYou own the cron
Historical trend dashboardsNot the purpose; export and diff CSVsBuilt inNot the purpose

Questions

The ones that come up in the first crawl

Yes, and the point is to let you see what those rules do before search engines find out. Read the directives, confirm the crawl respects them, then use the Robots.txt Architect to compose rules and test them against your own URL list.
That is the main reason this is a rendering crawler rather than an href harvester. A full JavaScript engine executes the page, so client-rendered routes and content appear in the crawl the same way a browser would find them.
Yes — being a desktop app, it crawls anything your machine can reach, including localhost and hosts that resolve only on your network or VPN. Nothing needs to be publicly accessible first, which is what makes pre-launch auditing possible.
XML for search engines, HTML for people and link discovery, JSON for pipelines and static-site tooling, and TXT for inventories and handovers. All four derive from one crawl, so they cannot disagree with each other.
No. Crawled URLs, response data and audit findings are processed and stored locally; exports are files you choose to create and where you choose to put them. There is no cloud relay, and no account to attach the results to.
No, and it would be a lie to say so. Search engines tell you what they actually indexed; SiteDirective tells you what is structurally there and what a crawler will find. Use the desktop audit to fix the site, then confirm the outcome in your webmaster tools once it is live.
Only if you let it. Request throttling, depth limits and URL filters exist to size a crawl to the environment. For a small VPS or a staging box, start with shallow depth and an aggressive throttle and increase from there.
Export the audit as CSV and diff it, or keep each generated sitemap under version control in your repository. There is no hosted history or trend dashboard — the artefacts are files you own, which is the trade we chose deliberately.

Documentation

Guides, downloads and the release record

Then go and fix the findings. Titles, descriptions, canonicals and breadcrumbs on this site are generated and checked with the same checklist SiteDirective runs — see Privacy for the no-tracking commitments behind our own crawl-friendly files, and the changelog for engine changes.

Ready to crawl

Download SiteDirective — map, audit and export, entirely offline

No cloud processing. No account. No telemetry. Just a high-performance crawler that renders JavaScript, finds broken links and generates compliant sitemaps — all on your machine.

Summary
Versionv2.0.0
PlatformWindows
PriceFree
Telemetry0 bytes