Search Evidence Audit for startups and small businesses in Dublin

Know what is holding your site back.

A practical Search Evidence Audit for a small business that wants clear answers. See what search systems can access, what the evidence actually proves, and which fixes deserve attention first.

What does the audit check?

Public pages first, then your accounts only if you grant read-only access. Inspect the three inspection layers below.

Illustrative interface only. Statuses, telemetry and figures below are samples, not findings from a live audit.

The 3-Layer Search & AI Audit Anatomy

Every finding belongs to one of three verification layers: access, parsing, or index telemetry.

Interactive Architecture

Layer 1: Server Reachability & Crawler Accessibility

Search engines and other user agents need to fetch a page and follow its access policies. This check observes access; it does not demonstrate indexing, rankings or AI citations.

Server Response & Canonical Match 200 OK Verified
Robots.txt AI Scraper Policy Claude & GPTBot Allowed
XML Sitemap Traversal & Canonical Match Clean Index
SSL / TLS Certificate & HSTS Headers TLS check shown
Edge Server Inspection HTTP/2 Telemetry
GET /services/seo-audit HTTP/2
Host: www.clarosi.ie
User-Agent: Claude-SearchBot
> HTTP/2 200 OK
> content-type: text/html; charset=utf-8
> x-robots-tag: index, follow
> strict-transport-security: max-age=31536000

Layer 2: Raw Byte Parsing & Machine Readability

We test what lightweight search crawlers read in the raw initial HTML payload versus what client-side JavaScript injects seconds later. Essential answers, headings, and schema must be present without relying on script execution.

Raw HTML Stream vs JavaScript DOM Diff Inspected
Heading Hierarchy (H1, H2, H3 Structure) Semantic Pass
Direct Answer Targets (First 100 Words) Answer Near Top
JSON-LD Schema Graph (Organization, Service) Pre-Rendered
First-Byte Raw Stream DOM Parser Diff
Initial HTML (What crawlers read)
<h1>SEO Audit Dublin</h1>
<p>A practical audit that proves what search systems can reach...</p>
<script type="application/ld+json">
{ "@type": "Service", "name": "SEO Audit" }
</script>

Layer 3: Search Console Data & AI Crawler Access

With read-only access, Search Console can provide impressions, clicks and average position. Server logs may separately show verified AI crawler requests; a request does not show an AI citation.

GSC Indexation Status & Crawl Frequency Measured Only
Impressions vs Organic Click Through Rate Direct Telemetry
AI Crawler Requests (Perplexity, ChatGPT) Observed Access
Confidence Rating on Every Finding High Confidence
Google Search Console API Verified Signals
Inspection: URL is indexed on Google
Query: "seo audit dublin startups"
> Impressions: 1,840 (Last 28 Days)
> Average Position: 3.2 (Page 1)
AI Scraper Requests (Monthly):
> Claude-SearchBot: 32 · Perplexity: 24

If you are weighing a free check against this audit, read Free vs paid SEO audit: what does each actually show? Planning a site relaunch? Use our website redesign SEO launch system to map pages, prepare checks and track the first month. Choosing the pages to target? Start with keyword research for small business in Ireland and Google Search Console.

See the report format before you enquire.

This is an illustrative deliverable format, not a client result. Your report uses your own URLs, plain words, and clearly labelled evidence.

📄 Search Evidence Audit Report
Example business: Fictional company (Dublin) Report date: Example only Reviewed by: ClaroSi Example scope: 18 URLs
Bot Access Health 100 / 100 Zero Server Blockers
Passed Checks 8 / 12 Verified Infrastructure
Action Items 3 Notices Remediation Ready
Critical Blocks 1 Header Staging Leak Detected
Executive Takeaway

Illustrative example only: the fictional site has sample response-time, rendering and indexing findings. A real audit records observations for the client's own URLs and account data; this panel is not evidence about a live business or client.

Check Target Evidence Type Status Finding & Recommendation
Server 200 OK & SSL Response Observed Pass Clean HTTP/2 200 response; HSTS headers active; valid TLS 1.3 certificate.
AI Crawler Access Policy Observed Pass robots.txt explicitly allows Claude-SearchBot, PerplexityBot, and OAI-SearchBot.
Raw HTML Pre-rendering (SSR) Observed Action Needed Answers on /guides/faq are injected after 1.8s by React; invisible to first-byte bot crawlers.
Canonical URL Consistency Observed Action Needed Trailing slash inconsistency on /services creates duplicate canonical signals.
Structured Schema JSON-LD Observed Action Needed Missing ProfessionalService and FAQPage markup on core conversion paths.
Commercial B2B Directory Indexation Measured Critical Block X-Robots-Tag: noindex detected on /solutions/b2b from legacy staging deployment.
Organic Search Clicks (28 Days) Measured 1,840 Clicks Illustrative values only: +38% clicks and 3.2 average position. Replace with verified account data in a real report.
01
Remove 'X-Robots-Tag: noindex' header on /solutions/b2b

Example priority: Critical. Removing a noindex directive lets Google consider the page for indexing; it does not guarantee indexing or rankings.

✓ Written Sign-off Approved
02
Pre-render Core FAQ Answers in Initial HTML Stream

Example priority: High. Makes answer text available in the initial HTML for parsing; indexing and AI citations remain separate outcomes.

Ready for Staging
03
Consolidate Canonical 301 Redirect on /pricing

Impact: Medium. Resolves URL ambiguity and concentrates page equity on a single canonical address.

Ready for Staging
04
Deploy Validated ProfessionalService & FAQ Schema JSON-LD

Impact: Medium. Enables rich snippet eligibility in Google search and authoritative entity grounding in AI search engines.

Awaiting Client Review

Clear answers before any work begins.

What we can check, what needs permission, and what the report can prove.

How is each finding labelled?

Observed, measured, inferred or unavailable. A crawler visit shows access; it does not show that an AI answer cited your page. Each finding names its source and date.

What access do you need?

A public review starts with your URL. Search Console and analytics require access you approve. We ask for named read-only access, never your password.

Can you audit a site before launch?

Yes, if there is a test version we can open. We can review its pages before publication. Rankings and traffic can only be measured when suitable live evidence exists.

Keep the evidence moving each month.

After a Search Evidence Audit, you can add a monthly comparison. It uses an agreed baseline and sources to show what changed, what remains uncertain and what may be worth doing next.

Set the comparison

Agree the reporting period, questions and data sources first. The audit can establish the baseline, or we can agree another suitable starting point in writing.

Read the evidence

Compare Search Console or analytics data where you approve read-only access, alongside public page and crawl checks in scope. Each finding is dated and labelled observed, measured, inferred or unavailable.

Choose what happens next

Get a short list of changes, open questions and recommended actions. The review does not make website changes; implementation is scoped and approved separately.

01 · Compare

Period and baseline

Show the reporting dates beside the previous agreed comparison.

02 · Source

Evidence and labels

Name each source and mark findings observed, measured, inferred or unavailable.

03 · Impact

Pages and questions

Point to the affected pages or search questions where the evidence allows.

04 · Decide

Next actions

Separate useful actions from open questions; you choose what to approve.

Before recurring work begins: the written scope sets the sources, review date, delivery window and fee. This is a scheduled review, not continuous monitoring or alerts; unavailable data is labelled, never guessed.

Ask about a monthly review

What happens after the audit?

You decide. If you want fixes made, the Technical SEO Improvements applies approved improvements and rechecks them. To compare agreed evidence each month, see the optional ongoing review. Or see the related services below.

Ready to see what search and AI can see?

Send your website address and what you want to know. Each price is quoted in writing before you commit.

Book the audit

What happens after you book the audit?

Four clear stages from agreed scope to decision. The delivery window is set before work begins; implementation and monthly comparisons need a separate written scope.

  1. 01 · Scope

    Agree what to check

    Share your URL and the pages or questions that matter. We confirm the sources and any read-only access you choose to provide.

  2. 02 · Evidence

    Review the agreed sources

    We check public pages and the approved data in scope. Missing access or evidence is marked unavailable rather than guessed.

  3. 03 · Report

    Get a dated audit

    See what search can reach, what is missing, and which opportunities or fixes the evidence supports.

  4. 04 · Decide

    Choose whether to act

    The audit ends with recommendations. Technical SEO, Local SEO, research-led drafts and monthly comparisons are separately scoped; nothing changes without your approval.

Tell us what you want to find out.

Pick a service, share your website address, and tell us what you want checked. You will receive a proposed scope and price before any work begins.

Ask ClaroSi about a free 2-week trial. We start with a short meeting to check we are a good fit. You are only charged if you want to keep working together after the two weeks.