1,540
Sessions in June
Homepage quality signals
The homepage recorded 269 entry visitors, 529 entry views, and a 23.5% bounce rate. Going forward, entry and engagement metrics will provide a clearer view of performance than raw page-view totals.
Executive Summary — June 2026
June establishes the reporting baseline
The site launched in June and recorded 1,538 sessions from about 1,190 unique visitors. Organic search accounted for 191 sessions, and the site generated 48 tracked lead-related interactions. Search traffic improved toward the end of the month. The next priorities are cleaning up the data, connecting Search Console, and confirming that conversion tracking is working correctly.
1,190
Direct share of sessions
191
Organic-search sessions
48
Tracked lead interactions
Source: PostHog, June 1–30, 2026. Raw totals include suspected datacenter and automated activity. June establishes the first reliable reporting baseline; previous-period percentage changes are excluded where tracking coverage was not comparable.
Executive Summary — June 2026
June establishes the reporting baseline
Direct traffic made up 1,178 sessions in June, or 77% of all traffic. Organic search contributed 191 sessions, while referral traffic accounted for 159. Organic traffic was slow early in the month but improved steadily, reaching 19 sessions on June 30. Some direct traffic may be automated, so it should not yet be used as a reliable measure of brand demand. The immediate priorities are filtering suspected bot traffic and connecting Google Search Console. A 25–35% organic traffic share is a long-term goal rather than a near-term forecast.
Sessions
1,540
From ~1,190 unique visitors
Organic Search
191
12% of sessions
Referral
159
10% of sessions
Organic Social
8
Under 1% · email: 2
Channels by Sessions — Sitewide
1779
191
159
8
2
Session-based, sitewide. Includes suspected datacenter and automated activity.
Organic Search — Daily Trend
June 1-7
0-1/day
June 8 - spike
17 sessions
Mid-month, good days
7–13 / day
June 30 — month high
19 sessions
The June 8 spike is unattributed — the analysis suggests checking Search Console for the source (a new page indexed, a local mention, or a seasonal uptick).
02 — Top Pages
Pages by Recorded View Events
The homepage recorded the most page-view events in June with 1,764. It was followed by /team with 387, /projects with 335, /services with 193, /about with 189, and /contact with 173.
Homepage Views
1,764
Differs from Page Reports' see note 02
Homepage Entries
269
Entry visitors · 529 entry views
Homepage Bounce Rate
23.5%
#6 page by views · see 05
Channels by Sessions — Sitewide
/
1,764
/team
387
/projects
335
/services
193
/about
189
/contact
173
/Projects — Business & Corporate
110
/Projects — Arts & Entertainment
107
/Services — Construction Management
106
/Projects — Athletics
97
Session-based, sitewide. Includes suspected datacenter and automated activity.
Notes from the Analysis
01
02
Two homepage totals
The 1,764 view-event total comes from a different PostHog query than the 576 homepage views reported in Page Reports. The query definitions should be aligned before the July report.
03
Columns to add next month
Next month’s report should include organic visitors, entry visitors, bounce rate, CTA actions, and conversion rate for each page. June will serve as the starting point for these metrics.
03 — Technical Health & Device Experience
June establishes the reporting baseline
The sitewide report shows 1,388 desktop sessions, or about 89% of traffic, compared with 172 mobile sessions, or about 11%.
Homepage Page Reports show a different split: 221 desktop visitors, or about 75%, and 72 mobile visitors, or about 25%.
The difference likely reflects how each report is scoped and calculated. On its own, it does not indicate a mobile SEO problem. Device reporting should use one consistent scope and measurement before a baseline is established.
Sitewide — Sessions by Device
89%
Desktop — 1,388 sessions
11%
Mobile — 172 sessions
Session-based; includes suspected automated traffic.
Homepage — Visitors by Device
75%
Desktop — 221 visitors
25%
Mobile — 72 visitors
Visitor-based; homepage only (Page Reports).
Data Standardization
Device reporting needs one consistent scope and unit before a reliable baseline can be established. Time on page is excluded because the current data contains multi-hour outliers, likely caused by inactive browser tabs or tracking issues. Once the data is corrected, time on page should be reported using the median or 75th percentile instead of the mean.
Technical Baseline — To Be Established
Core Web Vitals
Baseline not yet established
Crawl errors & broken links
Baseline not yet established
Schema coverage
Baseline not yet established
Mobile usability
Baseline not yet established
Indexing coverage
Baseline not yet established
04 — Audience & Local Reach
Visitors by Recorded Location.
Finding: sitewide, the largest recorded locations were San Jose (111), Tampa (95), Riverview (80), Ashburn (77), and Boydton (76), with 246 where location could not be reliably resolved. On the homepage, Tampa led with 59 visitors, then Riverview (19), San Jose (10), and Ashburn (8). Interpretation: traffic from San Jose, Ashburn, and Boydton appears consistent with datacenter or automated activity; Tampa-area locations align with the service area. City names alone do not confirm either. Action: validate suspected automated traffic before including it in prospect-level reporting.
Sitewide — Recorded Locations
Location not reliably resolved
246
San Jose — datacenter-consistent
111
Tampa
95
Riverview
80
Ashburn — datacenter-consistent
77
Boydton — datacenter-consistent
76
Atlanta
14
'Datacenter-consistent' traffic should be validated before inclusion in prospect-level reporting.
Homepage — Visitors by Recorded Location
Tampa
59
Location not reliably resolved
24
Riverview
19
San Jose — datacenter-consistent
10
Ashburn — datacenter-consistent
8
St. Petersburg
7
Land O' Lakes
6
Riverview generated 19 homepage visitors and 135 homepage views — an unusually high ratio that should be investigated before being treated as strong engagement.
For Future Reports
CTA actions by city · organic visitors by city · local conversion rate · a filtered human-traffic view · service-area share. Baseline not yet established.
05 — Conversions & Leads
48 Tracked Lead-Related Interactions.
June recorded 45 general CTA clicks, 2 email clicks, and 1 phone click, for a total of 48 tracked lead-related interactions. These are actions, not confirmed leads. CTA activity trended down during the month, but the comparison is not yet clean: the first periods cover seven days, the final period covers three, and some early activity may include bot or internal traffic. The next step is to confirm that each CTA event is firing correctly and review session recordings on /contact.
General CTA clicks
45
Email clicks
2
Phone clicks
1
Total tracked lead-related interactions
48
Tracking status: form-submission tracking — baseline not yet established. Call tracking — baseline not yet established. CTA event firing — verification scheduled. /contact session-recording review — scheduled (R—01).
CTA Clicks by Period — June
18
May 31 – Jun 6 · 7 days
18
May 31 – Jun 6 · 7 days
5
May 31 – Jun 6 · 7 days
3
May 31 – Jun 6 · 7 days
1
May 31 – Jun 6 · 7 days
Periods are unequal in length, so raw counts are not directly comparable. Future reports will use CTA clicks per day, clicks per 100 sessions, contact-page conversion rate, organic-session-to-lead rate, confirmed form submissions, and qualified inquiries.
06 — Wins & Recommendations
Wins & Action Plan.
Three evidence-based positives from June, followed by the action plan in three tiers: this week, this month, and ongoing. Each recommendation carries a rationale, an owner, a due date, and a success metric; progress is tracked in section 07.
01
Organic Closed at Its High
Organic search ended the month at its highest daily level — 19 sessions on June 30, after a near-silent first week. Sustaining that level is the clearest early SEO signal to watch.
02
98 Google-Referred Homepage Visitors
Google referred 98 recorded homepage visitors, with 21 from Bing and 2 from DuckDuckGo — search engines are already a meaningful homepage visitor source.
03
Organic Closed at Its High
The homepage drew 269 entry visitors and 529 entry views with a 23.5% measured bounce rate — the natural place to strengthen service-area messaging and lead pathways.
Priority Action Plan
R—02
This month — Search Console, referral audit, Business Profile
Connect and incorporate Google Search Console; identify the actual domains behind the 159 referral sessions; verify, complete, and optimize the Google Business Profile. Rationale: these establish the query-level and local-visibility baselines June could not provide. Owner: analytics consultant · Due: Jul 31 · Success metric: Search Console queries and named referral domains in the July report
R—01
This week — data cleanup & event verification
Standardize PostHog query definitions (one homepage total, one device view), filter internal and suspected automated traffic, verify all lead events fire correctly, and review /contact session recordings. Rationale: conflicting totals and unverified events currently limit every other conclusion in this report. Owner: analytics consultant · Due: Jul 17 · Success metric: one reconciled query set and a filtered human-traffic view live in PostHog
R—03
Ongoing — confirmed-lead tracking & local landing pages
Establish confirmed-lead tracking (form submissions, call tracking), then develop the local landing-page strategy for core service areas. Structured data is added only where eligibility is confirmed; review markup waits until valid first-party review content exists. Rationale: confirmed leads, not CTA clicks, are the metric this program is accountable to. Owner: web team + Envision marketing · Due: first read Aug 29 · Success metric: confirmed leads reported by source in the August report
07 — What's Next?
The July Roadmap.
Planned work, each item with an owner, a due date, and a success metric. The August report will mark every initiative completed, in progress, or blocked - with the measured result alongside.
| Initiative | Status | Owner | Due | Success Metric |
|---|---|---|---|---|
| Analytics cleanup | In progress | Analytics consultant | Jul 17 | Standardized queries; filtered human-traffic view |
| Conversion tracking audit | Not started | Web team | Jul 24 | All CTA, form, and call events verified |
| Contact-page review | Not started | Web team | Jul 24 | Session-recording review complete; fix list issued |
| Search Console baseline | Completed | Analytics consultant | Jul 31 | Queries, impressions & clicks in the July report |
| Referral-source audit | Not started | Analytics consultant | Jul 31 | Domains behind 159 referral sessions named |
| Local landing-page plan | Not started | Envision marketing | Aug 14 | Plan approved; first page live |
| Technical SEO baseline | Not started | Web team | Aug 14 | Core Web Vitals, indexing & crawl-error baseline recorded |