IntelGrab by Antrim Studios

A website review, in plain language

This fictional extract shows how we explain a finding and its next step. It is not a client report, a live crawl or evidence of business results.

Illustrative sample. An actual report includes the site address, check date, pages reached, crawl limits and any manual checks that could not be completed. These examples are invented to demonstrate the format.

Example 1 · Crawler observation, manually confirmed

An old service link reaches a missing page

Evidence: The example homepage links to /old-service, which returns HTTP 404.
Why it matters: A visitor following that particular link cannot reach the service information.
Recommended action: Update the link to the current service page, then check the destination and any other links to the old address.
How to recheck: Revisit the link and confirm that the intended page opens.

Example 2 · Manual enquiry-journey check

A form error is difficult to find on a phone

Evidence: In this fictional manual check, an incomplete form shows its error above the visible area without moving focus.
Why it matters: A visitor may not understand why the form has not submitted. The report does not establish how many enquiries are affected.
Recommended action: Connect field errors to their controls and move focus to the first invalid field.
How to recheck: Try the incomplete form with a keyboard and on a narrow screen.

Example 3 · Crawler observation, manually confirmed

Two service pages share the same title

Evidence: The example /repairs and /maintenance pages both use the title ‘Services’.
Why it matters: The title does little to distinguish the two pages. This alone does not prove a ranking problem.
Recommended action: Give each page a concise title that describes its actual service.
How to recheck: Recheck the page titles in the HTML and browser.

The work after the report

Your review includes indicative repair estimates. We check the platform, access and overlapping tasks before giving a firm quote. Any repairs need separate approval; you can also work with your own developer.

A Health Review includes a walkthrough and one recheck within 30 days of report delivery. Changes and untested areas are recorded; an absence of crawler warnings is not proof that a site has no problems.

Request a Health Review See scope and pricing