--- title: "Chicago license numbers, account numbers, and site records" description: "Distinguish Chicago license IDs, public license numbers, owner accounts, and site records before counting locations or planning agency website research" canonical: "https://scalewithsearch.com/articles/chicago-license-number-account-site-location-counts" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Chicago license numbers and site records: count business locations before planning agency research Choose what you want to count before counting Chicago business-license rows. A transaction record, a continuing license, an owner account, and a licensed location answer different questions. An agency planning location-page research needs to preserve those distinctions. Start with a manual worksheet. Keep the city's identifiers in separate columns, group repeated history cautiously, and record unresolved matches. Count verified research units only after deciding what evidence establishes a location for your task. The [agency website overview](/for/marketing-agencies-and-freelancers) describes the broader work. The [agency intelligence guide](/intelligence/marketing-agencies-and-freelancers) introduces launch research. This guide explains why a list of licensing rows cannot serve directly as a list of distinct storefronts or website clients. ## Four identifiers describe four different relationships The Chicago field dictionary distinguishes `LICENSE ID`, `LICENSE NUMBER`, `ACCOUNT NUMBER`, and `SITE NUMBER`. Read their descriptions before choosing a grouping rule. Their names are similar enough to invite mistakes, but the publisher gives them different purposes. [Chicago Business Licenses metadata and dictionary, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). | Field | Publisher's described purpose | Suggested research use | | --- | --- | --- | | LICENSE ID | Internal database identifier for each record | Preserve a reference to a transaction row | | LICENSE NUMBER | Public license reference that persists through its lifetime | Group the history of one license | | ACCOUNT NUMBER | Owner account shared across that owner's licenses | Preserve an owner-level relationship | | SITE NUMBER | Internal identifier for the licensed business location | Investigate the location within its account context | The research uses in the last column are recommendations. They do not establish that every possible match is resolved by one field. Keep the original row references so another researcher can inspect the evidence behind your grouped view. The dataset also has a field labeled `ID`, described as a calculated record identifier. Keep it separate from `LICENSE ID`. A generic spreadsheet heading such as “business ID” hides which field you preserved. [Chicago ID and LICENSE ID descriptions, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). Use the full source labels in your worksheet. If a colleague asks which identifier supports a proposed location, the answer should name the field and its role. ## LICENSE ID preserves the record you examined The publisher describes `LICENSE ID` at the record level. Its definition explains that one license can have several records through renewals and other transactions. Counting distinct internal license IDs therefore answers a record question, not necessarily a location question. [Chicago LICENSE ID definition, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). Keep this identifier when saving a research observation. It helps a reviewer return to the row behind a conclusion. Do not discard it after grouping records, because grouping can hide changes that later explain a disagreement. Suppose two records concern the same public license number. They may describe different events in its history. Preserve both records, their application types, and their date labels. A deduplicated summary should point to the underlying history rather than erase it. For event interpretation, use the companion [Chicago application-event guide](/articles/chicago-business-license-application-event-codes). Identity grouping answers which records belong together. Application type answers what transaction each record describes. Resolve these as separate steps. ## LICENSE NUMBER follows the continuing license Chicago describes `LICENSE NUMBER` as the public reference generally used by other sources. The dictionary says a license retains one number throughout its lifetime. Use that definition when assembling a license history. [Chicago LICENSE NUMBER definition, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). Do not interpret distinct license numbers as distinct websites or purchasing decisions. A location research task must still establish how each license relates to the operating location and current public business. The number identifies the license; the agency's service unit needs separate verification. Keep license descriptions beside the numbers. A reviewer should see why several licenses appear in a proposed location group. If their relationship is unclear, preserve separate candidates until someone checks them. When matching a second public source, record which identifier that source uses. Similar-looking numbers are not enough. Your worksheet should distinguish a source using the public license number from one presenting another internal reference. ## ACCOUNT NUMBER connects the owner's licenses The dictionary describes `ACCOUNT NUMBER` as the business owner's account reference, consistent across that owner's licenses. That relationship can help organize research across several license histories. It does not establish the number of operating locations or the scope of an agency engagement. [Chicago ACCOUNT NUMBER definition, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). For this task, retain the account relationship without collecting proprietor names or contact details. You are determining how public licensing records relate. You do not need an owner-contact enrichment exercise to prepare a location-count worksheet. Avoid turning an owner group into a presumed single client. Ask whether the work concerns one website, a shared website with location pages, or separate public brands. Establish that through verified business information and the responsible person's brief. The reverse mistake also matters. Do not split every license under one account into a separate proposed website sale. Keep the owner relationship available for review while leaving the commercial relationship unassigned. ## SITE NUMBER belongs beside the account context Chicago describes `SITE NUMBER` as an internal identifier indicating the licensed business location, accommodating owners with multiple locations. Preserve it beside the account number. The dictionary does not establish in this description that a bare site number is globally unique. [Chicago SITE NUMBER definition, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). For a manual worksheet, use an account-and-site pair as a candidate grouping reference. Label it as a research convention. Check the associated license history and public location evidence before calling the group a verified operating location. Do not turn that convention into an untested permanent identity rule. A conflicting account, site, or location statement should stop the merge. Preserve both candidate groups and name the evidence needed to resolve them. A site reference also does not establish a public opening date, current visitor access, or a need for a separate page. Those are operating and editorial questions. Ask them after you establish the likely location match. ## A fictional owner with two sites and several licenses The following worksheet is synthetic. Account Cedar, Site North, Site South, and the license labels are invented symbols. They are not Chicago identifier formats. No actual owner, address, license number, or business is represented. | Source row | Account label | Site label | Public license label | Event in the exercise | | --- | --- | --- | --- | --- | | Row A | Cedar | North | Lantern | ISSUE | | Row B | Cedar | North | Lantern | RENEW | | Row C | Cedar | North | Lantern | RENEW | | Row D | Cedar | North | Compass | ISSUE | | Row E | Cedar | South | Beacon | ISSUE | | Row F | Cedar | South | Beacon | RENEW | This fictional table contains six transaction rows, three continuing license labels, one account label, and two account-and-site candidate groups. Each count answers a different question. None establishes the number of available website projects. For a location-page review, begin with the two candidate groups. Retain the license histories underneath each group. Then verify whether the business currently presents both locations and how its website organizes them. If the verified website has one page per location, the researcher can review those two pages against approved facts. If the site describes a different structure, record the discrepancy and ask for clarification. Do not choose the website structure from the license count. Now add a seventh fictional row whose site label is missing. Keep it in an unresolved group. A shared account may suggest a relationship, but it does not tell you which location the missing value belongs to. The worksheet should still show six resolved historical rows and one unresolved row. Do not force the seventh row into North merely because that group appears first. A visible exception preserves the accuracy of the location count. ## A shared address is a clue to investigate Do not use a shared street address as your only merge rule. Check the license references, account relationship, site references, and current public business information. An address match alone does not establish which entity or website your agency would serve. Treat address normalization as a comparison aid. Preserve the original text beside any standardized version. Removing unit details or other distinctions can hide information relevant to a match. Avoid publishing actual address examples in the research handoff. The same account also does not prove one storefront. The publisher explicitly describes site numbers as accommodating owners with multiple locations. Keep that distinction visible when preparing an owner-level summary. [Chicago account and site definitions, checked October 28, 2026](https://data.cityofchicago.org/api/views/r5kz-chrr.json). If two public pages disagree about a location, save the exact statements and checked dates. Ask the business's responsible contact which statement governs the proposed work. Do not resolve an identity conflict by selecting the page that makes the opportunity list longer. ## Use a manual deduplication worksheet Start with a small, named research set and a written count definition. For example: candidate account-and-site groups for a location-page accuracy review. Record the selection period and date field separately. This makes the output interpretable when somebody revisits it. | Worksheet area | Information to retain | Decision it supports | | --- | --- | --- | | Source observation | Dataset, access date, record references | Reopening the evidence | | License history | Public license number, event type, labeled dates | Distinguishing transactions within a license | | Candidate location | Account, site, source location wording | Reviewing a proposed location group | | Public verification | Matched business page and checked facts | Establishing the current website relationship | | Exception | Conflicting values, missing fields, rejected matches | Keeping uncertainty visible | | Research disposition | Accepted group, held group, or no supported task | Explaining what the count includes | Work through one candidate at a time. Link all relevant rows before marking the candidate accepted. Have another person inspect ambiguous merges. A reviewer should be able to disagree with one match without reconstructing the entire worksheet. Keep two totals when uncertainty remains: accepted research groups and unresolved candidates. State the rule for each total. Do not combine them into a single apparently verified location count. Retain rejected merges with their reasons. The [business memory guide](/articles/business-memory-for-ai-agents-guide) explains how checked records support future work. Here, a saved rejection can prevent a later researcher from repeating the same incorrect match. ## Turn the count into a bounded research brief Finish with the question the agency can answer. “Review the verified location pages for these accepted groups” is a bounded task. “These license rows represent new clients” introduces a commercial claim that the worksheet has not established. Name the evidence still needed for held groups. A missing site reference, a conflicting public location, and an uncertain website match need different follow-up. Assign each question to a responsible researcher and preserve its unresolved state. The agency owner decides whether a verified inconsistency fits the firm's services. The business owner confirms the public facts before any content change. Licensing eligibility questions remain with the responsible people and authoritative city process. Scale With Search can scope a research worksheet and reviewed handoff around your chosen unit, evidence rules, and exceptions. Begin with a definition someone can check. [Describe the work](/work) Continue the website review: [Agency AI rules: data, approvals, and spend](/articles/agency-ai-rules-data-approvals-spend); [Anonymous agency case studies: show the evidence](/articles/agency-anonymous-case-study-website); [Embed Behance work on your agency website](/articles/agency-behance-portfolio-embed); [Clutch review widgets for an agency website](/articles/agency-clutch-review-widget); [Figma prototype embeds on an agency website](/articles/agency-figma-prototype-embed); [Google Partner badge on an agency website](/articles/agency-google-partner-badge-website); [HubSpot directory referrals: check your agency website](/articles/agency-hubspot-directory-website-handoff); [Squarespace file uploads for agency project briefs](/articles/agency-squarespace-file-upload-briefs); [AI-native agencies: the first functions to build](/articles/ai-native-agencies-first-functions); [Chicago business license events: distinguish a first license, renewal, move, and activity change](/articles/chicago-business-license-application-event-codes); [Adobe Portfolio custom domains for freelancers](/articles/freelancer-adobe-portfolio-custom-domain); [Freelance project availability on your website](/articles/freelancer-project-availability-page); [Google reviews for an agency: ask without filtering](/articles/marketing-agency-google-review-requests); [Marketing agency inquiry form: collect a useful brief](/articles/marketing-agency-project-inquiry-form). [marketing agencies and freelancers](/for/marketing-agencies-and-freelancers): website and search resources. ## Related: marketing agencies and freelancers - [Adobe Portfolio custom domains for freelancers](/articles/freelancer-adobe-portfolio-custom-domain) - [Freelance project availability on your website](/articles/freelancer-project-availability-page) - [Google reviews for an agency: ask without filtering](/articles/marketing-agency-google-review-requests) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```