NorthBayPlumbers.ca: 106 Pages. Perfect SEO Score.

The Challenge: Prove It Works

I built the Local SEO Engine to solve a problem I see with every contractor I work with: they are invisible in the searches that matter. A homeowner types "emergency plumber in Callander" and finds a directory page, a Google Ads link, or a competitor. My clients do not show up because they have 5 pages on their website targeting 3 keywords, competing against the entire internet.

The system I built generates hundreds of pages. Entity-driven content. Real local data woven into every paragraph. FAQ multiplication that turns 20 core pages into 100+ standalone pages. Answer engine optimization so ChatGPT, Perplexity, and Google AI Overviews can cite the content directly.

But a system is only as good as its output. I needed a live, verifiable site that anyone could visit, inspect, and measure. That site is NorthBayPlumbers.ca.

The Build Process

Step 1: Keyword Research and Service-Area Mapping

The build started with keyword research across multiple tools to identify every high-value search term related to plumbing services in the North Bay, Ontario region. I mapped out the core services (drain cleaning, water heater installation, pipe repair, sewer line replacement, emergency plumbing, bathroom renovations) and the service areas (North Bay, Callander, Powassan, Sturgeon Falls, Mattawa, West Nipissing, and surrounding communities).

This created the service-location matrix: every service combined with every area produces a unique page assignment. The keyword research also surfaced long-tail queries and seasonal patterns specific to Northern Ontario plumbing, things like frozen pipe prevention in Nipissing District and water softener requirements for the region's hard water.

Step 2: Entity Analysis for North Bay Neighborhoods

This is where the Local SEO Engine separates from everything else. For each service area, Google Gemini analyzed the actual local landscape and returned structured entity triples: subject-predicate-object relationships that form the semantic backbone of each page.

For North Bay, that means references to real places: the waterfront along Memorial Drive, the older residential areas around Cassells Street, the Highway 11 corridor, Laurentian Ski Hill, the North Bay Museum, Duchesnay Falls, Lee Park. For Callander, completely different entities: Callander Bay on Lake Nipissing, the Callander Museum, South River Road, the village's municipal water infrastructure. Every location page reads like it was written by someone who knows the area because the AI was given real data about the area before it wrote a single word.

Step 3: Content Generation and FAQ Multiplication

Claude wrote 800 to 1,500 words of original content per page, weaving in the entity data naturally. Each service-location page got 3 to 5 location-specific FAQs. These are not generic questions with a city name swapped in. They reference local conditions, local regulations, and local context.

Then FAQ multiplication kicked in. Every FAQ on every page became its own standalone page, targeting the exact long-tail query a homeowner would type into Google. "How much does drain cleaning cost in Callander?" becomes a dedicated page with a direct answer, schema markup, and internal links back to the parent service and location pages.

Step 4: Quality Scoring and Deployment

Every page was scored against the 37-factor quality scoring system before it went live. The system checks entity density, content uniqueness (less than 40% similarity between any two pages), heading hierarchy, schema completeness, internal linking, image optimization, FAQ presence, AEO paragraph structure, and more. Any page scoring below 80 gets blocked from deployment and regenerated.

All 106 pages on NorthBayPlumbers.ca scored 80 or above. All 10 critical gates passed. The site was deployed to a global CDN as static HTML, and blog posts were published through drip publishing to mimic natural site growth.

The Technical Results

The numbers are not theoretical. Run Google Lighthouse on any page of northbayplumbers.ca right now and you will see them yourself.

• PageSpeed 90: Static HTML on a global CDN. No WordPress, no bloated plugins, no database queries. Pages load in under 1 second on most connections.
• Accessibility 94: Semantic HTML, proper heading hierarchy, ARIA labels, sufficient color contrast, keyboard navigable. This is not just a performance metric. It means the site works for everyone.
• Best Practices 100: No deprecated APIs, no console errors, HTTPS everywhere, proper image formats, no render-blocking resources.
• SEO 100: Complete meta tags, canonical URLs, structured data (BreadcrumbList, FAQPage, LocalBusiness, Service schema), proper heading structure, mobile-responsive, fast load times.

These scores are consistent across the entire site, not cherry-picked from the homepage. The 37-factor quality scoring system enforces this consistency before any page goes live.

What This Means for Contractors

NorthBayPlumbers.ca covers one trade in one regional market. 106 pages. If the Local SEO Engine can build a site like this for a plumber, imagine what it builds for your business.

A HVAC contractor with 8 services across 25 areas gets 200 location pages before FAQ multiplication. A general contractor covering renovations, additions, decks, basements, and roofing across a metropolitan area could see 400+ pages. A painting contractor with interior, exterior, cabinet, and commercial services across 30 towns gets a 120-page foundation that FAQ multiplication can expand to 600+.

Every one of those pages would go through the same quality scoring. Same entity analysis. Same uniqueness validation. Same answer engine optimization. Same deployment process. The system does not care if it is 106 pages or 1,060 pages. The quality standard stays the same.

The difference between having this system and not having it is simple: with it, you show up when homeowners search. Without it, your competitors do. NorthBayPlumbers.ca is the proof that the system works. Your site could be the next one.