Do not expand a brokerage into more neighborhood, property-type, or market pages until the team can explain how inventory URLs are discovered, rendered, canonicalized, retired, and connected to durable pages. Score each item only after reviewing the stated evidence.
IDX crawl and renderability
Evidence required: Test representative listing, search-result, property-type, pagination, and filtered URLs in Google Search Console and a crawler. Record the initial HTML, rendered content, blocked resources, canonical target, indexability, and internal path used to reach each sample.
Pass condition: The intended public listing URLs are reachable through normal crawl paths, important content is available after ordinary rendering, canonical directives identify the intended version, and no critical template is unintentionally blocked or isolated.
Fail condition: Important inventory is available only through blocked or inaccessible states, conflicting URL variants compete for the same page, canonical signals point to the wrong destination, or users and crawlers cannot reach the pages through the brokerage site.
Severity: Critical when the defect affects inventory or market discovery across a template; otherwise High. Owner: Technical SEO lead with the website or IDX implementation owner. Corrective action: Fix the shared rendering, crawl, canonical, routing, or navigation defect at the template or platform layer.
Choose the implementation that reliably exposes the intended content and signals; do not assume a hosting location, framework, or rendering method creates ranking value by itself. Validation step: Re-crawl the repaired patterns, inspect live representative URLs, and confirm that the intended pages are discoverable and indexable through normal site architecture rather than depending on repeated manual submission.
Structured data accuracy
Evidence required: Compare every material property, business, office, or organization value in structured data with the visible page and the source system that supplies that fact.
Check syntax and vocabulary against Schema.org and Validator.schema.org where those references are appropriate. Pass condition: Markup describes facts visible or supportable on the page, uses properties valid for the selected type, and stays synchronized with the brokerage's actual source of truth.
Fail condition: Markup contains stale prices, incorrect addresses, unsupported properties, invented relationships, or material details that conflict with what users see. Severity: Medium, or High when inaccurate markup misstates important property or business information.
Owner: Technical SEO lead with the developer responsible for the affected templates. Corrective action: Remove invalid or unsupported properties, map structured data to the same maintained data source used by the visible page, and limit the markup to facts the brokerage can substantiate.
Validation step: Validate again after deployment, inspect the rendered markup, and manually reconcile it with the visible page. Treat structured data as machine-readable context, not as a guaranteed ranking or rich-result mechanism.
XML sitemap quality
Evidence required: Export the submitted sitemap set and compare a sample with live crawlability, canonical targets, indexability, redirect state, parameter handling, and current inventory status.
Pass condition: Submitted URLs are the canonical pages the brokerage intends search engines to discover, and the sitemap generation process removes or updates entries when the underlying page status changes.
Fail condition: Sitemaps repeatedly include unavailable inventory, redirecting pages, blocked URLs, noncanonical variants, or parameter combinations that are not intended for indexing. Severity: High when the issue affects large inventory groups; otherwise Medium.
Owner: Technical SEO lead with the CMS, feed, or platform owner. Corrective action: Build sitemap inclusion from the same canonical and status rules that govern the live site, and exclude URLs that are not intended to remain indexable.
Validation step: Compare a newly generated sitemap sample against the live crawl and Search Console index reporting. Close the task only when the submitted state matches the intended live state; do not promise instant indexing or require real-time generation unless the system actually supports it.
Retired listing status handling
Evidence required: Sample sold, withdrawn, expired, merged, and permanently removed property URLs. For each sample, record whether useful content remains, whether a genuinely relevant replacement exists, whether external or internal links still point to it, the canonical signal, sitemap state, and the final server response.
Pages intentionally removed may use 410; missing URLs may return 404; where the documented retirement policy calls for 410, verify that response directly. Pass condition: Each retired URL follows a documented rule based on remaining user value, replacement relevance, and the desired final state rather than a blanket redirect policy.
Fail condition: Every retired listing is redirected to a generic destination, left as a thin dead end, kept in discovery feeds after removal, or deleted without checking links, user usefulness, and replacement relevance.
Severity: High when the pattern affects a substantial inventory segment; otherwise Medium. Owner: Technical SEO lead with the listing-feed or CMS owner. Corrective action: Keep durable property information only when it remains useful, redirect only when a closely relevant replacement exists, or return the documented gone/not-found response when no useful replacement is available.
Validation step: Crawl a representative retired-listing sample and verify final response, redirect relevance when present, canonical behavior, internal links, and sitemap exclusion against the approved retirement policy.