Clear numbers, working handoffs

Google Analytics, Search Console, and connections that match your office

We set up Analytics and Search Console so you can see who visits, which pages pull weight, and when Google cannot read a URL. We also connect your site to CRMs, booking tools, and other services through custom APIs when email alone is not enough.

Request a measurement review
Start the quick brief

Priority reply

What measurement is missing?

1 / 4

Clear numbers and working handoffs — not vanity dashboards.

What is missing from your setup?
What do you need to track?
You
Anything else we should know?

You should know who visits your site, which pages bring calls and forms, and when Google cannot crawl a page you care about. We connect Google Analytics, Search Console, and the other accounts your business already uses so the numbers match what your office actually counts. We also wire custom connections when your site needs to talk to a CRM, booking tool, maps, or payment service.

What we set up

Google changes menus and rules, but the business questions stay the same. Are people finding us? Are forms and phone links working? Did a redesign break old URLs? We install and document the tools that answer those questions, and we connect your site to outside services when a form or checkout needs more than a plain email.

What we do not promise

We do not guarantee rankings, lead counts, or perfect attribution when browsers block cookies. We do not promise Google will never move a button or retire a view you liked. We do promise honest setup, written notes on what we configured, and custom dashboards with proprietary reporting tied to calls and forms your team recognizes.

We can help with

Measurement, search health, and connections that stay working.

  • Google Analytics (GA4): property, data stream, and events for calls, forms, and purchases you define.
  • Search Console: ownership verification, sitemap submission, and reading crawl and index reports.
  • Tag setup: direct site tags or a tag manager when that fits how your site is maintained.
  • Custom connections: APIs and integrations to CRMs, calendars, maps, payments, and dispatch tools.
  • Workspace basics: company email DNS, groups, aliases, and admin recovery planning.
  • Handoff docs: which account owns what, where to re-check quarterly, and who has admin access.

We will not

Stated plainly so expectations stay realistic.

  • Guarantee rankings or lead volume: analytics shows trends; it does not control Google or your market.
  • Hide bad months: flat traffic gets explained, not buried in jargon.
  • Leave orphan accounts: we flag duplicate properties and lost admin access before you need them.
  • Skip consent rules: tags respect the cookie choices you publish on the site.
  • Wire mystery scripts: every tag and connection should have a named owner and a business reason.

Problems we see often

Tracking that never matched dispatch. Search Console nobody verified. A CRM connection that stopped sending leads months ago. Open a card for the problem, what we do, and what to expect.

Analytics that does not match the office

The dashboard says 200 leads. Dispatch counted 40.

The problem: Form submits fire twice. Thank-you pages count as leads. Bot traffic inflates numbers. Cookie banners block tags on some visits but not others, so month-to-month reports quietly drift.

What we do: We name events the way your team talks: tap-to-call, form start, form submit, booked job. We test on phones and desktops. We align counting rules with what dispatch and sales actually use.

What to expect: Cleaner trends you can discuss in a weekly meeting. Not a magic multiplier on revenue.

Search Console never verified

The site went live. Nobody claimed it in Google.

The problem: Crawl errors pile up. Old URLs still show in search. The sitemap lists pages that no longer exist. You find out when a customer mentions a broken link, not when Google flags it.

What we do: We verify ownership, submit an accurate sitemap, and review coverage reports after launches or plugin changes. We tie console findings to fixes on the site, not just screenshots in a PDF.

What to expect: Earlier warning when index problems appear. Rankings still depend on competition and content; console shows whether Google can read your pages.

Broken custom connections

Forms, maps, or checkout stopped talking to the tools you pay for.

The problem: A plugin update rotated an API key. A booking widget points at a retired calendar. Payment callbacks fail silently. Leads duplicate into two CRMs because nobody documented which form goes where.

What we do: We map each connection: what sends data, what receives it, which keys and webhooks are in play. We scope keys to least privilege, add logging where it helps, and test after changes.

What to expect: Fewer silent failures. Clear notes so the next vendor or your staff knows what was wired and why.

Lost Google admin access

The old agency email owns Analytics. Workspace recovery is a dead phone.

The problem: You cannot add a user, rotate a key, or export history. A former vendor still holds owner rights. Two Analytics properties exist and nobody knows which one is live.

What we do: We inventory accounts, consolidate where it makes sense, and move ownership to addresses your business controls. We document recovery paths for Workspace admin.

What to expect: Access you can hand to your team. Some history may not transfer if accounts were misconfigured for years; we say that upfront.

Google Analytics: setup and how to read it

Analytics answers who came, what they looked at, and whether they took an action you care about. It does not replace your dispatch log or your books. It helps you spot trends and catch breaks early.

What we configure

  • Property and stream: one clear GA4 property tied to your live domain, not a leftover test account.
  • Events: phone taps, form starts, form submits, and other actions named the way your office talks.
  • Conversions: mark the events that count as a lead on your dashboard, with rules you approve.
  • Filters and views: exclude internal traffic and obvious bot noise where it helps.
  • Consent: tags fire in step with the cookie choices shown on your site.
  • Ads and campaigns: link Google Ads when you run paid search so spend reviews use the same events.

Numbers worth watching

  • Sessions: visits in the date range. One person can open several sessions across days or devices.
  • Users: distinct people, estimated. Useful for reach, not for payroll.
  • Page views: how many pages loaded. High views with low leads can mean navigation confusion.
  • Source and medium: where traffic came from (Google search, paid ad, direct, referral). Direct often hides untagged links; we reduce that where we can with UTM parameters.
  • Conversions: counted events you defined. Compare to dispatch, not to revenue alone.
  • Landing pages: first page seen in a session. Shows which service or city pages pull weight.

Season, weather, and competitor ads move these numbers. A dip in March might be normal for your trade. A sudden zero on form submits is a break worth fixing today. We help you tell the difference.

Search Console: setup and how to read it

Search Console is Google's side of the conversation: which pages it tried to crawl, what queries showed your site, and what errors block indexing. It complements analytics; it does not replace a site audit or honest content work.

What we configure

  • Verification: prove you control the domain via DNS or a file, then keep access under your accounts.
  • Sitemap: submit a current list of live URLs, updated when pages are added or removed.
  • URL inspection: check whether a specific page is indexed and why not.
  • Links to fixes: pair console errors with redirects, noindex, or content updates on the site.

Console views worth watching

  • Performance: queries, clicks, impressions, and average position. Position is a range, not a promise of traffic.
  • Pages: which URLs earn clicks. Spot thin pages or old URLs still getting attention.
  • Indexing: how many pages Google stored versus how many you submitted. Drops after a redesign need a redirect check.
  • Experience: mobile usability and core speed signals. Fix what hurts real visitors on phones.
  • Manual actions and security: rare but urgent. We flag these immediately if they appear.

Console shows search demand and crawl health. It does not show every phone call from maps. Pair it with analytics and what your office logs. Deeper search work lives on our organic SEO page.

Custom API connections for your website

Many sites need more than a contact form email. Your site may need to send a lead to a CRM, book a slot on a calendar, charge a card, show a map, or pull live inventory. Those handoffs use APIs: structured requests between your site and another service.

Google services on the page

Maps embeds, reCAPTCHA, Places lookups, and OAuth sign-in each need keys, domains allowlisted, and billing where Google requires it. We register keys under accounts you own, restrict them to your live domains, and document what each key does.

Lead and dispatch handoffs

Form plugins, custom code, or middleware can POST leads to HubSpot, ServiceTitan, Jobber, a shared inbox, or a webhook your IT team runs. We test duplicate suppression, field mapping, and failure alerts so a silent API error does not mean lost jobs.

Payments and bookings

Stripe, Square, and booking platforms need callback URLs, webhook secrets, and HTTPS that matches production. Checkout on a different domain than your main site complicates analytics; we plan for that instead of pretending one tag covers everything.

What good wiring includes

Named owners, scoped keys, timeouts, logging, and a test after every plugin or theme update that touches the connection. We write it down so you are not hostage to one person's memory.

Custom dashboards on what matters

A chart only helps if everyone agrees what the lines mean. We custom-make dashboards with proprietary reporting on the metrics your office actually uses: calls, forms, service lines, and search visibility. We set default date ranges, name events plainly, and walk through a sample review so your team knows what to watch. The sample below is illustrative, not your live data.

Top campaigns
Landing pages
> > > > > >
Illustrative rows only. IPs, cities, and referrers are made up for layout preview.
Source IP address City / region Country Page Device On site Referrer
Google 73.842.18.204 Tampa, FL United States /emergency-hvac iPhone · Safari 2m 14s google.com / organic
Facebook 104.28.64.118 Orlando, FL United States /emergency-service Android · Chrome 0m 48s facebook.com / paid
Google 68.132.44.91 Round Rock, TX United States /cities/round-rock Desktop · Chrome 4m 02s google.com / local pack
LinkedIn 142.112.203.57 Toronto, ON Canada /commercial-hvac Desktop · Edge 1m 36s linkedin.com / social
Instagram 185.220.101.42 Miami, FL United States /reviews iPhone · Instagram in-app 0m 22s instagram.com / story
Direct 92.118.39.16 London, England United Kingdom /financing iPad · Safari 3m 11s (direct)

How a typical setup runs

We start with access and goals, not a pile of tags. You tell us what a lead means in your office. We map what you already own, wire tools to that definition, test on real phones, and leave notes your team can use long after handoff.

Order shifts when analytics is on fire, a CRM stopped sending leads, or Search Console was never verified. Most setups still follow the same spine so surprises surface before you trust the numbers in a meeting.

1. Inventory

Map what already exists before we touch a tag or connection.

What we gather: Existing Google accounts (Analytics, Search Console, Ads, Tag Manager, Workspace), plugins and forms on the site, CRMs and booking tools, who holds owner and admin rights today, and any scripts nobody can explain.

What we do: Flag duplicate Analytics properties, orphan accounts, and billing tied to a former vendor. Consolidate where it makes sense and note what needs a password reset before configuration starts.

What you get: A written map of what your business controls and what still lives under an old agency login.

2. Goals

Define what counts as a lead the way dispatch and sales actually count it.

What we gather: Which actions matter (tap-to-call, form start, form submit, booked job, purchase), how your office logs them, and seasonal quirks such as emergency calls versus quote requests.

What we do: Name events in plain language your team already uses. Mark conversions with rules you approve. Note where analytics will never match dispatch one-for-one (cookie consent, multi-device visits, checkout on another domain).

What you get: Agreement on what the green lines on the dashboard mean before anyone presents numbers to ownership.

3. Configure

Wire Analytics, Search Console, tags, and connections on staging when your host allows it.

What we configure: GA4 property and data stream, Search Console verification, site tags or Tag Manager containers, UTM conventions for campaigns, Google Ads links when paid search is live, and API or integration handoffs to CRMs, calendars, and dispatch tools.

What we do: Restrict keys to live domains, align consent mode with your cookie banner, and avoid duplicate firing on thank-you pages or double form plugins.

What you get: A configured setup ready for real traffic, not a live experiment pasted into production without a test plan.

4. Verify

Test the paths customers use on phones and desktops, then fix what breaks on live URLs.

What we test: Tap-to-call and form events on iPhone and Android browsers, booking and purchase flows end to end, sitemap submission, crawl and index status after recent launches or plugin changes.

What we fix: Search Console errors tied to live pages, double-counted events, connections that stop sending leads without an alert, and consent gaps that block tags without an obvious warning in the dashboard.

What you get: Evidence that measurement matches reality before you budget or staff around the numbers.

5. Document and train

Short guide on monthly review views and who to call when numbers look wrong.

What we deliver: Plain-language handoff notes: which dashboard views to open each month, account access map, quarterly re-check list, and known limits (cookie blocking, cross-domain checkout, modeled data gaps).

What we do: Walk through a sample review with your office manager or marketing lead when scope includes training. Set default date ranges and name widgets the same way dispatch talks.

What you get: Your team can spot trends and catch breaks without calling us for every blip, and your next vendor inherits a map instead of guesswork.

What to send before kickoff

Speeds inventory and access recovery when accounts are messy.

  • Domains and brands: every site or subdomain that should report together.
  • Google logins you control: or a note that the old agency still owns them.
  • Forms and phone paths: which pages and plugins send leads today.
  • CRM or dispatch tool: name, login contact, and whether duplicates are a known problem.
  • What a lead means: one sentence from dispatch or sales, not a spreadsheet of hypotheticals.
  • Recent changes: redesign, new ads, plugin updates, or checkout moves in the last 90 days.

A net-new site with nothing configured usually runs inventory through handoff in one scoped engagement. Access recovery or emergency tracking fixes may reorder steps. We say that upfront so timeline and quote match reality.

What you get

  • GA4 property and events aligned to how your office counts leads.
  • Search Console verified with a current sitemap submitted.
  • Tags that respect your published consent choices.
  • Documented API and integration map with keys under your accounts.
  • Workspace DNS and admin recovery notes when email is in scope.
  • A plain-language guide to your custom dashboard: which widgets to check and what moves them.

Honest limits

Google updates interfaces and retention rules. Cookie laws and browser privacy features reduce how much you can attribute to a single ad click. Modeled data fills gaps; it is directional, not courtroom proof. We document what we configured and where to re-check quarterly. We do not guarantee uninterrupted history across every Google UI change.

Stuff that can change without warning:

  • Google retires a report or changes default attribution windows.
  • Consent choices block tags on part of your traffic, so totals shift month to month.
  • A third-party API changes pricing, fields, or auth and breaks a connection until someone updates it.
  • Checkout or booking on another domain splits measurement unless you planned for it.
  • Rankings and lead volume still depend on market, season, and competition. Better numbers help you decide; they do not guarantee growth.

Related services

Organic SEO Content and crawl fixes Search Console surfaces. Google Ads Paid traffic that shares the same conversion events. Website design and build Pages and forms measurement builds on. Website maintenance Keep tags and connections after plugin updates. Website troubleshooting When forms, tracking, or APIs break without warning.

Tell Archi FX which Google accounts you already have, what a lead means in your office, and any CRM or booking tools the site should connect to.

Ready to talk through your project?

We read every inquiry personally. Tell us what you need and we will respond with a clear recommendation.

Start a conversation View all services