Review what the AI created
Read an AI-built website as a product owner, not only as someone impressed by the first screen.
What you will finish
Understand the main files, verify the content and make a short list of fixes before publishing.
Step by step
- 01
Ask for a map
Ask the tool to explain the project structure, where page content lives, how styling works and what runs in the browser or on the server.
- 02
Verify every claim
Read the visible text. Remove invented facts, fake testimonials, unsupported numbers and promises you cannot keep.
- 03
Follow every path
Open the navigation, buttons, footer links and forms. Check empty, loading, success and error states.
- 04
Inspect dependencies
Ask why each external package or service is needed. Remove abandoned experiments and features you do not understand.
- 05
Make a fix list
Record issues by impact: unsafe, broken, confusing and cosmetic. Fix them in that order.
Use this as a starting point
Review this project with me. First explain the folder structure and the purpose of each important file in plain language. Then identify invented claims, broken journeys, accessibility problems, privacy risks, exposed secrets, unnecessary dependencies and missing error states. Do not change anything until you show me a prioritised fix list.Replace the bracketed notes with your own facts. Read the answer before using it.
Watch for these
- Approving a page because the first screen looks polished
- Changing code you cannot explain
- Ignoring forms and error states
- Publishing placeholder legal or business claims
Before you continue
- You can locate the page content
- Every public claim is true
- Every important link was opened
- Forms were tested
- You understand each external service