The “Near State Land” Problem Is a Creator-Marketing Problem in Disguise
Every social media operator I know is sitting on a version of the same gap: a claim that sounds specific but isn’t. “Near state land” on a rural listing is the same species of vagueness as “10x your reach” on a tool’s landing page or “viral hook” in a content template pack. The words imply adjacency, but nobody measures the distance. What caught my attention about Unfenced, a free map-based tool launched by David Clayton on Product Hunt, isn’t the land-search niche. It’s the operating principle: take a fuzzy claim (“borders public land”), replace it with a measured number (shared boundary in feet), and draw the edge so the user can see it. That is, more or less, the job description of a good social media manager. Your analytics dashboard says “engagement is up.” Your job is to find out whether that means a thousand people watched three seconds or two hundred people watched to the end. Unfenced is a small, single-purpose product in an unglamorous vertical, and I have no stake in it. But the way it handles data hygiene, claim verification, and the difference between “near” and “touching” is worth a long look for anyone who publishes across Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, and Pinterest for a living.
What Unfenced Actually Does (and Why the Mechanism Matters)
The maker’s story is the pitch: his grandfather and great-uncle bought roughly 240 acres of wooded land in Michigan’s northern Lower Peninsula that backed up to thousands of acres of state land, so “the property line was never really an edge.” Years later, shopping for land in the Poconos, he found listings that said “near state land” and had to cross-reference county GIS maps to figure out whether a parcel actually touched the boundary or was just somewhere in the vicinity. Unfenced automates that check across about 700,000 U.S. listings every week. Per the maker, it takes each property’s county parcel boundary, compares it against the USGS map of public land, and surfaces the parcels that actually touch it — with the shared boundary measured in feet and drawn on a map. Each property page also shows how much connected public land sits behind it and who manages it, elevation, whether a mapped road reaches it, and (new that week) FEMA flood zone and Forest Service wildfire hazard. Search is by ZIP code and distance, browse by state or national forest, or just pan the map. It’s free, no sign-up, no cookies.
The mechanism is the part I keep coming back to. This isn’t a listings site; the maker says plainly in the comments that Unfenced isn’t a listing platform and only updates weekly, so the right place to save favorites is still a Zillow or Redfin-type platform where prices and status are live. Each property links straight to its listing. The maker frames it as “the check you run first: does it actually touch public land, how much, and what’s the ground like.” That positioning — a verification layer that sits in front of the transactional layer — is the same architecture that separates a real analytics workflow from a scheduling tool that also shows you a bar chart.
The comment thread is the product roadmap, and that’s the tell
Read the replies and you see a maker doing discovery in public. Robert Smith notes that showing the actual shared boundary length is more helpful than marking two adjacent areas on a map; the maker agrees and says the number is “the heart of it” because “near state land can mean a mile away.” AyazAkram asks for a way to save and compare parcels; the maker redirects that job to the listing platforms and points to free email alerts for saved searches. Sukumar flags that flat and steep land look similar on a basic map; the maker says slope data (acres under a 15% grade, steepness where a road meets the parcel) is being built from USGS elevation data and would go live later that month. Mehmet asks the sharpest question in the thread: what happens when the county parcel layer and the listing disagree after a lot split? The maker’s answer is the most operationally interesting thing on the page — county parcel layers can lag a lot split by several months, so the listing still shows, measured against the parcel at the listing’s location, and the site checks the two against each other. If listed acreage and parcel acreage disagree badly (his example: a 5-acre lot sitting on a 200-acre parent tract), the property gets a note or the acreage is withheld.
I’d bet most social teams have no equivalent of that “withhold the number when the sources disagree” rule. They’ll happily report a reach figure pulled from one surface and a follower count pulled from another, even when the two are measuring different things across different windows.
How It Differs From the Tools You Already Pay For
The obvious comparison class for Unfenced is land and property search — Zillow, Redfin, LandWatch, Realtor.com. Against those, the differentiator is narrow and honest: it doesn’t try to be the marketplace. It’s a pre-filter that answers one question the marketplaces don’t answer well, then hands you off. That’s a deliberate scope decision, and it’s the kind of decision I wish more creator tools made. The scheduling-and-analytics category is crowded with products that do six things adequately because none of them wanted to be the one thing done precisely. Buffer, Hootsuite, Later, Metricool, Sprout Social — I’ve run accounts through most of them, and the pattern is consistent: the scheduling is fine, the inbox is fine, the reporting is fine, and the thing you actually needed (did this post reach the people it was supposed to reach, and did they stay?) is buried three clicks deep behind a vanity metric.
There’s a second comparison worth making, and it’s less flattering to the creator-tool category. Unfenced is free, requires no sign-up, and sets no cookies. The maker is explicit about it. I’m not naive enough to think that’s a sustainable business model forever — there’s no disclosed monetization, pricing page, or revenue figure anywhere in the source, and the maker doesn’t say how the project is funded. But as a trust posture it’s striking. Most tools in the creator economy ask you to connect your accounts, hand over OAuth scopes, and accept a data relationship before you’ve seen a single useful screen. Unfenced inverts that: prove the value first, ask for nothing. When I evaluate a new scheduling or analytics tool for my own stack, the first thing I check is what it wants access to before it shows me anything. That’s not a moral judgment; it’s a practical one about how much of my workflow I’m willing to expose to a product I haven’t validated.
Why this matters more to a solo operator than to an agency
An agency with a data team can build its own verification layer. A solo creator running five accounts across Instagram, TikTok, YouTube, X, LinkedIn, Facebook, Threads, and Pinterest cannot. They’re stuck trusting whatever number the native dashboard puts in front of them, and native dashboards are built to make the platform look good. Unfenced’s core move — take an authoritative external dataset, compare it to the claim, measure the overlap, show your work — is a workflow a solo operator can actually adopt manually. Pick two sources of truth for your key metric, reconcile them weekly, and flag the weeks where they disagree instead of averaging them into a number that flatters you.
What Creators and Social Teams Should Borrow From It
Measure the shared edge, not the proximity
The single most portable idea here is the distinction between “near” and “touching,” quantified in feet. In content terms: “near” is impressions, “touching” is watch time or saves or profile visits from a specific post. When I scheduled 30 posts across 5 platforms last month, the number that told me the least was total reach. The number that told me the most was, per platform, how many people who saw the first three seconds stayed for the last three. That’s a shared boundary. It’s measured, it’s attributable to a specific piece of content, and it doesn’t move when the algorithm decides to show your post to a different cohort. If you’re building a weekly report, pick one “shared edge” metric per platform and report it alongside — not instead of — the vanity numbers, so you can see when the two diverge.
Withhold the number when the sources disagree
The lot-split answer is the best thing in the thread. The maker doesn’t paper over the lag between county parcel data and live listings; he flags the disagreement and, in bad cases, withholds the acreage. Social operators should steal this wholesale. When your scheduling tool’s click count and your UTM-tracked Google Analytics session count disagree by more than a rounding error, don’t average them and don’t pick the bigger one. Flag it, investigate the attribution window, and if you can’t reconcile it, say so in the report. Clients and founders respect a number that comes with a caveat far more than a number that comes with a confident tone.
Treat the comment thread as the roadmap
The maker built the slope feature because multiple commenters asked for it, and he said so directly. He added a minimum price filter to list pages after Chip Hunnicutt pointed out the pages only had a maximum. That’s a tight feedback loop between the people who use the thing and the person who builds it. Most social teams have the opposite loop: they ship a content format, watch it underperform, and never ask the audience why. The cheapest research you can do this week is to reply to your own comment sections and ask what people wanted to see that they didn’t get. Not “what did you think” — that gets you emoji. “What were you hoping this post would answer that it didn’t?” gets you a roadmap.
Design for the handoff, not the walled garden
Unfenced links out to the listing rather than trying to keep you. That’s a content strategy lesson disguised as a product decision. The creators I see growing fastest right now treat each platform as a handoff point, not a destination — the TikTok drives to the newsletter, the newsletter drives to the YouTube long-form, the YouTube description drives to the product page. The platform that tries to be the whole journey usually loses the person at the first friction point. Build your content so each piece does one job well and hands off cleanly, and track the handoff with UTMs so you can see which edge is actually shared.
Why TikTok creators should care more than LinkedIn ones
The “near vs. touching” distinction bites hardest on short-form video, because that’s where the gap between impression and attention is widest. A TikTok that racks up views but has terrible retention is a parcel that’s “near state land” — it looks adjacent to success on the map, but the boundary is zero feet. LinkedIn rewards a different kind of adjacency: a post can get modest reach and still generate real inbound because the people who saw it were the right people. So the metric you treat as your shared edge should change by platform. On TikTok and YouTube Shorts, it’s retention and rewatches. On LinkedIn and X, it’s profile visits and DMs from people who match your ICP. On Pinterest, it’s saves and outbound clicks. Reporting the same three numbers across all of them is how you end up with a dashboard that’s technically full and practically useless.
Where My Judgment Says It Falls Short
I want to be clear about the limits, because the source is a launch page and launch pages are, by design, the most flattering possible framing.
First, the data freshness problem is real and the maker admits it. Weekly updates mean Unfenced can’t be your source of truth for price or availability, and the maker says as much — save favorites on Zillow or Redfin. That’s honest, but it also means the product’s value decays the moment a listing goes stale or a parcel gets split. The lot-split handling is a mitigation, not a fix. Second, the geographic scope is U.S.-only for now. A commenter asks “Europe when?” and the maker’s answer is that the hard part is listings data — there’s no open feed for European property listings like there is in the U.S., though he notes public land data is surprisingly good in Canada and New Zealand. So the “700,000 U.S. listings” figure is a ceiling, not a floor, and anyone outside the U.S. is out of luck for the foreseeable future. Third, there’s no disclosed business model. Free, no sign-up, no cookies is a lovely posture and an unproven one. I’d bet there’s a paid tier or a data partnership coming, but the source doesn’t say, and I won’t pretend to know.
The bigger limitation is conceptual, and it’s the one I’d flag to any creator tempted to draw a direct analogy. Unfenced works because public land boundaries are a stable, authoritative, government-maintained dataset. Your audience’s attention is not. The USGS map of public land doesn’t change its mind about where the boundary is on a Tuesday because a video did well in a test cohort. Platform algorithms do exactly that. So the lesson isn’t “find your USGS equivalent and trust it forever.” It’s “find the most stable source of truth available, measure against it consistently, and be honest when the sources disagree.” The stability is the aspiration, not the guarantee.
Where the math breaks
The shared-boundary-in-feet metric is clean because parcel geometry is clean. Social metrics are not. Attribution windows differ between platforms, UTM parameters get stripped by in-app browsers, and API rate limits mean your scheduled pull might miss the window when a post actually peaked. I’ve watched a single post report three different click numbers across the native dashboard, the scheduling tool, and analytics — none of them wrong, all of them measuring different things. If you try to build a “shared edge” metric without first documenting what each source is actually counting, you’ll end up with a precise-looking number that means nothing. Document the definitions before you build the dashboard.
What I’d Watch / Test Next
Three concrete things an operator can do this week, borrowed from how Unfenced works.
Pick one “shared edge” metric per platform and define it in writing. Not “engagement.” Something measurable and attributable, like “percentage of viewers who watched past the three-second mark” on TikTok and YouTube, or “profile visits from this post” on LinkedIn and X. Write the definition down, including which tool you’re pulling it from and what that tool counts. Then report it next to your vanity numbers for four weeks and watch where they diverge.
Run a reconciliation pass on your reporting stack. Pull the same week’s numbers from your native dashboards, your scheduler, and your analytics, and list every place they disagree by more than a few percent. Don’t fix anything yet — just document the gaps. That list is your lot-split problem, and knowing where it is beats pretending it isn’t there.
Ask your audience one specific question in the comments this week. Not “what do you think” — “what were you hoping this post would answer that it didn’t?” The maker of Unfenced built slope data and a minimum price filter because commenters asked for them by name. Your audience will tell you what to build next if you ask in a way that invites a real answer.
I’ll be watching whether Unfenced adds the slope layer on schedule, whether a monetization model surfaces, and whether the maker keeps answering hard data-hygiene questions in public as candidly as he did the lot-split one. That last habit is the thing most creator tools are missing, and it’s free to copy.
