Sixth City Marketing

AI audit vs. strategist audit · A roofing company

Right track. Wrong destination.

We ran a roofing client's website through a ChatGPT site audit. A lot of it sounds right, and some of it is right. The longer the track runs, the further off course it gets, and the misses are the ones that matter most.

Our strategy ChatGPT's audit
The two audits start together and split apart Both audits agree on location pages, project pages, and internal linking. After that, ChatGPT recommends a generic cost post and consolidating phone numbers, and never mentions link building, map pins, or the site's AI-written copy. Our strategy localizes the cost post, keeps CallRail, builds links, adds map pins in priority suburbs, and replaces the AI-written copy. Shared ground Where it drifts What it never saw Location pages Project pages Internal links Cost post, localized cost post, generic Keep CallRail "too many numbers" Link building not mentioned Map pins not mentioned AI-written copy not mentioned context gap
3 of 8: Internal links (shared ground)

Shared ground

At face value, it looks decent

These three recommendations are real, and they line up with what we would do. This is why AI audits are convincing: the first few stops are right.

Agree

Optimize location pages

Rewriting the city pages is core to our plan, starting with the suburbs that bring in the most revenue.

Agree

Build out project pages

Real jobs in real neighborhoods are proof a roofer works there. Good call.

Agree

Improve internal linking

Pointing links at the pages that make money is in our strategy too.

Where it drifts

Close enough to sound right. Wrong enough to cost us.

These are the hard ones to catch. The recommendation is in the right area, but acting on it as written would waste hours or break something that works.

Blog content

Drifts
RecommendationPublish blog content answering common questions, like "How much does a roof replacement cost?"
How much does a roof replacement cost?
How much does a roof replacement cost in [your city]?

Localize it, or AI eats it.

A generic cost question gets answered right in the AI response, so nobody clicks. Tie it to the client's city or a priority suburb and we become the local source AI is far more likely to cite.

Phone numbers

Drifts
RecommendationThe site shows several different phone numbers. Consolidate to one number for consistency and user trust.

Those numbers are CallRail, on purpose.

Different numbers let us tell which calls came from organic search. Before we set it up, the client couldn't separate organic calls from paid ones.

People don't memorize a roofer's number. They tap it. The tracking is worth far more than any confusion it could cause.

What it never saw

Three of the biggest levers weren't on the list

Nothing in the audit was wrong here. It was just blank. These are the moves most likely to grow leads for this client.

Authority and link building

Missed
Nothing about backlinks or authority.

The site desperately needs authority.

The companies holding the local map pack have much stronger sites. No amount of on-page work closes this gap by itself.

Map pack leader49
Map pack #236
Our client25
Ahrefs Domain Rating, 2026. Our client's 25 is inflated by spam links.

Map pins in priority areas

Missed
Nothing about map visibility or Google Business Profiles.

One pin can't cover the whole metro.

The only Google Business Profile that ranks sits on one edge of the metro. Its map rankings fade fast with distance, and the money is in suburbs on the other side of town. We need more pins in those priority areas, each with its own profile.

682 mi
403 mi
~410 mi
Local Falcon, "roof replacement," 2026. Share of top-3 map results.

AI-written content

Missed
Nothing about the copy being AI-written.

The site was riddled with AI writing, and a lot of it is still there.

Most pages were written with AI before we started. We've rewritten a lot of it, but plenty remains. Generic AI copy drains trust with buyers and holds back performance.

AI audits never flag this. They read AI-written copy as normal copy, so the tool is blind to one of the site's biggest problems.

All 10 blog posts on the site at kickoff read as AI-written. Only 2 showed any search impressions (Google Search Console, 90 days).

Why it missed

It audited a website. We manage a business.

ChatGPT only saw the pages. Every miss above traces back to something it had no way to know.

The kickoff call

The owners told us which suburbs are where the money is.

The competitors

Who actually holds the map pack, and how strong their sites are.

Map grid data

How far their one pin really reaches.

Our tracking

Why the site has more than one phone number.

How search is changing

Which content AI answers on its own, and which it still has to cite.

Who wrote the site

Where the copy came from. AI doesn't flag writing that sounds like itself.

The ChatGPT column paraphrases its audit of the client's site. Client details are anonymized.

Spotting the drift

Four questions to ask any AI recommendation

The differences are hard to see, and we have to catch them anyway. Run each recommendation through these before it goes into a strategy.

1

What didn't it mention?

Check for gaps, not just errors. Links, map presence, and AI-written copy are the usual blind spots.

2

Would it need client context to be right?

Priority areas, tracking setup, and past work all live with us, not on the site.

3

Is it local enough?

If the idea works for a roofer in any city, AI can answer it without us.

4

Is the "problem" something we did on purpose?

CallRail numbers, redirects, and noindexed pages often look like mistakes from the outside.