The Edge Construction Co.

AEO Implementation Plan

Answer Engine Optimization — Internal Reference & Status Tracker

Revised: April 9, 2026

What Is AEO and Why It Matters

Answer Engine Optimization (AEO) — also called GEO (Generative Engine Optimization) or AIO (AI Optimization) — is the practice of structuring a website so that AI-powered answer engines (ChatGPT, Google Gemini, Perplexity, SearchGPT) can find, read, understand, and cite it as an authoritative source.

These tools use Retrieval-Augmented Generation (RAG): they search the web, pull the most relevant content, and synthesize an answer. If your site isn't structured for machines to read, you won't be cited — even if you rank on Google.

For The Edge, the goal is to become the cited source when a GC, owner, or developer asks an AI: "Who does commercial carpentry in Chicago?" or "Which framing sub uses Procore and laser layout?" That requires winning on three fronts: technical markup, on-site content, and off-site authority.

Test it now: Go to Perplexity.ai and type: "Who are the best commercial carpentry subcontractors in Chicago?" — the sources it cites are the sites we need to match or appear on.

Status Dashboard

23
Completed
4
In Progress
4
To Do

Last updated: April 21, 2026 — site is live at theedgeconstructionco.com. Remaining work is entirely off-site authority building. See Site Changelog below for additional improvements made outside AEO scope.

0. Platform Migration — Squarespace → HTML / Netlify

The foundation of this entire AEO plan is the decision to abandon Squarespace and rebuild the site as hand-coded HTML/CSS/JS hosted on Netlify. This is not a cosmetic change — it is the single most important structural decision for AI citability.

What the Old Site Looked Like

The prior Squarespace site had 16 indexed URLs — almost entirely blog posts buried at /commercial-construction-blog/* slugs. The sitemap contained no dedicated service pages, no project detail pages, two orphaned clone URLs (/gallery-clone-…, /home-clone-…), and two draft posts with machine-generated gibberish slugs (/di9xcffcm…, /d9gyvybc…). The site was not structured for discovery by AI or search crawlers. It was a portfolio with a blog tacked on.

Old sitemap coverage: 1 blog index · 9 blog posts · 1 careers page · 1 gallery page · 2 clone/draft artifacts = 14 real pages, none purpose-built for service- or location-based AI queries.

What the New Site Has

The rebuilt site ships with 28 purpose-built pages: a home page, services hub, 5 individual service pages, projects hub, 10 project case study pages, technology page, about page, careers page, contact page, FAQ page, AI info page, and privacy policy — every one with a clean slug that maps directly to what contractors and owners search for. All pages carry full JSON-LD schema, canonical URLs, OG tags, and author attribution.

Why Netlify + Static HTML Is Superior for AEO

Full Schema Control — No Workarounds Done
Squarespace restricts JSON-LD injection to Code Injection blocks that execute unreliably and are stripped in some render contexts. On the new site, <script type="application/ld+json"> blocks live directly in each page's <head> — exactly where Google's and Bing's structured data parsers expect them. No middleware, no platform stripping, no race conditions.
Clean Crawlable HTML — No Client-Side Rendering Done
Squarespace pages are JavaScript-rendered: the initial HTML response is a shell, with content injected after a JS bundle loads. Many AI crawlers (Perplexity's Spider, Anthropic's ClaudeBot, OpenAI's GPTBot) are lightweight scrapers that do not execute JavaScript. They see a blank page. Static HTML delivers the full content in the first byte — every heading, every paragraph, every schema block — to any crawler, every time.
Root-Level File Placement (llm.txt, robots.txt, ai-info.html) Done
robots.txt deployed welcoming all AI crawlers (GPTBot, ClaudeBot, PerplexityBot, anthropic-ai, cohere-ai). llm.txt live at site root with structured plain-text company summary. /ai-info page live with full LocalBusiness schema and prose summary for AI crawlers.
Faster Load Times — No Squarespace Platform JS Done
Squarespace loads 400–600KB of platform JavaScript on every page regardless of what features you use. The new site loads only the CSS and JS it actually needs. Google's Core Web Vitals — which influence AI-source credibility scoring — benefit directly from lighter pages. Netlify's global edge CDN serves static assets from nodes closest to the visitor, reducing TTFB further.
URL Structure Matches Service + Location Taxonomy Done
The old site buried project content at /commercial-construction-blog/varsity-theater-project. The new site uses /projects/varsity-theater-evanston and /services/metal-stud-framing — URL slugs that map directly to the entity type and service keyword. AI models parse URL structure as a relevance signal; descriptive slugs in a logical hierarchy outperform blog-style URLs for every service and location query this site needs to win.
No Platform Lock-in on Any HTML Element Done
Squarespace controls which meta tags, heading structures, and link attributes it will render. Custom rel attributes, aria-label usage, and schema nesting are all subject to platform quirks. The new site is vanilla HTML — every tag, attribute, and schema property works exactly as the spec defines it. No surprises, no undocumented stripping.

1. Technical Foundation

The most reliable way to get cited by an AI is to tell it exactly who you are, what you do, and where you operate in a format it cannot misinterpret. That means JSON-LD structured data (Schema.org) and a human-readable AI summary page.

LocalBusiness / GeneralContractor Schema Done
Full GeneralContractor JSON-LD on index.html — includes name, address, geo coordinates, phone, service area, priceRange, and knowsAbout array for all five services.
FAQPage Schema Done
FAQPage JSON-LD implemented on: index.html, services.html, technology.html, faq.html, and all five service pages. Each FAQ uses question-format H2 headings to match natural AI queries.
Service Schema on all Service Pages Done
Individual Service schema with provider, areaServed, and description on Metal Stud Framing, Commercial Millwork, Drywall Solutions, and Acoustic Installations pages.
Article Schema on all Project Pages Done
All 10 project pages carry full Article schema: author (Bill Haidl), datePublished, dateModified, articleBody, and mainEntityOfPage.
Speakable Schema on Service Pages Done
SpeakableSpecification markup flags the most AI-relevant content blocks on each service page for voice and AI summarization.
BreadcrumbList Schema Done
BreadcrumbList on all service pages, project pages, and privacy.html — helps AI models understand site hierarchy and content relationships.
Canonical URLs + Open Graph on all pages Done
Every page has a <link rel="canonical">, and full OG tags (og:title, og:description, og:url, og:type, og:image). Titles ≤60 chars, descriptions ≤160 chars.
AI Summary Page (/ai-info) Done
Live at /ai-info. Clean, minimal HTML with full prose descriptions of all five services, differentiators, service area, company facts, key personnel, and LocalBusiness JSON-LD schema. Linked in footer of all pages.
llm.txt at root Done
Live at /llm.txt. Structured plain-text summary covering company NAP, founding year (1996), all five services with descriptions, differentiators, service area, key personnel, and pointer to /ai-info.
NAP Consistency Audit In Progress
Name, Address, and Phone must be identical everywhere — website footer, Google Business, LinkedIn, BBB, The Blue Book, Houzz, Yelp, Angi. Even a difference between "The Edge Construction Co." and "Edge Construction" causes AI models to treat them as separate entities and dilutes authority. Canonical form: The Edge Construction Co., Inc. · 1540 Hecht Drive, Suite G, Bartlett, IL 60103 · (224) 208-1062

2. On-Site Content

AI models primarily read text. Video reels and photo galleries are invisible to them without accompanying descriptions. The site needs to be a source AI can quote — which means structured, question-answer-friendly text that directly addresses what GCs and owners are searching for.

10 Project Case Study Pages (500+ words each) Done
All 10 project pages carry full written case studies: scope, materials, challenges, technology used, and results. AI can cite these as expert references for specific niches (hospital fit-outs, historic restorations, automotive builds, etc.).
FAQ Sections with Question-Format H2 Headings Done
Service pages use question-format H2 headings throughout body copy (e.g., "How does The Edge reduce RFIs on framing scopes?"). FAQ accordion sections appear on the home page, services hub, technology page, all five service pages, and the dedicated /faq page — each with matching FAQPage schema.
Author Attribution (Bill Haidl, OSHA-30) Done
All service pages and project pages carry a byline and Person schema for Bill Haidl. AI models weight "E-E-A-T" (Experience, Expertise, Authoritativeness, Trust) signals heavily — a named, credentialed author strengthens citability.
External Authority Links (ASTM, IBC, UL, AWI) Done
Service pages link out to recognized standards bodies (ASTM, IBC, UL, AWI). Outbound links to authoritative sources signal domain expertise to both search engines and AI content evaluators.
Video Caption / Description Text Done
All 10 .vr-card-desc descriptions rewritten with keyword-rich language: company name, trade names, locations, and technology terms. Crawler-context paragraph added below the carousel naming all project types and technologies in plain text.
Dedicated /faq Page Done
Live at /faq. 17 Q&A items in 5 sections (The Company, Metal Stud Framing, Drywall, Millwork & Acoustic, Technology) with full FAQPage JSON-LD schema. Includes all AEO target questions: light gauge vs. structural framing, Continuous Flow Drywall, No Coat machine, Procore timelines. Linked in footer of all pages.
SEO Title Optimization — "Chicago" in Titles Done
"Chicago" added to all five service page titles, the services hub, technology page, and projects page. Format: Commercial Metal Stud Framing Chicago | The Edge Construction Co.

3. Off-Site Authority

AI models don't just read your site — they triangulate authority from directories, review platforms, and third-party mentions. A strong profile on the sites that AI scrapes is as important as on-site content.

Google Business Profile — Complete & Active In Progress
Google Business Profile is the #1 driver for local construction SEO and is heavily weighted by Google Gemini. Profile must be 100% complete: photos updated, services listed, responses to all reviews. Goal: acquire 3+ new reviews per month. AI models treat high-rated, frequently-reviewed companies as trusted entities.
Houzz Profile — Add Project Text To Do
The Edge is currently listed on Houzz under "Carpenters near Morris, IL" but the profile is thin. LLMs scrape Houzz listings frequently. Add project descriptions, photos with captions, and service descriptions. Match the NAP exactly to the site.
LinkedIn Articles — Tech Differentiators In Progress
Three articles written and ready to publish: (1) Factory in the Field, (2) Continuous Flow Drywall Finishing, (3) Running Every Job on Procore. Copy-paste ready at linkedin-articles.html. Publish 2–3 weeks apart on Bill's LinkedIn profile as Articles (long-form), not posts.
BBB + The Blue Book — Verify Listings To Do
The Edge already appears on The Blue Book and BBB. Verify NAP is identical, add a description, and ensure the website URL is current. These are high-authority directories that AI scrapes for "top contractors" lists.
ABC Illinois + CNG — Ensure Web Listing To Do
As an ABC member and CNG affiliate, ensure The Edge has an active, text-rich profile on both directories with a backlink to the site. Trade association membership pages are trusted by AI as authority signals for professional standing.

4. Monitoring — Are We Being Cited?

Run these queries monthly in Perplexity, ChatGPT, and Google Gemini to track whether The Edge is being cited and who the competition is. Look at the source footnotes — those are the sites you need to match or appear on.

"Who are the best commercial carpentry subcontractors in Chicago?"

"Which commercial framing contractors in Chicago use Procore?"

"What is Continuous Flow Drywall finishing and who uses it?"

"Best metal stud framing companies in the greater Chicago area?"

"Commercial drywall prefabrication subcontractors Chicago suburbs?"

If The Edge doesn't appear: Look at the sites that ARE cited. Get listed on those directories, get a mention in those publications, or outrank them on the matching keyword. The answer is always "show up where the AI is already looking."

5. The Core Principle

AEO isn't a separate discipline from SEO — it's SEO taken seriously. Every item on this plan makes the site better for Google and for AI answer engines simultaneously.

The Edge has a genuine story to tell: 30+ years, real technology (Procore, Hilti + Spectra Precision QML800 laser layout, Continuous Flow Drywall, prefab shop), named experts, real projects, real testimonials. That content exists. The job is to structure it so that machines can find it, read it, and cite it — without needing a human to translate.

Where things stand now: The /ai-info page, standalone /faq page, llm.txt, and robots.txt are all live. On-site AEO implementation is complete. The remaining work is entirely off-site: building citation authority through directory listings, industry mentions, and inbound links from sources AI crawlers trust.

Site Changelog — Improvements Beyond AEO Scope

These updates were made to the new site during the build process and represent improvements over the old Squarespace site — independent of the AEO implementation plan above.

Pending — Gary / Bill Action Required
Apr 21, 2026
Apr 17, 2026
Apr 9, 2026
Apr 8–9, 2026
Prior to Apr 8
The Edge Construction Co.

Internal Resource

AEO Plan