A redesigned website can look right while pagination, canonicals or indexing rules have changed underneath. Those details need acceptance tests before launch.

For each page type, define:

What crawlers should be able to reach.

Which URLs should be eligible for indexing.

What links, content and metadata the page should return.

Who checks the implementation and what counts as a pass.

One example: if you rely on a page’s noindex directive, blocking that page in robots.txt prevents Google from reading it.

I put together a practical guide to turning technical SEO requirements into a specification developers and QA can actually use.

Projects and client work: NikoCodes

This is a useful acceptance-test framing, Niko. I use the same approach for small launches: map the critical page types, check navigation and canonical/indexing behavior, then give the developer a short evidence pack. If a team needs a quick independent pass before launch, my...

5 things I check when someone says:

"My website isn't converting."

The headline

The CTA

The offer clarity

Trust signals

The user journey

Notice what's missing?

"Make the button prettier."

Design matters.

But design can't compensate for a confusing offer.