Estate Sale Websites:
CMS Architecture for Sale Companies

Most estate sale companies do not have a website. The ones that do usually have a static page with a phone number and a link to their EstateSales.NET listing. This is a missed opportunity. A proper branded website gives you SEO authority, client trust, and a home for your business that you control — not a listing on someone else's platform.

But estate sale websites have specific CMS requirements that generic website builders do not anticipate. Sale listings with date ranges. Photo galleries with dozens of images per sale. Address privacy that reveals the location only after a certain date. Category-based browsing. Integration with EstateSales.NET where your primary audience already lives.

This guide covers the CMS architecture that estate sale companies actually need, the collections and fields that make it work, and how Trellis can generate the entire structure automatically.

Why Estate Sale Companies Need a Proper Website

SEO and local search

When someone searches "estate sales near me" or "estate sale company [city name]," they should find your website — not just your EstateSales.NET listing. A branded website with proper SEO fields, structured data, and location-specific content ranks in Google Maps, local search results, and organic search. EstateSales.NET is a marketplace. Your website is your brand.

Client trust

Estate sale clients are trusting you with their family's belongings — often during emotionally difficult times. A professional website with past sale galleries, testimonials, and clear process documentation signals competence and care. A Facebook page with inconsistent posts does not communicate the same level of professionalism.

Control over your business presence

EstateSales.NET, Craigslist, Facebook Marketplace — these are distribution channels, not your business identity. Algorithm changes, policy updates, or platform shutdowns can reduce your visibility overnight. Your website is the one place on the internet that belongs entirely to you.

The CMS Collections You Need

Estate sale websites need four core collections and two optional supporting collections. Here is the architecture.

1. Sales (the primary collection)

Each CMS item represents one estate sale. This is the collection your site is built around.

Essential fields:

• Sale Name — the primary identifier, usually the neighborhood or a descriptive name (never the client's surname for privacy)
• Slug — auto-generated URL path
• Status — Option field: Upcoming, Active, Completed, Cancelled
• Description — Rich Text field for the sale narrative: what is being sold, highlights, special items
• Street Address — Plain Text, conditionally displayed (see address privacy section below)
• City — Plain Text, always displayed
• State — Plain Text
• ZIP Code — Plain Text
• Neighborhood — Plain Text, useful for SEO and browsing
• Address Reveal Date — Date/Time field, controls when the full street address becomes visible
• Featured Image — the hero image for the sale listing card
• Categories — Multi-Reference to the Categories collection
• Sale Dates — Multi-Reference to the Sale Dates collection
• Sale Photos — Multi-Reference to the Sale Photos collection
• EstateSales.NET URL — Link field pointing to the listing on EstateSales.NET
• Terms and Conditions — Rich Text or Plain Text, often standardized across sales
• Payment Methods — Plain Text (e.g., "Cash, credit cards, Venmo")

2. Sale Photos (companion collection)

Estate sales are photo-driven. Buyers want to see what is available before they show up. A typical sale has 30 to 100 photos. This companion collection handles the gallery.

Fields:

• Photo Name — descriptive name or auto-generated
• Image — the photo itself
• Caption — optional description of the item
• Sort Order — Number field for controlling display order
• Sale — Reference back to the parent Sale item
• Category — optional Reference to Categories (allows filtering photos by type)

This is the companion photo pattern: a separate collection with a reference back to the parent. It solves Webflow's single-image-per-field limitation and allows unlimited photos per sale. Display them using a nested collection list filtered by the parent reference.

3. Sale Dates (companion collection)

Estate sales run for specific date ranges, often with different hours on different days and discount schedules. A single Date field on the Sales collection cannot represent this.

Fields:

• Date Label — e.g., "Day 1 (Full Price)" or "Day 2 (25% Off)"
• Date — Date/Time field
• Start Time — Plain Text (e.g., "9:00 AM")
• End Time — Plain Text (e.g., "3:00 PM")
• Discount — Plain Text or Number (e.g., "25% off")
• Sale — Reference back to the parent Sale item

This structure lets you display a clean date schedule on each sale page: "Thursday 9-3 (full price), Friday 9-3 (25% off), Saturday 9-1 (50% off)." It also powers date-based filtering on your sales listing page.

4. Categories

Categories let buyers browse sales by what they are looking for: Furniture, Antiques, Art, Jewelry, Tools, Kitchenware, Collectibles, Vehicles, Real Estate.

Fields:

• Category Name — the display name
• Slug — for category landing pages
• Icon or Image — optional visual identifier
• Description — optional SEO description for the category page

5. Testimonials (optional)

Client testimonials build trust. Keep this simple: Client Name, Quote, Sale Reference (optional), Date, Star Rating (Number 1-5).

6. Team Members (optional)

If your company has multiple sale managers or a recognizable team, a Team Members collection adds a personal touch: Name, Photo, Role, Bio.

The Companion Photo Pattern

The companion photo pattern deserves special attention because it is central to estate sale websites and is the most common source of architectural mistakes.

The wrong approach: adding Image 1, Image 2, Image 3 through Image 10 as separate fields on the Sales collection. This burns 10 of your 54 custom fields on images alone, hard-codes the maximum number of photos, and creates an awful editing experience where you upload images one by one into numbered fields.

The right approach: a separate Sale Photos collection with a reference back to the parent Sale. Each photo is its own CMS item. The sale page displays them using a nested collection list. Adding a photo means creating a new item and setting the reference — no field limit concerns, no hard cap on the number of photos.

In Airtable, this is even simpler. Airtable's attachment field holds multiple images per record. You drag all 50 photos into a single field. Trellis creates and manages the companion collection in Webflow automatically — each attachment becomes a gallery item, properly referenced and ordered.

Address Privacy Handling

Estate sale companies have a specific privacy requirement that most CMS architectures do not anticipate: the sale address should be hidden until a specific date, usually the day before or the morning of the sale.

This protects the client's privacy (people showing up days before the sale, theft risk) and creates a sense of anticipation that drives attendance.

In Webflow, you handle this with conditional visibility. The Street Address field is always present in the CMS but only displayed when a condition is met. You can use Webflow's conditional visibility to show/hide elements based on a switch field ("Address Visible") that you toggle manually, or you can use custom code that compares the current date against the Address Reveal Date field.

With Trellis, you manage the Address Reveal Date in Airtable. When the date arrives, Trellis can sync the updated visibility flag to Webflow automatically, eliminating the manual toggle.

Date Range Display

Estate sales are time-bound events. Displaying the date range clearly is critical for both SEO and user experience. Buyers need to see at a glance: when is the sale, what are the hours, and is there a discount schedule.

The Sale Dates companion collection lets you display this as a clean, scannable schedule rather than a blob of text. On the sale card (listing page), show a condensed range: "March 15-17, 2026." On the sale detail page, show the full schedule with hours and discount tiers.

For structured data (schema.org), each sale can be marked up as an Event with startDate and endDate, improving how it appears in Google search results. Buyers searching for "estate sales this weekend [city]" are more likely to see a rich result with dates and location.

EstateSales.NET Integration

EstateSales.NET is where estate sale buyers go first. Most companies list their sales there because that is where the audience is. A branded website does not replace EstateSales.NET — it complements it.

The integration pattern is straightforward: your sale listings on your website include a link to the corresponding EstateSales.NET listing (the URL field on the Sales collection). Buyers who find you through Google land on your branded site. Buyers who find you on EstateSales.NET see your professional listing there. Both channels work together.

With the Trellis EstateSales.NET connector, you can sync sale data bidirectionally. Create a sale in your Airtable, and Trellis pushes it to both your Webflow website and your EstateSales.NET listing. Photos, dates, descriptions, and categories stay in sync across all channels. You manage your sales in one place.

How Trellis Generates the Entire Structure

Setting up this CMS architecture manually takes hours. You need to create the collections, define every field with the right type, set up the references between collections, and then populate test data to verify the structure works before you start designing.

Trellis generates the entire architecture in minutes. Tell it you are building an estate sale website, and it creates the Sales, Sale Photos, Sale Dates, and Categories collections in both Airtable and Webflow with the correct field types, references, and naming conventions. The companion photo pattern, the date range structure, the address privacy fields — all set up automatically.

From there, you manage your sales in Airtable — adding photos by dragging them in, setting dates with a calendar picker, writing descriptions in a familiar spreadsheet interface — and Trellis keeps your Webflow site in sync. When you add a new sale in Airtable, it appears on your website. When you update a description or add photos, the changes sync automatically.

For a deeper look at the content architecture patterns for estate sale websites, read the Estate Sales CMS Architecture wiki article.