After launching a contractor website, measure whether the site remains available, appears for relevant searches, helps the right visitors understand the service, delivers genuine enquiries into the operating system, and contributes to qualified opportunities and completed work. Do not reduce that chain to traffic, rankings, button clicks, or raw form submissions.

A useful scorecard connects six layers:

  1. website and tracking health;
  2. search and local visibility;
  3. visitor journeys;
  4. successful contact delivery;
  5. lead quality and business handling; and
  6. booked or completed outcomes.

Each layer needs a precise definition, a source of truth, an owner, a reporting delay, and a decision it can support. A click is not a delivered lead. A delivered lead is not necessarily qualified. A qualified lead is not a booked estimate. A booked estimate is not completed revenue. When a report uses “conversion” for all of them, it cannot show where the system is working or failing.

This guide owns the post-launch measurement model. The contractor quote-form checklist owns form and CRM implementation, while the ongoing website maintenance guide owns keeping measurement and delivery systems operational.

Define the business decision before the metric

Begin with the decisions the contractor needs to make. Examples include:

  • Is the website technically healthy enough to serve and measure customers?
  • Are the right services and markets becoming discoverable?
  • Which pages assist genuine enquiries?
  • Are calls, forms, chats, and bookings reaching an accountable owner?
  • Which enquiry sources produce work the company can actually perform?
  • Where do qualified opportunities stall?
  • Which content, service, or follow-up process should be improved next?

Only then choose measurements.

“Increase website traffic” is not a complete decision. More visits from irrelevant locations, job seekers, suppliers, bots, or services the contractor does not offer can increase traffic without helping the business. “Improve lead quality” is also incomplete until the business defines qualification consistently.

A practical measurement statement looks like this:

Determine whether organic visitors reaching the roof-repair service page produce successfully delivered enquiries that match the approved service area and job criteria, then identify whether losses occur before submission, during delivery, or during business follow-up.

That statement names the source, page purpose, delivery requirement, qualification rule, and diagnostic use. It does not promise a lead count or ranking.

Separate launch acceptance from marketing performance

Launch acceptance asks whether the released system works. Marketing performance asks what happens as people and search systems encounter it over time.

Launch acceptance

  • Canonical pages return the intended status and content.
  • Navigation and primary actions work on supported devices.
  • Forms validate, submit, confirm, and reach the correct CRM record.
  • Phone, chat, and booking destinations are configured correctly.
  • Agreed analytics events fire once with approved parameters.
  • Search Console, analytics, Business Profile, and CRM access are owned.
  • Privacy and consent configuration matches the approved plan.
  • No test data, staging host, draft copy, or private value is public.

Ongoing performance

  • Relevant pages gain or lose impressions and clicks.
  • Search queries align or fail to align with offered services.
  • Visitors move through key journeys.
  • Contact attempts succeed or fail.
  • Enquiries become qualified, disqualified, booked, won, or lost.
  • Response handling improves or degrades.
  • Website experience and technical health change over time.

Do not call a website unsuccessful because a new page has little search data immediately after launch. Do not call it successful because test submissions passed. Both views are necessary, and they operate on different clocks.

Build a measurement contract

For every metric, record:

| Field | Required definition | | --- | --- | | Business question | The decision the metric informs | | Event or state | Exact occurrence being counted | | Inclusion rule | What qualifies | | Exclusion rule | Tests, spam, duplicates, internal activity, or invalid records | | Grain | Event, session, user, enquiry, contact, opportunity, job, page, or query | | Source of truth | System that owns the accepted count | | Supporting source | System used for diagnosis or attribution | | Identity key | Safe identifier used for reconciliation | | Time basis | Event time, receipt time, qualification time, booking time, or close time | | Reporting delay | Expected time before data is complete enough to review | | Owner | Person responsible for correctness and interpretation | | Decision threshold | Condition that triggers investigation or action |

This contract prevents two common errors: comparing different grains as if they were equal, and treating one platform as authoritative for a state it cannot observe.

For example, Google Analytics can observe a browser event for a form interaction. The application can confirm that the server accepted a submission. The CRM can confirm receipt and ownership. Only the business can confirm whether the opportunity fits its service, area, urgency, and capacity. Those counts should relate, but they need not be identical.

Use one post-launch funnel

The following Nexxen measurement map is an original operating framework, not a report of unverified customer results.

| Funnel stage | Definition | Preferred evidence | | --- | --- | --- | | Search impression | A page or property appeared under the platform’s reporting rules | Search Console or Business Profile | | Search or profile click | A person clicked through under the source platform’s rules | Search Console or Business Profile | | Landing-page view | The destination page loaded and the approved analytics condition was met | Web analytics | | Meaningful service interaction | A defined action showed engagement with the decision path | Web analytics with a narrow event definition | | Contact attempt | A visitor initiated a call, form, chat, or booking action | Website or channel event | | Accepted submission or connection | The website or provider accepted the action | Server, telephony, form, chat, or booking system | | CRM receipt | One usable record reached the correct account and workflow | CRM | | Working lead | A representative began the approved handling process | CRM | | Qualified lead | The record met documented business criteria | CRM or operating system | | Booked opportunity | An estimate, consultation, or site visit was scheduled and remained valid | Calendar or CRM | | Converted opportunity | The business recorded the approved completed outcome | CRM, job, or accounting system |

Use stable names and avoid skipping stages. If “lead” means a button click in analytics but a qualified opportunity in the CRM, every rate built from those figures will be misleading.

Google Analytics currently recommends lead-generation events including generate_lead, qualify_lead, disqualify_lead, working_lead, close_convert_lead, and close_unconvert_lead. A contractor does not need to adopt those names blindly. It does need comparable, documented states and must send only data the platform and privacy plan permit.

Assign a source of truth to each layer

No single dashboard sees the whole contractor journey.

Search Console

Use Search Console for Google Search impressions, clicks, click-through rate, average position, queries, pages, countries, devices, and search appearances under Google’s definitions.

Search Console explains that Performance data can be aggregated by property or by page, and those views count impressions, clicks, and position differently. It also assigns most performance data to canonical URLs. Record the view, filters, search type, and date comparison used before interpreting a change.

Search Console is not the source of truth for:

  • all website visits;
  • calls placed after a visitor memorizes the number;
  • form delivery;
  • CRM receipt;
  • lead quality;
  • booked work; or
  • revenue.

Web analytics

Use web analytics for defined on-site interactions: landing pages, navigation, content engagement, call-link taps, form starts, form success states, booking starts, and other approved events.

Google Analytics describes events as measurements of interactions or occurrences and provides Realtime and DebugView for implementation checks. An event proves that the configured collection condition fired; it does not prove the downstream business outcome.

Website and integration logs

Use controlled application evidence for server acceptance, validation failure, webhook delivery, retries, provider responses, and integration errors. Logs should use safe record identifiers and should not become a second uncontrolled store of enquiry content.

CRM

Use the CRM for the accepted customer record, owner, deduplication, contact status, qualification, disqualification reason, appointment, opportunity stage, and follow-up history.

Telephony and booking systems

Use the provider for accepted calls, call outcomes available under the approved configuration, booking creation, cancellation, rescheduling, and provider failures. A call-link tap and a connected call are different measurements.

Job or accounting system

Use the authorized operating or financial system for completed work and accepted value measures. Do not manufacture revenue attribution when the website, CRM, and job systems are not reconciled.

Establish a baseline and annotation record

Measure change against a known state. Before launch or as soon as ownership is available, preserve:

  • canonical page and query performance from Search Console;
  • index and crawl issues;
  • website analytics configuration and existing events;
  • form, phone, chat, calendar, and CRM paths;
  • Business Profile performance exports where available;
  • current qualified-lead definitions and CRM stages;
  • known seasonality, capacity, service-area, pricing, or operational changes;
  • active campaigns and tracking destinations; and
  • current field performance data where sufficient.

Annotate the launch date, domain or URL changes, tracking changes, major content releases, form changes, profile changes, outages, campaign launches, and business interruptions. A time series without an operating log invites false explanations.

If there is no reliable pre-launch baseline, say so. Start a clean post-launch baseline after validation rather than presenting old, incompatible data as a precise comparison.

Monitor website and measurement health

Health measurements answer whether the system can be trusted before anyone interprets marketing results.

Monitor or review:

  • production availability and important route statuses;
  • forms, calls, chats, bookings, and fallbacks;
  • CRM and notification receipt;
  • analytics tag and consent-state operation;
  • unexpected event loss or duplication;
  • canonical, sitemap, robots, and index-state drift;
  • application and integration errors;
  • Core Web Vitals and material performance regressions; and
  • test records and internal traffic exclusions.

A sudden drop to zero may be a tracking failure, form failure, outage, canonical change, consent change, or real demand change. Check system health before rewriting content or increasing spend.

Maintain synthetic tests separately from customer reporting. Mark test records clearly so they can be excluded without deleting evidence that the workflow was verified.

Measure search visibility by intent and page

Search visibility should be evaluated against the contractor’s actual services and markets.

Review:

  • impressions and clicks for approved commercial and supporting pages;
  • queries that describe offered services and customer decisions;
  • branded and non-branded patterns where reporting supports them;
  • pages shown for the same query;
  • country and device differences relevant to the business;
  • indexing and canonical state;
  • rich-result or search-appearance changes where applicable; and
  • changes around annotated releases.

Average position is contextual, not a complete score. Search Console recommends focusing on trends in impressions and clicks rather than position alone. Position is an average of the topmost result under the report’s aggregation rules; it is not a promise that every searcher saw the same placement.

Do not combine unrelated queries into one victory metric. An increase in impressions can indicate expanding relevance, but it can also reflect queries outside the service area or work the contractor does not perform. Review the query and destination together.

For every priority page, keep a page-purpose record:

| Page | Intended search decision | Qualified next step | Business owner | | --- | --- | --- | --- | | Service page | Confirm fit for a specific offered service | Call or request an estimate | Service owner | | Market page | Confirm genuine coverage and local relevance | Request service in that operating area | Operations owner | | Project page | Understand applicable proof and constraints | Explore the related service | Evidence owner | | Resource | Resolve a material buyer question | Continue to the relevant service | Editorial owner |

This protects the report from rewarding traffic that the page was never meant to attract.

Measure website journeys without inventing engagement

Page views and time metrics can support diagnosis, but they should not become automatic evidence of buying intent.

Define meaningful interactions around the page’s job:

  • viewing the service qualification section;
  • opening a clearly labelled pricing or process explanation;
  • selecting a phone, quote, booking, or chat path;
  • starting a form;
  • reaching a server-confirmed success state;
  • using an accessible fallback; or
  • continuing from a resource to its commercial owner.

Avoid firing a “lead” event because a visitor scrolled, remained on the page, or clicked a generic button. Those can be engagement signals, not accepted enquiries.

For each event, document:

  • exact trigger;
  • pages or components;
  • parameters;
  • consent requirement;
  • duplicate prevention;
  • test method;
  • downstream expectation; and
  • owner.

Measure abandonment only where the implementation can distinguish it responsibly. A form start without success can mean confusion, validation difficulty, a technical failure, a visitor choosing to call, or normal reconsideration. Use the pattern as a diagnostic prompt rather than claiming one cause.

Prove contact delivery before counting leads

A customer-facing success message is not sufficient proof that a contractor received the enquiry.

For a form, distinguish:

  1. form displayed;
  2. form started;
  3. submission attempted;
  4. server accepted;
  5. provider or integration accepted;
  6. CRM record created or updated;
  7. correct owner assigned;
  8. contractor notification delivered where observable; and
  9. customer confirmation presented or sent.

The contractor quote-form checklist explains the detailed acceptance and recovery workflow.

For calls, distinguish:

  • phone link selected;
  • dialler opened;
  • provider received the call;
  • call connected;
  • call answered, missed, abandoned, or sent to voicemail where the provider can establish it;
  • caller matched to one CRM record where lawful and configured; and
  • business outcome recorded.

Do not describe a tap-to-call event as a phone lead. Do not describe a provider-accepted text or form webhook as customer delivery without the corresponding evidence.

For bookings, distinguish calendar view, slot selection, submission, confirmed appointment, reschedule, cancellation, no-show, and completed appointment. The contractor booking-calendar checklist owns those implementation details.

Define qualified leads from business facts

Lead quality cannot be inferred reliably from traffic source or a form field alone. The contractor needs documented criteria.

Possible criteria include:

  • the requested service is genuinely offered;
  • the location is within the real operating area;
  • the job type and scope fit the business;
  • the timing is serviceable;
  • the requester is a plausible decision-maker or authorized contact;
  • the enquiry contains enough information for the next step; and
  • it is not spam, a duplicate, a job application, a supplier pitch, or another excluded class.

Do not silently change the definition to improve the qualification rate. Version the criteria and annotate the effective date.

Use controlled disqualification reasons, such as:

  • outside service area;
  • unsupported service;
  • scope too small or too large under the current business rules;
  • schedule unavailable;
  • duplicate;
  • spam or solicitation;
  • employment enquiry; or
  • insufficient information after the approved follow-up.

These reasons reveal whether the website is attracting the wrong demand, failing to explain scope, or simply encountering a capacity constraint.

Sensitive customer details belong in the authorized operating system, not in analytics event labels, page URLs, or dashboards.

Measure response handling separately

The website can deliver a qualified enquiry that the business fails to handle. Keep website performance and operational response connected but distinct.

Useful handling states include:

  • received;
  • assigned;
  • first response attempted;
  • two-way contact established;
  • qualification completed;
  • estimate or consultation offered;
  • booked;
  • follow-up due;
  • won;
  • lost; and
  • closed for an approved reason.

Choose time measures carefully:

  • enquiry event time;
  • CRM receipt time;
  • assignment time;
  • first human action;
  • first successful contact;
  • booking time; and
  • final decision time.

“Response time” is ambiguous unless the start and end are named. Automated confirmation is not the same as a human response, and an attempted call is not the same as a completed conversation.

Report missing states rather than forcing them into a positive outcome. An unworked record is not disqualified. It is an operational gap.

Connect Business Profile activity carefully

For an eligible, verified Google Business Profile, the performance report can include views, searches, calls, website clicks, directions, messages, bookings, and other interactions depending on the profile.

Google defines calls as clicks on the call button, not verified completed calls. Website clicks are clicks on the profile’s website link, not sessions, leads, or jobs. Direction requests do not prove a visit or completed service.

Use the profile report to understand discovery and action patterns, then reconcile website clicks, tracked calls, messages, or bookings with their destination systems where possible.

The Google Business Profile and website consistency checklist owns profile eligibility, business identity, service-area, contact, and content alignment.

Do not add inconsistent campaign URLs, phone numbers, or categories solely to make attribution easier. Customer and business accuracy come first.

Track content as a contribution, not a last-click claim

A resource can help a prospective customer understand a decision without being the final landing page before an enquiry. Measure content in layers:

  • search impressions and relevant queries;
  • organic entrances;
  • internal movement to a related service;
  • assisted journeys where the consented analytics configuration supports them;
  • calls, forms, or bookings initiated from the resource;
  • sales-team feedback about recurring questions; and
  • content corrections, updates, or consolidation decisions.

Do not claim that a blog post generated revenue merely because it appeared somewhere in a visitor path. Attribution models are representations built from observable touchpoints; they cannot recover every offline conversation, device change, privacy choice, dark social share, or delayed decision.

Use the evidence to decide whether to maintain, expand, merge, reposition, or retire the page. Do not publish another keyword variant simply because one article has low traffic.

Include customer experience and performance

A slow or unstable website can affect the visitor journey even when tracking still fires.

Review current Core Web Vitals:

  • Largest Contentful Paint for loading;
  • Interaction to Next Paint for responsiveness; and
  • Cumulative Layout Shift for visual stability.

Use field data for real-user trends when enough data exists and lab tests for controlled diagnosis. Record page type, device, date, and release context. A site-wide aggregate can hide a slow quote form or service template.

Also monitor accessibility and usability evidence from real support issues, form errors, keyboard checks, mobile journeys, and third-party components. Do not turn a scanner score into a claim of conformance.

The Core Web Vitals contractor guide owns metric thresholds, field-versus-lab interpretation, and remediation priorities.

Protect privacy in the measurement design

Collecting more data does not automatically improve decisions.

Google Analytics policies prohibit sending data that Google could recognize as personally identifiable information, including email addresses and personal phone numbers. Google warns that PII can leak through page URLs, titles, form fields, campaign parameters, custom dimensions, and event values.

Use analytics-safe values such as:

  • page or content identifier;
  • service category from an approved fixed list;
  • generic interaction type;
  • form identifier;
  • component location;
  • success or failure class; and
  • non-sensitive campaign identifiers.

Do not send:

  • names;
  • email addresses;
  • phone numbers;
  • street addresses;
  • free-text enquiry details;
  • uploaded filenames containing personal information;
  • fine-grained customer locations;
  • CRM notes; or
  • secrets and tokens.

The Office of the Privacy Commissioner of Canada’s PIPEDA principles include accountability, identifying purposes, consent, limiting collection, limiting use and retention, accuracy, safeguards, openness, access, and recourse. Its meaningful-consent guidance emphasizes explaining key elements in understandable ways.

Privacy obligations vary by organization, province, sector, technology, and use. Identify the applicable requirements and approved reviewer rather than treating this guide as legal advice.

Record:

  • purpose for each tool and event;
  • data collected;
  • lawful and consent basis determined by the organization;
  • recipients and integrations;
  • retention settings;
  • access owners;
  • deletion and correction paths;
  • cross-system identifiers;
  • advertising features;
  • test process; and
  • change approval.

Do not use consent configuration as a cosmetic banner task. Verify actual collection under each approved state.

Reconcile systems instead of forcing totals to match

Different systems count different events, use different time zones, process data on different schedules, apply privacy thresholds, filter invalid activity, and observe different parts of the journey. Exact equality is not the objective.

Build a reconciliation table:

| Comparison | Expected relationship | Investigate when | | --- | --- | --- | | Form success events vs server acceptances | Similar after exclusions | Events fire without acceptance or acceptance lacks events | | Server acceptances vs CRM receipts | One usable CRM result per accepted enquiry, subject to documented deduplication | Missing, delayed, or duplicate records | | Call-link taps vs provider calls | Provider calls are a subset or different observable set | Large unexplained drift after configuration changes | | CRM leads vs qualified leads | Qualification is a documented subset | Unknown states or shifting criteria dominate | | Booked appointments vs qualified leads | Relationship depends on workflow | Bookings exist without valid records or records never update | | Search clicks vs analytics organic sessions | Directionally related, not identical | Structural break around a release, consent, domain, or tag change |

Choose a shared reporting time zone and state whether counts use event date or current record state. A lead created last month but qualified this month belongs to different cohorts depending on the question.

Preserve both cohort views:

  • what happened to leads created in a period; and
  • which stage changes occurred during a period.

Mixing them creates apparent rate changes that are only timing differences.

Use a reporting cadence matched to the data

Daily or alert-driven

  • site and critical journey failure;
  • sudden form, call, booking, or CRM delivery loss;
  • major tracking break;
  • security or spam anomaly;
  • widespread status, canonical, or index-control regression.

Weekly after launch

  • technical and delivery checks;
  • priority-page indexing and query emergence;
  • enquiry receipt and unresolved records;
  • lead-stage completeness;
  • annotated release effects; and
  • obvious irrelevant demand.

Monthly

  • search impressions, clicks, queries, and landing pages;
  • profile discovery and actions;
  • website journey events;
  • accepted enquiries by channel;
  • qualified and disqualified lead reasons;
  • bookings and outcomes by created cohort;
  • response handling;
  • content contributions;
  • field performance where available; and
  • recommended actions with owners.

Quarterly

  • service and market priorities;
  • qualification definitions;
  • attribution limitations;
  • privacy and access review;
  • event and CRM taxonomy;
  • content ownership;
  • platform and vendor changes; and
  • whether each metric still supports a real decision.

Avoid reacting to every daily fluctuation. Contractor demand can vary with weather, season, capacity, emergencies, advertising, and local conditions. Compare meaningful periods and annotate known changes without inventing causation.

Build a contractor website scorecard

Keep the executive scorecard small enough to use.

| Layer | Core question | Example measures | Owner | | --- | --- | --- | --- | | Health | Can customers and measurement systems complete the journey? | Availability, journey tests, delivery failures, event anomalies | Website and integration owner | | Search | Are relevant services becoming discoverable? | Relevant impressions, clicks, landing pages, index state | SEO owner | | Experience | Can visitors understand and act? | Service-path interactions, form starts, accessible failures, Web Vitals | Website owner | | Delivery | Do contact attempts become accountable records? | Accepted submissions, connected calls, CRM receipt, duplicates | Integration owner | | Quality | Are enquiries appropriate for the business? | Qualified rate, reasoned exclusions, unknown status | Sales or operations owner | | Handling | Does the business act on suitable opportunities? | Assignment, contact, booking, unresolved records | Operations owner | | Outcome | What approved business result followed? | Booked, won, lost, completed outcome under defined rules | Business owner |

Every reporting line should include:

  • current value;
  • comparison period;
  • definition version;
  • data completeness note;
  • relevant annotation;
  • interpretation;
  • decision;
  • owner; and
  • due date.

A dashboard without actions is a monitoring display. A useful scorecard creates accountable decisions.

Run a measurement acceptance checklist

  • [ ] Website health and marketing performance are reported separately.
  • [ ] Every metric has a business question, definition, grain, owner, and source of truth.
  • [ ] Search Console views, filters, date ranges, and aggregation are recorded.
  • [ ] Page, call, form, chat, and booking events use distinct names.
  • [ ] A browser event is not treated as downstream delivery evidence.
  • [ ] Server acceptances reconcile to CRM records.
  • [ ] Qualification and disqualification criteria are documented and versioned.
  • [ ] Response timing names its exact start and end.
  • [ ] Booked and completed outcomes come from authorized operating systems.
  • [ ] Test, spam, duplicate, internal, and unknown records have explicit handling.
  • [ ] Analytics receives no names, emails, phone numbers, addresses, free text, or other prohibited data.
  • [ ] Consent, retention, access, correction, and deletion processes have approved owners.
  • [ ] Business Profile actions are interpreted according to Google’s definitions.
  • [ ] Field and lab performance data are not mixed without context.
  • [ ] System comparisons account for delay, time zone, counting, privacy, and identity differences.
  • [ ] Launches, content changes, campaigns, outages, and business changes are annotated.
  • [ ] Each report ends with a decision, owner, and review date.

Use measurement to improve the system

The goal is not to produce the largest dashboard. It is to locate the next defensible improvement.

If relevant impressions rise but clicks do not, review query and result fit. If visits arrive but meaningful actions do not, inspect the page’s decision path, mobile experience, proof, and next step. If submissions succeed but CRM receipts fall, investigate delivery. If suitable leads arrive but remain unworked, fix operational ownership. If many leads are disqualified for the same service or area, correct the site’s promise or the business rule.

No measurement setup can guarantee rankings, leads, bookings, or revenue. It can make the website’s contribution, failures, and limitations more observable.

For Canadian contractors connecting search visibility, Business Profile activity, website journeys, lead handling, and qualified outcomes, Nexxen’s contractor SEO service is the commercial owner for this resource.