A directory of team members, properties or distributors on your site: how to build one that stays accurate

By Ranjit Bhinge, founder of Blur Studio · Updated · 9 min read

Short answer: A directory on your site is a list of people, properties or distributors where each item has its own page and visitors can filter the list. The safe way to build one is to keep each item as a single row in a table, make one page from each row, and use filters only to help visitors, not to create thousands of extra web addresses for Google. A CMS (content management system, the part of a site that stores content separately from the page design) does this; options range from a shared spreadsheet to a database built into your site platform.

Ranjit Bhinge

You need a directory of people, properties or distributors on your website and want it to be easy to update and good for search.

I'm Ranjit, and I run Blur Studio: 15+ years building software, 120 apps taken live, and clients who have gone on to raise $10M+. I build AI systems and processes that help businesses do a lot more with a lot less time. I also work differently from most of what else is out there, more on that further down this page. Say hello.

A directory looks simple until the third person leaves, the fifth property sells, or a distributor changes its phone number. Then you find the same details in a spreadsheet, a page, a PDF and an old social post. The fix is the same for team members, properties and distributors: one table is the truth, and the website shows it.

This page covers how to design the table, what each item page needs, how filters should work without hurting search, what Google does and does not reward, and how to keep the directory fresh. One option for the build is Ploy, an AI platform that builds and hosts business websites and includes a built-in database for this kind of content. It is one of several options below.

This page may contain affiliate links from which Blur Studio earns commissions.

The pattern: one row, one page, filters on top

  1. One row per item. A person, a property, a distributor. Each row holds every fact you show.
  2. One page per row. This is the page Google can find and show. It has its own address and its own content.
  3. One list page with filters. This is for visitors who want to narrow the list by role, city, price or product line.

Filters are for visitors. Item pages are for search. If you remember only that, you will avoid the most common directory mistake, which is turning every filter combination into a separate web page.

Step 1: design the table

Write the columns before you open any tool. Here are starting columns for three common directories. Add or drop to fit.

DirectoryColumns to start with
Team membersName, role, short bio (2 to 4 sentences), photo, office, email or contact form, phone, areas of work, languages, status (current or left), last reviewed date
PropertiesAddress or area name, type, price or rent, bedrooms, size, features, photos, status (available, let, sold), contact, last reviewed date
Distributors or dealersBusiness name, address, city, region, phone, website, product lines carried, hours, status (active, paused), last reviewed date

Two columns matter more than the rest. A status column lets you hide a row without deleting it. A last reviewed date tells you which rows have gone stale. Without those, a directory slowly fills with wrong details, and wrong details are worse than a shorter list.

For property lists, check your local rules on how homes can be described and advertised before you publish. Our page on building and neighborhood pages for property management sites covers fair housing checks in the US, and it is information, not legal advice.

Step 2: what each item page needs

  • A unique, readable title and heading (the person's name and role, the property's area and type, the dealer's name and city).
  • Text that is specific to the item. Ten dealers with identical paragraphs and different names is thin content. See doorway pages and thin content at scale.
  • One clear next step: a contact form, a call button, or a quote request.
  • Links back to the list and to related items (the same office, the same city).
  • A real photo with alt text (the short description of an image used by screen readers).
  • An accurate address for any real location. Never invent places or people to fill pages.

If the directory is for a product distributor with a large catalog, the same ideas apply at bigger scale; see product catalog websites for distributors with thousands of SKUs.

Step 3: filters without creating a search mess

Google's page on faceted navigation (filters that create many address variations) says that if you do not need filtered pages in search results, you should prevent them from being crawled. Keep the item pages and one unfiltered list crawlable. Its advice, as of November 2026:

  • Use the normal & separator in filter addresses. Anything after a # is ignored by Google, so filtering that happens after the hash creates no pages.
  • Blocking filter addresses in robots.txt is more effective than relying on rel=canonical alone, per Google. Search blogs often recommend canonical only. Google's own page is the source I follow.
  • Return a 404 (page not found) for filter combinations that have no results.
  • Use real links for list pages (page 2, page 3). Google ignores fragment identifiers and no longer uses rel next and prev. Do not point page 2 and beyond at page 1 with canonical.

A simple build rule: for a directory with under a few hundred items, filter in the browser so no new addresses exist at all, and list every item on a plain page that search engines can follow. As a made-up example, a list with 5 roles, 10 cities and 6 price bands can make 5 x 10 x 6 = 300 filter addresses from one list page. A directory with three filters can do the same.

Be careful with "add this markup to rank higher" claims. Google's structured data gallery, as read in November 2026, lists 25 feature types including Organization, Local business and Profile page. It does not list a standalone Person feature or a RealEstateListing feature.

  • Team members: Google's ProfilePage guide allows employee pages on a company website, as long as the page's main focus is one person affiliated with the site. It requires a main entity with a name. Google documents no promised result, so treat it as clean labelling, not a ranking tool.
  • Offices and dealers: LocalBusiness markup needs a name and address, and each location should have its own markup. Use the most specific subtype and make the url point to that location.
  • Properties: there is no Google listing feature for real estate in that gallery. The closest is Vacation rental, which covers vacation properties only. Do not add markup expecting a special result. Good titles, clear photos and fresh status do more.
  • The company: Organization markup has no required properties and belongs on the home or About page.

Google's local business page recommends review and rating markup only for sites that collect reviews about other businesses, so do not mark up reviews of your own firm.

Step 5: pick where the table lives

Options from least to most effort. Prices are as of November 2026, so check each vendor.

  • A shared spreadsheet and hand-edited pages. Free. Fine for under 15 items that rarely change. Breaks when two people edit different copies.
  • WordPress (a free publishing system many sites run on). Custom post types and plugins can make directories. Plugin choice and hosting vary, so check the plugin's page and update policy.
  • Webflow (a visual website builder). Its full CMS comes with the Premium site plan, $25 a month billed yearly or $39 monthly, in USD. Basic at $15 yearly or $25 monthly is for sites without a CMS, and the free Starter plan has a limited CMS and 2 static pages. Webflow's CMS CSV import accepts files up to 4 MB.
  • A custom-coded site by a developer. Priced by quote. Best when you need maps, search, user accounts or an admin screen.
  • Ploy. It has a spreadsheet-style database, called PloyDB, built in. Ploy's docs say you describe a page and its Agent builds the listing page (such as a directory) and a detail page for each row, and edits reach visitors within about a minute without republishing. See the PloyDB guide and what an agentic CMS is.

Ploy's published limits for the database, from its docs as of November 2026: up to 97 columns per table, 128 KB per text value, CSV import up to 32 MB, CSV export up to 10,000 rows per export, a rolling 30-day history with restore points, and no stated cap on total rows. Docs say CSV export is for interchange and not a backup. Ploy's plans: Free at $0, Starter at $50 a month billed monthly, Pro at $300 a month billed monthly, Enterprise by custom quote, and Ploy's docs say unused credits do not carry over. Check Ploy's pricing page for current numbers. Ploy's docs also warn that unreviewed, low-quality content can perform poorly in search, so read what each page shows before it goes live.

A worked example with made-up numbers

A regional equipment dealer network wants a list of 42 dealers across 9 states. Staff track them in a spreadsheet.

  1. Columns: name, city, state, phone, website, product lines, hours, status, last reviewed. That is 9 columns.
  2. Pages: 42 dealer pages, one list page, and 9 state pages (each with a short, real description and a list of its dealers). That is 52 pages, all useful.
  3. Filters: state and product line, done in the browser. No filter addresses are created. The 9 state pages exist because people search by state, not because of the filter.
  4. Maintenance: someone owns the review date. Every 90 days, they check each row. Dealers who leave are set to "paused", which hides the page, and the page redirects to the state page.
  5. Result to measure: contact requests that name a dealer, and the number of rows reviewed on time. Not rankings, which nobody can promise.

Keeping it fresh: the part rankers skip

  • Name an owner for the table, plus a backup.
  • Use a removal rule. When a person leaves, a property sells or a dealer ends, change status first. Then either redirect the page to its parent list (301) or return a 410 (gone) if there is nothing relevant to point to. Do not leave a page with a former employee's details.
  • Review on a calendar, such as the first Monday of each quarter. Sort the table by the last reviewed date.
  • Keep a copy. Export a CSV monthly to your own storage. If you use PloyDB, remember the 30-day history is not a long-term archive.
  • Privacy. For staff, ask before showing a photo, phone or personal email. Check local law.

Test plan before launch

  1. Build 5 items end to end, not 50.
  2. Open each item page on a phone. Pass: the name, the main fact and a contact method show without scrolling.
  3. Change one value in the table. Pass: the page shows it within a few minutes (about a minute on Ploy, per its docs).
  4. Set one row to hidden. Pass: the page no longer shows and the list does not link to it.
  5. Apply every filter. Pass: no filter creates a new indexable address, and an empty result does not show a blank page that returns 200.
  6. If you need a map or radius search, test it with your real data now. Ploy's database docs do not describe maps or location search, so confirm before you rely on it.
  7. Export a CSV. Pass: you can open it and re-import a test copy.

When to skip a built-in database

  • You need a map with a radius search, user logins, or lots of custom fields and approvals. A custom app is a better fit.
  • You have more than a few thousand rows with complex relationships. Check each platform's limits, and plan a pilot.
  • Your content lives in another system, such as a property management system or an inventory system. Sync from that source instead of keeping two copies.
  • You have under 15 items and change them once a year. A hand-edited page is fine.

How I'd approach this

I would start with the table and a rule for who owns it, not with a tool. Then I would build five items on whatever platform the site already uses and decide only after that. If you have no CMS and want to try a built-in one, Ploy's Free plan is a low-cost way to test the pattern before paying for anything.

First-week plan. Day 1: list the item types and the columns. Day 2: clean the data, with one row per item and no duplicates. Day 3: build five items and their pages. Day 4: run the test plan. Day 5: set the status and review rules, and decide the platform. If you need a custom app, an admin screen or a data model that fits your business, Blur Studio builds those; see what it includes.

Related guide: Waitlist and RSVP Forms Without Buying Another Tool.

A closely related page covers the same ground from another angle: How to Store Form Entries and Leads as Rows You Can Use.

For the next step, see Ask AI About Website Visitors Without Opening a Dashboard.

Questions people ask

What is the best way to build a directory on a small business website?

Keep every item as one row in a table, make one page from each row, and add filters for visitors that do not create extra indexable addresses. Whether the table lives in a spreadsheet, WordPress, Webflow, a developer's code or a built-in database like PloyDB depends on how many items you have and how often they change.

Should filter pages be indexed by Google?

Usually not. Google's faceted navigation page says that if you do not need filter addresses in search, you should prevent crawling of them, and that blocking in robots.txt is more effective than canonical alone. Keep item pages and one unfiltered list crawlable.

Can I use Person or RealEstateListing schema to rank higher?

No. Google's structured data gallery does not list a standalone Person feature or a RealEstateListing feature. For employee pages, Google's ProfilePage guide allows markup on employee pages, but documents no guaranteed result. Treat markup as labelling, not a ranking trick.

What happens to a page when someone leaves or a property sells?

Set the row's status first. Then redirect the page to its parent list with a 301, or return a 410 if nothing relevant exists. Do not leave stale details live. A last reviewed column helps you catch these early.

How many rows can PloyDB hold?

Ploy's docs state limits for columns (97 per table), text size (128 KB per value), CSV import (32 MB) and CSV export (10,000 rows per export), but do not state a total row cap. Check Ploy's current docs and pilot with your real data. See the PloyDB guide.

Can I get my data out if I leave?

Ploy's docs say CSV export is for interchange, not backup, and may not re-import exactly. Export regularly to your own storage and test a re-import on a copy. Code and data export terms should be confirmed with the vendor. See who owns your website and content.

Do I need a map or dealer locator?

Only if visitors search by distance. A list by state or city with filters is enough for most small networks. If you need radius search, test it with your real data on your platform before you commit.

Is it okay to show staff photos and details online?

Ask each person first, and let them update or remove their entry. Privacy rules differ by place, so check local law.

More in this topic: Websites: forms, directories and editing on the go (5 guides) →

Sources

Ready for the next step?

A 30 minute call. If you do not need me, I will tell you.

Ranjit Bhinge You talk to me, Ranjit. I reply within a few hours.

Not sure what you need? Tell me what is going on. I will point you the right way, even if it is not me.

Blur Studio · 30 minute call

Book a 30 minute call

You talk to me, Ranjit. If you do not need me, I will tell you.

  • We talk about your business and what is going on.
  • You leave with a clear next step, even if it is not me.
  • I reply to every message within a few hours.
Loading the calendar…