Boost Real Estate SEO with Propertybase and Salesforce: From Search Click to Closing
SEO wins the click. What happens next decides whether it was worth it. This guide shows how to connect your website to Propertybase so every organic enquiry arrives with its source, reaches an agent fast, and can be traced to the closing it produced.
Key Takeaways
- Propertybase doesn't rank your pages. It makes SEO measurable and profitable by turning each organic enquiry into a Contact and Inquiry with its source attached, then tracking it to the closing.
- Capture the source at the form: Propertybase webforms accept hidden fields for lead source, landing page and campaign parameters. The WebToProspect REST API adds data clean-up, custom duplicate logic and Classic support.
- You can't see the Google search term behind each lead. Store the landing page instead, and join it to Search Console's page-level query data to see which searches feed the pages that close deals.
- Speed is where SEO leads are lost. Use Lead Router to assign them and a Salesforce Flow scheduled path to escalate any that nobody contacts in time.
- Your listing data drives your listing pages. Keep it complete, synced and accurately dated in sitemaps, and treat structured data as a description of the page, not a ranking promise.
Real estate SEO with Propertybase and Salesforce is about what happens after someone finds you on Google. Search brings a buyer to a listing or neighbourhood page. Propertybase, the real estate CRM built on Salesforce, decides whether that enquiry is recorded with its source, reaches the right agent quickly, and shows up in a report next to the commission it earned.
This guide is for marketing leads, operations managers and Salesforce admins at growing and mid-market companies in real estate: brokerages, developers and agencies that already invest in SEO and run Propertybase. It covers the lead flow, the capture options, attribution that holds up, routing, listing data and the dashboard that ties them together. Every product detail links to the vendor's own documentation.
How Does Propertybase and Salesforce Integration Help Real Estate SEO?
It closes the loop between search traffic and revenue. Your website earns the ranking. The integration makes sure each organic enquiry lands in Propertybase as a Contact and Inquiry carrying its source and landing page, is routed to an agent within your service level, and can be reported all the way to the closing. That tells you which pages deserve more SEO investment.
Search matters in this market. In the National Association of REALTORS® 2025 Profile of Home Buyers and Sellers, 52% of US buyers found the home they bought online, and 70% used a mobile or tablet device during the search. The same survey found that 88% of buyers used an agent or broker. Buyers search online and then hand the deal to a person, so the hand-off from website to agent is where SEO pays off or leaks away.
What the integration does: records every organic enquiry with its source and landing page, links it to the listings the visitor viewed, routes it to an agent, and lets you report organic leads through showings, offers and closings in Salesforce.
What it doesn't do: it won't raise your rankings by itself. Content, page speed, links and accurate listing pages still do that. Nor can it tell you the exact Google search term behind each lead, as Section 04 explains.
How Does an Organic Lead Flow From Google Search to a Propertybase Closing?
In seven steps, and each one is a place to lose data or time. A search query leads to a page, the page's form creates Propertybase records, automation routes and follows up, and the deal moves through showings, offers and closings. Attribution only works if the source captured at step three survives to step seven.

pba__Request__c) with the search criteria, and adds Linked Listings for the properties the visitor asked about.For the full object model behind these steps, see our guide to Propertybase Salesforce CRM architecture.
Which Propertybase Lead Capture Method Should Your Website Use?
Use Propertybase Webforms if you want the fastest setup, and the WebToProspect REST API if your developers need control. Both create Contacts, Inquiries and Linked Listings from your website. Webforms are simpler but pass data through as it is. The API lets you clean data, apply your own duplicate logic and work with Propertybase Classic.
Propertybase's Front Desk offers four ways to capture website leads:
| Method | Best for | Strengths | Watch out for |
|---|---|---|---|
| Propertybase Webforms Fastest | Brokerage sites on Propertybase Lightning with a standard enquiry form | Quick to set up; maps form fields to any Contact, Inquiry or Listing field; supports hidden values | Lightning only; no way to modify incoming data; validation must happen in the browser |
| WebToProspect REST API Most control | Custom sites, multi-step forms, sites that need data clean-up | Modifies incoming data, supports custom plugins and duplicate logic, works with Lightning and Classic | Needs web development and Propertybase webservices; each call counts toward your Salesforce API limit |
| JSON-to-Email webforms | Sources that can only send leads by email | Works with Lightning and Classic; structured data in an email body | Depends on email formatting staying consistent |
| XML-to-Email webforms | Older sources that send XML by email | An alternative when the other methods aren't possible | Same email-format dependency |
What Propertybase Webforms give an SEO team
Once Front Desk is enabled, you embed the form from Control Center and add fields by their API names, such as contact[Phone] for the Contact or request[pba__City_pb__c] for the Inquiry. Three features matter most for SEO:
- Hidden values. Propertybase's own example sets
contact[LeadSource]to "Website" and sends the page address to the Inquiry'spba__WebsiteSearchUrl_pb__cfield. A short script can read the page URL and its parameters and submit them the same way. - Linked Listings. Pass the listing's external ID in
favorite_unique_ids[], matched on a field such aspba__Broker_s_Listing_ID__c, and the enquiry is linked to the exact listing page the buyer came from. - Duplicate check by email. Webforms check for an existing Contact only when the form includes an email field. Without one, every submission creates a new Contact.
When to step up to the WebToProspect API
The WebToProspect REST API takes a JSON payload with a contact map, a request (Inquiry) map and a list of favourite listings, and can set the record owner directly. It suits sites with multi-step forms, valuation tools or saved searches, where your developers want to normalise phone numbers, map campaign values or check for duplicates by an external ID before the record is written. Propertybase notes that its older requestFromListing option was deprecated in April 2021: send favourite listings instead, and enrich the Inquiry with automation once it is in Salesforce.
If your site also feeds a CRM from other systems, our Propertybase API integration team designs the capture layer so every source writes the same fields.
How Do You Track Which SEO Pages Produce Closings in Salesforce?
Record the first source and landing page on the Contact and Inquiry, carry them to the deal, and compare them with Search Console by page. Salesforce can then answer the question that matters: which pages and topics produce closings, not just traffic. Store first-touch values once and never overwrite them; keep latest-touch values in separate fields.
Why "the keyword behind each lead" isn't available
Many SEO-to-CRM guides promise a lead record tagged with the search term that found it. For organic search, that is not how the data works. Google's campaign URL guidance defines the utm_term parameter as the paid keyword, and Search Console reports organic queries in aggregate, by site or by page, not by visitor. So capture the landing page on every lead, and use it as the join key: Search Console tells you which queries reach a page, and Salesforce tells you which leads and closings that page produced.
Fields worth capturing
| Field | Where to store it | How it is filled | What it answers |
|---|---|---|---|
| Lead Source | Contact (standard LeadSource) | Hidden form value, such as "Website" | How much business the website produces overall |
| Landing page URL | Inquiry (pba__WebsiteSearchUrl_pb__c or a custom field) | Script reads the page address on submit | Which pages and topics produce leads and closings |
| Channel (organic, paid, email, portal) | Custom fields on Contact and Inquiry | Script reads utm_source, utm_medium and utm_campaign; no parameters plus a search-engine referrer means organic | Organic versus paid versus portal performance |
| Listing viewed | Linked Listing | favorite_unique_ids[] or the API's favourite listings | Which listing pages turn into enquiries |
| First-touch fields | Contact, written once | A flow fills them only when they are blank | Which channel first brought a buyer who later closed |
Follow Google's advice on campaign parameters: always set source, medium and campaign, and keep values in one consistent lowercase convention, because the values are case-sensitive and "Email" and "email" report as two sources. The same discipline keeps your Salesforce picklists clean.
How Fast Should Organic Leads Reach an Agent, and How Do You Enforce It?
Set a response time, assign every lead automatically, and escalate any lead that misses it. Propertybase's Lead Router handles assignment. A Salesforce Flow scheduled path watches the clock and reassigns or alerts a manager when no contact is logged in time. The right target depends on your market, but it should be measured in minutes, not hours.
Lead Router sets the Contact's Routing Source when new Contacts and Inquiries arrive, which assigns the lead to a Team. The team's Distributor then picks the agent by Click to Claim, Auto-Assign or Round Robin. Two behaviours affect SEO leads in particular:
- Returning leads skip routing. An existing contact who enquires again goes to the previous owner, and Propertybase says this is not configurable. Your escalation flow must cover owners who have left or stopped responding.
- Text alerts are regional. Agents can be alerted by Chatter or text message, but text alerts work only in North America and Australia, and agents must opt in.
To enforce the response time, add a record-triggered flow on the Inquiry with a scheduled path timed from creation. If no call or email is logged when the path runs, it can reassign the lead, notify the team lead, or both. Our guide to advanced Propertybase workflows covers this SLA clock step by step.
What this looks like in practice: for a residential brokerage with more than 120 agents, Twopir Consulting built three-tier Flow routing by geography, property type and agent capacity. The published case study reports that lead response went from 4–6 hours to under 15 minutes.
How Does Propertybase Listing Data Affect Your Website's SEO?
Your listing pages are only as good as the listing records behind them. When Propertybase is the source for your website and portal feeds, missing photos, stale prices and sold homes still marked active all reach the page. Keep the records complete, publish changes promptly, date them accurately in your sitemap, and describe each page with structured data that matches what visitors see.
One source of listing truth
Every Propertybase Listing creates a matching Property record and keeps the two in sync. Feed your website from the Listing, not from a spreadsheet copy.
Controlled syndication
Portal Syndication publishes listings to portals from Control Center, and Auto Publish sends only listings marked "Allowed for Auto Publish".
Accurate sitemap dates
Google uses a sitemap's lastmod only when it is consistently accurate. Set it from the listing's last real change, such as price, status or photos.
Honest structured data
Schema.org has a RealEstateListing type. Google doesn't guarantee markup appears in results, and only visible content should be marked up.
Two myths worth dropping
- "Push new listings to Google's Indexing API." Google says the Indexing API can only be used for job posting and livestream video pages. For listings, rely on accurate sitemaps and good internal links.
- "Portal copies will outrank us anyway." When the same text appears in several places, Google chooses one canonical URL. Give your own listing pages something portals don't have: your own description, neighbourhood context, agent expertise and related listings. That is the kind of people-first content Google says it rewards.
A data quality gate before a listing goes live
A validation rule can stop a listing being marked "Allowed for Auto Publish" until its price, photos, description and address fields are complete. Validation rules apply to every save, including integrations, so test them in a sandbox first. For listing copy, keep a human review step: in the US, HUD states that the Fair Housing Act applies to the advertising of housing, and other markets have their own advertising rules.
What this looks like in practice: for Sotheby's International Realty (UAE), Twopir Consulting built an Apex REST endpoint that serves live listing XML to external property sites, replacing manual uploads. For another luxury brokerage in Dubai, we built direct Zoopla and Rightmove integrations with Publish, Check Status and Unpublish actions on the record.
What Should a Real Estate SEO-to-Closing Dashboard Show?
Six numbers per page or topic: organic leads, response time, showings, offers, closings and Search Console clicks. Together they show where SEO creates revenue and where it stalls. A page with many clicks and few leads needs a better form or offer. A page with many leads and few showings points to follow-up, not SEO.
| Metric | Source | What a weak number usually means |
|---|---|---|
| Clicks and impressions by page | Search Console | Weak rankings or titles; an SEO content task |
| Organic leads by landing page | Salesforce report on Inquiries | Weak form, call to action or page intent |
| Median time to first contact | Inquiry created date versus first logged activity | Routing or agent capacity problem |
| Leads to showings | Showings linked to organic contacts | Qualification or matching problem |
| Offers and closings by first source | Offers and Closings joined to the Contact | The true value of each channel and page group |
Send the report to the people who act on it. Salesforce report subscriptions email refreshed results on a schedule, so the marketing lead and sales manager see the same numbers each week. Our post on Propertybase reports in Salesforce covers report types and dashboards in more detail.
What Mistakes Break SEO Lead Tracking in Propertybase?
Most failures are small configuration choices that quietly lose data. Forms without an email field create duplicates, overwrite settings erase good data, private sharing hides existing contacts from the webservice, and old Process Builder automation stops getting fixes. Check these six before you trust any SEO report.
contact[Email]. Without it, every enquiry from a returning buyer becomes a new Contact, and attribution splits across records.Where Should a Brokerage Start?
Start with the fields, then the forms, then the automation, then the dashboard. Mapping what you will capture comes first, because every later step depends on it. Most brokerages can get trustworthy SEO-to-closing reporting in a few focused phases, built and tested in a sandbox before anything touches live leads.
For the SEO side of the work, our SEO audit checklist for Propertybase websites and our guide to high-intent keyword strategies cover content, technical checks and keyword choice.
The Bottom Line
SEO brings buyers to your website; Propertybase and Salesforce decide whether those visits become measurable revenue. Capture the source at the form, protect it from duplicates and overwrites, get every lead to an agent within minutes, keep listing data clean, and report organic leads all the way to the closing. Then you can invest in the pages that actually sell homes.
- 1
Capture lead source and landing page as hidden values on every Propertybase form.
- 2
Use the landing page, not the keyword, to join Salesforce results with Search Console.
- 3
Keep first-touch fields write-once and duplicate behaviour on enrich.
- 4
Assign with Lead Router and escalate with a Flow scheduled path.
- 5
Treat listing records as SEO assets: complete, synced and accurately dated.
Connect Your Website to Propertybase the Right Way
On a 30-minute discovery call, a Twopir Salesforce architect will trace an organic enquiry through your website forms and Propertybase org, show you where source data or response time is lost, and tell you what to fix first.
Schedule a Discovery CallFrequently Asked Questions
No. Propertybase is a real estate CRM built on Salesforce, and rankings still come from your website's content, speed, links and listing pages. What the integration adds is measurement and follow-up: each organic enquiry lands as a Contact and Inquiry with its source, reaches an agent quickly, and can be reported through to the closing.
Not for organic search. Search Console reports queries in aggregate, by site or by page, and Google's campaign guidance defines the utm_term parameter as the paid keyword. Capture the landing page on each Inquiry instead, then compare it with Search Console's query data for that page to see which searches lead to closings.
Propertybase Webforms are the fastest option on Propertybase Lightning and support hidden values for lead source and landing page. Choose the WebToProspect REST API when developers need to clean incoming data, apply custom duplicate logic or support Propertybase Classic. JSON-to-Email and XML-to-Email webforms suit sources that can only send leads by email.
Include an email field, because Propertybase Webforms only check for duplicates by email. With the WebToProspect API, keep the default enrich behaviour and choose identification by external ID, email or phone. If Contacts are private, share them with the webservice user through a public group, and add Salesforce duplicate rules as a second check.
You can describe listing pages with schema.org's RealEstateListing type in JSON-LD, but Google doesn't guarantee that structured data appears in search results. Mark up only what visitors can see on the page, and generate the markup from the Propertybase Listing record so price and status stay in step with the page.
Feed your website from the Propertybase Listing record, update pages as soon as price, status or photos change, and set each page's sitemap lastmod date from that real change, because Google only trusts lastmod when it is consistently accurate. Google's Indexing API is limited to job posting and livestream pages, so it isn't an option for listings.
Within minutes, not hours. Let Propertybase Lead Router assign each new lead to a team and agent, then add a Salesforce Flow scheduled path that reassigns the lead or alerts a manager if no contact is logged in time. In one published Twopir Consulting case study, lead response went from 4 to 6 hours to under 15 minutes.
Twopir Consulting
Twopir Consulting helps growing and mid-market companies solve complex CRM, integration, and business system challenges. We implement, rescue, optimize, and integrate complex CRM and revenue systems, including Propertybase implementations, website and portal integrations, and automation for real estate businesses in the US, UK, UAE, Australia and Canada.