Real Estate · SEO · Propertybase

SEO Audit Checklist for Propertybase Real Estate Websites

A step-by-step audit for brokerages that run Propertybase on Salesforce: what to check on the website, how to handle listing, sold and filter pages, what Google's documentation actually says about speed and structured data, and how to prove in Salesforce that organic search brings clients.

Key Takeaways

  • A real estate website SEO audit checks whether Google can crawl, render and index your pages, whether listing and area pages are worth ranking, whether the site is fast on phones, and whether search visits become leads in your CRM.
  • Propertybase is the CRM, not the website. Fixes to robots.txt, sitemaps, canonicals, redirects and page templates happen on the website platform, so find out who controls it before you start.
  • Listing pages need the most care: shared MLS listings duplicate other sites, sold listings disappear, and search filters can create endless URLs. Each has a clear rule in Google's own documentation.
  • There is no Google rich result for property listings. Use structured data that Google supports, such as your organisation, office and breadcrumbs, and make it match what the page shows.
  • An audit is finished only when organic enquiries reach Propertybase with their source intact, so you can report leads and closings from search in Salesforce.

A real estate website SEO audit is a structured check of everything that stops your brokerage's pages from being found, chosen and acted on in Google. For a brokerage running Propertybase on Salesforce, it covers the website and the CRM together: the pages buyers and sellers search for, the listing data that feeds them, and the leads they send back into Propertybase.

This checklist is for marketing leads, operations managers and Salesforce admins at growing and mid-market companies in real estate: brokerages, developers and agencies. It replaces our 2025 version of this article. Every technical rule links to Google's own documentation, every product detail links to the vendor's help centre, and the unsourced figures and examples from the earlier version are gone.

Section 01 · Short Answer

What Is a Real Estate Website SEO Audit?

It is a review of seven areas: crawling and indexing, listing page handling, JavaScript rendering, speed and mobile experience, structured data, on-page content and local signals, plus lead tracking into the CRM. Each area gets a pass, a fix or a "not applicable", with an owner and a way to prove the fix worked. The output is a prioritised list of changes, not a score.

Audit areaThe question it answersMain tool
Crawling and indexingCan Google reach and keep the pages you want in search, and skip the rest?Search Console Page indexing report
Listing pagesAre shared, sold and filtered listing URLs handled on purpose?A site crawl plus URL Inspection
JavaScript renderingDoes the content Google renders match what visitors see?URL Inspection live test
Speed and mobileDo real visitors on phones get a fast, stable page?Core Web Vitals report, PageSpeed Insights
Structured dataIs the markup valid, supported and true to the page?Rich Results Test
On-page and localDo titles, descriptions, images and office pages match what people search for?Search Console Performance report, Google Business Profile
Lead trackingDo organic enquiries reach Propertybase with their source?Google Analytics plus Propertybase and Salesforce reports

Search is where most buyers start. 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 in their search. Those two figures explain where an audit spends its time: on listing pages and on phones.

The same audit also covers Google's AI features. Google says there are no additional requirements for appearing in AI Overviews or AI Mode: a page must be indexed and eligible to show with a snippet, and normal SEO best practice applies. No special files or markup are needed.

How often should you run one?

Run a full audit once or twice a year, and a targeted one after any event that changes URLs or templates: a website redesign or platform move, a new IDX or listing feed, a change to how Propertybase sends data to the site, or a new language or market. Between audits, check the Page indexing and Core Web Vitals reports monthly.

Section 02 · How It Fits

Where Do You Fix SEO Issues on a Propertybase Website?

Mostly on the website platform, not in Propertybase. Propertybase is a real estate CRM built on Salesforce: it holds listings, contacts and inquiries, and it supplies listing data to the site. The site itself controls robots.txt, sitemaps, canonical tags, redirects, page templates and speed. The CRM side of the audit is data quality and lead capture.

Brokerages usually connect a website to Propertybase in one of three ways. Confirm which one you run before the audit, because it decides who can make each fix:

SetupWhat it isWho makes technical SEO fixes
Propertybase WebsitesWebsites powered by Boston Logic, described as "packed with SEO features", with website activity tracked inside PropertybaseThe website platform's settings and its support team
Your own site using WebListingsA developer pulls listing data and media from Propertybase through the Propertybase API and builds the pages on any CMSYour web developer, who controls everything
Front OfficeLone Wolf's web presence product, formerly Propertybase GO, sold separately from the Salesforce-based CRMThe Front Office platform

Listing data reaches Propertybase from your MLS. The industry standard for that feed is now the RESO Web API; RESO says the older RETS standard "has been deprecated and is no longer supported". If your feed still runs on RETS, plan the move with your MLS and integration partner, because a feed change usually changes listing URLs and page templates too, and that calls for a fresh audit. The diagram shows where each part of the audit sits.

1 MLS feed (RESO Web API) into Propertybase 2 Website builds listing and area pages 3 Google crawls, renders and indexes 4 Buyers and sellers arrive from search 5 Form creates a Contact and Inquiry with source 6 Salesforce reports leads and closings
Where the audit looks. Steps 2–4 are the website and Google; steps 1, 5 and 6 are Propertybase and Salesforce.
Section 03 · Crawling and Indexing

How Do You Check Crawling and Indexing on a Real Estate Website?

Start in Google Search Console's Page indexing report, then confirm robots.txt, noindex rules and sitemaps match your intent. The goal is not to get every URL indexed. Google says you should expect only canonical pages to be indexed, so the audit checks that the pages that matter are in, and that filter, sort and duplicate URLs are deliberately left out.

CheckWhat good looks likeGoogle's rule
robots.txtBlocks only low-value URL patterns, such as filter or sort parameters; never blocks scripts, styles or images pages needrobots.txt manages crawling and "is not a mechanism for keeping a web page out of Google"
noindexUsed on thank-you pages, saved-search and account pages, and any page you want out of resultsFor noindex to work, the page "must not be blocked by a robots.txt file"
XML sitemapsGenerated from the site's database, canonical URLs only, separate files for listings, areas and blog, under 50,000 URLs eachGoogle ignores priority and changefreq and uses lastmod only when it is consistently accurate
Sitemap submissionSubmitted in Search Console and named in robots.txtSubmitting a sitemap is "merely a hint", not a guarantee
Status codesLive pages return 200, retired pages return 301, 404 or 410 on purpose, and no "not found" page returns 200A friendly error page that returns 200 is a soft 404

Reading the Page indexing report

The report lists why URLs are not indexed. Four reasons cause most of the confusion on listing-driven sites:

  • Crawled – currently not indexed. Common, and Google says it "doesn't necessarily indicate an issue". Look for patterns: if area guides or office pages sit here, they may be too thin or too similar to each other.
  • Discovered – currently not indexed. Google found the URL but has not crawled it yet. A large and growing number usually means filter and parameter URLs are flooding the crawl (Section 04).
  • Duplicate without user-selected canonical. Google picked a different canonical than you expected. Check whether your listing and area templates output a canonical tag at all.
  • Indexed, though blocked by robots.txt. The page is in results without a description. If you want it out, remove the robots.txt block and add noindex instead.

For any single page, use the URL Inspection tool. It shows the version Google indexed, the canonical Google selected, and, in a live test, a screenshot of the rendered page and the resources it loaded. Check one URL of each template: home, listing, sold listing, search results, area guide, agent and blog.

Section 04 · Listing Pages

How Should Listing, Sold and Search Filter Pages Be Handled?

Treat each type of listing URL as a decision. Active listings should be indexable with content of their own. Sold or withdrawn listings should redirect to a relevant live page or return 404 or 410, never a friendly error page that returns 200. Search filter URLs should mostly be kept out of the crawl. Area and building pages should carry your ranking effort.

Active listings

Index

Goal: one canonical URL per listing, with something no other site has.

An MLS listing appears on every participating broker's site, so the photos and the standard description are the same everywhere. Google consolidates duplicate URLs and chooses one to show, and a page with nothing extra has little reason to be chosen. Add what only you know: agent remarks, nearby schools and transport from your area guide, a link to the building or development page. Make sure each listing has one URL, without tracking parameters or alternate paths, and that its canonical tag points to itself.

Sold and withdrawn listings

Redirect or retire

Goal: no dead ends and no soft 404s.

When a listing is retired and a closely related page exists, such as the building, development or neighbourhood page, use a permanent 301 redirect; Google treats a 301 as a strong signal that the target should be processed instead. When no relevant page exists, return 404 or 410: Google's crawl budget guide recommends exactly that for permanently removed pages. Redirecting every sold listing to the home page sends visitors and Google somewhere unrelated, and a "this property is no longer available" page that returns a 200 status is a soft 404. Some brokerages keep sold pages live as a record of their track record; if you do, make the page say clearly that it sold and link to similar active listings.

Search filter and sort URLs

Mostly block

Goal: stop filters from creating endless URLs.

Price, bedroom, area and sort filters on a property search page can combine into millions of URLs. Google's guide to faceted navigation says these "can generate infinite URL spaces", which leads to overcrawling and slower discovery of new listings. If filter results don't need to rank, block those parameters in robots.txt or use URL fragments. Google calls canonical and nofollow "generally less effective in the long term" for this job. If a few filter combinations should rank, such as "2-bedroom apartments in a named area", give them clean, consistently ordered URLs and return 404 for combinations with no results.

Area, building and development pages

Invest here

Goal: stable pages that rank for the searches listings can't.

Listings come and go; area guides, building pages and development pages stay. They are where you can show local knowledge and where retired listings can redirect. Write them from your agents' experience and keep them few and useful: Google's helpful content guidance asks for "original information, reporting, research, or analysis", and hundreds of near-identical suburb pages work against you.

Most brokerage sites don't need to worry about crawl budget itself. Google's guide is aimed at sites with more than a million pages, or more than 10,000 pages that change daily, and says that for smaller sites keeping the sitemap current and checking the Page indexing report "is adequate". A large multi-market portal with a full MLS feed can cross those lines, which is when the filter rules above matter most.

Section 05 · Rendering

Can Google See Listings Loaded by JavaScript?

Usually, but not always quickly, and not if the page is built carelessly. Google crawls, then renders JavaScript, then indexes, and a page can wait in the rendering queue. Listing search tools and map views often load content with JavaScript, so the audit checks that the rendered page contains the listing text and links, and that every listing is reachable through a normal link.

Google's JavaScript SEO basics set out what to check:

Content in the rendered HTML

Run a live test in URL Inspection on a listing page. If the price, description or address is missing from the rendered HTML, Google can't index it.

Real links to every listing

Google can only follow <a> elements with an href. Map pins and "load more" buttons that use click handlers alone leave listings undiscoverable.

Clean URLs, not fragments

Single-page search apps should use the History API for real URLs. Google generally doesn't crawl URL # fragments as separate pages.

Canonical and noindex in the HTML

Keep one canonical tag and don't change it with JavaScript. If the HTML says noindex, Google may skip rendering, so removing it with a script may not work.

Server-side rendering, not dynamic rendering

The 2025 version of this article recommended dynamic rendering. Google now says dynamic rendering "was a workaround and not a long-term solution" and recommends server-side rendering, static rendering or hydration instead. Google also notes that server-side or pre-rendering "is still a great idea", because it makes the site faster for users and for crawlers that can't run JavaScript. If your listing pages are rendered only in the browser, that is a conversation for your website platform or developer.

Section 06 · Speed and Mobile

How Do You Audit Page Speed and Mobile Experience?

Use field data from real visitors, judged against Google's Core Web Vitals thresholds, and check the mobile version first. Google indexes and ranks the mobile version of your site, so listing pages must show the same content, structured data and metadata on phones as on desktop. Photo-heavy listing pages are where speed problems usually show up.

MetricMeasuresGoodPoorCommon cause on listing pages
LCP (Largest Contentful Paint)Loading≤ 2.5 s> 4 sAn oversized hero photo or a slow listing data call
INP (Interaction to Next Paint)Responsiveness≤ 200 ms> 500 msHeavy map, gallery or chat scripts
CLS (Cumulative Layout Shift)Visual stability≤ 0.1> 0.25Images, banners or widgets without reserved space

The thresholds come from web.dev and are measured at the 75th percentile of page loads; INP replaced First Input Delay as a Core Web Vital in 2024. The Search Console Core Web Vitals report uses real-user data, groups similar URLs (so all listing pages tend to pass or fail together), and leaves out groups without enough traffic. Use PageSpeed Insights or Lighthouse to diagnose one page, remembering that lab tests can't measure INP.

Keep speed in proportion

Google says there is no single page experience signal, that good scores don't guarantee top rankings, and that chasing a perfect score "just for SEO reasons may not be the best use of your time". Its page experience checklist asks about Core Web Vitals, HTTPS, mobile display, excessive ads, intrusive pop-ups and clear main content. It doesn't ask for any particular page format, so the AMP recommendation in our earlier version has been dropped.

Mobile checks

  • The mobile version has the same listing text, headings, structured data, title and meta description as desktop.
  • Primary content doesn't load only after a tap, swipe or typing; Google won't trigger those.
  • Gallery images use the same alt text and stable URLs on mobile and desktop.
  • Lead forms work on a phone and aren't hidden behind a full-screen pop-up.
Section 07 · Structured Data

Which Structured Data Helps a Real Estate Website?

Markup for the rich results Google actually supports: Organization, LocalBusiness (with the RealEstateAgent type for offices), BreadcrumbList, Article for guides, and Event for open houses or launches you publish as events. Google's search gallery has no rich result for property listings, so listing markup won't produce price-and-photo snippets, whatever a plugin promises.

Worth adding. Organization on the home page with your logo and profiles; LocalBusiness on each office page, using the most specific type, RealEstateAgent; BreadcrumbList across the site; Article on guides and market reports; Event for public events you list. All of these appear in Google's search gallery.

Don't expect much from it. Schema.org's RealEstateListing type is valid vocabulary and can describe a listing page, but no Google rich result uses it, and schema.org still places it in its "new" area. Add it if your platform does so cleanly; don't count it as an SEO win. Vacation rental markup is for holiday rental listings only.

Google's structured data policies set three rules an audit checks. Mark up only content that is visible on the page. Never mark up misleading content, such as a price or status the page doesn't show. And use JSON-LD where you can. Breaking the rules can bring a manual action that removes rich result eligibility, and even valid markup is not guaranteed to show. Test one page per template in the Rich Results Test, and recheck after any feed or template change, because listing markup that drifts from the visible price is a common fault on data-driven sites.

Section 08 · On-Page

What On-Page Elements Should a Real Estate SEO Audit Check?

Titles, meta descriptions, headings, images and, for multilingual sites, language tags. On a listing-driven site these are generated by templates, so the audit fixes the template rather than individual pages. A good template builds a unique, specific title and description from listing fields, and never repeats the same boilerplate on hundreds of pages.

ElementTemplate rule for listing and area pagesSource
TitleProperty type, bedrooms, street or building and area, then the brokerage name; no keyword stuffing and no repeated boilerplateTitle links
Meta descriptionGenerated from listing fields (price, size, key features, area) so every page is unique; Google encourages programmatic descriptions on "larger database-driven sites"Snippets
H1 and headingsOne H1 that matches the title's intent; headings for features, location and agentSearch Essentials
ImagesPhotos in <img> elements, not CSS backgrounds, which Google doesn't index; descriptive file names and alt text; a fallback src with srcset; an image sitemap if photos sit on a CDNImage SEO
Language versionshreflang on every translated page, each version listing itself and all others, with x-default for a language selectorLocalized versions

Language versions matter for brokerages that sell to international buyers, for example an English and Arabic site in the UAE or a site with pages for overseas investors. Google ignores hreflang tags unless the pages point to each other, so a single missing return link breaks the pair. Pick one method for the tags: HTML, HTTP headers or the sitemap.

Then compare templates with demand. The Search Console Performance report shows the queries each page already appears for. If area pages show impressions for "homes for sale in" searches but few clicks, the title and description are the first things to rewrite.

Section 09 · Local

How Does Local SEO Fit into the Audit?

Check that every office has an accurate Google Business Profile linked to its own office page, and that the office page carries the same name, address and phone number with LocalBusiness markup. Google ranks local results mainly on relevance, distance and prominence, and prominence reflects links and reviews, so office pages are worth the effort.

  • One page per office, with its address, hours, team and the areas it covers, linked from the matching Google Business Profile.
  • Consistent details. The office name, address and phone number match across the profile, the office page and its RealEstateAgent markup.
  • Agent pages linked from their office page, with stable URLs that don't change when an agent moves.
  • Links that point to these pages. Our guide to building quality backlinks for a Propertybase website covers how to earn them within Google's rules.

Keep the Business Profile current for another reason too: Google's guidance on AI features asks site owners to keep Business Profile information up to date.

Section 10 · CRM Tracking

How Do You Connect SEO Results to Leads in Propertybase and Salesforce?

Make sure every website form sends its lead source and landing page into Propertybase, then report organic leads and closings in Salesforce. Search Console shows clicks and Google Analytics shows sessions, but only the CRM shows which pages produced clients. Without that link, the audit can prove a page ranks but not that it pays.

Layer 1 — Google

Search Console

Impressions, clicks and queries per page. AI Overviews and AI Mode traffic is counted here too, under the "Web" search type.

Layer 2 — Website

Google Analytics

Organic sessions and form submissions by landing page. Use UTM parameters on links you control, such as email and portals, so they don't blur the organic numbers.

Layer 3 — CRM

Propertybase and Salesforce

Front Desk captures website leads through webforms, the WebToProspect REST API or JSON and XML email. Pass the lead source, landing page and channel into fields that are never overwritten by later activity, then report leads, appointments and closings from organic search. With a Propertybase Website, website activity is also tracked inside Propertybase.

The CRM half of the audit asks four questions. Does every form, including the listing enquiry, valuation and contact forms, reach Propertybase? Does each record show the page it came from? Are duplicates merged rather than recreated? And can a manager run one report of organic leads to closings without exporting anything? Our post on real estate SEO with Propertybase and Salesforce integration goes further into lead capture and attribution. If the website and CRM aren't connected cleanly, that is a Propertybase integration job rather than an SEO one.

Section 11 · Checklist

The Complete SEO Audit Checklist for Propertybase Websites

Work through these checks in order: foundations first, then templates, then measurement. Fixing listing titles is wasted effort if Google can't crawl the listings, and growth in organic traffic can't be judged until leads carry their source. Assign each check to the website owner, the marketing team or the Salesforce admin before you begin.

#CheckOwner
1Confirm the website setup (Propertybase Website, WebListings site or Front Office) and who can change templates, redirects and robots.txtMarketing
2Verify the site in Search Console, including every subdomain and language versionWebsite
3Review robots.txt: no blocked scripts, styles or images; filter and sort parameters blocked if they shouldn't rankWebsite
4Check noindex on thank-you, account and saved-search pages, and that none of them is also blocked in robots.txtWebsite
5Confirm XML sitemaps are generated automatically, list canonical URLs only, and are submittedWebsite
6Review the Page indexing report for patterns by templateMarketing
7Run URL Inspection on one URL per template and compare the rendered page with what visitors seeMarketing
8Check that each listing has one URL with a self-referencing canonical tagWebsite
9Set the sold and withdrawn listing rule: 301 to a relevant page, or 404/410; no soft 404sWebsite
10Check that every listing is reachable through an <a href> link, not only through a map or scriptWebsite
11Confirm listing content is server-rendered or pre-renderedWebsite
12Review Core Web Vitals field data for listing, search and area templatesWebsite
13Compare mobile and desktop versions for content, markup and metadataWebsite
14Fix title and meta description templates so every listing and area page is uniqueMarketing
15Check image delivery: <img> elements, alt text, file names, image sitemap if on a CDNWebsite
16Validate structured data per template in the Rich Results Test, and check it matches the visible pageWebsite
17Check hreflang return links on every language versionWebsite
18Match each Google Business Profile to its office page and detailsMarketing
19Review area and building pages for thin or near-duplicate contentMarketing
20Test every website form end to end into Propertybase, with lead source and landing pageSalesforce admin
21Build a Salesforce report of organic leads to appointments and closingsSalesforce admin
22Record a baseline and schedule the next audit and monthly report checksMarketing

The earlier version of this post had a five-point "Twopir-proven checklist": test page speed, validate schema, crawl for duplicate URLs, check robots.txt and verify form tracking. All five are still here, as checks 3, 8, 12, 16 and 20.

Section 12 · Pitfalls

What SEO Audit Mistakes Should Real Estate Websites Avoid?

Most problems come from using the right tool for the wrong job: robots.txt to remove pages, redirects to hide sold listings, markup to chase snippets that don't exist, and scores in place of leads. Each one either hides pages you want found or spends effort where Google's documentation says it won't pay off.

1. Blocking pages in robots.txt to remove them. Blocked pages can still be indexed if other sites link to them, just without a description. Use noindex, and leave the page crawlable so Google can see it.
2. Hiding sold listings badly. A blanket redirect to the home page helps nobody, and a "no longer available" page that returns 200 is a soft 404. Redirect only to a closely related page, or return 404 or 410.
3. Letting search filters run free. Endless filter and sort URLs slow the crawl of new listings. Block the parameters you don't want indexed instead of relying on canonical tags alone.
4. Expecting listing rich results. Google has no property listing rich result. Spend markup effort on Organization, LocalBusiness, BreadcrumbList and Article, and keep it true to the page.
5. Chasing a perfect speed score. Fix poor Core Web Vitals in field data, especially on mobile listing pages, then stop. Google says good scores don't guarantee rankings.
6. Publishing a page per suburb from one template. Hundreds of near-identical area pages read as scaled content, not local knowledge. Fewer, better guides do more.
7. Auditing traffic but not leads. If organic enquiries lose their source between the website and Propertybase, you can't tell which fixes paid off. Test the forms as part of every audit.
Section 13 · Bottom Line

The Bottom Line

An SEO audit for a Propertybase website is a website audit and a CRM audit in one. Google's own documentation answers almost every technical question, from robots.txt to sold listings to Core Web Vitals, and none of the fixes need guesswork. What makes the audit worth running is the last step: proving in Salesforce that the pages you fixed bring buyers and sellers.

  1. 1

    Find out who controls your website's templates, redirects and robots.txt before you start.

  2. 2

    Use the Page indexing report and URL Inspection to check one URL of every template.

  3. 3

    Set clear rules for active, sold and filtered listing URLs.

  4. 4

    Fix Core Web Vitals in field data, on mobile first, and use only supported structured data.

  5. 5

    Finish by tracing organic enquiries into Propertybase and reporting them to the closing.

Ready to Start

Find Out Where Your Organic Leads Get Lost

On a 30-minute discovery call, a Twopir Salesforce architect will trace an enquiry from your website into Propertybase, show you where the source or the lead drops out, and tell you which fixes to make first.

Schedule a Discovery Call

FAQ

Frequently Asked Questions

Crawling and indexing, the handling of active, sold and filtered listing URLs, JavaScript rendering, Core Web Vitals and mobile experience, structured data, titles and descriptions, local signals such as Google Business Profile, and lead tracking into the CRM. Each check ends with a pass, a fix with an owner, or not applicable.

Partly. Propertybase is a real estate CRM built on Salesforce, so robots.txt, sitemaps, canonical tags, redirects and page templates are controlled by your website platform. Propertybase Websites, powered by Boston Logic, include SEO features; a custom site using the Propertybase API is controlled by your developer.

Redirect a sold or withdrawn listing with a 301 to a closely related live page, such as its building or neighbourhood page, or return a 404 or 410 if nothing relevant exists. Avoid redirecting everything to the home page and avoid "no longer available" pages that return a 200 status, which Google reports as soft 404s.

Shared MLS listings appear on many brokers' sites, and Google picks one version to show rather than penalising the rest. To give your version a reason to be chosen, add content only you have, such as agent remarks and local context, and keep one canonical URL per listing.

No. Google's search gallery has no rich result for property listings. Structured data still helps Google understand your business: use Organization, LocalBusiness with the RealEstateAgent type, BreadcrumbList and Article, keep it matched to the visible page, and test it in the Rich Results Test.

Yes. Google says there are no additional requirements for its AI features: a page must be indexed and eligible to show with a snippet, and normal SEO best practices apply. Accurate structured data and an up-to-date Business Profile also help. AI feature traffic appears in Search Console under the Web search type.

Run a full audit once or twice a year, and a targeted audit after any change that affects URLs or templates: a redesign, a new listing feed or IDX provider, a change in how Propertybase feeds the site, or a new language or market. Check the Page indexing and Core Web Vitals reports monthly.

TC

Twopir Consulting

Salesforce Partner · HubSpot Partner

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 lead capture integrations, and marketing operations for real estate businesses.