What this stage does
Skills are good at producing repeatable parts. A footer Skill can build the footer. A content Skill can shape page copy. A SEO Skill can prepare metadata. That is useful, but it does not automatically make a website feel finished.
This stage is where Codex becomes the glue. The job is to inspect how the parts meet, find the missing connections, and make the shared behavior consistent across the whole site.
Steps
Guide
List the Parts That Were Built Separately
Start by naming every part that came from a separate Skill or separate prompt. This usually includes the header, footer, page sections, content blocks, metadata, images, legal links, language behavior, analytics, and search tags.
This list matters because integration gaps often hide between responsibilities. One Skill may build the footer perfectly, while another creates pages that do not leave room for it. One Skill may prepare language labels, while another forgets to update the route structure.
Give Codex the list and ask it to compare the parts against the actual website. The first task is not to fix code immediately. The first task is to find where the pieces disagree.
Read MorePrevious guide
Open the guide for turning repeatable website work into reusable Skills.
Ask Codex to Find the Integration Gaps
The best prompt at this stage is direct: inspect the website as a whole and report mismatches between shared components, routes, content, metadata, and expected behavior before editing anything.
For example, Codex should check whether the header and footer use the same navigation model, whether all page links point to real routes, whether mobile navigation exposes the same important destinations as desktop, and whether the language switcher behaves consistently across sections.
It should also look for technical mismatches that are easy to miss in a visual review: duplicate element IDs, missing language attributes, unstable list keys, broken internal links, inconsistent metadata, and components that work on one page but fail when reused elsewhere.
Turn Each Gap Into a Small Glue Task
Do not ask Codex to make the whole website better in one large pass. Convert each mismatch into a small glue task with a clear before and after state.
A good glue task sounds like this: make the language switcher use the same route map in the header and footer. Or: replace hardcoded footer links with the shared navigation source. Or: make every repeated navigation item use a stable key from the data instead of its visible label.
This is the difference between building more parts and connecting the parts that already exist. The output should be a small set of focused changes, not a redesign.
Run Human Review on the Connected Website
After Codex closes the first gaps, review the site like an operator, not only like a developer. Click the paths that matter. Switch languages. Move from a page to a contact action. Open the footer links. Try the mobile navigation. Scan the page title and summary as if you found the site through search.
This review should produce practical notes, not vague taste feedback. Write comments such as: the Dutch route works but the footer label is still English, the mobile menu hides the main service page, the legal link exists but opens the wrong page, or the CTA copy changes meaning between pages.
Then send those notes back to Codex as another small batch of glue tasks. The loop is simple: find a gap, name the expected behavior, fix it, verify it, then move to the next gap.
Promote Repeated Glue Into a Future Skill
Some gaps happen only once. Others appear on every website. The repeated ones should become future Skills.
If every build needs the same header-footer route check, make a navigation integration Skill. If every multilingual site needs the same language switcher checks, make a language integration Skill. If every project needs the same metadata consistency pass, make a search metadata Skill.
This is how the Website Factory improves. Codex handles the glue today, then the repeated glue becomes tomorrow's reusable instruction layer.
Read MoreGround-level guide
See how one repeatable website part becomes a concrete Skill.
Be Aware
Codex is asked to fix everything at once.
Break the work into narrow glue tasks: routes, language behavior, header-footer consistency, metadata, responsive behavior, then final review.
The separate Skills all work, but their assumptions conflict.
Create one shared source for routes, labels, legal links, and repeated navigation data, then make the components read from that source.
The site passes a quick desktop glance but fails mobile or language switching.
Review the connected flows on mobile and across language routes before treating the integration stage as complete.
A recurring integration problem stays trapped in one project.
Turn the repeated check into a new Skill so the next website starts with better instructions.
Return to the Main Guide?
Main guide
Start Your Website Factory
