# Website launch QA, schema and CMS collections

## What it does

The last layer of a website build: the CMS collections the site needs, the per-page schema markup and SEO plan, and two launch checks: performance (speed, accessibility, SEO scores) and a visual review that renders the pages and flags design problems.

## Set it up

The collection schemas and the schema/SEO pack are built from the approved sitemap (see website planning). The QA checks work on any public URL, so run them once the site is on staging.

## Use it

1. **"What CMS collections do I need for the client?"** lists the collections the approved sitemap implies (blog, case studies, team, services, resources and so on), with each field's name, slug and type. ✋ Create them in the Webflow Designer; Nexus then fills them with items.
2. **"Compile the discoverability pack."** writes the JSON-LD schema for each page, a robots.txt that allows AI crawlers, and a title / description / social-card plan for each page. ✋ Paste them into Webflow: page custom code, site settings, page SEO. Nexus can't change Webflow site settings.
3. **"Is the site launch ready?"** runs PageSpeed on mobile and desktop and grades it against the launch targets: Performance 90+, Accessibility 95+, Best Practices 95+, SEO 100, LCP under 2.5s, CLS under 0.1. Failing pages come with a fix list, most important first.
4. **"Review [url] for visual issues."** renders the page on mobile, tablet and desktop and flags spacing, type, alignment, stretched images, broken layouts and horizontal scroll, in an audit doc. It works on any site, including Webflow, WordPress and Wix.

Run both checks for a full launch review: the PageSpeed check doesn't look at the design, and the visual review doesn't measure speed.

## Troubleshooting

- **The collections or the pack say there's no approved sitemap.** Approve the sitemap first.
- **The visual review missed a page.** It checks the URL you give it. Ask once for each page you care about.

## Prompts

- "What CMS collections do I need for the client?"
- "Compile the discoverability pack."
- "Is the site launch ready?"
- "Review [url] for visual issues."