Use Codex to ship SEO improvements with evidence

Describe the defect and the expected page

A good task names the affected route, the observed issue, and the intended behavior. For example: “The article template uses the collection description on every post. Generate the description from each article’s reviewed summary and preserve the current URL.” Attach the audit evidence so the coding task starts from a confirmed problem.

Codex is useful here as an implementation workflow. A coding agent cannot establish that a keyword has demand or that a rewritten title will improve clicks merely by inspecting the repository. Keep those hypotheses attached to the task, rather than presenting them as facts.

Put important project guidance in AGENTS.md

OpenAI documents AGENTS.md as a way to give Codex project instructions. Guidance can be scoped to the repository and relevant directories. Read the current instructions guide.

For a content site, record the source files, generation command, public directory, route conventions, and meaningful checks. Say which publication dates are historical. Document where enquiry and payment flows live so a content edit does not inadvertently alter them. Instructions should explain the project’s actual constraints, rather than repeat a generic coding checklist.

Use an implementation brief

Fix the confirmed metadata issue described in audit-notes.md.
Read the applicable AGENTS.md and find the source template first.
Preserve public URLs, publication history, forms, and analytics consent.
Update the source and generated output where the project requires both.
Verify the affected routes and one unaffected route.
Return the changed files, check results, and a preview for review.
Report deployment separately from a local build.

That last sentence prevents an ambiguous handoff. “Built” might mean source files exist; “live” should mean a deployed response has been checked.

Make the check reflect the actual risk

For a metadata change, inspect the served HTML and escaping. For a route change, verify redirects, query strings, internal links, and a genuine not-found response. For a generated article, check that headings, source links, canonical URL, and structured data agree with the visible content.

Keep the check proportionate. A paragraph correction usually needs a careful content and page review. A shared template change deserves coverage of more than one content type. Do not ask the agent to claim a browser review if it only inspected a file or ran a DOM simulation.

Close the release with a decision record

Save the commit or release reference, affected pages, previous version, live-check result, and the reason for the change. If deployment fails, retain the known working version and explain the failure; a successful source upload alone is not the completion signal.

Illustrative release note: “Article descriptions now use each article’s summary. Five affected routes and one unchanged page returned the intended metadata after deployment. Search impact has not yet been measured.” This is a useful engineering result without an unsupported marketing claim.

Then return to your research brief. Review impressions, clicks, and qualified actions over a suitable period, accounting for other changes. Let Codex help with the implementation loop while keeping the business decision grounded in observed evidence.