A brokerage should not scale location or market content until listing discovery, canonicalization, status handling, and internal links are understood. Use the following items as pass/fail checks. The source version included a previously published 70 percent mobile-access statement without a supporting source URL; preserve it only as historical context pending source reconciliation.
IDX crawl and renderability
Evidence required: Inspect representative listing, search-result, property-type, and pagination URLs in Google Search Console and a crawler. Confirm what HTML is available, whether important content depends on blocked resources, and whether canonical directives match the intended indexable URL.
Pass condition: Search engines can reach the intended public listing URLs, important page content is available after normal rendering, and the pages are not unintentionally blocked, canonicalized elsewhere, or isolated from internal navigation.
Fail condition: Listings exist only inside an experience that is blocked, inaccessible to normal crawling, duplicated under conflicting URLs, or disconnected from the brokerage's crawl paths. Severity: Critical when important inventory and market paths are systematically inaccessible; otherwise High.
Owner: Technical SEO lead with the website or IDX implementation owner. Corrective action: Fix crawl barriers, rendering dependencies, canonical conflicts, or URL routing at the template level. Do not assume that moving content to a particular host or rendering method automatically creates ranking value.
Validation step: Re-crawl the affected templates, inspect representative live URLs, and confirm the intended pages can be discovered and indexed without relying on a manual URL submission workflow.
Structured data accuracy
Evidence required: Compare any property or organization structured data against visible page content and the vocabulary actually supported by the chosen schema type. Use Schema.org and Validator.schema.org for syntax and vocabulary checks where appropriate.
Pass condition: Structured data reflects visible facts, uses valid properties, and does not describe content or relationships that the page does not support. Fail condition: Markup contains stale prices, incorrect addresses, unsupported properties, fabricated relationships, or data that conflicts with the visible page.
Severity: Medium, or High when inaccurate markup affects material business or property information. Owner: Technical SEO lead with the developer responsible for templates. Corrective action: Remove unsupported properties, synchronize structured data with the visible source of truth, and keep markup limited to facts the brokerage can substantiate.
Validation step: Re-run validation after deployment and manually compare the rendered markup with the live page. Treat structured data as machine-readable context, not as a guaranteed rich-result or ranking mechanism.
XML sitemap quality
Evidence required: Compare submitted sitemap URLs with crawlable, canonical, indexable URLs and current inventory status. Review whether stale, redirected, duplicate, or parameterized URLs are being submitted.
Pass condition: Sitemaps contain the canonical URLs the brokerage actually wants search engines to discover and are regenerated when inventory or page status changes. Fail condition: Sitemaps repeatedly submit unavailable inventory, noncanonical variants, blocked pages, or URLs that redirect elsewhere.
Severity: High for large inventory sets; Medium for isolated errors. Owner: Technical SEO lead with the CMS or feed owner. Corrective action: Generate sitemap entries from the same canonical source used by the live site and remove URLs that are not intended for indexing.
Validation step: Compare a fresh sitemap sample with the live crawl and Search Console index reports. Do not promise instant indexing or require real-time regeneration unless the underlying system genuinely supports it.
Retired listing status handling
Evidence required: Sample expired, sold, withdrawn, merged, and permanently removed property URLs, then record user value, replacement relevance, inbound links, canonical signals, and server responses.
Compare the live response with the documented retirement policy without assuming that one status is correct for every removed listing. Pass condition: Each retired URL follows a documented policy based on whether useful content remains and whether a genuinely relevant replacement exists.
Fail condition: All retired listings are redirected indiscriminately, retained as thin dead-end pages, or removed without considering links and user value. Severity: High when the pattern affects a large portion of inventory; otherwise Medium.
Owner: Technical SEO lead with the listing-feed or CMS owner. Corrective action: Preserve useful evergreen property information when appropriate, redirect only to a closely relevant replacement, or return the documented gone or not-found response when no useful replacement exists.
Validation step: Crawl a representative retired-listing sample and confirm final status, destination relevance, canonical behavior, internal links, and sitemap exclusion match the documented policy.