Quality control after converting an AI website to WordPress

Review by template, not by page

A converted site may have dozens or hundreds of pages, but they are built from a handful of layouts: the home page, service pages, articles, listing pages and a contact page. I review one representative page per layout in depth on desktop, tablet and mobile. When a spacing or font issue appears, fixing it in the theme or a block style corrects every page that uses that layout at once.

Small visual differences compared with the original are normal after a conversion. They are typically resolved in minutes in the block editor or with a plugin setting, and they never require rebuilding the site.

Content and media integrity

Compare page counts between the old sitemap and the new one, then spot-check headings, lists and tables for completeness. Confirm that images were imported into the media library rather than linked from the old host, because those external links disappear when the old project is switched off. Add meaningful alternative text to informative images and leave decorative images with empty alt attributes.

Accessibility basics

Check that each page has exactly one H1, that heading levels do not skip, that colour contrast meets WCAG AA and that every interactive element can be reached and operated with the keyboard. Visible focus styles matter: many AI-generated designs remove them. Automated tools such as Lighthouse or axe catch roughly a third of issues; a short manual keyboard test catches most of the rest.

Launch readiness

Before switching DNS, set the WordPress site address to the final domain, enable HTTPS, configure redirects, generate the XML sitemap and remove any 'discourage search engines' setting left from staging. After launch, verify the raw HTML of key pages for title, canonical and language attribute, submit the sitemap and keep the old project available read-only for a few weeks as a reference.