The website, rebuilt
Property listings, leasing information, and inquiry forms brought together in a redesigned site. Separate paths help tenants and property owners find the information that matters to them.
Selected work / Website & search
From zero traffic
to hundreds of
search clicks.
Parker & Associates, Inc.
A complete website overhaul, SEO, and AI search work for an Orange County commercial real estate brokerage. The available reporting window shows 208 Google search clicks, alongside 134 sessions attributed to ChatGPT.
Starting point reported by Noah. Measured results: May 7–September 15, 2026. Google clicks and ChatGPT sessions are counted separately.
See what went into it- Business
- Commercial real estate
- Location
- Orange County, California
- Work
- Website · SEO · AI search
- Project by
- Noah Stegman, at Endcap
01 / The work
More than a new look.
The website wasn’t bringing in traffic, according to Noah’s account of the starting point. This was a complete overhaul, paired with search work across the site and its content, to make the brokerage easier to find, understand, and contact.
Content with a purpose
Articles and keyword targeting support the brokerage’s services and markets. The work goes beyond the homepage, giving people more useful ways to discover the business through search.
Visibility in AI search, too
The project also included GEO and AEO: work on how the business and its content can be understood and surfaced by AI search and answer tools. Below, Google performance and traffic attributed to ChatGPT are measured separately.
Explore the rebuilt websiteVisit Parker & Associates
02 / Google search results
208 search clicks.
A business being found.
Across the available May 7–September 15, 2026 reporting window, Google recorded 208 clicks through to the website and 22,810 appearances in search results.
The first available 28-day reporting period recorded 11 Google search clicks. The latest complete period in this snapshot recorded 77. Search appearances grew from 873 to 7,882 across the same two windows.
Clicks from Google
Clicks through to the website from search results
1177
May 7–June 3 vs. August 19–September 15, 2026
Appearances in Google
Times the site appeared in search results
8737,882
May 7–June 3 vs. August 19–September 15, 2026
The full reporting timeline
Each point totals the preceding 28 days, including that date.
Search appearances eased from the preceding 28-day period, while clicks continued to rise. Both are shown here, including the most recent movement.
Reporting periods, source & context
Source: Google Search Console, Web search, all countries and devices. Snapshot captured September 17, 2026; complete daily data runs May 7–September 15, 2026. The chart starts June 3, the first date with a full 28-day window.
| Period (2026) | Clicks | Appearances |
|---|---|---|
| May 7–June 3 · First available | 11 | 873 |
| July 22–August 18 · Previous | 66 | 9,264 |
| August 19–September 15 · Latest | 77 | 7,882 |
Noah reports that the website started with zero traffic and estimates that the overhaul and search work began about three months before the increase became noticeable. That starting point comes from his account, not a retained zero-traffic analytics report. The 208 clicks cover the full May 7–September 15 window, not a single month.
The 28-day comparisons use the earliest available and latest complete periods in this snapshot; they are not verified pre-launch and post-launch periods. The data shows search growth during the available timeline, without isolating the effect of any individual change.
Clicks and search appearances measure discovery, not confirmed inquiries, clients, or revenue. Traffic attributed to ChatGPT is reported separately below.
Download the daily search data03 / ChatGPT traffic
Another way in: ChatGPT.
Across May 7–September 15, 2026, site analytics recorded 134 sessions attributed to ChatGPT. These are measured separately from the Google clicks above. Some visits continued to other pages and the contact form.
Before the website and GEO/AEO work, there were no ChatGPT-attributed visits, according to Noah. The latest measured 28-day period recorded 68 sessions.
Sessions attributed to ChatGPT
Tracked website sessions with a ChatGPT source signal
068
Before the work vs. August 19–September 15, 2026
Starting point reported by Noah. Latest 28-day period measured in PostHog (UTC).
Within those 68 sessions
- Pageviews
- 119
- Sessions visiting multiple distinct pages
- 14
- Recorded form-submission events
- 3
Form events were recorded in the browser. Delivery and lead quality were not independently verified.
How we identified the traffic
All 68 sessions carried a ChatGPT source tag in the landing-page link. Of those, 21 also recorded chatgpt.com as the referring site; the remaining 47 had a direct or missing referrer. These are traffic-attribution signals, rather than a count of verified AI recommendations.
ChatGPT measurement details
The zero starting point refers to the period before the website and GEO/AEO work, as confirmed by Noah. The saved PostHog report records 38 sessions for July 22–August 18 and 68 for August 19–September 15, 2026. Both of those measured periods came after the work began; the earlier one is not the pre-project baseline.
Source: a PostHog analytics snapshot captured September 17, 2026. The full May 7–September 15 window contains 134 ChatGPT-attributed sessions; the first captured production pageview was May 11. All measured periods use UTC. Sessions were counted once if they included a production pageview and either a ChatGPT session-entry referrer or an explicit utm_source=chatgpt.com tag on the landing URL.
The 21 sessions with a matching referrer are included within the 68 tagged sessions. The 14 sessions visiting multiple distinct pages and the 3 sessions recording a form event also overlap; they are not additional visitors. Sessions are not unique people.
Sessions with a captured bot flag were excluded. Internal visits, self-tests, and unrecognized bots could not be fully separated in the saved report. A source tag or referrer does not establish that a visit came from an unpaid recommendation or that a particular website change caused it.
The form figures are browser analytics events, not independently confirmed delivered inquiries, qualified leads, clients, or revenue. Google Search Console clicks and PostHog sessions use different measurements and are not added together here.
About source tags and referrers