Release surfaces
Inspect the page where people and machines actually meet it.
Canonical identity
Title, description, canonical URL, and social image describe the same page and route.
Crawl surface
Sitemap, robots, feed, and machine-readable pages expose the route consistently.
Structured claim
Schema is generated from the article record so dates, author, image, and relationships do not become a second hand-maintained copy.
Release check
Verify the output after the content is already valid.
Content validation cannot tell us whether a generated route exposes the intended metadata in the final production build. Both checks are needed.
01
Validate the source record
Reject missing titles, dates, images, sources, relationships, and invalid publishing metadata.
02
Generate crawl outputs
Produce sitemap, feed, and machine-readable surfaces from the same published corpus.
03
Build the actual site
Use production output to reveal routing and rendering mistakes that a development server can hide.
04
Smoke the public routes
Check the homepage, article index, canonical article, robots, sitemap, feed, and machine-readable route.
What this does not prove
A valid crawl surface makes the page eligible to be understood. It does not guarantee ranking, citation, or traffic.
Those outcomes need Search Console and reader evidence after launch. The release gate can only prove that Mannvit did not publish contradictory technical claims.
Bring a route that feels polished but is hard to trust in search.
We can inspect its public surfaces as one release contract.
Bring the page, report, or workflow as it is now.
We reply with the clearest next step, or an honest no.
