BTA SEO Engine Playbook

Programmatic SEO Operating Manual & Progress Tracker

The complete system for building and deploying 800+ unique, quality-scored pages for buildtechadvisor.com

Prepared for BuildTech Advisor | March 16, 2026

1. Executive Overview

This document is the operating manual for building and deploying the BuildTech Advisor programmatic SEO engine. It governs every session, every page, and every quality check across the entire 800+ page build. It exists because an 800-page build across dozens of Claude Code sessions will drift, duplicate, and drop quality unless every step is locked down. This playbook prevents that.

2. Site Architecture

Page Types & Counts

Page Type	Count	Words/Page	Priority
Core Pages	10	1,500 - 2,500	Phase 1
Software Category Pages	18	1,500 - 2,500	Phase 2
Trade-Specific Pages	15	1,500 - 2,500	Phase 2
Category x Trade Matrix Pages	~165	1,200 - 1,800	Phase 3
Comparison Pages	50	1,200 - 1,800	Phase 3
FAQ Standalone Pages	~548	300 - 500	Phase 4
Hubs & Technical Files	~4	N/A (index)	Phase 1-2
Total	~810

URL Structure

The 4 Phases

10 core pages, design system/CSS, schema templates validated, technical files (sitemap, robots, llms.txt).

All 18 category pages, all 15 trade pages, FAQ Hub, hubs for /software/ and /trades/, comparison hub. ~37 pages total.

High-priority matrix pages first (~90), then Tier 1 comparisons (15), medium-priority matrix (~75), Tier 2 comparisons (20), Tier 3 comparisons (15). ~215 pages. Build rate: 5-8 pages/session, ~3 sessions/week.

Extract FAQs from all completed pages, generate standalone pages in clusters. Build rate: 15-20 FAQ pages per session. ~548 pages estimated.

3. The Content Matrix

18 Software Categories

#	Category	Slug	Key Products	Target Keywords
1	Project Management	project-management	Procore, Buildertrend, CoConstruct, Contractor Foreman, RedTeam	construction project management software
2	Estimating	estimating	STACK, ProEst, Buildxact, JobTread, RSMeans	construction estimating software
3	Takeoff & Measurement	takeoff-measurement	Bluebeam, PlanSwift, OnScreen Takeoff, Togal.ai	construction takeoff software
4	Accounting & Job Costing	accounting-job-costing	Sage 100, Foundation Software, Sage 300 CRE, QuickBooks+Knowify	construction accounting software, job costing software
5	Scheduling	scheduling	Primavera P6, Microsoft Project, Planera, SmartPM	construction scheduling software
6	Field Service Management	field-service	ServiceTitan, Jobber, Housecall Pro, FieldPulse, FieldEdge	field service management software
7	CRM & Sales	crm-sales	Buildertrend CRM, JobNimbus, MarketSharp, Leap	construction CRM software
8	Bidding & Preconstruction	bidding	BuildingConnected, SmartBid, PlanHub, iSqFt	construction bidding software
9	Safety & Compliance	safety-compliance	SafetyCulture (iAuditor), Procore Safety, Safety Reports, HammerTech	construction safety software
10	BIM	bim	Autodesk Revit, Navisworks, Tekla Structures, Trimble Connect	BIM software for construction
11	Time Tracking	time-tracking	Busybusy, ClockShark, ExakTime, TSheets/QuickBooks Time	construction time tracking software
12	Daily Reporting	daily-reporting	Raken, Procore Daily Log, Fieldwire, PlanGrid	construction daily reporting software
13	Payroll	payroll	Foundation Payroll, Sage Payroll, ADP, Paychex	construction payroll software
14	Document Management	document-management	Procore Docs, PlanGrid, Bluebeam Studio, Aconex	construction document management
15	Equipment & Fleet	equipment-fleet	Tenna, HCSS Equipment360, Samsara, Verizon Connect	construction equipment management software
16	Subcontractor Management	subcontractor-management	GCPay, Procore, Textura, Paskr	subcontractor management software
17	Procurement	procurement	Procore Procurement, ProcurePro, BuildOps, eSUB	construction procurement software
18	Design & Proposals	design-proposals	Houzz Pro, Cedreo, Chief Architect, SoftPlan	construction proposal software

15 Construction Trades

#	Trade	Slug	Unique Software Needs
1	General Contractors	general-contractors	Multi-project oversight, sub management, complex scheduling, change orders
2	Electricians	electricians	Service dispatch, panel scheduling, load calculations, code compliance tracking
3	Plumbers	plumbers	Service/repair dispatch, permit tracking, parts inventory, drain camera integration
4	HVAC	hvac	Equipment lifecycle tracking, seasonal demand, maintenance contracts, load calculations
5	Roofing	roofing	Aerial measurement, material waste calculators, weather scheduling, crew tracking
6	Home Builders & Remodelers	home-builders-remodelers	Client selections, design integration, phase scheduling, warranty tracking
7	Painting	painting	Square footage estimation, color management, crew/room scheduling
8	Concrete	concrete	Batch tracking, pour scheduling, mix design, weather-dependent scheduling
9	Excavation & Earthwork	excavation-earthwork	GPS/grade control, haul tracking, volume calculations, equipment management
10	Landscaping	landscaping	Design visualization, seasonal maintenance, irrigation planning, recurring routes
11	Drywall & Insulation	drywall-insulation	Material takeoffs, crew productivity, phase coordination with other trades
12	Flooring	flooring	Material estimation, pattern layout, waste calculation, product spec management
13	Masonry	masonry	Block/brick estimation, mortar calculations, scaffold scheduling
14	Steel & Structural	steel-structural	Fabrication tracking, erection sequencing, BIM coordination, shop drawing mgmt
15	Fire Protection	fire-protection	Code compliance, inspection scheduling, hydraulic calculations, as-built docs

Category x Trade Priority Map

Every Category x Trade intersection is classified as HIGH, MED, or SKIP. HIGH = strong search intent and unique content angle (build first). MED = viable page, built in Phase 3. SKIP = thin content angle, not worth a standalone page.

Top 50 Comparison Pages

#	Comparison
1	Procore vs Buildertrend
2	ServiceTitan vs Housecall Pro
3	Jobber vs Housecall Pro
4	Buildertrend vs CoConstruct
5	Procore vs PlanGrid
6	Sage 100 vs Foundation Software
7	Bluebeam vs PlanSwift
8	ClockShark vs Busybusy
9	ServiceTitan vs Jobber
10	Procore vs Contractor Foreman
11	JobNimbus vs Buildertrend
12	STACK vs PlanSwift
13	QuickBooks vs Sage (for Construction)
14	Raken vs Procore Daily Log
15	Primavera P6 vs Microsoft Project

#	Comparison
16	Procore vs RedTeam
17	STACK vs ProEst
18	FieldPulse vs FieldEdge
19	Houzz Pro vs Cedreo
20	SafetyCulture vs Procore Safety
21	Aspire vs Jobber (Landscaping)
22	BuildingConnected vs PlanHub
23	ServiceTitan vs FieldEdge
24	Buildxact vs JobTread
25	ExakTime vs ClockShark
26	Tekla vs Revit
27	SmartBid vs BuildingConnected
28	Buildertrend vs Contractor Foreman
29	Samsara vs Tenna
30	Foundation vs QuickBooks+Knowify
31	CoConstruct vs Houzz Pro
32	MarketSharp vs Leap
33	ProcurePro vs Procore Procurement
34	Fieldwire vs PlanGrid
35	GCPay vs Textura

Remaining niche comparisons sourced from the full matrix file. These target lower-volume but highly specific search queries with minimal competition.

4. Quality Scoring System

The 3 Scoring Pillars

37 Scoring Factors

Page Structure (25% weight) - 7 Factors

#	Factor	Requirement
1	Semantic HTML5	Uses header, nav, main, article, footer elements
2	Heading hierarchy	H1 > H2 > H3, no skipped levels
3	No inline styles	External CSS only
4	Image dimensions	All images have width/height attributes
5	Lazy loading	Below-fold images use lazy loading
6	Hero preload	Hero image is preloaded
7	Clean HTML	Minified, no unnecessary markup

Content Quality (40% weight) - 8 Factors

#	Factor	Requirement
8	Word count minimum	Category/Trade: 1,500+, Matrix/Comparison: 1,200+, FAQ: 300+
9	Direct-answer paragraph	Self-contained, citeable answer in first 200 words
10	Entity triples	15+ entity triples woven naturally into content
11	FAQ quality	3-5 FAQs with substantive, multi-sentence answers
12	No boilerplate	No repeated content from other pages
13	E-E-A-T signals	Specific products named, real features cited, trade-specific detail
14	Content uniqueness	Distinct angle from all sibling pages
15	Actionable specifics	Every paragraph contains specific, actionable information

SEO Optimization (35% weight) - 9 Factors

#	Factor	Requirement
16	Title tag	50-60 chars, keyword front-loaded
17	Meta description	150-160 chars, keyword + CTA
18	Schema markup	Present and valid for page type
19	Internal links out	3+ internal links with contextual, descriptive anchor text
20	Inbound links	2+ inbound links from other pages
21	Breadcrumbs	BreadcrumbList schema present
22	Image SEO	Keyword filename, alt text, WebP format, <150KB
23	Canonical URL	Set correctly, points to proper URL
24	OG tags	Complete Open Graph meta tags

10 Critical Gates

Every gate is binary pass/fail. ALL 10 must pass before a page can be deployed.

#	Gate	Failure Trigger	Pass/Fail
1	H1 Present	Missing or more than one <h1> tag	☐
2	Title Tag	Empty or outside 50-60 character range	☐
3	Schema Valid	JSON-LD missing or structurally incorrect	☐
4	No Duplicate Content	Page angle overlaps with sibling pages	☐
5	Mobile Responsive	Missing viewport meta or fixed-width elements	☐
6	Canonical Tag	Missing or points to wrong URL	☐
7	HTTPS	Any URL using http:// instead of https://	☐
8	NAP Consistency	Business name doesn't match across pages	☐
9	No Orphan Page	Page has zero inbound links or fewer than 2 outbound links	☐
10	Word Count Minimum	Below threshold for page type	☐

Grading Scale

5. Content Generation SOP

Pre-Session Checklist

1. Read this playbook (you're doing it now)
2. Open the tracking file — check what's built, what's next
3. Identify today's cluster — e.g., "Project Management category + its 6 high-priority trade pages"
4. Read 3 existing completed pages from a related cluster to calibrate tone and depth
5. Confirm the batch: 5-8 pages max

The 6-Step Per-Page Process

• Check the matrix for: slug, target keywords, priority, parent/child relationships
• Identify 3-5 real software products relevant to this specific page
• Identify 3-5 trade-specific pain points or workflow requirements
• Note which pages this page must link to (parent, siblings, children)

Create 15-25 structured entity triples per page in [Subject] -- [Predicate] -- [Object] format:

Procore -- provides -- project management features suited to electrical contractors
Electrical contractors -- require -- panel schedule tracking integrated with project timelines
Buildertrend -- offers -- client portal features useful for residential electrical projects
NEC code compliance -- affects -- how electricians manage project documentation
Service dispatch -- differs from -- project management in electrical contracting workflows

Use the locked prompt templates below (one per page type). These are non-negotiable — every page must be generated using its corresponding template.

Follow the standard HTML page structure template (shown below).

All 10 gates must pass. Any failure blocks deployment.

Score all 3 pillars. If it fails, fix and re-check. If it passes, mark complete in tracking.

Locked Prompt Templates

Category Page Template

Trade Page Template

Matrix Page Template

Comparison Page Template

FAQ Standalone Page Template

HTML Page Structure Template

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>[Title Tag - 50-60 chars, keyword front-loaded]</title>
    <meta name="description" content="[150-160 chars, keyword + CTA]">
    <link rel="canonical" href="https://buildtechadvisor.com/[path]/">
    <meta property="og:title" content="[OG Title]">
    <meta property="og:description" content="[OG Description]">
    <meta property="og:type" content="article">
    <meta property="og:url" content="https://buildtechadvisor.com/[path]/">
    <meta property="og:image" content="https://buildtechadvisor.com/images/[slug]-og.webp">
    <link rel="stylesheet" href="/css/main.css">
    <!-- JSON-LD Schema (see Section 8) -->
</head>
<body>
    <nav>[Breadcrumbs]</nav>
    <main>
        <article>
            <h1>[Exactly one H1]</h1>
            [Direct-answer paragraph - first 200 words]
            [Body content with H2/H3 hierarchy]
            [FAQ section - fully expanded, no JS toggles]
            [CTA block]
        </article>
    </main>
    <footer>[Standard footer with internal links]</footer>
</body>
</html>

6. Uniqueness Strategy

Matrix pages for the same category across different trades (or same trade across different categories) can drift toward similar content. The solution is Angle Locking.

The Angle Locking System

Before writing any matrix page, define its unique angle in the tracking file. This locks the content direction and prevents overlap with sibling pages.

Per-Session Uniqueness Checks

1. Before writing a new page, read all sibling pages in the same cluster
2. List the key topics, products, and examples used in each sibling
3. Explicitly define what this new page covers that siblings do NOT
4. After writing, compare the first 3 paragraphs against siblings. If the opening feels similar, rewrite it.

Cross-Session Uniqueness Checks

• When starting a new session, read the unique_angle field for all completed pages in the current cluster
• These angles are constraints — do not repeat them
• If angle overlap is noticed after the fact, flag it in the tracking file for future correction

7. Internal Linking Rules

Pillar-Cluster Architecture

Linking Rules Per Page Type

Page Type	Links UP to	Links DOWN to	Links ACROSS to
Category Page	/software/ hub	All its matrix pages	2-3 related category pages + FAQ standalones
Trade Page	/trades/ hub	All its matrix pages across categories	2-3 related trade pages + FAQ standalones
Matrix Page	Parent category page AND parent trade page	—	2-3 sibling matrix pages + FAQ standalones
Comparison Page	/compare/ hub	—	Category pages for both products + related comparisons + FAQ standalones
FAQ Standalone	—	—	Source page (back-link) + 2-3 related FAQ pages

Link State Management

State	Meaning	Link Behavior
Active	Page is deployed and live	Links rendered normally
Pending	Page is in current batch	Links about to activate
Deferred	Page is in future queue	Links suppressed (no broken links / 404s)

8. Schema Templates

Category / Trade Pages

// JSON-LD for Category and Trade Pages
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "name": "[Page Title]",
      "description": "[Meta description]",
      "url": "https://buildtechadvisor.com/[path]/",
      "breadcrumb": {
        "@type": "BreadcrumbList",
        "itemListElement": [
          {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://buildtechadvisor.com/"},
          {"@type": "ListItem", "position": 2, "name": "[Parent]", "item": "https://buildtechadvisor.com/[parent]/"},
          {"@type": "ListItem", "position": 3, "name": "[This Page]"}
        ]
      }
    },
    {
      "@type": "FAQPage",
      "mainEntity": [
        {
          "@type": "Question",
          "name": "[Question text]",
          "acceptedAnswer": {
            "@type": "Answer",
            "text": "[Answer text]"
          }
        }
      ]
    },
    {
      "@type": "Organization",
      "name": "BuildTech Advisor",
      "url": "https://buildtechadvisor.com",
      "description": "Neutral, AI-powered construction software matching"
    }
  ]
}

Comparison Pages

// JSON-LD for Comparison Pages
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "WebPage",
      "name": "[Software A] vs [Software B]",
      "url": "https://buildtechadvisor.com/compare/[slug]/"
    },
    {
      "@type": "SoftwareApplication",
      "name": "[Software A]",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web"
    },
    {
      "@type": "SoftwareApplication",
      "name": "[Software B]",
      "applicationCategory": "BusinessApplication",
      "operatingSystem": "Web"
    },
    {
      "@type": "FAQPage",
      "mainEntity": [...]
    }
  ]
}

FAQ Standalone Pages

// JSON-LD for FAQ Standalone Pages
// NOTE: Uses Article schema, NOT FAQPage.
// FAQPage stays on the source page to avoid competing for the same rich result.
{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "[Question]",
  "author": {"@type": "Organization", "name": "BuildTech Advisor"},
  "publisher": {"@type": "Organization", "name": "BuildTech Advisor"},
  "datePublished": "[YYYY-MM-DD]",
  "url": "https://buildtechadvisor.com/faqs/[slug]/"
}

9. Image Generation Process

Per-Page Image Requirements

Page Type	Hero Image	In-Content Images	Total
Category / Trade Pages	1 (1200x630px, WebP, <300KB, preloaded)	2-3 (800x450px, WebP, <150KB, lazy-loaded)	3-4
Matrix Pages	1 (1200x630px)	1-2 (800x450px)	2-3
Comparison Pages	1 (1200x630px)	Product logos / screenshots	2-3
FAQ Standalones	None	None	0

Naming Convention

// Format: [category]-[trade]-[descriptor].webp

project-management-electricians-panel-schedule.webp
procore-vs-buildertrend-comparison-hero.webp
estimating-software-feature-overview.webp
hvac-contractors-field-management.webp

Image Metadata (4 Required Elements)

#	Element	Requirement
1	File name	Lowercase, hyphenated, keyword-rich
2	Alt text	Descriptive, natural language, includes primary keyword
3	Caption	Visible text adding context (optional for hero images)
4	Title attribute	Brief descriptor

Brand Parameters

• Primary colors: Dark navy (#0a1628), bright blue (#2563eb)
• Accent: White text on dark, dark text on light
• Style: Professional, clean, tech-forward
• Avoid: Generic stock photo aesthetics, cartoonish illustrations
• Preferred: Dashboard mockups, workflow diagrams, UI screenshots, data visualizations

10. Batch Workflow & Build Order

Session Structure (8-Step Process)

Step	Action	Time
1	Read Playbook — this file	2 min
2	Read Tracking File — what's built, what's next, any flags from last session	1 min
3	Select Today's Cluster — pick ONE cluster, identify 5-8 pages	2 min
4	Calibration Read — read 3 completed pages from a related cluster, note tone/depth/structure	5 min
5	Build Pages (5-8) — define, entity triples, write, build HTML, run gates, quality score	15-20 min/page
6	Internal Linking Pass — add links from new pages to existing, update existing pages to link to new	10 min
7	Update Tracking File — mark pages complete, note issues, set next batch	5 min
8	Deploy Batch — only pages that passed all gates. Update sitemap, llms.txt.	5 min

Build Order by Phase

• Core pages (10 pages)
• Design system / CSS
• Schema templates validated
• Technical files (sitemap, robots, llms.txt)

• All 18 category pages
• All 15 trade pages
• FAQ Hub, /software/ hub, /trades/ hub, /compare/ hub
• Total: ~37 pages

• High-priority matrix pages first (~90 pages)
• Tier 1 comparison pages (15 pages)
• Medium-priority matrix pages (~75 pages)
• Tier 2 & 3 comparison pages (35 pages)
• Build rate: 5-8 pages/session, ~3 sessions/week = 15-24 pages/week
• Total: ~215 pages

• Extract FAQs from all completed pages
• Generate standalone pages in clusters (by source page)
• Build rate: 15-20 FAQ pages per session (shorter content)
• Total: ~548 pages

Drip Publishing Schedule

Wave	Content	When	Batch Size
1	Core pages, hubs, technical files	Day 1	All at once (~15 pages)
2	Category pillar pages	Days 2-5	4-5 per day
3	Trade pillar pages	Days 6-9	4-5 per day
4	High-priority matrix pages	Days 10-30	3-5 clusters per day
5	Tier 1 comparison pages	Days 15-20	3 per day
6	Medium-priority matrix + Tier 2 comparisons	Days 30-60	3-5 clusters per day
7	FAQ standalones	Days 20-90	10-20 per day
8	Remaining comparisons + long-tail	Days 60-90	3-5 per day

11. Progress Tracker

Live build status as of March 16, 2026. Playbook created, matrix defined, ready to begin Phase 1 when Rob confirms.

Summary Dashboard

Status: Not Started

Status: Not Started

18 Software Categories

15 Construction Trades

Hubs

Status: Not Started

Matrix pages will be populated from the priority map. High-priority combinations (~90 pages) are built first, followed by medium-priority (~75 pages). Tier 1 comparisons (15) interleave during high-priority matrix builds. All 15 Tier 1 comparison slugs are tracked and ready.

Status: Not Started

FAQ standalone pages are estimated at: (33 pillar pages x 4 FAQs) + (165 matrix pages x 3 FAQs) + (50 comparisons x 3 FAQs) = 777 potential pages, filtered down to ~548 after deduplication and relevance scoring. Actual count will be determined as source pages are completed.

12. Quality Recovery Process

When a page fails gates or scores below 80, follow this 5-step recovery process:

Which gate failed? Which pillar scored low? Document the specific failure in the tracking file's issues section with the page slug, date, and description.

Patching creates inconsistency in tone, depth, and structure. Rewrite the weak section entirely to maintain content quality and coherence with the rest of the page.

After the fix, re-run ALL 10 critical gates — not just the one that failed. A rewrite can introduce new issues.

Record the issue in the tracking file with: date, page slug, description, and resolution. This creates a learning log for future sessions.

If one page failed for a content reason, its sibling pages might have the same problem. Review 2-3 siblings in the same cluster to verify they don't share the deficiency.