Reviewing a Delivered Website and Coordinating the Fixes

1. The Client's Situation

My client is a professional who takes her brand seriously. She invested in a web developer to create a polished, functional website that matched her vision. She handed over her written copy, imagery direction, and layout preferences.

When the developer delivered the site, it looked decent on the surface. But my client had a gut feeling that things weren't quite right. She asked me to review it before she signed off.

2. Building the Crawler with AI

Rather than spending hours clicking through every page and inspecting elements manually, I used Claude (an AI assistant) to help me build a web crawler. The crawler was designed to visit every page on the site and check for specific quality markers.

These are the things the crawler looked for:

• ●Broken links and 404 errors across the entire site
• ●Missing or duplicate meta titles and descriptions
• ●Images without alt text (an accessibility and SEO issue)
• ●Pages with missing or incorrect headings hierarchy
• ●Placeholder text or lorem ipsum that was never replaced
• ●Inconsistent formatting and styling across pages
• ●Missing or incorrect contact information
• ●Pages that weren't mobile-responsive

The crawl itself took minutes. It returned a structured report that I checked by hand before walking through it with my client line by line. A crawl finds the defects it is written to look for, not every quality or accessibility issue, so the manual check was part of the review.

3. What the Review Found

The report listed issues in several categories. Some were cosmetic. Others affected how the site read and how it would be found in search.

Without going into specifics that would identify the client, the issues fell into a few categories:

• ●Copy that was provided by the client but never added to the pages
• ●SEO basics that were completely ignored. No meta descriptions, duplicate page titles, images with generic file names instead of alt text
• ●Broken internal links that led to dead pages
• ●Styling inconsistencies where fonts, spacing, and colours didn't match across sections
• ●Mobile layout issues where content was overlapping or cut off

These were not design preferences. They were checkable errors, and I confirmed each one before it went on the list.

4. What the Client Did With the Report

With the checked report, my client went back to the developer with a documented list of the issues. The project was refunded.

5. Fixing the Agreed Issues

My client then asked me to fix the issues. I went through the checked report and worked through the agreed list:

• ●Added all the missing copy the client had originally provided
• ●Wrote and implemented proper meta titles and descriptions for every page
• ●Added descriptive alt text to every image
• ●Fixed the heading structure for proper SEO hierarchy
• ●Repaired the broken links found in the crawl
• ●Cleaned up styling inconsistencies across the site
• ●Checked each page on mobile and tablet and fixed the layout issues found

By the end, the client had a record of what was found and what was fixed, and the site carried the copy and details she had provided.

6. Why This Matters for Business Owners

Most business owners do not have a way to check whether a delivered website matches what they asked for. A review before sign-off gives them a list, with each item checked, to take back to the developer or to hand to whoever does the fixes.

In this case the client used the list for both. That review and the follow-through are part of the operations support I provide.

7. Using AI to Build the Crawler

I did not write the crawler from scratch. Claude helped me build it, and it did the page-by-page checking that would have taken hours by hand.

The crawler found the checkable items. Deciding what to look for, confirming the findings, and fixing them was my work.