What a Redstone Audit Looks Like

Not a grade sheet. A structured look at what is working, where the gaps are, and what to address first so the modernization path is built on evidence, not assumptions.

Request an audit About modernization

The purpose of an audit

An Honest Look Before Anyone Starts Building

Most modernization projects stall not because the work was hard, but because the team discovered problems mid-build that should have been mapped before the first line changed. A migration that hits an unexpected redirect gap, a rebuild that inherits the same analytics holes as the old site, an SEO handoff that loses rankings in month two.

A Redstone audit runs before any of that. Six areas, documented findings, a prioritized path forward. The deliverable is not a slide deck with amber circles. It is a working document your team can act on.

What we examine

Six Areas, Each With Teeth

Each area covers a different failure mode. Some problems show up in metrics. Many do not until something breaks or a migration goes wrong. The patterns below are not hypothetical.

Technical Foundation

The Part Visitors Feel But Cannot Name

Core Web Vitals, render paths, mobile responsiveness, server configuration, image delivery, and caching strategy. Most sites have at least one quiet problem here that costs conversions without ever showing up in a bounce rate.

Patterns we frequently find

Layout shift caused by late-loading fonts or unresized images
Slow server response time masked by a fast CDN edge cache
Third-party scripts blocking the critical render path
Mobile forms that work on desktop but break on the keyboard

Lead and Conversion Systems

The Machinery Behind the Submit Button

Form routing, validation, CRM field mapping, email delivery, autoresponders, source attribution, and internal handoff. This is the area most often built once and never verified again. The result is real inquiries going nowhere.

Patterns we frequently find

Forms that submit successfully but email never arrives
No source or campaign context attached to the lead record
Thank-you pages that load but fire no conversion events
Follow-up emails that arrive from a no-reply address and feel automated

SEO and Search Continuity

The Signals Search Engines Actually Use

Title and description coverage, canonical URL structure, internal link architecture, structured data accuracy, crawl budget, and the redirect map. Gaps here are quiet — rankings erode slowly and the cause is rarely obvious.

Patterns we frequently find

Duplicate pages indexed under both www and non-www versions
Service pages with identical metadata copied from the homepage
Broken internal links pointing to pages that no longer exist
Structured data present but describing the wrong entity type

Analytics and Tracking

Whether the Numbers You Are Seeing Are Real

GA4 event coverage, tag manager configuration, conversion tracking accuracy, cross-domain tracking, attribution window alignment, and the source data attached to each session. Most analytics installs are partial. Many are misleading.

Patterns we frequently find

GA4 installed but only pageviews tracked, no form events
Conversion goals still pointing to UA properties that no longer exist
Paid media pixels firing on every page rather than only on conversions
Self-referral traffic from the payment gateway inflating organic numbers

Content Systems and CMS Health

Whether the Site Can Be Maintained Without You

CMS architecture, content block flexibility, media handling, publishing workflow, and how much technical help is required to make a routine content change. Sites that require a developer to update copy create expensive dependency chains.

Patterns we frequently find

Page templates that hardcode layout so editors cannot change structure
Image uploads with no compression or format guidance
Navigation items that require code changes to update
No staging or preview environment for reviewing before publishing

Architecture and Path Forward

What Should Change and in What Order

A prioritized finding list is not the same as a to-do list. Some fixes require migration. Some can be done in an afternoon. The audit separates high-leverage, low-effort wins from the longer bets so you know where to start and what can wait.

Patterns we frequently find

A redirect chain that started after one migration and compounded after the next
A plugin dependency graph that makes upgrading the CMS version risky
A codebase with no local development environment documented
A vendor contract that owns critical infrastructure without a handoff clause

The deliverable

What You Walk Away With

The audit closes with a working session, not an email attachment. Findings are explained in context so the team understands the decision, not just the recommendation.

Request an audit About modernization

Annotated Finding List

Every finding documented with the affected URL, the observed behavior, the likely cause, and the recommended fix.

Priority Tier

Findings sorted into three tiers: address before launch, address in the first month, and address when the opportunity arises.

SEO and Redirect Map

A complete picture of current URL structure, canonical state, and the redirect logic needed to protect search continuity through any migration.

Analytics Gap Report

A clear list of events that should be tracked but are not, with the tag manager or code changes needed to close the gap.

Walkthrough Session

A structured review of findings with your team so the document is understood, not just delivered.

Next step

The Audit Comes Before the Roadmap

If you are planning a migration, a rebuild, or a platform change, an audit is the right first engagement. It defines the scope of what needs to move, what can wait, and what should be redesigned rather than carried forward.

Request an audit Modernization overview