Google Ads guide

Free Google Ads Audit North Dakota: A State Campaign Guide

A useful North Dakota Google Ads audit must connect a search to the place, industry, operating capacity, and business outcome behind it. Energy-service demand around the Bakken, value-added agriculture, autonomous systems and aerospace, technology businesses in Fargo or Grand Forks, manufacturing, local services, and tourism can all appear in a statewide account while requiring different targeting and measurement decisions.

The North Dakota Department of Commerce economic-development overview identifies technology, autonomous systems, energy, value-added agriculture, and tourism among the state’s growth areas. Those sectors help an auditor form relevant questions. They do not prove that an advertiser has demand, serves every North Dakota county, or should raise its budget. The account’s search terms, service map, sales stages, capacity, and margin evidence remain the source of the recommendation.

North Dakota’s distances and operating conditions make the boundary especially important. A local contractor may serve a tight radius around Bismarck, Fargo, Minot, or Williston. An energy or industrial supplier may sell across the country from a North Dakota facility. A tourism business may want visitors searching from outside the state. An agriculture or UAS company may need a qualified technical or commercial audience rather than broad local traffic. The audit should make those distinctions visible.

What a North Dakota Google Ads audit should prove

Start with one decision question, such as “Are our campaigns producing qualified energy-service opportunities in western North Dakota?” or “Are our tourism ads generating profitable visitor bookings?” A state-level audit should then prove, or mark as unknown, the following:

  • Reach: whether campaigns serve the counties, towns, facilities, projects, routes, destinations, or service radius the advertiser can support;
  • Intent: whether searches are for the product or service, rather than jobs, education, grants, news, free information, repair, used equipment, or unrelated research;
  • Measurement: whether calls, forms, RFQs, demos, field visits, applications, orders, bookings, and imported sales stages are defined and traced;
  • Economics: whether spend can be compared with qualified pipeline, revenue, contribution margin, travel, freight, sales lag, cancellations, and operating capacity;
  • Experience: whether the ad and page make the location, technical fit, availability, proof, and next step clear;
  • Action: whether the evidence supports a correction, a controlled test, a request for better data, or no change.

Do not begin by assuming that a small population means a small opportunity or that a statewide campaign should be split by city. The correct unit may be an oilfield service area, a farm or elevator territory, a data-center or technology buyer, an institutional procurement market, a tourism route, a branch radius, or a nationwide industrial offer.

Define the boundary before reading performance

Write down what “North Dakota” means for the account. It may mean the entire state, a metro such as Fargo-Moorhead or Bismarck-Mandan, a local service radius, western energy counties, a college or research community, a project site, or visitors outside the state searching for a North Dakota destination. Record where the business is licensed, staffed, stocked, installed, able to travel, or able to deliver.

Separate operating contexts before interpreting a statewide rollup:

  • Fargo and Grand Forks may combine technology, higher education, healthcare, manufacturing, agriculture, retail, and professional services;
  • Bismarck may combine state government, healthcare, energy services, construction, professional services, and regional commerce;
  • Minot and the north-central region may combine military, energy, agriculture, healthcare, construction, and local services;
  • Williston and western counties may combine oil and gas, energy infrastructure, industrial supply, workforce, housing, transportation, and field services;
  • rural communities may depend on agriculture, equipment, value-added processing, healthcare, education, and long travel distances;
  • Theodore Roosevelt National Park, lakes, hunting, fishing, events, and other destinations may create visitor intent that is seasonal and geographically dispersed.

The grouping is a hypothesis, not a substitute for delivery data. A location report can include people physically in North Dakota, workers who travel there, people showing interest in its businesses or destinations, and searches from Minnesota, South Dakota, Montana, Canada, or elsewhere. Mark missing location definitions, service maps, call outcomes, CRM stages, booking data, or margin feeds as unknown or partial instead of using an incomplete denominator to make a budget recommendation.

Audit North Dakota location targeting and service reach

Google’s location-targeting documentation explains that location options use signals such as physical presence, regular presence, or interest in a place, and that those signals are best effort. Review selected locations, exclusions, location options, overlap, and the page or route after a click. Compare them with the advertiser’s counties, branch radius, project sites, field-service territory, delivery routes, facilities, campuses, destinations, and appointment capacity.

Review North Dakota reach at the level that matches the business decision:

  • statewide versus Fargo, Grand Forks, Bismarck, Minot, Williston, Dickinson, Mandan, or another named market;
  • metro, county, ZIP, radius, farm, elevator, well pad, plant, airport, campus, hospital, branch, venue, park, or project targeting versus actual operating coverage;
  • people physically in North Dakota versus people showing interest in its energy projects, companies, universities, jobs, products, events, or destinations;
  • overlapping city and statewide campaigns, shared budgets, branch routing, local inventory, field staffing, road conditions, project schedules, and seasonal availability;
  • impressions, clicks, cost, conversions, qualified outcomes, revenue, cancellations, freight, travel, and margin by region where the data supports that comparison.

Distance is part of the commercial decision. A contractor may be able to reach Bismarck or Fargo but not western oilfield sites. A manufacturer or software company may sell nationally and need North Dakota as an operating location rather than as the only audience. A tourism advertiser may want nonresidents planning a trip, while a restaurant or local service business may need people already near the location. The correct location option follows the offer and fulfilment model.

Do not apply a Fargo or Bismarck average to every county. A low-converting rural campaign can reflect sparse demand, travel, weather, long sales cycles, limited staffing, or a page mismatch. A high-volume local campaign can still produce weak results if the conversion is an unqualified form. Before changing a location or budget, confirm the date range, location definition, primary conversion, denominator, and operating outcome.

Match the audit to North Dakota business models

North Dakota Commerce describes technology, autonomous systems, energy, value-added agriculture, and tourism as targeted growth areas. Use those categories to form questions while keeping the advertiser’s actual offer in control:

  1. Energy, natural resources, and energy technology: distinguish operator, mineral, field-service, equipment, infrastructure, environmental, workforce, project, and general-information intent. A click from a consumer researching energy is not the same as a qualified industrial opportunity.
  2. Agriculture and value-added processing: separate producer, farm-equipment, input, commodity, processing, food, ethanol, logistics, cooperative, and research intent. Define territory, season, crop or livestock context, and the business stage behind an inquiry.
  3. Autonomous systems, aerospace, and advanced technology: use the state’s autonomous-systems material as context, then distinguish UAS testing, procurement, software, hardware, training, engineering, regulatory, education, and general-interest searches.
  4. Manufacturing, construction, logistics, healthcare, and professional services: align specification, supplier, facility, project, appointment, staffing, and local-service searches with RFQs, booked work, qualified opportunities, or other meaningful outcomes.
  5. Tourism, hospitality, outdoor recreation, and events: account for visitor versus resident intent, route planning, season, weather, event dates, lodging inventory, travel distance, cancellation terms, and the difference between a click and a profitable booking.

The North Dakota energy and natural-resources overview describes a broad energy portfolio, including conventional and renewable resources and related research. It is useful background for audit hypotheses, not a forecast of clicks, leads, or profitability for a particular account.

Review North Dakota conversions, search terms, and campaign economics

Correct location targeting cannot rescue an account that optimises toward the wrong event. Review conversion definitions beside the searches, devices, campaigns, and North Dakota regions that produced them. Google’s conversion-tracking guidance describes conversions as valuable actions after an ad interaction; the audit must establish what “valuable” means for this advertiser.

Prove what counts as a conversion

For each primary conversion, record its business definition, source, counting method, value rule, import path, delay, and owner. A form might be an equipment RFQ, a farm inquiry, a UAS partnership request, a job seeker, a student, a tourism question, an out-of-area service lead, a duplicate, or spam. A call might reach the wrong branch, dealership, field team, venue, clinic, or sales office. A purchase, contract, or booking can still be unprofitable after freight, travel, discounts, commissions, cancellations, weather, and fulfilment.

Trace representative events through the complete path:

  • browser form, booking, chat, application, product view, add-to-cart, ticket, or checkout event;
  • phone number, answer status, destination, caller location where available, and call outcome;
  • CRM lead, qualification, supplier tier, opportunity, RFQ, proposal, appointment, reservation, production, and won stage;
  • order, refund, cancellation, repeat-customer, booking value, contribution-margin, contract, and fulfilment record where relevant;
  • timestamps, consent, deduplication, offline imports, and the relationship between native and imported events.

For a Williston energy account, a form may need operator, basin, service, safety, equipment, location, and timing qualification. For a Fargo technology business, a demo may be a student, job seeker, researcher, or early-stage company rather than a buying committee. For a tourism campaign, a booking can have different economics by season, event, stay date, weather, cancellation rate, and capacity. Preserve those distinctions instead of flattening every event into “lead.”

If a later CRM stage is imported for optimisation, verify its source, match rate, lag, and value rule. A qualified opportunity can be more meaningful but sparser and slower than a form submission. Document the tradeoff and the evidence required before changing the account’s primary conversion.

Read North Dakota search terms by intent and region

Use the Google Ads search terms report to inspect what actually triggered ads. Group searches by product or service, buying stage, city or region, industry, resident versus visitor intent, season, weather, and business fit. A query containing “North Dakota” does not prove statewide serviceability, and a Fargo, Bismarck, Minot, or Williston query does not prove that the offer is available there.

Look for patterns such as:

  • energy, oilfield, pipeline, equipment, environmental, and industrial searches that need operator, basin, service, safety, project, or procurement qualification;
  • agriculture, farm equipment, processing, ethanol, food, and logistics searches that vary by producer, season, territory, commodity, and purchase stage;
  • UAS, autonomous, aerospace, engineering, software, university, or government searches that mix buyers with students, job seekers, researchers, and general-interest audiences;
  • Fargo, Grand Forks, Bismarck, Minot, or Dickinson searches that require different branch, appointment, campus, or service-radius handling;
  • tourism searches for parks, fishing, hunting, events, lodging, scenic routes, or attractions where visitor origin, season, weather, and inventory change the economics;
  • employment, education, grant, news, free-information, used, repair, do-it-yourself, or unrelated intent;
  • high-cost searches with recorded conversions but no qualified stage, site visit, RFQ, order, booking, contract, revenue, or margin;
  • valuable searches lost because the ad and page are too broad for the project, town, buyer, facility, season, route, or offer.

Before adding a negative keyword, inspect the complete query, match context, ad, location, page, conversion quality, weather, season, event, project schedule, and sales feedback. A term that is poor for a consumer or tourism campaign may be valuable for an energy, technical, institutional, agricultural, or supplier campaign. Record the query, scope, evidence, owner, and review result so a negative is reversible and explainable.

Compare spend with North Dakota economics and capacity

Google’s budget guidance explains how campaign budgets relate to delivery. The business conclusion depends on qualified outcomes, gross margin, freight, travel, field time, staffing, seasonality, sales lag, inventory, booking value, cancellation risk, weather, project schedules, and capacity. A Williston industrial lead, a Fargo software opportunity, a farm-equipment inquiry, and a park-area booking can have very different economics even when their reported acquisition costs look similar.

Review a budget or bidding conclusion in this order:

  1. Confirm that the conversion used for optimisation is the outcome the advertiser values.
  2. Check whether there is enough comparable evidence to compare North Dakota regions, branches, campaigns, industries, seasons, projects, or locations; label uncertainty when there is not.
  3. Compare spend with qualified outcomes, revenue or contribution margin, sales lag, cancellations, travel, freight, and operational capacity.
  4. Separate a true budget constraint from a relevance, measurement, page, location, seasonality, weather, event, project, or fulfilment problem.
  5. Record one supported decision, or no change until the missing evidence is available.

Commerce’s industry categories can explain why an audience or message deserves investigation, but they cannot serve as a demand forecast for the account. Only the advertiser’s query, lead, opportunity, RFQ, appointment, order, booking, contract, cancellation, and margin evidence can support a spend decision.

Check the landing page and the promise after the click

The landing page has to make the North Dakota offer believable to the person who clicked and usable for the business that must fulfil it. Review the path from query to ad to page to form, call, booking, application, quote request, or sales conversation. Google’s landing-page experience guidance is a technical and relevance reference, but the audit should also test the local promise: who is served, where, under what conditions, and what happens next.

Compare the search and ad with the page’s visible evidence:

  • the state, region, county, town, facility, well pad, farm territory, campus, venue, park, or service radius is explicit when it affects eligibility or fulfilment;
  • the offer is specific enough for the buyer, whether that is an energy-service request, UAS evaluation, software demo, agriculture equipment inquiry, industrial RFQ, project, booking, ticket, or local appointment;
  • the headline, proof, pricing or qualification language, availability, lead time, travel policy, and call to action agree with the ad rather than implying coverage the operator cannot provide;
  • the page explains the next step, response expectation, required information, and routing for a multi-location or field-service business;
  • forms, phone numbers, calendars, checkout, consent notices, downloads, quote tools, and other conversion paths work on the devices and browsers that matter to the account;
  • the page makes seasonal, weather, road, inventory, project, appointment, or delivery constraints clear when they affect the decision.

For a western energy page, inspect operator or project relevance, safety and technical proof, service area, equipment, response time, and contact routing. For a Fargo technology page, look for buyer fit, integration, security, company size, and a real sales next step. For a tourism page, make dates, access, lodging or ticket inventory, route planning, weather caveats, cancellation terms, and booking path clear. A page can look polished and still fail if it asks the wrong visitor to submit a form.

Separate technical defects from message problems

Record defects with evidence instead of collapsing them into a vague “landing page issue.” A broken form, dead phone route, slow or blocked page, missing conversion event, unavailable booking date, or incorrect quote path is a technical or operational finding. A broad headline, unclear North Dakota service boundary, unsupported sector promise, weak proof, or mismatch between project and page is a relevance or message finding. A lead that cannot be handled by the right branch, field team, plant, venue, or sales group is a routing or capacity finding.

For each finding, capture the query or campaign, location scope, exact ad and page, observed behaviour, likely business effect, and smallest testable correction. Do not infer a page failure from a low conversion rate alone. First check traffic quality, device, consent, event firing, call handling, season, weather, availability, and the actual destination. Conversely, do not dismiss a low-quality-lead problem as a conversion-rate problem when the form is collecting the wrong people successfully.

Prioritise findings and verify the next change

A useful North Dakota Google Ads audit ends with an ordered decision list, not a catalogue of every possible setting. Rank each finding by the damage it can cause to measurement, qualified demand, budget, or customer experience; the evidence supporting it; and the smallest safe change that would test the diagnosis. Separate a confirmed defect from a strong hypothesis and from an observation that needs more data.

FindingEvidence to preserveSmallest next action
North Dakota location or region is outside the service boundarylocation settings, report definition, delivery, branch or field mapcorrect targeting or exclusion, then check delivery and qualified outcomes
Conversion is not a qualified business outcomeevent path, CRM stage, call result, booking, order, refund, or margin recordrepair the definition or import path before changing bids
Search intent does not match the offersearch term, ad, location, page, and sales dispositionadd a targeted negative, split intent, or revise the relevant message
Region or sector needs a distinct promisequery cluster, outcome quality, page evidence, capacity, and operating boundarycreate a narrow test with matching copy, page, and routing
Spend is limited but economics are provencomparable date range, qualified value, lag, margin, and capacitytest budget or bidding change with a stated success measure
Page or tracking path is brokenreproducible browser, device, form, call, booking, or event evidencefix and re-test the path before interpreting performance

For the test, name the affected campaigns or ad groups, North Dakota locations, dates, conversion, owner, and observation window. Avoid changing location settings, budget, bidding, ads, landing page, negatives, and conversion definitions at the same time unless the current setup is actively causing harm and the combined correction is unavoidable. If several changes are necessary, record the order and the evidence that will distinguish them.

Decide what not to change

An audit can correctly conclude that no change is justified. Do not split a campaign only because North Dakota contains many towns; split when the service, intent, economics, message, routing, or measurement requires a different decision. Do not add a Fargo, Williston, or tourism page because a report contains one place query when the offer and evidence are statewide. Do not raise a budget because impressions are available if qualified outcomes, fulfilment, or margin are unknown. Do not remove a rural region because its apparent conversion rate is low before checking distance, weather, sales lag, seasonality, data completeness, and capacity.

Write “no change” with the missing proof that would change the decision. That is more useful than a speculative recommendation and gives the next review a concrete evidence request.

Common mistakes in a North Dakota Google Ads audit

Several patterns make a statewide audit look more certain than it is:

  1. Treating North Dakota as one market. Fargo, Grand Forks, Bismarck, Minot, Williston, Dickinson, rural farm communities, tribal communities, and destination markets can have different buyers, distances, sectors, seasonality, and fulfilment constraints. A statewide rollup is a reporting view, not automatically a campaign structure or economic unit.
  2. Confusing presence with serviceability. A person may be in North Dakota, travel there for work, or show interest in its businesses and destinations without being inside the advertiser’s service boundary. Searches from Minnesota, South Dakota, Montana, Canada, or another market may be valuable, but they should be identified rather than silently mixed into a North Dakota conclusion.
  3. Using a target-industry list as performance evidence. Energy, agriculture, autonomous systems, technology, manufacturing, and tourism are useful hypotheses. They do not prove demand, qualification, conversion value, or profitable capacity for a particular account.
  4. Optimising a proxy because it is plentiful. Forms, calls, page views, downloads, quote starts, or booking starts can be useful signals, but the audit must compare them with qualified leads, site visits, appointments, RFQs, orders, bookings, contracts, revenue, cancellation, and margin where those outcomes exist.
  5. Adding negatives without reading the whole query. A word can be irrelevant for a tourism or consumer campaign and valuable for an energy, technical, agricultural, institutional, or supplier campaign. Preserve the query, match context, page, location, and outcome before excluding it.
  6. Changing too many variables at once. A new campaign split, budget, bid strategy, conversion event, landing page, and negatives make a result hard to explain. Establish the issue, choose the smallest test, and keep a record of what changed.
  7. Ignoring operating conditions. A campaign can generate apparently good demand that a field team, branch, plant, venue, resort, dealership, or sales group cannot serve because of distance, weather, road conditions, project timing, inventory, or staffing. Those constraints belong in the audit conclusion.

What a free adz.so audit can and cannot do

A free adz.so Google Ads audit can help organise the account review around campaign structure, queries, locations, conversions, ads, landing pages, and the evidence needed for a next decision. It is a starting point for finding questions and possible defects; it does not replace access to the advertiser’s CRM, call outcomes, booking system, order data, contribution margin, operating map, project schedule, regulatory review, or local team knowledge.

Use the output as a working document. Confirm important findings in the Google Ads interface and the systems that own the business outcome. Mark assumptions, missing fields, and unknowns. For an agency managing several accounts, the agency audit workflow can be a useful companion to account-specific review. For a store, catalogue, or booking business, compare the same principles with the ecommerce audit guide, especially around product, checkout, shipping, returns, and margin evidence.

The honest result may be a correction, a focused experiment, a request for better measurement, or a decision to leave a stable part of the account alone. The value is in making that decision traceable to North Dakota delivery and business evidence.

Practical next steps for a North Dakota Google Ads audit

Start with one defined operating question: which North Dakota locations, buyers, or sectors should receive demand, and which business outcome proves that the spend is working? Then:

  1. Export the relevant campaigns, search terms, locations, devices, ads, landing pages, conversions, and date range.
  2. Mark the actual service boundary, branch or team ownership, licensing, travel, delivery, booking, project, and capacity constraints.
  3. Trace representative North Dakota events from click through lead, call, appointment, RFQ, site visit, order, booking, contract, or margin outcome.
  4. Separate Fargo, Grand Forks, Bismarck, Minot, western energy, rural, cross-border, and seasonal patterns only when the data and business decision justify it.
  5. Rank findings by confirmed impact and choose the smallest reversible correction or test.
  6. Assign an owner, evidence source, review date, and success measure, then record what the audit still cannot prove.

For a North Dakota advertiser, the strongest audit is specific without pretending to know more than the account can show. It connects geography to serviceability, local context to search intent, conversion events to real outcomes, and recommendations to distance, capacity, and economics. Run the free audit, verify important findings against the advertiser’s own records, and use the result to make one defensible next decision.