Your site's morning briefing.
Only what changed. Already prioritised.

Each area covers a coherent slice of what makes a page work, with fifteen plus checks inside. Search visibility covers ranking setup: heading structure, internal linking, topic coverage, meta quality. AI quote readiness covers the moves that earn answer-engine quotes: a quotable opening summary, question headings, FAQ block. Technical health covers speed, mobile, links. Content quality covers voice, freshness, depth.

Because static noise is why most audit tools quietly stop being opened. A report that shows the same hundred-page list every morning trains the team to ignore it: yesterday's broken pages are still broken, and the new things drown in the history. Within a week the team stops opening it. Site Inspector reverses this by surfacing only what is new, so every morning the report is short enough to read and act on.

Impact comes from the page's importance and the severity of the issue. Effort comes from the complexity of the fix and whether automation can handle it. A regression on a high-traffic pillar page scores higher impact than one on a low-traffic article. A missing FAQ block Ranko can generate scores lower effort than a restructure. The two combine into a single queue position, with each score visible to override.

Asana, ClickUp, Trello, and Linear are the four named trackers with direct one-click integration. The connection is configured during onboarding through the same Imports and Exports layer that handles other tracker connections. For a different tracker, Ranko supports Google Sheets export as the universal escape hatch. The ticket always carries the page link, impact and effort scores, suggested fix, and the relevant area.

Page Refresher is for sit-down rewrite projects; Site Inspector is for ongoing morning vigilance. Page Refresher is the tool the team opens to bring their library up to current standards: they pick the pages, review rewrites, and publish in waves. Site Inspector runs continuously, checking the whole site every night and surfacing what changed. It flags the pages that need attention; deeper work batches into Refresher.

Yes. The sixty plus checks are the default set, and the team can customise which run, how they are weighted, and what thresholds trigger an issue. Some teams care more about technical health than content quality and weight accordingly. Some have brand standards and add custom checks. Some switch checks off entirely. The default works well, but the hooks are there to reflect each team's priorities.