What it provides
Answers your front desk gives out all day, automated
A public plat and CC&R search for your website — no login, no county portal, just answers.
Smart subdivision search
Visitors type what they know. The widget understands recorder shorthand ("no. 3", "3rd", and "third" all match), merges spelling variants, and offers "did you mean" instead of a dead end.
The whole chain, grouped
Each subdivision shows its recorded plat, the declaration of CC&Rs, and every amendment — grouped and dated, so the current rules are obvious.
A real viewer, on any device
Documents open right in the page with zoom, pan, rotate, and page navigation — full screen with pinch-to-zoom on phones — plus a printable PDF. No county portal, no login.
Your brand, your leads
Fully branded, minimal, or headerless to match your site. Optionally ask for a name and email before a download — every request routes to your team as a lead.
How it works
Cached, fast, and hands-off
The reason a homemade version of this is hard isn't the search box — it's the syncing, caching, and name cleanup behind it. That's the part we run for you.
We read your plant
SubdivisionIQ connects to your existing title plant — a PropertySync document group, a Title Tools county plant, or any image source — and pulls the subdivision list plus every plat, declaration, restriction, and amendment.
We normalize and cache
Subdivision names are cleaned and merged (BROWNE'S ADD and BROWNES ADDITION become one entry) and documents are cached on our infrastructure. A document's first open pulls from the plant; every view after that serves from the cache — your visitors never generate load against your plant.
It stays current
Recorded history never changes, so it caches forever. Covenants and amendments refresh automatically, so a newly recorded amendment shows up on your site without anyone lifting a finger.
Integrations
Bring your plant, whatever it runs on
PropertySync plants
Connect a PropertySync document group and SubdivisionIQ reads the addition list and documents directly — including multiple counties on a single embed key, each selectable in the widget.
- Multi-county on one key
- Instrument types mapped to plat / CC&R / amendment buckets
- Documents cached — no per-visitor API traffic
Title Tools county plants
Counties we index through the Title Tools platform are ready out of the box, with subdivision names normalized from the recorded legal descriptions.
- Go-forward posting keeps it current
- Same widget, same embed
Any image source
Plant on another system? If we can reach the images — an export, a drive, a legacy plant — we index the plats, CC&Rs, and amendments and serve them the same way.
- Unify counties across different systems
- One widget across your whole footprint
- One-time setup may apply for document indexing
Pricing
Simple, per county
- Unlimited searches, views, and downloads
- All three embed sizes, unlimited placements
- Document caching and daily refresh included
- Lead capture and usage analytics included
- PropertySync plants: no setup — turn it on, paste the snippet
- Other plant systems: fully supported; a one-time setup may apply to index your documents
FAQ
Common questions
Does it work on WordPress / Squarespace / our custom site?+
Yes. The widget is three lines of HTML that work on any platform that lets you paste a script — WordPress, Squarespace, Wix, Drupal, or fully custom sites. It renders in an isolated container, so your site’s styles and the widget’s never conflict.
Do we need PropertySync?+
No. PropertySync plants connect seamlessly — turn it on and it works. SubdivisionIQ also serves counties from the Title Tools plant or any image source we can index; those may involve a one-time setup to index your documents. You can mix sources across counties and your visitors will never know the difference.
How fresh is the data?+
Recorded documents never change, so they’re cached permanently. Subdivision lists, covenants, and amendments refresh automatically — a newly recorded amendment appears on your site within a day, with no work on your side.
Will public searches hit our plant’s API?+
No. That’s the point of the cache: visitor traffic is served entirely from our infrastructure. Your plant is only touched by the background refresh.
Can it match our branding?+
Three header styles: fully branded (your logo and colors), a slim minimal bar, or no header at all for pages that already carry your branding. Colors come from your embed key — no code changes.
What about anonymous visitors?+
Search and browsing are anonymous and free for the visitor. You choose whether downloads require a name and email (which routes to your team as a lead) or stay completely open.

