What changed in SEO between 2020 and 2026
SEO advice from five years ago is largely obsolete for a BC roofing site. The 2020 playbook centered on keyword targeting, on-page density, backlink quantity, and exact-match anchor text. The 2026 playbook centers on entity coverage, semantic completeness, page experience, named-author EEAT, and earned authority through industry citations. The vocabulary is similar; the underlying mechanics are unrecognizable.
Three forces drove the change. First, Google's Helpful Content System and the multiple core updates of 2023–2025 systematically devalued shallow, keyword-driven, AI-spun content. Second, the rise of LLM answer engines (ChatGPT, Gemini, Perplexity, Claude) created a parallel discovery channel where citation depth and source clarity matter more than traditional ranking signals. Third, Core Web Vitals became a hard ranking factor, meaning a slow or layout-shifting site loses positions regardless of content quality.
For a BC strata roofing contractor, the practical consequence is that you can no longer outrank a thinly written 800-word service page by writing a thinly written 1,200-word version. You have to actually cover the topic — the assembly, the failure modes, the BC code references, the typical cost ranges, the maintenance considerations, the related services, the relevant cities — at the depth that genuinely answers the question.
Entity coverage: the new keyword strategy
Modern search treats your site as a graph of entities — services, cities, materials, manufacturers, regulations, people, projects — and ranks pages based on how completely the graph is built and how clearly the entities relate to each other. A roofing site with a single "strata roofing" page targeting Vancouver loses to one with twenty interlinked pages covering each service, each city, each assembly, each common council question, all clearly cross-linked.
For a BC strata roofing contractor, the entity coverage you need looks roughly like this: every service (re-roof, repair, maintenance program, emergency response, inspection, depreciation-report support); every assembly type (SBS torch-on, TPO, PVC, EPDM, BUR, asphalt shingle, cedar shake, metal); every relevant city in your service area with local detail; every regulatory framework (Strata Property Act, BC Building Code, RCABC, CHOA, WorkSafeBC); every named team member with credentials; and a steady cadence of in-depth blog content that links the entities together in the way councils actually consume them.
The test is the "can a council answer their question entirely on this site" test. If a council member lands on your TPO page and can navigate to the relevant city, the relevant warranty discussion, the relevant case study, the maintenance program that supports it, and the team member who would lead the project, your entity coverage is working. If the page is a dead end, it isn't.
Internal linking that mirrors council decision flow
Internal linking is the most underused SEO lever on trade websites. A correctly linked roofing site moves PageRank to the pages most likely to convert (quote, contact, flagship-service) while simultaneously guiding councils through the actual sequence of a roofing decision: identify the problem, understand the options, learn the cost and timeline, see comparable projects, verify the contractor, and request a quote.
The internal-link map should be intentional, not accidental. Every blog post should link to the relevant service page, the relevant city page, the relevant case study, and the next logical post in the council's information journey. Every service page should link back to the supporting blog content, the cities where the service is delivered, and the team page. Every city page should link to the services available there, the case studies in that city, and the local regulatory references.
Done correctly, this produces a site where Google can crawl the entire entity graph in a few hops and where a council member can traverse from any landing page to a quote request in three clicks or fewer. Done incorrectly — sidebar links, footer dumps, unrelated cross-links — it produces noise that actively dilutes ranking signals.
Page experience and Core Web Vitals
Page experience is now a non-negotiable. Google measures Largest Contentful Paint (LCP), Interaction to Next Paint (INP), and Cumulative Layout Shift (CLS), and pages that fail any of the three lose ranking positions regardless of content quality. For a BC roofing site, the most common failures are oversized hero images that blow out LCP, render-blocking third-party scripts (chat widgets, analytics, ad pixels) that wreck INP, and late-loading fonts or images that cause CLS jumps.
The fixes are well known: serve hero images at the actual displayed dimensions, set explicit width and height on every image to prevent layout shift, defer or remove non-essential third-party scripts, preload the critical font and the LCP image, and adopt a static-site or SSR architecture so the first paint is HTML rather than a JavaScript hydration stub. None of this is exotic, but most trade websites still fail at least one of the three metrics.
For councils, Core Web Vitals are also a procurement signal in a quiet way. A contractor whose website loads instantly, never jumps as you scroll, and responds immediately to taps is signalling discipline. The same discipline tends to show up in the warranty registration paperwork.
Author EEAT on every byline
Every substantive page on a roofing site should carry a clear author byline with credentials, a link to a real team-page bio, and a visible last-reviewed date. This is partly about EEAT (covered in our companion piece on EEAT for roofing websites) and partly about ranking. Google's quality systems specifically reward content with traceable authorship in YMYL (Your Money or Your Life) topics, and a six-figure capital decision on a strata building qualifies.
The author byline should include the writer's full name, role, and any relevant credentials (Red Seal, RCABC, manufacturer certifications, years in trade). The team-page bio should expand on this with a photograph, a project history, and the writer's specific area of expertise. The last-reviewed date should be honest — only updated when the content is genuinely re-checked — because date inflation is a known signal that quality systems learn to discount.
For BC strata content specifically, the author should be visibly local. A roofing article about Vancouver that is signed by a generic "Editorial Team" or by a writer based in another province sends the wrong signal to both Google and the council reading it.
Earned authority: links from CHOA, RCABC, property managers
Backlinks still matter, but the link inventory that moves rankings in the BC strata roofing niche is narrow and specific. The links that genuinely lift authority are the ones from CHOA, RCABC, the BC Building Code resource pages, the major property management associations, the strata insurance brokers, the depreciation-report consultancies, and a small group of local news and trade publications. Generic directory links, paid placements, and PBN links contribute little and often hurt.
Earning the right links is a slow process. It comes from publishing technical content other industry actors actually want to cite, from speaking at CHOA seminars or property-manager events, from contributing to depreciation-report consortia, and from being the contractor whose work is referenced in case studies by other professionals. None of these are quick wins. All of them compound.
For councils evaluating contractors, the link inventory is also a credibility signal. A contractor whose site is referenced by CHOA and RCABC has earned that reference through years of industry presence. A contractor with a backlink profile dominated by directories has not.
Common SEO mistakes on BC roofing sites
- Thin city pages. A 200-word page repeating "roofing in [city]" twenty times. Replace with substantive city-specific content — local building permit office, typical strata stock, climate notes, local case studies.
- Duplicate service descriptions. The same boilerplate copy on every service page with a swapped headline. Each service page needs unique technical depth.
- AI-spun blog content. Generic articles with no first-person experience, no local references, no named author. Quality systems detect this and demote the entire domain.
- Missing schema. No Organization JSON-LD, no LocalBusiness, no Service schema, no BlogPosting markup. Schema is how search engines and LLMs disambiguate your entities.
- Broken internal links. Links to deleted pages or wrong slugs that erode crawl budget and user trust. Run a regular audit.
- No XML sitemap discipline. Sitemap missing pages, listing 404s, or not partitioned by content type. Search Console will flag this; act on it.
- Ignoring Core Web Vitals. Hero images at 4 MB, render-blocking chat widgets, fonts loaded synchronously. Each costs ranking positions.
- No author bylines. EEAT-blank content in a YMYL niche. Add named authors with credentials immediately.
A 90-day SEO improvement plan for a strata roofing site
Days 1–14: Audit. Map every page, every service, every city, every blog post. Identify thin pages, duplicate copy, missing schema, broken internal links, Core Web Vitals failures. Output a prioritized action list.
Days 15–45: Fix the technical foundation. Compress and resize hero images, set explicit dimensions on every image, defer non-essential scripts, add Organization, LocalBusiness, Service, and BlogPosting schema across the site, fix every broken internal link, and partition the sitemap by content type.
Days 46–75: Deepen the entity coverage. Rewrite thin city pages with local detail. Rewrite duplicate service pages with unique technical depth. Add named author bylines with credentials. Publish three new in-depth blog posts (2,500+ words) on topics with strong council search demand.
Days 76–90: Earn authority. Reach out to CHOA, RCABC, and property management associations with the new technical content. Submit case studies to industry consortia. Pitch local trade publications. Measure rankings, organic traffic, and quote requests against a baseline taken on Day 1.
This is not a magic formula. It is what works because it mirrors what credible contractors actually do: build the site the way you would build the roof — with discipline, depth, and named accountability.
Why this matters to councils, not just contractors
If you are reading this as a strata council member rather than a contractor, the takeaway is the inverse: a contractor whose website demonstrates the disciplines above is signalling the kind of operational rigor that translates to your roof. A contractor whose website is thin, duplicated, AI-spun, slow, and undated is signalling the opposite. The website is not the work, but it is a reasonable proxy for how the work will be documented, warranted, and stood behind.
For your next contractor evaluation, spend ten minutes on the candidate's website with the lens above. The ones that pass deserve a closer look. The ones that fail will almost certainly produce close-out binders that look the same. To see how this plays out in practice on a council-ready proposal, see our process page or request a quote.
Schema markup specifics for BC strata roofing
Schema is the structured-data layer that tells search engines and LLMs exactly what your pages describe. For a BC strata roofing site, the schema set should include Organization or RoofingContractor (sitewide identity with full address, geo, phone, parent company, and aggregateRating where supported by real data), LocalBusiness (per-city if you have multiple branches), Service (one per service offering with provider and areaServed), Person (named team members with credentials), Article and BlogPosting (each post with author, datePublished, dateModified, articleSection), FAQPage (every question-and-answer block), HowTo (procedural content like inspection checklists), and BreadcrumbList (navigation path on every interior page).
Schema must mirror the visible content. Inflated review counts, fictitious certifications, or area-served claims that do not match actual delivery are quality violations that can trigger sitewide demotions. Schema is best treated as a contract: only assert what is true and verifiable.
Local SEO and the BC trade context
For a BC strata roofing contractor, local SEO is not a sub-discipline; it is the discipline. The Google Business Profile must be claimed, fully completed, and actively maintained — categories set correctly (Roofing Contractor as primary, plus relevant secondaries), service area defined accurately, photos refreshed quarterly, posts published monthly, reviews responded to within a business day. Local citations on industry-relevant directories (RCABC, BBB, BuildLink, HomeStars) need to carry consistent name, address, and phone (NAP) data.
The single highest-leverage local-SEO action for a strata roofing contractor is collecting and responding to genuine reviews from named property managers and council members on Google. Reviews from real strata clients with real building references signal local authority more strongly than any backlink campaign.
Content cadence and editorial calendar
SEO momentum requires consistent publishing. For a BC strata roofing site, a sustainable cadence is two to four substantive blog posts per month (1,500–3,000 words each, named author, BC-specific), one updated service or city page per quarter, and one new case study per quarter. The editorial calendar should be built from the council question inventory described in our companion AEO article, prioritized by search volume and quote-conversion potential.
Cadence beats burst. A site that publishes consistently for thirty-six months at this pace will outperform a site that published forty articles in one quarter and went quiet, even if the burst-published site has more total content. Quality systems weight freshness, consistency, and ongoing investment as positive trust signals.
Measurement and the metrics that matter
The vanity metrics in SEO (total impressions, total backlinks, domain rating) are weakly correlated with revenue for a trade. The metrics that matter are quote requests per month from organic search, organic ranking on the highest-intent council queries ("strata roof replacement [city]", "strata roof inspection [city]", "flat roof contractor [city]"), the share of branded search queries (an indicator of memorability and direct trust), and the conversion rate from quote-request page view to submitted intake form. Track these monthly, set quarterly targets, and treat the vanity metrics as diagnostic only.
Page-level Core Web Vitals from Search Console are the technical metric to monitor weekly. Pages drifting into the "needs improvement" or "poor" buckets should trigger immediate fixes, because the ranking penalty for sustained Core Web Vitals failures is steep and slow to recover.
What this looks like for a council reading a contractor's website
If you are reading this as a council member rather than a contractor, the lens above doubles as a procurement lens. A contractor whose website covers the entities thoroughly, links them coherently, loads instantly, and carries credentialed authorship and visible review dates is signalling the same operational discipline that produces a clean roof installation and a complete close-out package. A contractor whose website is thin, slow, AI-spun, anonymous, and undated is signalling the inverse. Neither signal is a guarantee, but both are correlated with real outcomes more strongly than councils typically realize.
Final notes for councils and property managers
The disciplines covered in this article are not a one-time checklist; they are a continuous operating standard. Councils that adopt them as a habitual procurement filter make better contractor selections, run smoother capital projects, and produce depreciation reports and close-out documentation that hold up under scrutiny years later. Property managers who internalize the same standards bring more value to every council they serve, because the same evaluation lens that filters roofing contractors also filters mechanical, envelope, and life-safety contractors with very little adaptation.
The single most important habit is to write the standard down. A council with a documented two-page contractor evaluation rubric — covering credentials, experience, EEAT signals, references, insurance, warranty terms, and documentation discipline — runs a fundamentally different procurement process than one relying on informal memory. The rubric does not need to be elaborate. It needs to exist, be applied consistently, and be revisited at every council turnover so institutional memory survives the inevitable changes in council membership.
For our own engagements with strata clients, we provide a sample evaluation rubric on request and walk new councils through how to apply it to any contractor in any trade, not just roofing. The framework is genuinely portable and the multi-trade benefit is one of the larger long-term wins councils can capture from an otherwise narrow roofing decision. To talk through how this applies to your building, contact us directly, browse our services and blog, or request a council-ready quote.
Service area for this work
We deliver strata roofing services across Metro Vancouver and the Fraser Valley. For city-specific permit, climate, and housing-stock notes, see our pages for Vancouver, Burnaby, Richmond, Coquitlam, and the full cities index.
From our network
For more strata-specific roofing analysis, see CHOARoofers.com. If you're a council member or property manager, contact us directly or request a council-ready quote.