Scrutiny 12 12.12.4 Mac

Web developers and SEO analysts who need more than a surface-level scan often turn to Scrutiny 12. PeacockMedia's crawler digs through every link on a domain and reports back with the kind of detail you can act on.

SEO checks, broken images, and load times in one crawl

• Running SEO checks that inspect page titles, heading structures, meta descriptions, and keyword presence across an entire site.
• Validating images and flagging broken resources before a client notices.
• Measuring page load speed across multiple URLs in a single crawl.
• Automating post-crawl actions — the app can email a report, save it to disk, open a file, trigger an AppleScript, or FTP a fresh sitemap XML on completion.
• Viewing link data in HTML, plain text, or XML sitemap format.
• Checking spelling across page content.
• Scheduling crawls to run unattended.

English and French only on Intel and Apple Silicon

• Requires macOS 10.14 or later; runs on both Intel and Apple Silicon Macs.
• Interface languages are limited to English and French.
• The developer offers a family of related tools — Integrity Pro, Integrity Plus, and Integrity — which may overlap depending on your needs.

First moves after installing

Before crawling your own production site, point Scrutiny at a small, known-stable domain — a personal blog or a five-page test project works well. A first crawl on something low-stakes lets you gauge how the app traverses internal links without waiting through a multi-thousand-page queue. Pay attention to the crawl speed slider in the toolbar; pulling it back a notch during early runs avoids hammering a server while you learn the interface.

Open the Preferences and set a default report directory. Scrutiny can generate HTML, CSV, and XML sitemaps automatically after each crawl, and having them land in a predictable folder saves hunting later. If you plan to use scheduled runs, configure the alerts panel on day one — even a simple ping when a crawl completes prevents the tool from running silently in the background for weeks while a 404 list grows.

Auditing a client site from crawl to report

Start by entering the site's root URL and switching the mode to Spell Check & SEO if the project calls for a full content review. Let the crawl finish — the sidebar populates with sections for broken links, slow pages, missing titles, and image issues. Focus first on the Errors tab: any internal link returning a 404 or 500 is a direct fix, so export just that list as plain text and hand it to a developer or queue the work yourself.

Next, move to the SEO panel and sort by missing meta descriptions. A site with thirty pages lacking descriptions is common; Scrutiny shows the current state of each tag, so you can triage high-traffic pages first. For load-speed checks, switch the view to page weight and sort descending — the heaviest assets appear at the top, often bloated images or unminified scripts. Drag those URLs into a task list outside the app.

When the audit is complete, configure an end-of-crawl action: save an HTML report for the client, then trigger an AppleScript that copies the sitemap XML to a staging server via FTP. The whole sequence runs without manual steps once you set it in the Scheduler.

Bump the timeout to catch slow third‑party failures

Three preferences make an immediate difference. First, raise the timeout from its default if your sites rely on slow third-party APIs — a 10-second threshold catches more real failures than timeouts. Second, enable the option to check external links but limit their depth to one hop; external crawling can balloon a scan overnight if left unrestricted. Third, in the HTML-check settings, toggle on the rule that flags empty alt attributes on images — it is off by default and worth the small noise cost.

If you are running a build from a Scrutiny 12 torrent for Mac, the app's own crawl behaviour remains unchanged regardless of the source. What matters is that the monitoring log stays clean and the scheduled runs fire on time, so test a midnight schedule once with a small domain before trusting it with a production report.

• macOS 10.14 or later
• Intel or Apple Silicon Mac