Skip to main content

GHL Prospecting Audit Accuracy SOP

Purpose​

This SOP defines quality control procedures for GHL Prospecting audit reports before they are used in outreach. Audit reports are auto-generated from public data and can contain inaccuracies. Sending outreach based on incorrect findings damages credibility. This SOP ensures every report used for outreach has been verified.

Scope​

Covers:

  • Which audit sections to include or exclude per prospect
  • Section-by-section accuracy verification
  • Report refresh rules
  • Red flags that should pause outreach
  • Quality checklist before adding a prospect to the pipeline

Does Not Cover:


Section Selection Rules​

Not every audit section applies to every prospect. Including irrelevant sections (e.g., Website Performance for a business with no website) weakens your outreach.

A worked example of every section is filed in Drive. Symphony Core's own audit, run 2026-09-23, at sc-docs-storage/03-sales/enablement/2026-09-ref-symphony-core-own-marketing-audit-report.pdf — the tool's own filename was report_2026-09-23_en-US.pdf. Open it before verifying your first report: the section names in this SOP are the summary-page labels, and the section headings the report prints are different. KB-015 carries both, side by side.

SectionInclude?Condition
Business DetailsAlwaysCore identity -- always relevant
Technology StackAlwaysReveals what tools they use (or don't)
Google Business ProfileAlwaysEssential for any local business
ListingsAlwaysDirectory presence matters for all local businesses
Online ReputationAlwaysReviews are universal to local businesses
Website PerformanceConditionalOnly if the business has a real website (not just a Facebook page or Yelp listing)
SEO AnalysisConditionalOnly if the business has a real website with indexable pages
AI Search VisibilityConditionalLocal presence always applies. Crawler access, AI readability and agent readiness only if the business has a real website

Rule: If a business has no website, do not reference Website Performance, SEO Analysis or the website-based AI Search Visibility areas in your outreach. Focus on GBP, Listings, Reputation and AI local presence instead.


Section-by-Section Accuracy Guide​

1. Business Details​

ItemHow to VerifyCommon False Negatives
Business nameGoogle search the businessMay flag a DBA vs. legal name difference as an error
AddressCheck GBP listing directlySuite/unit numbers often mismatch across sources
Phone numberCall the number or check the websiteTracking numbers may differ from main line
Website URLVisit the URLMay flag a redirect (e.g., www to non-www) as missing
HoursCheck GBP or websiteSeasonal hours cause false discrepancies

Accuracy confidence: High -- this section is usually reliable.

2. Technology Stack​

ItemHow to VerifyCommon False Negatives
CMS detectionView page source or use WappalyzerCustom-built sites may show "No CMS detected"
AnalyticsCheck for GA4/GTM tags in page sourceTag Manager containers may hide analytics from detection
Chat widgetsVisit the site and wait 5-10 secondsSome widgets load on delay or only on specific pages
Scheduling toolsLook for booking links in the nav/footerEmbedded iframes may not be detected

Accuracy confidence: Medium -- detection depends on how the site is built. False negatives are common for SPAs and heavily cached sites.

3. Google Business Profile (GBP)​

ItemHow to VerifyCommon False Negatives
Profile existsSearch "[Business Name] [City]" on GoogleMulti-location businesses may have a different GBP than expected
Photo countOpen the GBP listing and check Photos tabCount may lag behind actual uploads by a few days
Recent postsCheck the Updates/Posts section on GBPPosts expire after 7 days -- a "no recent posts" flag may be accurate
AttributesCheck the "About" section on GBPSome attributes are Google-sourced, not owner-set

Accuracy confidence: High -- GBP data is pulled directly from Google's API.

4. Listings​

ItemHow to VerifyCommon False Negatives
Directory presenceSpot-check 2-3 directories (Yelp, BBB, Facebook)Some directories block automated checks
NAP consistencyCompare name/address/phone across 3+ sourcesMinor formatting differences (St vs. Street) may be flagged
Listing countCompare against industry benchmarksNew businesses legitimately have few listings

Accuracy confidence: Medium -- directory data varies by scraping access. Verify at least 2-3 listings manually.

5. Online Reputation​

ItemHow to VerifyCommon False Negatives
Review countCheck Google Maps listing directlyMay not include reviews from other platforms
Average ratingCheck Google Maps listing directlyRating may have changed since report generation
Response rateScroll through reviews to check owner repliesRecent responses may not be reflected yet
Review recencyCheck dates of last 5 reviewsSeasonal businesses may have legitimate gaps

Accuracy confidence: High for Google reviews. Medium for cross-platform aggregation.

6. Website Performance​

ItemHow to VerifyCommon False Negatives
Page speed scoreRun Google PageSpeed Insights manuallyScores fluctuate by 5-10 points between runs
Mobile responsivenessOpen site on mobile or use Chrome DevToolsSome sites use separate mobile URLs (m.example.com)
SSL certificateCheck for padlock icon in browserRecently renewed certs may show as missing briefly
Core Web VitalsCheck Google Search Console (if accessible)Lab data vs. field data can differ significantly

Accuracy confidence: Medium -- scores vary between testing tools and time of day. Use as directional, not exact.

7. SEO Analysis​

ItemHow to VerifyCommon False Negatives
Title tagsView page source, check <title>Dynamic titles (React/JS apps) may not be detected
Meta descriptionsView page source, check <meta name="description">Same dynamic rendering issue as title tags
Schema markupUse Google's Rich Results TestSchema may exist but not be detected by the audit tool
Heading structureView page source, check H1-H6 tagsVisual headings using styled <div> won't be detected

Accuracy confidence: Low-Medium -- SEO audits are the most prone to false negatives, especially for JavaScript-rendered sites. Always cross-check with a manual page source review if you plan to reference SEO findings in outreach.

8. AI Search Visibility​

The section is a readiness check. It scores whether AI assistants can find, read and act on the business. It does not ask any AI assistant anything. Scoring detail is in KB-017.

ItemHow to VerifyCommon False Negatives
Crawler access (GPTBot, ClaudeBot, PerplexityBot, Google-Extended)Open <domain>/robots.txt and look for a Disallow under those user agentsA block set at the CDN or firewall (for example Cloudflare bot rules) does not show in robots.txt, so "Allowed" can still be wrong
Phone number found / call actionOpen the home page on a phone and tap the numberA number inside an image or a JS-rendered header can be missed
Inquiry form / booking buttonCheck the home page, then the contact and booking pagesAgent readiness tests one page only. A business with a contact form or booking page elsewhere still shows "Not ready"
Structured data fieldsGoogle's Rich Results Test on the home pageSchema injected by JavaScript or on another page may not be counted
Content dependent on JavaScript (%)View page source and compare with the rendered pageNoisy on Elementor, Wix and Squarespace sites, which load most content through scripts even when crawlers read it fine
Business directories needing attentionSpot-check one listed directory before quoting the countVendor directory data; same scraping limits as Listings

Accuracy confidence: High for crawler access and the phone check (binary, and the prospect can confirm them in about twenty seconds). Medium for structured data and directories. Low for the JavaScript percentage and for agent readiness "Not ready" until other pages are checked.

Rules for outreach:

  • Prefer crawler access and the phone check as the AI finding to quote. They pass the twenty-second test in the Pre-Call Gate.
  • Check for a contact or booking page before quoting "not ready" for inquiries or booking.
  • Do not lead with the JavaScript percentage.
  • Spot-check one directory before quoting a directory count.
  • Never tell a prospect the report shows what ChatGPT, or any assistant, says about them. It does not. Say it shows whether AI assistants can find, read and act on the business.

Report Refresh Rules​

ScenarioRefresh Required?Reason
Report is less than 7 days old, first outreachNoData is fresh enough
Report is 7-14 days old, first outreachYesData may have changed
Report is older than 14 daysYesStale data risk is high
Before sending Follow-Up 1 (Day 3)NoToo soon for data to change
Before sending Follow-Up 2 (Day 7)NoStill within original report window
Before re-engagement (Day 60-90)YesSignificant time has passed
Prospect mentions they made changesYesVerify their claims before responding

Red Flags: When to Pause Before Outreach​

Stop and investigate before proceeding with outreach if any of these conditions exist:

  1. Business appears to be closed: GBP shows "Permanently Closed" or website is down
  2. Business is already an SC client: Check the CRM contact list before reaching out
  3. Business is a direct competitor: Marketing agencies, web design firms, CRM consultants
  4. Audit data is clearly wrong: NAP data doesn't match any online source
  5. Business is outside SC's service area or ICP: Non-local businesses, enterprise companies, government entities
  6. Recent negative press: Google the business name -- if there's active controversy, skip
  7. No contact information found: If you can't find a real person's name and email, the outreach won't land

Action on red flag: Do not add to the pipeline. Note the reason in the prospect record and move on.


Pre-Call Gate​

The checklist below gates every first touch, spoken or written. It applies to a call exactly as it applies to an email, and on a call it matters more: a finding quoted aloud cannot be retracted, and an inaccurate one confirms the prospect's suspicion that the call is a scam.

Two call-specific additions to the standard checks:

  1. The finding you plan to lead with must be verifiable by the prospect in about twenty seconds on their own phone. If they cannot check it while you are talking, choose a different finding.
  2. Record which finding you used in Audit Finding Used on the opportunity, so the call and the paired email tell the same story and so opener performance can be compared later.

If the audit resolved to the wrong business, do not call. Log wrong-business and flag the report for refresh. See the Prospect Phone and Call Execution SOP.

Quality Checklist​

Complete this checklist before a prospect is cleared for outreach. Passing it is what the prospecting-audit-verified tag attests to:

  • Business is confirmed to be open and operating
  • Business is not an existing SC client or active lead
  • Business fits SC's ideal client profile (local service/professional business, 1-50 employees)
  • At least 3 audit sections have been spot-checked for accuracy
  • Conditional sections (Website Performance, SEO) are excluded if no real website exists
  • At least 1 clear, verifiable finding identified for outreach personalization
  • A real contact person has been identified (name + email or LinkedIn). See Prospect Email Discovery SOP for step-by-step lookup methods.
  • Report is less than 7 days old (or has been refreshed)
  • No red flags present (see list above)

On pass: record the verification in GHL​

The checklist result must be visible to the system, not just to the person who ran it:

  1. Record on the contact: the shareable report link in audit_pdf_url (open it in a private browser window to confirm it loads without login), Audit Finding Used, and Opener Used. There is no audit-date field — the report's own generation date plus checklist item "less than 7 days old" is the freshness record
  2. Correct the contact's name fields. The prospecting agent writes the business name into First name — replace it with the verified contact person's first name (and Last name where known), or clear it. No outreach merges first_name until this is done
  3. Apply the tag prospecting-audit-verified. It also triggers C-021.Prospecting - 01.generate audit, which generates the report and writes its link. Since 2026-11-04 it sends no email: the first email is Email 1A, sent by the caller before the call (Execution SOP Step 5)
  4. When contact verification is also complete (prospecting-contact-verified, per the Call Execution SOP), apply prospecting-cadence-start — the deliberate start signal for outreach. Apply it last, after both verification tags are on: it is the one tag that starts the cadence, whether run by hand or by the C-024 workflows

A prospect failing the checklist gets no tags. Note the reason on the record and either refresh the report or discard.

Re-activation gate​

The single permitted re-activation touch reuses this checklist. Before anyone applies prospecting-reactivation-approved to a dormant prospect, refresh the audit and re-run the checklist — the "less than 7 days old" item is the freshness gate the C-024 reactivation workflow relies on; the workflow itself does not check dates. A prospect already tagged prospecting-reactivated has used its one re-activation: do not apply the approval tag again.



Document History​

VersionDateChanges
1.62026-11-12Adds the AI Search Visibility section (seen on SC's report 2026-11-11): selection rule, a verification table, confidence levels and five outreach rules, chief among them that the section never shows what an assistant says about the business
1.52026-11-04The verification tag's side effect restated: prospecting-audit-verified triggers 01.generate audit, which generates the report and no longer sends an email
1.42026-09-23Points at a filed worked example: SC's own audit, every section rendered. Notes that this SOP's section names are the report's summary-page labels and that the printed section headings differ, which is how a blog post came to be drafted from the wrong artifact
1.32026-08-27Field-model simplification (PRD v2.2): verification records audit_pdf_url, Audit Finding Used, Opener Used on the contact only (opportunity fields and Audit Date retired — checklist freshness item is the record). Added the Re-activation gate section: checklist re-run + audit refresh before prospecting-reactivation-approved; prospecting-reactivated marks the one permitted use
1.22026-08-22Quality-checklist pass now writes system state: audit fields recorded, prospecting-audit-verified applied, and prospecting-cadence-start applied last as the deliberate outreach start signal. Removed the stale "Report Ready" pipeline-stage reference (the four-stage pipeline was never built)
1.12026-08-18Added the pre-call gate: the checklist now explicitly gates spoken touches, with a verifiability test on the finding led with and a wrong-business stop
1.02026-03-02Initial version -- section selection rules, accuracy guide, refresh rules, quality checklist

Document Information

  • Version: 1.3
  • Created: 2026-03-02
  • Updated: 2026-08-27
  • Location: 04-operations/sops/ghl-prospecting-audit-accuracy-sop.md