Case Study · May 2026 · Pre-Launch
What an AI-assisted pre-launch audit catches before your customers see it.
A growing local service business in Western Massachusetts was preparing to relaunch on a new domain and a new platform. The launch was imminent. We ran a pre-launch audit, AI-assisted, delivered in under one business day. Here is what we found before it shipped.
Companion case study: Post-launch follow-up (May 14, 2026) — what happened three days after launch when the dev team pushed back on the audit findings.
13Working well
13Bugs shipping
12SEO gaps
10Prioritized fixes
The two findings the client cared about most:
Highest-leverage fix
A single typo, "range of servics" instead of "services", was repeated on roughly 120 templated city and service pages. One search-replace in the platform's template fixes all of them.
Most damaging finding
The owner's personal email was published in the site's structured data with a domain mismatch. Crawlable plain-text, spam-bait, and unprofessional given it referenced a legacy domain rather than the new one.
ErrorsShipping live before launch
Representative cross-section. The full audit report is delivered to the client.
| Category | Finding | Why it matters |
| Site-wide typo | Same misspelling on ~120 templated city and service pages | Visible in search snippets, looks unprofessional, single-edit fix |
| Internal-linking failure | Every "explore other service" button on every city page pointed back to the same page it was on, not the other service | Hundreds of self-referencing links. Massive crawl-equity waste. Template variable mis-bound. |
| Wrong-state copy | "Massachusetts families have counted on us…" appeared on Connecticut city pages | Connecticut customers seeing Massachusetts-only positioning. Conversion killer. |
| Draft IDs in live URLs | 7 city pages had unintentional hex strings appended to their URLs (e.g. /[city]--[state][hex-id]) | Internal CMS artifacts shipping as public URLs. Duplicate-content and ugly-link problem. |
| Slug inconsistency | Multiple city pages live at two URLs simultaneously (one with single dash, one with double) | Duplicate content. Split SEO juice. Confused crawlers. |
| Schema type regression | New schema declared the site as generic LocalBusiness. The previous site correctly used the industry-specific type. | Lost industry signal to Google. Free SEO downgrade. |
| Owner email exposed | Email crawlable as plain text in structured data, with a domain mismatch | Spam risk. Trust signal damage. |
| Two parallel page systems | Each city had both a root city page and a city × service combo page. Up to 7 URLs per city competing for the same intent. | ~180 city-related URLs total. Doorway-page risk under Google's Helpful Content classifier. |
| Branded image filenames | Logos and key images had auto-generated filenames like Untitled-design-XXXX.png | No SEO value from filenames. Easy rename, surprisingly common miss. |
GapsStructured data that could have shipped on day one
Most modern site-builders make structured data trivial to add. The new site was missing pieces that, once added, qualify a site for review stars, FAQ rich results, and breadcrumb appearance directly in Google's search results.
| Missing schema | What it unlocks |
aggregateRating | Gold review stars in the SERP. The client had real reviews on Google and BBB, just not marked up. |
FAQPage | Dropdown FAQ rich results in search. The site already had ~20 Q&A pairs on its FAQ page. None structured. |
Service per service type | Helps Google understand the business's service taxonomy. |
BreadcrumbList | Better SERP appearance, clearer site structure to crawlers. |
areaServed | The client served 60+ towns; declaring them in schema strengthens local relevance. |
openingHoursSpecification | Lost in migration. Local-pack signal. |
priceRange | Lost in migration. Positions tier in local pack. |
For a service business with real reviews and real local presence, the combined upside from these is typically the difference between page-2 and page-1 in local-pack queries.
WorkingWhat they did well
A real audit acknowledges what's working. From this client's new site:
- Geographic intent baked into the title tag: clear regional positioning
- Real on-page differentiation ("we are not the cheapest movers, and that's by design")
- A modern, distinct brand palette that differentiates from generic competitors in the space
- A genuine long-form local content piece (researched, real numbers, real civic context, not AI slop)
- A substantive FAQ page with answers that match a serious operator
- 60+ city and region landing pages: a real local-SEO scaffold most competitors in their market don't have
- Apex to www redirect working, sitemap served correctly, canonical tags present
The site is well above average for its category. The audit's job was to find the gap between "well above average" and "ready to launch without leaving money on the table."
PlanHow we sequence the fixes
Most audits give clients a long unprioritized list. We don't. Every recommendation is mapped to impact-per-edit, so the highest-leverage fixes get done first.
Priority 1. Site-wide template fixes
One edit, hundreds of pages affected. Typo fix, broken-link fix, wrong-state copy fix, slug strategy decision. Maybe two hours of platform work. Fixes 95% of the per-page error surface.
Priority 2. Schema additions
One snippet per template, qualifies the site for rich-result eligibility. Half a day of structured-data work, weeks of compounding SEO upside.
Priority 3. Content depth
A strategic decision the client makes: invest in unique per-city content, or consolidate. The audit names the tradeoff and recommends a path. It doesn't dictate.
Priority 4. Polish
Small visible fixes that add up: branded filenames, social-share images, schema cleanup, robots and sitemap hygiene.
MetaSelf-audit, included in every deliverable
This is the section most audits don't have.
Every Got It Done audit includes a pass where we audit our own findings. On this engagement the second pass caught three of the highest-impact issues that the first pass missed: the typo replicated across ~120 templated pages, the self-referencing service-card links, and the wrong-state copy appearing on Connecticut pages. Without the meta-pass, those would have shipped.
Why we do this: an audit that pretends to be infallible isn't trustworthy. Showing the meta-pass, what we initially missed and what we corrected, is what separates a thorough audit from a hand-wave.
PricingFour engagement tiers
Pricing is scoped to the size of your site and the depth of the engagement. Every quote is custom; we send one within one business day of your audit request. The case study above corresponds to the Standard Audit tier.
Quick Scan
For small businesses wanting a fast health check on a live site without committing to a full audit.
- Homepage plus 5 sampled pages scanned
- Top 10 critical issues identified
- Concise written brief focused on the top issues
- Markdown and PDF deliverable
- Evidence trail per finding
24 hours
Standard Audit Case study tier
For sites at any launch stage needing a thorough technical and content review. The most common engagement.
- Full site scan via crawl
- Structured data review with rich-result gap analysis
- On-page error check across templated pages
- Content-depth assessment
- Prioritized fix sequence ranked by impact-per-edit
- Self-audit pass on findings
- Full written brief with prioritized findings, evidence-backed throughout
- Markdown and PDF deliverable, evidence-backed
1 to 2 business days
Comprehensive Audit
For pre-launch sites, platform migrations, or strategic relaunches needing the full stack.
- Everything in Standard Audit
- Competitor comparison, up to 5 competitors crawled and analyzed
- SERP positioning snapshot for target queries
- Schema validation against Google's Rich Results test
- Pre-launch checklist with sign-off
- Stakeholder presentation deck included
3 to 5 business days
How quoting works. Send a request with your domain and a one-line description of where you are in your launch cycle. We respond within one business day with a tier recommendation and a fixed-fee quote based on site size, complexity, and the depth of detail you want. Nothing starts until you approve the quote.
ScopeAudit tiers identify. Fix Pack implements.
Audit tiers (Quick Scan, Standard, Comprehensive) are advisory: we find what's wrong, explain it in plain English, and tell you exactly what to ask your web developer to fix. You hand the brief to your developer and they ship the changes.
If you don't have a developer, or yours is buried, the Fix Pack tier ($449 flat) is the implementation option: we run the audit and then ship the fixes ourselves. The price is flat on purpose so we have no incentive to invent extra "work" to bill against, and the scope is bounded by audit findings drafted before any payment for fixes.
Audits are paid in full at delivery. Findings are non-refundable. You're paying for the analysis and the prioritized recommendations, which are delivered in full at the agreed turnaround time.
VoiceWritten for humans, not developers
Every finding in a Got It Done audit follows the same plain-English structure. Your audit reads like a conversation, not a technical manual.
Example, from this audit
What's wrong. The phrase "range of servics" appears on roughly 120 of your city and service pages. It should say "services." It's a single misspelled word in your template.
Why it matters. Search engines and visitors notice typos. It makes the site look careless. Because the typo is in your page template, it appears on every city page at once, so the impression of carelessness compounds.
What to do. Ask your web developer to search the city and service page template for "range of servics" and replace it with "range of services." It's a single edit that fixes all 120 pages at once.
That's the structure of every finding in every audit. You can read it and forward it to your web developer without needing to translate.
FitWho this is for
- Small businesses with existing websites that aren't actively maintained for technical SEO quality
- Operators who want more organic traffic without enterprise-level spend
- Service businesses, retailers, professional firms, anyone whose website matters to their growth but who doesn't have an in-house SEO or technical reviewer
- Sites at any launch stage: pre-launch, recently launched, or established and underperforming
- Founders or operators who'd rather pay a focused fee for a clear, actionable audit than a long-term agency retainer
Who this is not for
- Large enterprises with dedicated in-house SEO teams. Out of scope.
- Pure e-commerce funnels focused on Shopify-checkout optimization. Different problem set.
- Operators who want their audit results dictated to them, not explained. We explain the tradeoffs; the client makes the call.
BookReady when you are
A typical audit kicks off the same week, delivers the next business day, and saves the client more in pre-launch fixes than the audit itself costs. Every single time.