Design 6
AI Ops Partner
AI Search Readiness Audit
July 17, 2026  ·  Prospect Mode
Domain: roofix.org
Type: Local Service — Roofing (Multi-Market / National)
Primary Platform: Google AI Overviews
Market: 48 States · HQ Arlington, TX
AI Search Readiness Report

Roofix

https://www.roofix.org/

Roofix operates in 48 states with real branch addresses, a named leadership team, and — on one page — proof the team can build genuinely strong local content. But the site is almost entirely unreadable to AI systems. Zero LocalBusiness or Service schema, no llms.txt, no reviews anywhere, and a scatter of duplicate and placeholder pages mean AI Overviews, Perplexity, and ChatGPT Search have almost nothing reliable to cite — despite the raw material already being there.

30
/ 100
Foundation Absent
Pillar Scores
6 pillars · weighted
Crawlability & Indexation15%
57% (12/21)
Site Structure & Semantics15%
43% (9/21)
Structured Data15%
14% (3/21)
Local Trust Signals15%
43% (9/21)
Content Quality & Proof15%
29% (6/21)
GEO / AI-Citation Readiness25%
8% (2/24)
Foundation Absent (0–39)
Basic Visibility (40–59)
Competitive (60–79)
AI-Ready (80–100)
Top 5 Issues — Ranked by Impact
Sorted High Impact first
#1
Real Branch Addresses for 48 States — Zero Schema Behind Them
The /locations page lists a real street address and phone number for every state Roofix operates in, but none of it is marked up — the only JSON-LD on the site is a generic WebSite block with a name and logo. AI systems have no machine-readable way to confirm Roofix operates in any specific state.
Fix: Deploy Organization schema with a location/branch entry (or individual LocalBusiness schema) for each state office, using the address data that already exists on the page today.
This is the rare case where the underlying data already exists — schema is the only missing step between "invisible" and "citable" for every one of those 48 markets.
Critical Low effort
#2
No llms.txt File
roofix.org/llms.txt returns a 404 — there's no structured, machine-readable brief on services, the 48-state footprint, leadership, or licensing for AI crawlers to ingest before they parse pages.
Fix: Publish /llms.txt summarizing services (residential, commercial, repair, storm damage), the national footprint, licensing, leadership team, and contact info.
Perplexity and ChatGPT Search consume llms.txt as a priority document before parsing pages — without it, they start from zero context on a company that operates nationwide.
Critical Low effort
#3
Duplicate and Placeholder Pages Diluting the Site
The sitemap includes duplicate URLs alongside the real ones (/home-1, /home-page, /roofing-2, /contact-1) and blog posts still on their unedited template slugs — one URL (/blog/blog-post-title-four-l6pw2) resolves to a page titled "About Roofix," a leftover placeholder rather than an actual post.
Fix: Remove or redirect duplicate pages, delete or rewrite placeholder blog posts, and confirm canonical tags point to the single correct version of each page.
Duplicate and junk URLs waste crawl budget and create ambiguity about which page is authoritative — AI crawlers can end up citing the wrong or empty version.
High Low effort
#4
No Reviews, Ratings, or Testimonials Anywhere on the Site
Across the homepage, service pages, and a /gallery page that exists but isn't linked from navigation, no review content, star rating, or testimonial was found anywhere — despite the company operating in 48 states.
Fix: Add a visible reviews section with AggregateRating + Review schema on the homepage and key service pages, sourced from existing Google/BBB reviews if available.
Review signals are one of the strongest citation triggers for Google AI Overviews on "best roofing company" queries — right now there's nothing for it to point to.
High Med effort
#5
Location Coverage Is a Plain Address List, Not Content Pages
The /locations page is a flat list of 48 state addresses with no local content. Meanwhile a genuinely strong city-specific page exists for Columbus, OH — real local detail, clean single-H1 structure, licensing and service info — but it isn't linked from primary navigation or from /locations itself, so it's effectively invisible.
Fix: Build dedicated, linked landing pages for major markets using the existing Columbus page as the template, and link every one from /locations.
Roofix has already proven it can build the right kind of page — the Columbus example just needs to be replicated and connected, not invented from scratch.
High Med effort
Platform Impact
Where Roofix is losing citations

As a national local-service roofing company, the primary citation battleground is Google AI Overviews — where homeowners search by city. Here's what each platform needs, and where the site currently fails.

Primary Target
Google AI Overviews
No LocalBusiness/Service schema despite real address data for all 48 states.
No reviews or ratings to cite for "best roofing company near me" queries.
Only one true local content page (Columbus) exists across a 48-state footprint.
Secondary Target
Perplexity
No llms.txt — no structured business brief before parsing pages.
Duplicate and placeholder URLs create ambiguity about which page is canonical.
Tertiary
ChatGPT Search
Same schema gaps as Google — Bing index finds the same empty structured data.
No FAQ content or schema for snippet-style answers.
The Opportunity

Roofix already has what most competitors would need years to build: a real 48-state footprint with actual branch addresses, a named leadership team, and at least one page (Columbus, OH) that proves the team knows how to write content AI systems would actually cite. The gap isn't the business — it's that none of this is applied consistently or made machine-readable.

Closing the schema and llms.txt gaps, cleaning up duplicate pages, and replicating the Columbus page pattern across a handful of priority markets would move this site from 30/100 (Foundation Absent) toward real citation coverage — using material the company has already built.

Let's fix the pipeline

A focused technical pass — schema across your existing state addresses, llms.txt, a cleanup of duplicate pages, and a repeatable location-page template — is a scoped engagement, not a full rebuild. Happy to walk through exactly what that looks like.