Add website
The setup page for adding a site you own or control to your local Siteimp workspace before ownership verification, crawl settings, monitoring setup, and the first scan.
Siteimp is a local-first Windows application for inspecting website structure, content, performance, accessibility, links, images, and monitoring evidence.

Siteimp helps you inspect a website as a whole system, not just as a pile of disconnected pages. Run scans, review page-level evidence, inspect links and images, check accessibility and best practices, and use the results to decide what deserves attention next.
The application runs locally on Windows, so it fits naturally into development, consulting, QA, support, and content workflows where you need evidence you can review, explain, and act on.
Siteimp scans websites and turns the results into practical evidence: what was discovered, what changed, what broke, what looks healthy, and where deeper review may be worthwhile.
Crawl a website, collect page evidence, and review results at both the scan level and the page level. Siteimp helps you see patterns that are hard to notice when you only test one URL at a time.
Siteimp surfaces practical information about links, images, headings, accessibility, Lighthouse results, page structure, and scan behavior so you can make decisions from evidence instead of guessing.
Use monitoring to keep an eye on important websites and targets over time. Siteimp is built for the quiet regressions too: the things that drift, break, slow down, or change when nobody is watching.
Siteimp includes practical support material for the screens and workflows built directly into the app. These articles explain what each page is for, what you can do there, and how the pieces fit together.
The setup page for adding a site you own or control to your local Siteimp workspace before ownership verification, crawl settings, monitoring setup, and the first scan.
The website-level control center for one saved site, including scan history, ownership status, robots.txt rules, crawl settings, scan-start gating, monitoring pause behavior, interrupted scan recovery actions, and the path into scan results.
The first Siteimp scan can take longer to start because Siteimp has to wake up and coordinate the scanning machinery. Later scans may feel faster once the app, browser tooling, local database, and scan environment are already warmed up.
Siteimp resources go deeper than button-by-button help. They explain the thinking behind website integrity, content structure, monitoring, images, accessibility, and the evidence Siteimp collects.
Accessibility is a long-term practice, not a one-time checklist. These ten practical habits can help developers build websites and applications that work better for more people: learn one screen reader, use semantic HTML, support keyboard navigation, write clear headings and links, label forms properly, provide alternatives for media, and avoid treating overlays or ARIA as shortcuts.
Canada’s adoption of CAN/ASC - EN 301 549:2024 is a major accessibility shift for organizations that build information and communication technology for the Government of Canada. This article explains how the standard broadens accessibility beyond websites to include software, documents, hardware, communication systems, documentation, support services, and procurement. It also explains why automated testing alone will not be enough and why teams should treat accessibility as a practical design, development, support, and procurement responsibility.
HTTP response status codes are the small numbers that explain what happened when a browser, crawler, or monitoring tool requested a resource. This primer explains the major status code classes, including informational responses, successful requests, redirects, client errors, and server errors, and connects them to website structure, monitoring, search engines, and user experience.
The blog follows the product as it changes: release notes, design decisions, development stories, and the occasional hard-earned lesson from building a local-first website integrity application.
After a week of building and internal testing, I just deployed the very first Siteimp build to a beta user who I know from the old GT Surveillance days. Watch is currently monitoring a large cannabis operation and ensuring their systems are all up.
Siteimp Watch is a standalone local monitoring app built from the same monitoring module that powers Siteimp. This post explains the 78 solutions method behind my software work, why reusable modules matter, and why Siteimp Watch exists as a smaller, faster monitoring-focused product for local visibility, internal tools, home lab services, and endpoints your own computer can reach.
Siteimp now has a dedicated accessibility resources section with practical articles on screen reader usage, ARIA, machine-readable structure, and the work required to make websites and applications more usable. This post explains why accessibility matters to Siteimp, why better websites matter more than waiting for better assistive technology, and why more accessibility resources are on the way.

Siteimp includes local monitoring for important websites and targets. You can configure ping checks, fetch checks, or both, then review response status, response time, final URLs, errors, alerts, and recoveries from inside the application.
The same monitoring module is also being prepared as Siteimp Watch , a focused standalone Windows uptime monitor for people who only need local monitoring. It can watch public websites, private apps, staging environments, local-network targets, and other web-accessible services your computer can reach.
Siteimp is the full website integrity application. Siteimp Watch is the monitoring piece by itself. Both are local-first, both support structured support requests, and both can route alerts and recoveries through your own Slack or Discord destinations using Formimp.
Siteimp is built as a desktop application for Windows. It is meant for people who want to run scans when they need them, keep results close to their own workflow, and inspect evidence without turning every website check into another hosted service.
That makes it useful for developers, consultants, agencies, technical site owners, and anyone who needs to understand what is happening across a website before deciding what to fix. And the best part? You buy it once and only once because subscription based software sucks and we're sick of it.
Siteimp is intentionally evidence-first. It collects information about pages, links, images, headings, accessibility, performance, best practices, monitoring targets, and support context so the next step is easier to reason about.
It's not about telling you how to fix your website or what to do. Rather, the goal is to show enough useful structure that you can understand the site, prioritize changes, create tickets (or create evidence to show a generative AI the problem) and explain your decisions clearly.
Siteimp has moved from an older reporting system into a new desktop application. The beta release focuses on practical website inspection, monitoring, support, and evidence you can use without turning every check into a subscription.
If you only need local monitoring, explore Siteimp Watch . It is the same monitoring idea in a focused standalone Windows app.
Explore Siteimp Support