Skip to content
Back to work

CloakScan

Two views of the same site

A security product that compares visitor and crawler views to investigate hidden content and redirects.

Founder and developer

CloakScan’s public website with its URL scan entry point and visitor versus crawler comparison
CloakScan’s public website and scan entry point.

The problem

A website can look normal to a visitor while serving different content to a search engine. Reviewing only the visible homepage can leave hidden spam and suspicious redirects unexplored.

What I built

I built CloakScan to compare what visitors and search engine crawlers receive. Site owners and agencies can start with a URL, review the differences and return to findings as they monitor their sites.

  • Visitor and crawler comparisons without a plugin or hosting access.
  • A workspace for reviewing site findings and scan history.
  • Scheduled monitoring, alerts and PDF reporting on paid plans.

The outcome

The product is live. Its published, anonymised WordPress case study documents an incident where visitors saw the normal homepage while Googlebot received spam content. The comparison made both versions visible for investigation.

Read the published WordPress incident

What matters

A useful security interface needs to show the evidence behind a finding, so the person responsible for a site can decide what to investigate next.

Have a similar challenge?

Tell me about the people, the process and the problem you want to solve.

Tell me about your project