Inside the collection.
Open a tool to see its workflow, returned fields, recorded results and costs.
Apify
Apify
supplied the detail behind the social profiles—not just a list of
accounts
Five principal collection tasks returned 9,806 items in the
retained September receipts. They supplied company descriptions, website
links, audiences, opening hours, service areas, employee information and
post-level activity. The practical value was joining those details to
the website assessment for the same business.
Apify’s reported programme cost was $55.07. The retained September
consumption ledger covers $31.48 of Apify work; the five principal tasks
below account for $30.57 within that ledger. These are different scopes,
not competing totals.
Facebook took
most of the principal-task spend
Facebook’s two tasks account for $27.68—about 91% of the spend in
this five-task comparison. That makes their output quality the first
place to look when judging value from this part of the project. The
profile and post tasks also answer different questions: who the business
is and how it describes itself, versus what it has been publishing.
Facebook supplied website values in 2,730 records, email values in
2,486 and opening-hours values in 1,903. This is substantially more
useful to business research than a recommendation percentage that barely
varies. These fields describe whether the profile offers a next step and
explains when and where the business operates.
The retained output also includes recommendation and rating fields,
page-advertising state, price-range information and further
linked-platform fields. They remain available in the field catalogue;
rating ceilings are not promoted into business-performance headlines.
Account details are assessed after matching them to the business.
Facebook
posts: what was being published and the response it received
Post text was available in 2,681 records and media in 2,882. Together
with the post date, this material gives the analyst the substance behind
an activity figure: project photographs, service descriptions, offers
and other business updates. The shared-post reference also allows a
reshare to be distinguished from material the business published
itself.
For a contractor, the valuable comparison is whether current work is
visible and whether a post leads to useful information or an enquiry.
Likes and views add context to individual posts. They are not a
substitute for that assessment, and a latest-post sample does not
measure the performance of an entire campaign.
LinkedIn
details: business context that a follower count cannot supply
LinkedIn returned a website in 1,480 of 1,495 company-detail records
and a description in 1,478. Founded year was available in 1,192 returned
records. These are useful inputs to company-age and service comparisons
once the company identity is accepted; they are not a reason to assume
every record in the business master has a reliable founding date.
Employee count and company-type fields add a different perspective
from consumer-facing platforms. A business with a small social audience
may still present a substantial organisation through its company
description, specialities and workforce information. That is why the
study retains the detail rather than reducing LinkedIn to “account
found”.
LinkedIn
posts: company information and publishing activity are separate
outputs
The post collection includes text in 1,045 records, video links in
113 and document titles in 34. Those formats help explain how businesses
demonstrate expertise: short updates, longer articles, video and
documents are different forms of presentation. An analyst can connect
the material to the company’s stated specialities and website services,
rather than guessing its marketing strategy from follower count.
The TikTok task returned 367 profile identities and 344 dated video
records, while a bio link was populated in 93 records. That distinction
matters to a business using video to attract attention: the profile and
its content are one part of the journey; a destination for the
interested viewer is another. At business level, the retained bio link
can be checked against the website and enquiry routes already
collected.
What we derived after
collection
The research added eight completeness checks where the relevant field
exists: phone, website, about text, logo, biography, email, reported
hours and categories. It also classified ownership, retained collection
outcomes and calculated posting recency. These checks make the raw
fields comparable without pretending every platform has the same
schema.
A business-facing table therefore shows the available accounts, the
measured audience and dated activity, with a short platform note. The electricians edition demonstrates that
approach. The practitioner’s output is the field catalogue and the
collection results; the owner’s output is the comparison and a practical
recommendation.
Download the aggregate field
catalogue. It lists populated field counts, not business identities
or profile values.
How collection outcomes
were handled
Collection errors were retained as explicit outcomes alongside the
usable profile and post records. They formed part of the operational
account of the work: submissions, material returned, errors encountered
and the evidence available for qualification. They were not treated as
business attributes or used to erase the useful fields collected
elsewhere.
For a practitioner, this makes the process reviewable. Facebook
details delivered 2,849 page identities and Facebook posts delivered
3,145 post identities. LinkedIn supplied company detail and publishing
evidence through separate tasks. Those outputs then supported the
business-level ownership checks, audience comparisons, service analysis
and posting timelines.
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Make
Make connected
Instagram profiles to their posts
The retained social receipts record 16,345 Make operations
against 2,991 submitted candidates. The Instagram export contains 2,434
profile records, 7,205 post records and 414 error records.
Make’s job in this project was the Instagram collection workflow. It
brought profile and post material into the research so that audience,
biography, website and current activity could be joined to the same
business. A single Instagram account could produce several post records;
an operation was a workflow step, not a business or a post.
What the workflow returned
The raw export mixes these record types. A row with a post caption is
not another company profile. Keeping them separate allows a practitioner
to compare the cost of collection with both the account detail and the
material it delivered.
Fields available for the
research
The denominator here is the combined 10,053-row Instagram export.
Profile fields and post fields belong to different record types; a field
absent from a post row is not a missing field on the company
profile.
The export has dated post values in 7,184 rows and captions in 6,900.
Those fields provide the material behind a current-work comparison.
Follower count describes the audience already accumulated; captions and
dates show the work being presented to it.
In the electrician study, Instagram was available for 28 businesses,
but only five had a post within 30 days. The automation’s commercial
output is that distinction and the underlying project material. It
allows a conversation about keeping an existing profile useful, rather
than merely recommending Instagram because it is popular.
How the pieces fit together
The retained workflow submitted account candidates, collected profile
and post outputs, saved them with the business reference and then
normalised the fields for the social assessment. Ownership and
collection outcome were handled before business-level comparisons. This
let profile information, latest activity and website evidence appear
together in the same business report.
For a practitioner, the reusable pattern is to preserve that join
through the automation: business reference → account → profile fields →
dated posts → report measures. Make’s operation count measures workflow
consumption. The profile and post counts describe the evidence
delivered. The report’s business counts describe the final analytical
population.
The reported programme cost for Make was $18.82. That cost and the
16,345-operation receipt total have different accounting scopes, so this
edition does not manufacture a cost per successful business from their
division.
Aggregate field catalogue · Electrician audience and activity
comparison
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Firecrawl
Firecrawl
captured pages from 559 of 607 difficult-site domains
A verified qualification round retained pages from 92.1% of
its Firecrawl queue and added verified website evidence for 395
businesses. That is a concrete contribution to the research:
businesses that would otherwise have had less website evidence could
proceed with a better-supported profile.
This edition describes the 14–19 August qualification round, whose
parent population was 4,703 prospects. In that executed round, ordinary
retrieval and candidate verification preceded a difficult-site Firecrawl
batch. The wider project contract also specified Firecrawl Batch Scrape
for resolved business-owned URLs; the executed round and the broader
design should not be confused.
What the difficult-site
batch produced
All 559 HTML/metadata pairs were retained and hash-reconciled.
Capturing a page and accepting it for a particular business were
separate steps: the first is a retrieval result; the second makes the
material useful to the business profile.
What was saved,
and what was extracted from it
The first four groups describe retrieval evidence. The later groups
describe material extracted from the captured pages; they are not all
direct Firecrawl response fields. The project’s retrieval contract
requested contact-bearing content, including headers and footers, so
useful business information was not discarded with a main-text-only
view.
It recovered more
than obvious access blocks
Firecrawl recovered 24 of 37 cases previously labelled as TLS
failures and 11 of 14 labelled as other transport failures. Those
results show why a failed ordinary request was not sufficient reason to
abandon the business’s website evidence.
The round also exposed a cost problem: a gateway timeout could leave
a provider job running. Retrying without reconciling that job risked
another charge. Payloads reported 559 credits; the balance showed 619
spent at the last observation, with an estimated 660–700 after
outstanding jobs. Small batches of 10–15 URLs were the reliable
operating size observed under that round’s 90-second gateway
timeout.
The practical lesson is to save the provider job reference before
polling, reconcile a timeout against that job, then decide whether a
retry is needed. That protects the spend and preserves pages already
collected.
How retained
pages paid for more than one analysis
The round stored 3,510 HTML occurrences across direct retrieval,
candidate verification and Firecrawl, representing 3,478 distinct pages
after content deduplication. Those saved pages supported website
features, service wording, contact extraction and social-link discovery.
The same source could be analysed again without paying to collect it
again.
The wider programme recorded 6,720 Firecrawl credits, with a reported
cost of roughly £30/$40. Those programme figures are separate from this
named batch, and credits are not requests.
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Exa
Exa
searched 687 missing-site records in under four minutes
In the verified August qualification round, Exa processed all
687 remaining discovery records in 236.2 seconds at a recorded cost of
$4.809. It returned a high-confidence or plausible website candidate for
598—87.0%.
The job was specific: find candidate websites for prospects whose
initial record lacked a captured website. Google outbound-link
resolution ran first. Parallel’s free route completed 40 searches before
its fair-usage throttle interrupted that approach; Exa handled the
remaining 687 records.
What the search produced
The useful output was a candidate destination linked to the business
being researched, followed by a decision about relevance. A directory
result could help identify the business without becoming its official
website. A likely domain then went through page capture and identity
verification.
Search and
qualification did different work
Across the missing-site discovery and verification stage, 258 of the
original 1,320 prospects without a captured website gained verified
owned-site evidence. That is a result of the joined stage, not 258 sites
that can all be attributed to Exa alone.
The distinction is useful to anyone building prospecting automation.
Search expands the options quickly; retained page evidence turns an
option into something a business report can use. Making these outputs
explicit allows search performance and website qualification to be
assessed separately.
The named Exa batch averaged about $0.007 per processed record. The
wider programme’s reported Exa cost was $22.12. These figures describe
different scopes; neither is a current price quote.
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Website evidence and direct retrieval
6,131 distinct website captures
The combined evidence register records 6,131 distinct HTML content hashes matched to 6,562 business records. Shared captures can support more than one business record. This is the combined collection across capture routes, not a direct-retrieval-only total or a fresh physical-file count.
August direct-retrieval campaign: 2,383 domains
The documented August campaign attempted 2,893 canonical
domains and retained HTML from 2,383—82.4%. It spent zero provider
credits. The saved content supported website assessment,
contact extraction and discovery of social-account links.
The number of businesses scored differs from the number of domains:
business records and domains are different units. Similarly, 5,423 links
became 4,008 candidate accounts because repeated links and URL variants
needed reconciliation.
One saved
page supplied several kinds of evidence
The extraction examined visible text, links, structured JSON-LD,
metadata, contact links and forms. It supplied service wording, website
contact routes, social-account candidates and technical features used by
the assessment. Retaining the original page meant those outputs could be
checked and recalculated without another collection request.
For an automation builder, the important design choice is to save the
source once and extract several useful outputs from it. The page becomes
more valuable than a single score: it can explain what the business
does, where the customer can go next and which social accounts should be
collected in the next phase.
The campaign’s remaining retrieval queue showed the limit of ordinary
fetching. The Firecrawl edition explains the
later difficult-site work and its verified results. Zero provider
credits describes this retrieval lane’s metering, not zero labour or
infrastructure cost.
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
X
X
supplied account history as well as the latest post
The retained receipts record 3,049 X requests against 1,622
submitted candidates. The export contains 1,478 result records, with a
resolved user identity in 1,386 and a latest-post date in
1,298.
X used its API route rather than the Apify tasks. The output combined
profile information and public metrics with the latest recorded post. It
also kept reply, repost and quote flags, which help distinguish original
business material from other activity.
What the records contain
Of the 1,386 records with a resolved account, 1,298 also contain a
latest-post date: 93.7%. This makes recency a useful companion to the
audience figure in this returned record set. Description text is
available in 1,277 records, providing wording to compare with the
website and sector label.
In the electrician sample, five of eight accepted X accounts had
latest recorded posts more than a year old. That points to an
existing-profile maintenance issue, rather than evidence that
electricians should rush to add another X account. An owner can decide
whether to refresh the profile or concentrate current project updates on
a channel they already maintain.
The reported programme cost was $19.38. Requests, submitted
candidates and accepted business accounts are different units; they are
shown separately. Counts for likes, replies and impressions describe the
returned latest post, not a campaign average or a rate of winning
enquiries.
Aggregate field catalogue · Electrician platform comparison
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
YouTube
YouTube
revealed the difference between having a channel and having a video
library
The retained receipts record 820 submissions and 1,956
YouTube quota units. The export contains 766 result records: 616 with a
resolved channel and 582 with a latest-video date.
YouTube used the Data API route. Its contribution was different from
a social-profile check: it supplied the size of the video library,
accumulated channel views and the latest video’s title, date and
response. These fields let an analyst distinguish a channel page from
visible work a customer can actually watch.
What was captured
Of the 616 resolved channel records, 582 contain a latest-video
date—94.5%. Latest-video views are available for all 582, while likes
are available for 569 and comments for 546. Showing those denominators
avoids treating the absence of a response field as zero engagement.
A channel’s total views and its latest video’s views answer different
questions. The first describes accumulated viewing across its history;
the second describes one piece of material. The report keeps them
separate so a large historic library cannot silently become a claim that
the business is publishing actively now.
For an electrical contractor, video can demonstrate a completed job
or explain a service. The dataset supports comparing how businesses
present that material through titles, descriptions and dates. The
electrician sample itself contains only three accepted YouTube accounts,
so it supports a description of those accounts rather than a sweeping
recommendation for the whole trade.
The programme recorded no YouTube cash charge. Quota units still
measure API consumption; they are not a dollar amount or a count of
videos. Subscriber-hidden state is retained alongside subscriber values
and should be respected before making audience comparisons.
Aggregate field catalogue · Electrician platform comparison
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Companies House
Companies
House linked 261 prospects to exact company records
All 4,703 prospects in the August pilot were processed; 261
matched the approved normalised-name-and-postcode rule. Every matched
company also had people-with-significant-control evidence in the
retained source.
The automatic match rate was 5.55%. Its purpose was to establish an
exact company link, not to judge the proportion of local businesses that
were incorporated. The basic-company snapshot was dated 1 August and the
PSC snapshot 14 August 2026.
What the match added
The pilot connected a prospect identity and postcode to an
authoritative company record, then retained matching status and PSC
coverage. Its output was a separate company-enrichment workbook with
matched, unmatched and review material. It was not silently joined into
every business row in the qualification master.
For a practitioner, this is a distinct stage from searching for a
trading website. A trading name can lead to the correct website while
still requiring a separate legal-identity match. The retained exact
matches provide that corporate context without changing the website and
social observations.
For the case studies, company-age or size comparisons must use an
established company link or a clearly labelled platform-reported field.
Account creation date is a different measure. Keeping those distinctions
in the source design prevents a plausible-sounding story about younger
firms from being built on the age of a social profile instead.
Source: the August qualification closeout and the Companies House
pilot receipt, including reconciliation of all 4,703 dispositions and
the 261 exact matches. Identifiable company and PSC records are not
included in this reader edition.
These figures come from retained project receipts and outputs. Field
counts describe populated values in returned records, including repeated
observations; they are not counts of unique businesses. A returned error
item is reported separately from a returned profile. Blank fields are
not converted into zero. Completeness flags, ownership decisions and
qualification scores are derived after collection, not supplied as
scores by the scraper. No additional collection was performed for this
edition.
Source material: September provider-consumption receipts, platform
raw-record exports in the combined research database, and the verified
August qualification closeout where explicitly stated. Programme-wide
reported costs and individual collection-window costs are kept separate.
Identifiable source records remain private.
Sources are the retained project editions and their receipts. Named batches, programme totals and record types retain their original scope. Nothing was collected again for this prototype.
Who’s standing out?
Who’s falling behind?
8,976 business records. 12 locations. A closer look at the websites, social profiles and recent work a customer can actually find.
Different professions. Different pictures.
A website, a social account and a current update tell different parts of the story. Move through four familiar professions to see the contrast.
The website is there. The recent work is harder to find.
18
of 42 · latest post over a year old
101 of 114 electricians had a website. But among the 42 with accepted social accounts, just 17 had posted within 90 days.
18 of those 42 had a newest recorded post more than a year old.
The work gives them something worth showing.
44
of 58 · posted within 90 days
44 of 58 hairdressers with accepted social accounts had posted within 90 days—75.9%, compared with 40.5% for electricians.
A finished style can supply material for a profile, a website gallery and a follow-up post. One piece of work can support several useful updates.
Here, social activity is part of the picture.
47
of 51 · posted within 90 days
63 of 70 wedding venues had a website, and 51 had accepted social accounts. Of those 51, 47 had posted within 90 days.
A maintained channel can keep the setting, events and recent work visible while a website answers the practical questions.
A strong website is only one part of being visible.
8.0
out of 10 · median website score
Accountancy firms had a median website score of 8.0 across 93 assessed sites. Among 64 firms with accepted social accounts, 35 had posted within 90 days.
A useful explanation or a timely answer gives a professional firm something substantive to share. Website quality and publishing activity are separate choices.
18 of 42
The newest recorded post was more than a year old.
For nearly half the electricians with an accepted social account, even their latest recorded update was over a year old. Keeping one existing channel useful is a concrete place to start. Read the electrician edition.
Current posts.
Larger audiences.
On Instagram, accounts with a post in the last 30 days had a median 1,089.5 followers. For accounts whose latest post was over a year old, the median was 207.
Choose a platform to see its own audience scale.
Explore Social media — six social-channel chapters.
Median followers / subscribers · grouped by newest post
Is your profession
ahead of the picture?
Start with all 8,976 businesses, then compare a profession or a location against the same study baseline.
Find your benchmark.
How the research became one connected record.
From prospect searches to website evidence and social qualification.
Follow the process →617,704
populated business-table cells.
172 fields across 8,976 business records. The value lies in connecting them: what a firm offers, where it can be found, and how current its presence looks.
Find the part that matters to you.
Newest post over a year old.
Read the electrician edition ↗Recent activity among businesses with accepted social accounts.
Explore the hairdresser comparison ↗Social-account businesses had posted within 90 days.
Explore the venue comparison ↗Median website quality across 93 assessed sites.
Explore the accountancy comparison ↗Without a website available through either check.
See what a first website needs ↗Businesses in the town’s retained research view.
Explore Hemel Hempstead ↗Research method, definitions and sources
The first list became a much richer business record.
In the original round, the same 4,703 businesses went from a 17-field prospect list to a 60-field qualification record. The completed research now connects business assessments with detailed social-account records.
17 fields per business
4,703 rows × 17 fields
79,951 cell positions
Business names, locations, website and social links, telephone numbers, addresses and the sources behind each record.
60 fields per business
4,703 rows × 60 fields
282,180 cell positions
Website assessments, review volumes, contact evidence, social candidates and the reasoning behind qualification scores. The record expanded by 43 fields.
53 fields per account observation
272,063 populated cells
Across 11,793 rows in the current account export
Platform, account ownership, audience, latest posts and profile completeness: information that shows what sits behind a social link.
The result is a business picture that can be compared from several directions: the website, the contact details, the social profiles and how recently those profiles were used.
How these totals are counted
The first two figures describe the same original-round population. Rows multiplied by fields gives spreadsheet capacity, including blanks; it is not a count of collected facts. The final business and account totals count non-empty cells, including recorded scores, classifications and source information. They are separate views with overlapping information and are not added together as unique facts. A field can also contain several links or pieces of text.
The current account export contains 11,793 rows; the earlier population bridge used elsewhere in this prototype records 11,722 observations. These describe different retained versions. Account rows can include repeated or unreadable observations and are not a count of unique accepted profiles.
Sources: original prospection closeout of 14 August 2026 (4,703 × 17); qualification master and field-lineage audit of 19 August 2026 (4,703 × 60); current combined business and account CSV exports checked for this update.
Automation gathers the material. People decide what it means.
The workflow connects repeated retrieval and extraction tasks with structured records. That makes it possible to compare the same kinds of evidence across thousands of businesses. Human work remains in setting the questions, checking matches, judging comparisons and explaining a practical response.
A strong website score is not the same thing as recent social activity. A review count is not a measure of enquiry handling. Keeping those distinctions clear helps turn the research into specific advice rather than a single verdict on a business.
The units matter because the stages do different work.
The initial 10,073 search-result occurrences include repeated appearances. Earlier consolidation retained 9,590 acquisition rows; the current combined research contains 8,976 business IDs. These are separate recorded populations. The numerical difference is not presented as a measured conversion rate or a complete count of exclusions.
Social-account observations also include unreadable or differently attributed material. They are not 11,722 unique business accounts. The explorer uses accepted accounts assigned to the business and readable through the study.
A selected geography, with room for useful comparisons.
The programme covers twelve selected places: . Hemel Hempstead and Bovingdon remain separate. Harrow is a London borough in historic Middlesex.
A future study could apply the same questions to a larger city. This edition describes the locations actually studied.
Evidence and scope
Source: retained September 2026 combined business research and its population bridge. Website model: website-1.0.0. Social recency comparisons end 8 September 2026. The private explorer contains aggregate records only. No new collection was used to build this prototype.
Measured full-run timing and cost claims are not included here because the complete comparable-run reconciliation is not yet part of this prototype. No four-hour or 10× delivery claim is implied by the record totals.
Choose where to look next.
The overview shows how businesses appear online. Explore the six social channels in detail, or see how a clearer website can help the next customer take action.
Explore the social media chapters ↗
Explore use cases ↗
Sources & method
Retained business research · snapshot 8 September 2026. No new business collection was performed for this presentation.
Read the chart data and definitions
Study locations
Platform presence and recorded activity
Business counts, once per platform. Recent = latest recorded post within 90 days of 8 September 2026. Categories and platforms overlap.
Selected categories
Instagram audience
Within 30 days: median 1,089.5 followers, 896 distinct accounts. Over a year: median 207, 329 accounts. Matched audience/date sample. Association does not establish causation.