Where 71 proposal requests came from

This pulls directly from SearchPod's own lead-capture log across every conversion form on searchpod.com, get-proposal, book-a-call, and general contact forms, for the 120 days ending 2026-09-23. The underlying export deliberately strips names, emails, and company details, and reports counts only, by the page path the form was submitted from, the recorded utm_source, the services checked on the form, the month, and the form type.

Because this counts form submissions rather than verified customers, it measures interest expressed on our own site, not closed business, and it says nothing about which of these 71 requests turned into a signed client.

Six pages produced 61 of the 71 requests, 85.9 percent of the total: /get-proposal led with 36, /book-demo had 8, /contact had 7, /google-ads had 3, and /partners had 2. The homepage shows up twice in the raw data, recorded as an empty path 4 times and separately as “/” once, a data quirk in how the homepage's own path gets logged rather than two different pages; treated as one homepage, that's 5 requests.

The remaining 10 requests, 14.1 percent, came one or two at a time from nine different niche marketing landing pages: /tutoring-marketing supplied 2, and /financial-advisor-marketing, /collision-repair-marketing, /window-tint-marketing, /locksmith-marketing, /security-guard-marketing, /summer-camp-marketing, /dog-daycare-marketing, and /pet-grooming-marketing each supplied exactly 1. No single niche landing page drove more than 2 requests in 120 days; the volume for this business comes from a small number of core conversion pages, not from any one niche page.

62 of the 71 requests, 87.3 percent, carry no recorded utm_source. 9 of the 71, 12.7 percent, are recorded with chatgpt.com as the source. The data file does not specify whether that reflects a formal UTM parameter appended by ChatGPT's own link handling or a referrer-based attribution; we are reporting the field exactly as it's labeled in our own export rather than assuming which.

On the request forms that captured services, Google Ads was checked most often, on 22 of the submissions, followed by SEO on 20, lead-capture on 19, web development on 12, content marketing on 11, analytics and email marketing on 6 each, branding on 4, other on 3, and custom apps on 1. Those figures add up to more than 71 because several forms let a visitor check more than one service; one submission alone was logged with all five of google-ads, email-marketing, lead-capture, seo, and analytics checked at once.

Requests rose across the window: 5 in May 2026, dropping to 1 in June, then climbing to 12 in July, 25 in August, and 28 in September. September's total is a partial month, the export was pulled on 2026-09-23, so that figure reflects roughly three weeks, not a full calendar month, and is not directly comparable to the four full months before it.

We are not attributing this rise to any single cause. The window covers the same period as several site changes and content pushes described elsewhere in our own program notes, but this dataset alone cannot isolate which of those, if any, drove the increase.

This describes one agency's own inbound requests over one 120-day window; it is not a benchmark for what another business should expect. The utm_source and page-path fields are self-reported by our own analytics setup and were not independently audited for this article, and the homepage being logged under two different paths shows that even our own tracking has small inconsistencies worth naming rather than smoothing over.

A form submission is also not a verified lead. We know a visitor filled out a form asking about a specific service on a specific page; we do not know from this dataset whether that visitor was a real buyer, a duplicate submission, or eventually became a client.