Create one authoritative record for each real location
“Multi-Location SEO” describes the network service; this resource reviews the working records of real locations. Begin with the actual operating location inventory. Open, temporarily closed, moved and permanently closed branches need distinct statuses. Give each location a durable identifier that survives a name or street change. Serving customers in a city does not prove that a branch exists there. Before adding campaign target areas to the register, ask the responsible operations team for evidence of the real location and its current function.
Field authority and evidence
Identify the authoritative source for address, phone, hours, services and the way customers are received. A local manager may know daily operating changes while a central team controls branding and publication. These can be different roles. Record the source of a change, its effective time and the person accepting it. Copying information from an old webpage does not establish that it accurately describes present operations.
Conflicts and exceptions
If a central spreadsheet and local record disagree, do not arbitrarily pick a value for publication. Open an exception with an owner and required evidence. Holiday hours, appointment-only arrangements and services offered on limited days deserve explicit treatment. Missing information is not ordinary business hours. Resolve the actual operating condition before expanding an unapproved change across the network, and preserve the explanation for later reviewers.
| Field | Authoritative input | Owner role | Acceptance condition |
|---|---|---|---|
| Location identity | Operations register | Central operations | Durable ID matches a real location |
| Address and model | Current local record | Location manager | Customer-facing conditions are accurate |
| Hours and services | Operations approval | Local operations | Effective time and exception are recorded |
| Profile access | Permission inventory | Account owner | Business ownership and role are verified |
Two kinds of authority
Local operations
Confirms actual hours, services and customer access.
Central team
Controls brand, publication and change approval.
Show the distinct value of each location page
“Web Design and Development” owns page implementation; this review determines location-specific content requirements. The reason for a branch page is to help a customer choose the appropriate location. Actual directions, accessible entrances, appointment arrangements, services and preparation requirements can support that decision. Replacing only the city name in repeated copy does not provide local value. Review two representative pages together and ask whether a visitor can distinguish which task each location can genuinely fulfil.
Local facts and shared brand information
Do not reproduce the entire company service list as if every location offers everything. If a service is only available elsewhere, give the customer an accurate alternative. Verify the relationship and permission for any location photograph, team reference or project example. An image can illustrate premises without proving delivery results. The source does not claim that Prix has a staffed branch, local team or approved location-specific result in a particular city.
Page ownership and customer paths
Record the existing URL owner for each genuine location and the path from the branch directory to its details and appropriate contact or booking task. Plan to test that path as a customer would use it. If both old and new addresses exist, decide which owner should explain the current location. This source does not open a route or automatically redirect an existing page.
Audit profile eligibility separately from access ownership
“Google Business Profile Checklist” supports field-level inspection; the network review separates eligibility from permissions. A physical location does not automatically qualify for a profile in every context. Current Google Business Profile requirements must be checked for the country, activity and actual customer-facing model. Receiving visitors at a location differs from travelling to a customer. Do not represent a mailing address or promotional city label as a verified staffed customer location. Tie the eligibility check to operational evidence instead of assuming that a page or map pin proves it.
Existing records and potential duplicates
Review existing business records and their represented locations before proposing a new profile. Similar names may describe different businesses, or duplicate records may represent the same one. That distinction must be understood before any removal, merging or ownership request. Keep location ID, profile ID, business name and related URL in one review record. An unresolved relationship is incomplete, even if the records appear in search results.
Central and local permissions
List the profile owner, managers and local escalation contact separately. Permissions should match tasks; shared passwords or access-bearing values do not belong in the worksheet. A departing employee needs a documented handover owner and access review. Being able to view a profile does not establish editing rights or ownership by the business. This writing task neither signs into an account nor applies a profile change.
Accept a limited pilot before a network-wide change
“SEO Migration Services” owns migration implementation; this section plans acceptance for a pilot and location changes. Choose a small, bounded location group before rolling out a change across the network. Represent differences in operating model or page template where they matter. Write the expected information, effective time and required acceptance evidence first. A correct preview still needs separate verification of its published counterpart on the site, profile and directory. A count of attempted updates cannot certify that the whole network now presents correct information.
Change records and recovery
Each task should retain the prior value, intended value, reason and owner. Planned publication and actual acceptance times are different. If a change fails, identify which information remains valid and who must correct the exception. Repeating a bulk operation can create duplicate work, so its safety must be established before a retry. This checklist describes the review sequence; it runs no bulk edit, migration or automation.
Moves and permanent closures
A moved branch retaining its identity is different from a permanently closed branch. Decide whether the customer needs a new address, a genuine replacement location or a clear closure explanation. Consider the URL, profile, visible message and response behaviour together. Redirecting every closed page to the homepage is not a universal solution. Obtain a reasoned business decision and a specific acceptance test before changing historical information.
| State | Customer need | Planned task | Acceptance evidence |
|---|---|---|---|
| Open | Reach the right location | Current page and information | Source-consistent task path |
| Temporarily closed | Understand service availability | Explain actual conditions | Operations-approved visible message |
| Moved | Find the new address | Review identity and address transition | Reasoned URL/profile decision record |
| Permanently closed | Real alternative or explanation | Choose the closure response | Test of the relevant customer need |
Pilot acceptance
Before
State expected values, locations and ownership.
After
Inspect actual presentation and exception behaviour.
Compare branches with shared definitions and local context
“Local SEO Checklist” supports the single-business checks; network comparisons also need common definitions and local context. Use a consistent period, timezone and event definition in network reporting. A phone-link click, answered conversation, booking and delivered service are not the same output. Show evidence availability for each branch. If profile reporting cannot be accessed, a blank value does not establish lost visibility. Resolve the access gap before interpreting performance, then review the result alongside the operating conditions of the location.
Capacity and seasonal differences
Do not rank branches with one unexplained score when opening days, available services, local holidays and appointment capacity differ. A branch with fewer enquiries may still fill its available capacity; that is a possible interpretation, not an inspected client result. Record the local explanation and its evidence owner. A small sample or short period does not identify a definite SEO cause for a difference.
Qualified enquiries and private data
Define the field assigning an enquiry to a location and the process for correcting a misrouted request. Shared reporting should omit customer names, phone numbers and free-form messages. Qualified enquiries can use the business’s agreed definition, but this source does not build the CRM process that records them. Do not report a page click as acknowledged lead capture or delivered work; server and operational evidence are separate requirements.
Give central and branch teams closable tasks
“International SEO Services” keeps market and language decisions separate; this worksheet closes accountable real-location tasks. Divide the worksheet into data correction, local content, profile access and technical publication tasks. Each item needs an input, evidence, owner and acceptance condition. Not applicable requires a reason; unavailable access remains incomplete. When one template defect affects many location pages, a single technical root task may be sufficient, with the affected locations listed in the evidence rather than duplicating the same implementation request.
Priorities and review triggers
Start with concrete customer obstacles such as a wrong address, incorrect hours or a path to the wrong branch. Record impact, confidence and dependencies. A tool score alone should not order the work. Alongside a routine review, define triggers for relocation, staff handover or service changes. For each task, name the representative example to recheck and the role authorised to accept the outcome.
From source acceptance to publication
These bodies and worksheets are specifications, not evidence of a functioning lead journey or delivered download. The parent must separately inspect private previews, accessible tables, native editorial quality, account conditions and service capacity. FA public routes and normal publication gates remain held. Only genuinely verified branch records can be marked complete. City counts, proposed pages or researched topics cannot substitute for publication or delivery acceptance.
What Does This Checklist Cover?
Start with page and query inventories and technical accessibility. Prioritize findings by business impact, implementation effort and ownership. Compare new content with existing pages serving the same intent. Include post-implementation checks and Search Console monitoring; rankings or results by a fixed date are not guaranteed.
Preparation: Verify location lists
Baseline information and ownership
- Verify location lists
- Standardize location codes
- Match addresses and hours
Implementation and Test Checks
Record evidence for each check
- State services by location
- Build genuine local pages
- Assign profile owners
- Review duplicate profiles
Handover and Follow-Up Checks
Next actions and acceptance
- Add central update workflows
- Separate location leads
- Align report periods
How to Use the Findings
Mark each item complete, incomplete or not applicable. Attach a screen, URL or test result to incomplete items. Address findings that block critical user tasks first. Share the list with the team and assign ownership and a retest date.
Checklist evidence worksheet
| Check | Input | Evidence | Owner | Acceptance |
|---|---|---|---|---|
| Verify actual location inventory | Open, moved and closed locations | Operating records | Central operations | Service areas are not counted as real branches |
| Check durable location identity | Branch ID and historical mapping | Identifier dictionary | Data owner | Identity remains traceable after a name change |
| Match address and operating model | Actual address and customer-facing conditions | Local operations confirmation | Location manager | Virtual or mailing address is not assumed customer-facing |
| Verify hours and exceptions | Normal/holiday hours and effective date | Approved local calendar | Local operations | Page and profile agree with the source |
| State services actually available | Current services and exclusions | Location-specific service record | Location manager | Company-wide services are not incorrectly copied |
| Test the page’s distinct value | Directions, preparation and booking information | Comparison of two actual locations | Content and local operations | More than repeated copy with a changed city |
| Check profile conditions separately | Country, activity and operating model | Current official rule and operational evidence | Account owner | Eligibility evidenced or pending, never assumed |
| Identify profile owners and roles | Profile ID and permission inventory | Task-appropriate roles and handover record | Account owner | Business ownership and permission verified in actual account |
| Review suspected duplicates | Name, profile and location mapping | Same-versus-different business review | Local operations and account owner | No deletion or merge without investigation |
| Select a bulk-change pilot | Bounded representative location group | Before/after values and actual presentation | Central publishing owner | Pilot accepted before network expansion |
| Separate moves from closures | State, real alternative and current URL | Reasoned response and profile decision | Operations and technical team | No automatic homepage redirect |
| Align branch reporting definitions | Period, timezone and event | Shared dictionary and access state | Analytics owner | Missing access is not zero performance |
| Define qualified enquiries separately | Location code and qualification rule | Operations-approved enquiry definition | Sales or booking owner | Click is not lead acceptance or delivery |
| Close tasks with acceptance evidence | Priority, owner and repeat test | Actual source and customer-path check | Central and local acceptors | Critical gaps visible; no approval or publication claim |
Frequently asked questions
How many branches justify this checklist?
It becomes useful when maintaining shared information across more than one genuine location; no compulsory threshold is claimed.
Is every served city a branch?
No. A service area or advertising target does not prove a physical location; operational evidence is needed.
Does each location qualify for a profile?
Current country, activity and customer-facing conditions must be checked. This source did not inspect an account.
Does every branch need a page?
Consider one when it can provide genuine location-specific decision information. Repeated city copy is insufficient.
Should closed pages redirect home?
Not automatically. Customer needs, real alternatives and the closure reason determine the appropriate response.
Does this file accept lead capture or publication?
No. Actual previews, account evidence, server acknowledgement, CRM delivery and normal release checks are separate.
What does an incomplete item mean?
An incomplete item alone is not proof of a failure. Review evidence and scope before choosing a remedy.
What should I prepare for an initial discussion?
Share your current system, priority problem, sample outputs and decision-making team. These help define an initial scope without adding unnecessary work.
How are costs and timing determined?
Assess scope, existing data, integrations, review rounds and continuing work together. A binding schedule and price follow initial technical or content assessment.
Can you work with our existing team?
Define a collaboration model with internal and external responsibilities, access and acceptance criteria. The proposal states who owns each task.