Kestrel SOC 2 readiness (demo)

Target URL

https://kestrelcompliance.example/soc-2-readiness

Target query

“soc 2 readiness consultant” user-provided

Audit timestamp

2026-09-18 10:00 UTC

Search discovery

Found at position 3 in checked results

Fetch extraction

Content extracted

Browser verification

Verified in a rendered page

Actionable findings

7

Most important issue

Page carries a noindex robots directive

Recommended first action

Remove noindex from the meta tag or X-Robots-Tag header if the page should be discoverable.

These results describe sampled retrieval evidence from 1 search request(s) and 1 fetch request(s) at one point in time. They are not guaranteed universal AI rankings.

Observed rows report something a tool returned. Inferred rows are conclusions drawn from absence and may need confirmation. “Not checked” means no evidence was collected, never that it passed.

1. F-001 Page carries a noindex robots directiveSeverity: HighConfidence: ●●● high confidence

   Deterministic checkConfirmed by evidenceindexing

   What the evidence shows

   robots meta contains "noindex, follow".

   Evidence excerpt

   robots meta contains "noindex, follow".from ev_fetch_1

   Why it may matter

   A noindex directive asks search engines to leave the page out of their results.

   Recommended fix

   Remove noindex from the meta tag or X-Robots-Tag header if the page should be discoverable.

   Suggested replacement copy or code

   <meta name="robots" content="index, follow">

   Expected outcome (no guarantee)

   The page becomes eligible for indexing once recrawled. Ranking is not guaranteed.

   How to verify

   Fetch the page again and read the robots metadata.

   Evidence: ev_fetch_1ev_browser_1 · Section: Technical checks

2. F-002 robots.txt contains Disallow rules for AI crawlers (GPTBot, ClaudeBot)Severity: MediumConfidence: ●●● high confidence

   Deterministic checkObservedaccess

   What the evidence shows

   robots.txt has user-agent-specific groups that disallow this path for the crawlers listed. Other crawlers may be unaffected.

   No verbatim excerpt is attached to this finding.

   Why it may matter

   If you want these assistants to be able to retrieve the page, these rules work against that. If it is deliberate, no action is needed.

   Recommended fix

   Confirm the rules are intentional; remove them for the crawlers you want to allow.

   Expected outcome (no guarantee)

   Named crawlers that honour robots.txt would be permitted to fetch the page.

   How to verify

   Re-fetch /robots.txt.

   Evidence: ev_robots_1 · Section: Technical checks

3. F-003 Structured data failed to parseSeverity: MediumConfidence: ●●● high confidence

   Deterministic checkObservedstructured-data

   What the evidence shows

   1 block(s): no @type · 1 failed to parse

   Evidence excerpt

   1 block(s): no @type · 1 failed to parsefrom ev_browser_1

   Why it may matter

   Invalid JSON-LD is ignored by consumers that read it.

   Recommended fix

   Fix the JSON syntax and validate with a structured-data testing tool.

   Expected outcome (no guarantee)

   Structured data becomes machine-readable.

   How to verify

   Re-run with browser verification.

   Evidence: ev_browser_1 · Section: Technical checks

4. F-004 Canonical URL points to a different addressSeverity: MediumConfidence: ●●○ medium confidence

   Deterministic checkObservedindexing

   What the evidence shows

   Canonical points to https://staging.kestrelcompliance.example/soc-2-readiness, which differs from the fetched URL.

   Evidence excerpt

   Canonical points to https://staging.kestrelcompliance.example/soc-2-readiness, which differs from the fetched URL.from ev_fetch_1

   Why it may matter

   Search engines may consolidate this page into the canonical target.

   Recommended fix

   Confirm the canonical is intentional; otherwise point it at this URL.

   Expected outcome (no guarantee)

   Consistent consolidation signals.

   How to verify

   Re-run the audit.

   Evidence: ev_fetch_1 · Section: Technical checks

5. F-005 The service is described in the FAQ, not in the headline or opening copySeverity: MediumConfidence: ●●○ medium confidence

   AI-interpretedObservedmessaging

   What the evidence shows

   The H1 reads 'Compliance, simplified' and the first paragraph is company history. The words readiness assessment and the 8 to 12 week timeline appear only under the FAQ.

   Evidence excerpt

   Most clients are audit-ready in 8 to 12 weeksfrom ev_fetch_1

   Why it may matter

   The search snippet for this page was assembled from the generic opening. Competing results lead with the concrete offer and its timeline.

   Recommended fix

   Lead with what you deliver, for whom, and how long it takes; move the company history lower.

   Suggested replacement copy or code

   <h1>SOC 2 readiness consulting for growing SaaS companies</h1>
   <p>A fixed-scope readiness assessment, a prioritised gap list and an 8–12 week path to audit-ready.</p>

   Expected outcome (no guarantee)

   The offer is stated where extractors and snippet generators look first. Rankings are not guaranteed.

   How to verify

   Re-run the audit and compare the extracted H1 and first paragraph with the search snippet.

   Evidence: ev_fetch_1ev_search_1 · Section: Visibility gap analysis

6. F-006 URL is not listed in the sitemapSeverity: LowConfidence: ●●○ medium confidence

   Deterministic checkObserveddiscovery

   What the evidence shows

   Sitemap found (31 URLs) but this URL is not listed.

   Evidence excerpt

   Sitemap found (31 URLs) but this URL is not listed.from ev_sitemap_1

   Why it may matter

   Sitemaps help crawlers find pages that are weakly linked.

   Recommended fix

   Add the URL to the sitemap.

   Expected outcome (no guarantee)

   Crawlers have an explicit path to the page.

   How to verify

   Re-fetch the sitemap.

   Evidence: ev_sitemap_1 · Section: Technical checks

7. F-007 Competing results emphasise terms this page never statesSeverity: LowConfidence: ●○○ low confidence

   Deterministic checkPotential issuecompetitor-comparison

   What the evidence shows

   At least two competing results mention: auditor (2), fixed (2). None appear in the extracted page.

   No verbatim excerpt is attached to this finding.

   Why it may matter

   These may be expectations searchers associate with the query. They are hypotheses from a small sample, not requirements.

   Recommended fix

   Review whether any of these terms describe your offering truthfully and add them where relevant.

   Expected outcome (no guarantee)

   Better coverage of the vocabulary used for this query.

   How to verify

   Check against the competing pages in the Search evidence.

   Evidence: ev_search_1ev_fetch_1 · Section: Visibility gap analysis

Every finding and check cites these records. Records store normalized, sanitized data only: no keys, headers or credentials.

{
  "request": {
    "query": "soc 2 readiness consultant",
    "location": "US",
    "language": "en"
  },
  "metadata": {
    "demo": true
  }
}

{
  "query": "soc 2 readiness consultant",
  "page": 0,
  "totalResults": 5,
  "results": [
    {
      "position": 1,
      "title": "SOC 2 readiness consulting | Auditline",
      "url": "https://auditline.example/soc-2-readiness",
      "snippet": "SOC 2 readiness consultants for startups. Gap assessment, policies and evidence collection in 8 weeks.",
      "siteName": "auditline.example"
    },
    {
      "position": 2,
      "title": "SOC 2 readiness assessment services — Vantage Assure",
      "url": "https://vantageassure.example/soc-2",
      "snippet": "Our SOC 2 readiness assessment finds control gaps before your auditor does. Fixed-fee consultants.",
      "siteName": "vantageassure.example"
    },
    {
      "position": 3,
      "title": "SOC 2 Readiness | Kestrel Compliance",
      "url": "https://kestrelcompliance.example/soc-2-readiness",
      "snippet": "Kestrel guides growing companies through SOC 2. Our team has 15 years of experience in security and compliance.",
      "siteName": "kestrelcompliance.example"
    },
    {
      "position": 4,
      "title": "How to choose a SOC 2 consultant",
      "url": "https://secburo.example/blog/choose-soc-2-consultant",
      "snippet": "Questions to ask a SOC 2 readiness consultant: audit firm relationships, fixed fees, timelines.",
      "siteName": "secburo.example"
    },
    {
      "position": 5,
      "title": "SOC 2 readiness consultants for SaaS",
      "url": "https://trustbridge.example/soc-2",
      "snippet": "TrustBridge SOC 2 readiness consultants: gap assessment, policy templates and auditor introductions.",
      "siteName": "trustbridge.example"
    }
  ],
  "match": {
    "position": 3,
    "method": "exact",
    "url": "https://kestrelcompliance.example/soc-2-readiness"
  }
}

{
  "request": {
    "urls": [
      "https://kestrelcompliance.example/soc-2-readiness"
    ],
    "format": "markdown",
    "links": true,
    "page_metadata": true,
    "ttl": 0
  },
  "metadata": {
    "demo": true
  }
}

{
  "requestedUrl": "https://kestrelcompliance.example/soc-2-readiness",
  "finalUrl": "https://kestrelcompliance.example/soc-2-readiness",
  "title": "SOC 2 Readiness | Kestrel Compliance",
  "description": "Kestrel guides growing companies through SOC 2 with practical, plain-English advice from experienced security professionals.",
  "language": "en",
  "author": null,
  "publishedDate": null,
  "textLength": 1342,
  "textTruncated": false,
  "pageMetadata": {
    "canonical": "https://staging.kestrelcompliance.example/soc-2-readiness",
    "robots": "noindex, follow",
    "og": {
      "title": "Kestrel"
    }
  },
  "links": [
    "https://kestrelcompliance.example/",
    "https://kestrelcompliance.example/contact",
    "https://kestrelcompliance.example/about",
    "https://www.linkedin.com/company/kestrel-example"
  ],
  "latencyMs": 640,
  "text": "# Compliance, simplified\n\nKestrel Compliance was founded in 2011 by two security engineers who were tired of audit season. Today our team has 15 years of combined experience helping growing companies earn trust.\n\n## Why Kestrel\n\nWe believe compliance should be practical. We work with your team, not around it, and we explain every control in plain English.\n\n## How we work\n\nWe start with a conversation, then agree a plan that fits your calendar and your budget.\n\n## Frequently asked questions\n\n### Do you offer a SOC 2 readiness assessment?\n\nYes. Our SOC 2 readiness assessment compares your controls with the Trust Services Criteria and ranks the gaps by effort.\n\n### How long does SOC 2 take?\n\nMo… [642 more characters]"
}

{
  "request": {
    "url": "https://kestrelcompliance.example/soc-2-readiness",
    "objective": "Verification requested: compare the rendered page with the Fetch extraction."
  },
  "metadata": {
    "demo": true
  }
}

{
  "requestedUrl": "https://kestrelcompliance.example/soc-2-readiness",
  "finalUrl": "https://kestrelcompliance.example/soc-2-readiness",
  "title": "SOC 2 Readiness | Kestrel Compliance",
  "headings": [
    {
      "level": 1,
      "text": "Compliance, simplified"
    },
    {
      "level": 2,
      "text": "Why Kestrel"
    },
    {
      "level": 2,
      "text": "How we work"
    }
  ],
  "visibleTextLength": 2900,
  "visibleTextSample": "Compliance, simplified. Kestrel Compliance was founded in 2011 by two security engineers.",
  "jsonLd": [
    {
      "valid": false,
      "types": [],
      "sample": "{\"@context\":\"https://schema.org\",\"@type\":\"Service\",\"name\":\"SOC 2 readiness\","
    }
  ],
  "canonical": null,
  "robotsMeta": "noindex, follow",
  "linkCount": 40,
  "missingFromFetch": [],
  "objective": "Verification requested: compare the rendered page with the Fetch extraction."
}

{
  "request": {
    "url": "https://kestrelcompliance.example/robots.txt"
  },
  "metadata": {
    "demo": true
  }
}

{
  "url": "https://kestrelcompliance.example/robots.txt",
  "status": 200,
  "bodySample": "",
  "genericDisallowsPath": false,
  "aiBotDisallows": [
    "GPTBot",
    "ClaudeBot"
  ],
  "sitemaps": [
    "https://kestrelcompliance.example/sitemap.xml"
  ]
}

{
  "request": {
    "url": "https://kestrelcompliance.example/sitemap.xml"
  },
  "metadata": {
    "demo": true
  }
}

{
  "url": "https://kestrelcompliance.example/sitemap.xml",
  "status": 200,
  "isIndex": false,
  "listsTarget": false,
  "urlCount": 31
}

• Search is one request to TinyFish Search per query (one page of results). Position means order in that response, not a Google, Bing or universal AI ranking. A page missing from the sample is “Not found in checked results”, which does not mean “not indexed”.
• Fetch returns extracted Markdown plus metadata and links. HTTP status, response headers, JSON-LD and exact markup are not returned, so Sniffsite never infers them from text. TinyFish may serve a cached copy even when a live fetch is requested.
• Browser runs only with a concrete verification objective or when you enable it. It is one session from TinyFish’s network and may differ from what other visitors see.
• robots.txt and sitemap are read directly by Sniffsite from the public site. Directives are declared preferences; compliance depends on each crawler.
• Deterministic checks are computed only from observed data. AI-interpreted findings are produced by a language model from the collected evidence, validated against a schema, and any excerpt that is not verbatim in the cited evidence is discarded.
• Broken links are not tested. A successful Fetch does not prove a page is indexable or readable by every AI tool.
• Semantic analysis: used. API calls made: search 1, fetch 1, browser 1, Gemini 1.