Rule (Ontario builder/renovator sites): build a dedicated /affiliations or /memberships page listing each HBA with a one-sentence description AND year joined, marked up with Organization schema + memberOf properties

On Ontario builder/renovator client websites, build a dedicated /affiliations (or /memberships) page that lists each membership the firm holds:

• Local HBA (WRHBA / BILD / GOHBA / WEHBA / LHBA)
• OHBA (automatic via local)
• CHBA (automatic via local)
• RenoMark (if applicable)
• BBB
• Other industry bodies (CaGBC, OBOT, local Chamber of Commerce, etc.)

For each: a one-sentence description, the year joined, and a link to the parent organization (or to the client's own profile on that org's member directory).

Add Organization schema with memberOf properties in JSON-LD on the page, one per membership.

Example:

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "[Client Co]",
  "memberOf": [
    {
      "@type": "Organization",
      "name": "Waterloo Region Home Builders' Association",
      "url": "https://wrhba.com/"
    },
    {
      "@type": "Organization",
      "name": "Ontario Home Builders' Association",
      "url": "https://www.ohba.ca/"
    },
    {
      "@type": "Organization",
      "name": "Canadian Home Builders' Association",
      "url": "https://www.chba.ca/"
    }
  ]
}

Why:

1. Year joined is a differentiator. None of the sites surveyed in Two HBA display patterns across Ontario builder/renovator sites: Pattern A (small custom + renovation firms show HBA + RenoMark prominently in footer); Pattern B (large production builders rarely show HBA logos, lead with HCRA + Tarion) show a member-since date. A "WRHBA member since 2003" line is concrete and trust-building in a way an undated logo isn't — and costs nothing to add.
2. Organization schema with memberOf is rarely done by Ontario builders (Two HBA display patterns across Ontario builder/renovator sites: Pattern A (small custom + renovation firms show HBA + RenoMark prominently in footer); Pattern B (large production builders rarely show HBA logos, lead with HCRA + Tarion) — "a clear SEO opportunity"). Schema markup helps Google knowledge panels and AI search engines (Perplexity, ChatGPT, Gemini, AI Overviews) extract memberships and surface them in answers — the same discipline applied to credentials at Rule (Tier-2 ICI GC sites): use schema.org Person + hasCredential + EducationalOccupationalCredential markup so Gold Seal credentials surface in Google knowledge panels and AI overviews.
3. A dedicated page is what procurement leads and architects look for when pre-qualifying a firm — the same logic as the Gold Seal /credentials page at Rule (Tier-2 ICI GC sites): build a single dedicated /credentials page listing every team credential (P.Eng., GSC, P.GSC, PMP, CET, LEED AP, Red Seal, COR, CHSC) with brief descriptions, no puffery.

How to apply:

• Single page, link from global footer (under "About") and from team-bio mentions of credentials.
• Update every January after annual membership renewal.
• Validate every JSON-LD block with the Schema Markup Validator (validator.schema.org) before deploy.
• For RenoMark specifically, also implement Rule (renovator client sites): build a dedicated /renomark page with the verbatim 10-point Code and the current-year certificate image — the dedicated /renomark page lives alongside /affiliations, not inside it.