WE2AI
Console ↗
Home/AI Marketing Classroom/Codex Handbook
WE2AI CLASSROOM / GUIDE 01

B2B marketing with Codex.
From products to inquiries.

A practical handbook for exporters and B2B teams using Codex or the Codex workspace in ChatGPT desktop. Turn product knowledge into market research, useful website pages and a measurable inquiry workflow.

Start with the setup ↗Explore 27 workflows ↓
Paper-cut illustration connecting a manufacturer’s bottle, a website and an overseas inquiry
Practical handbook27 SOPs
AI-generated concept illustration, not product photography or evidence of results.
Who it is forExporters, B2B marketers and website teams
ToolsCodex / ChatGPT desktop
FormatWalkthroughs, prompts and acceptance checks
Updated20 Oct 2026 · check your app’s current features
THE LEARNING PATH

Follow the workflow, or find a specific task.

Validate one product before repeating the process.

01 / RESEARCH

Find a real market need

Choose buyers, markets and keywords.

02 / BUILD

Build useful pages

Plan, write, preview and upload.

03 / IMPROVE

Improve the website

Review content, links and usability.

04 / ACQUIRE

Measure real inquiries

Connect ads, indexing and search data.

05 / ITERATE

Update from evidence

Refresh content and page ownership.

00

Tell Codex who you are and what to deliver.

You do not need to start by learning to code. Supply reliable files, set the task boundaries and define a reviewable result.

First session: five steps

  1. Install and sign in to the official desktop app. Choose Codex in the product selector, then New chat. If your app has no such entry, check the official installation and feature guidance for your version.
  2. Create or select a project linked to a local folder. Examples: D:\codex\company-export on Windows or ~/Documents/codex/company-export on macOS. No particular drive is required.
  3. Add shareable company information, specifications, buyer profiles, brand requirements and current URLs. Remove credentials, customer personal data and material you lack permission to share.
  4. Use the project brief below. Review the missing-information list and task plan before assigning focused chats.
  5. When browser work is needed, name the site and allowed actions. Sign in yourself. Review the concrete result before publishing, sending messages, spending money or changing global settings.

Source: official OpenAI desktop guide ↗. Availability and menus vary by version, OS, account and organization settings.

Follow the actual product interface

Codex desktop screenshot highlighting the Codex selector and the selected codex-project in the project menu
User-supplied product screenshot with private project/chat details redacted. Labels, model names and permission status reflect the captured version; your app may differ.
Close-up: Codex and New chat controls
1. Choose Codex, then New chatUse the top-left product selector. Check that it reads Codex, then use New chat for a focused task.
Close-up: project selection and New project control
2. Choose or create the projectOpen the project picker above the composer. Select your marketing project, or use New project. The checkmark identifies the selected project.
Before sending a task, check the project name and permission control below the composer. This screenshot shows Full access, which is not a requirement for this tutorial. Start with restricted access and authorize only what your task needs. Do not copy the captured model or permission setting blindly.
WORKSPACE / FILES
company-export/
├── 00-project/     profile.md · handoff.md
├── 01-market-research/ sources · keywords.csv
├── 02-website/     page-map · local-preview
├── 03-content/     copy · images · reviews
├── 04-release/     draft-urls · screenshots
└── 05-measurement/ GSC-exports · inquiries.csv

One chat, one responsibility

00 Coordinator maintains the plan; 01 Research investigates markets; 02 Writing drafts content; 03 Review checks evidence; 04 Release handles drafts and acceptance.

Share explicit file paths across chats. A new chat should read the handoff rather than assume it can access another chat’s full history.

Teaching example of a task brief with scope, source files, deliverables and acceptance checks
Figure 01. Browser-rendered teaching example, not a screenshot of the Codex interface.
Copyable prompt · replace the example details
Act as my B2B marketing project assistant. Read the company and product files and create 00-project/profile.md with the company, my role, products, markets, buyers, brand voice, working preferences, sources and unanswered questions.
This task is for organizing information only. Do not build, publish or send messages. Save outputs in this project and show the proposed directory first; do not move or overwrite existing files.
For each task state the goal, inputs, steps, deliverables and acceptance checks. Ask for missing facts; never invent market numbers, certifications or case studies. Record agreed working rules and ask each new chat to read them.

Habits that make the workflow repeatable

SituationPractical approach
Personal contextKeep your role, buyers, principles, style and preferences in profile.md. Review it when the business changes, or every two months. A saved profile is project context, not model training.
Long conversationsAt a milestone or when context becomes confused, save goals, confirmed facts, files, evidence, remaining work, risks and the next step. Have the next chat read and restate the handoff.
ArchivingArchive inactive chats to keep the sidebar usable. Archiving is not a file backup; verify that important outputs are saved and backed up separately.
Separate responsibilitiesKeep writing, review and coordination in focused chats with matching project/task names. Start every new chat with its scope and expected result.
File formatsUse Markdown for briefs, CSV/XLSX for data, HTML for pages and PNG/WebP for images. Codex is not limited to Markdown output.
Browser accessGrant only the sites and apps needed for the task. Routine browsing does not require enabling developer/CDP access. Use restricted permissions for onboarding; broad access needs a clear purpose and informed authorization.
MCP, APIs and exportsUse existing authorized connections first. Browser work or manual exports are alternatives. APIs/MCP may need setup, credentials, subscriptions and permission; a prompt does not grant access.
Scheduled reportsRun the process manually first. Specify timezone, reporting dates, sources and output folder. Scheduling and local runtime requirements depend on your environment; report missing data explicitly.
ObsidianUse an authorized Vault as a local knowledge folder and update its index at handoff. Cross-device continuity depends on your own backup/sync configuration, not account switching.
Models and limitsChoose from the models currently available to your account based on capability and budget. Test a small sample first. Do not rely on old model nicknames, account switching to bypass limits, or assumed cross-account chat continuity.
SpeedModel choice, task size, tools, website response and network all affect time. Split large tasks into reviewable outputs and preserve errors for diagnosis.
Copyable prompt · replace the example details
Update 00-project/handoff.md and the project index for a new chat that has not read this conversation. Record the goal, confirmed facts with sources, exact file paths, completed work with verification, unfinished tasks, decisions needed, failure causes and the next action. Keep assumptions separate from facts and preserve original materials.
For the next chat: read profile.md and handoff.md, verify the files exist, and restate the current status and acceptance criteria before continuing.
Download project & handoff template ↓Download inquiry tracker ↓
This guide does not execute tasks. File access, browsing, image generation and publication take place in your authorized Codex / ChatGPT environment. Verify official-account features separately from a WE2AI API connection.
01—27

Finish one task before starting the next.

Each workflow includes inputs, steps, a copyable prompt and a completion check. FAQ improvement, independent review and product upload are integrated into the relevant workflows.

Showing 27 of 27 lessons

01Analyze the business modelChoose a buyer and market before investing in a website.
INPUT / WHAT TO PREPAREProduct catalog, target countries, margin and lead-time ranges, and public market sources.
OUTPUT / WHAT TO DELIVER01-market-assessment.md: buyer profile, market evidence, supply-chain advantages and entry conditions.

Steps · you supply facts, Codex executes, the owner reviews

  1. Ask Codex to map buyer roles, use cases, order economics and repeat purchasing. Mark missing business data as unknown.
  2. Research trade data, market reports and policy originals using a consistent country, year, currency and HS-code scope. Keep source URLs and dates.
  3. Import licensed keyword exports. Separate broad industry interest from procurement intent; search volume is not total market size.
  4. Compare demand, recent Chinese exports, manufacturing clusters and certification requirements. Have the business owner select one market to validate.
Copyable prompt · replace the example details
Act as a B2B market analyst. Work only in 01-market-research. Product: stainless steel insulated bottles. Candidate market: Germany. Buyers: brand sourcing teams and wholesalers. Read our company files first and list missing facts. Assess demand, competition, supply capability, policy and margin constraints. Cite every market figure with its year and scope. Separate facts, estimates and assumptions. Save 01-market-assessment.md and a validation checklist. Do not forecast inquiry counts.
✓ Acceptance checkFigures are traceable; years and HS codes are not mixed; one priority buyer segment and clear reasons to pause are documented.
02Select product keywordsTurn search demand into pages that answer purchasing questions.
INPUT / WHAT TO PREPAREThree to five relevant competitor domains, target country/language, licensed keyword CSVs and your product range.
OUTPUT / WHAT TO DELIVER02-product-keywords.csv: phrase, intent, product fit, destination page and decision rationale.

Steps · you supply facts, Codex executes, the owner reviews

  1. Export competitor organic keywords from the same country database in an authorized Semrush account. If browser access is unavailable, export the CSV yourself.
  2. Deduplicate spelling variants. Identify procurement intent such as manufacturer, supplier, wholesale and custom; remove irrelevant brands and specifications you do not sell.
  3. Cluster by material, capacity, application and buyer problem. Leave unavailable search-volume fields blank.
  4. Manually review representative search results before assigning product or category pages. Avoid creating a separate page for every synonym.
Copyable prompt · replace the example details
Read the keyword CSVs in 01-market-research. We sell stainless steel insulated bottles to B2B buyers in Germany. Group phrases by purchasing intent, product fit and page type. Preserve original terms, source domain, country and export date. Do not invent search volume. Show ten sample rows for review before processing the full dataset. Save 02-product-keywords.csv and a separate list requiring manual search-result review.
✓ Acceptance checkEach retained term has an intent and destination; unknowns remain blank; ten sampled rows trace back to the export.
03Find informational article topicsAnswer buyer questions and connect useful guides to relevant products.
INPUT / WHAT TO PREPARECompetitor top-page exports, the product keyword map and real presales questions.
OUTPUT / WHAT TO DELIVER03-content-topics.csv: buyer question, intent, angle, evidence and related product.

Steps · you supply facts, Codex executes, the owner reviews

  1. Use authorized reports to collect competitor article URLs, titles, keywords, estimated traffic and export dates.
  2. Separate selection, comparisons, maintenance and purchasing processes. Reject popular topics unrelated to your buyers.
  3. Define the decision each article helps the reader make. Add your engineering experience, test evidence or practical limitations.
  4. Plan original evidence and useful internal links. Learn from demand patterns without copying competitor text.
Copyable prompt · replace the example details
Act as a B2B content planner. Read competitor page exports and 02-product-keywords.csv. Propose topics for sourcing managers with the buyer question, intent, draft title, original evidence, related product page and next action. Label competitor traffic as a third-party estimate. Do not copy their articles. Flag topics missing firsthand material. Save 03-content-topics.csv.
✓ Acceptance checkEach topic has a defined reader, original contribution and product connection; estimated traffic is not presented as a result for your site.
04Plan the website and design the UIReview working local pages before publishing.
INPUT / WHAT TO PREPAREBrand assets, the keyword map, reference URLs and owned product photography.
OUTPUT / WHAT TO DELIVERA page map, homepage/product wireframes and a working local preview.

Steps · you supply facts, Codex executes, the owner reviews

  1. Explain which navigation, information order or visual elements you like in reference sites. Do not copy their brand, images or wording.
  2. Map the homepage, products/categories, capabilities, about and contact pages. Give each page an intent, buyer question and primary action.
  3. Ask for a local preview and instructions to open it. Review desktop and mobile; describe feedback by location, problem and expected result.
  4. Check readability, specifications, forms and images before the site owner approves upload. A visual mockup alone is not a working website.
Copyable prompt · replace the example details
Act as our website planner and designer. Use approved brand and product files to create a bottle OEM product page. First propose the structure, then build a runnable local preview and explain how to open it. Include specifications, customization, evidence, FAQs and a Request a Quote button. Review desktop and mobile screenshots, and list missing assets. Work locally in this task.
✓ Acceptance checkThe preview opens; mobile has no horizontal overflow; the quote action is clear; certification and capacity claims have evidence.
05Write product-page copyUse verified specifications and buying conditions to earn a relevant inquiry.
INPUT / WHAT TO PREPAREThe current page template, specifications, customization capabilities and original certification documents.
OUTPUT / WHAT TO DELIVER05-product-copy.md plus a local preview using the approved template.

Steps · you supply facts, Codex executes, the owner reviews

  1. Ask Codex to list facts required by each module. Do not invent minimum orders, certificates or lead times.
  2. Work through the first product together: value, specifications, customization, quality control, delivery and the inquiry action.
  3. Insert approved copy into the template and preview it locally. Keep blog article writing in a separate task.
  4. Have the writing chat self-check, then ask a separate review chat to compare the draft with source files. A business owner resolves disputed claims.
Copyable prompt · replace the example details
Write product-page copy from the current template and verified specifications. Focus on procurement decisions, retain units and limitations, and mark unsupported MOQ, lead-time, certification and numeric claims as awaiting confirmation. Deliver an English draft plus a native-language fact-check version where needed. Complete one sample before the full batch, then insert it into a local HTML preview. Include a fact-check table.
✓ Acceptance checkSpecifications match the source and any translation; claims have evidence; the quote module is present.
06Write helpful new articlesSolve a purchasing problem before optimizing the phrasing for search.
INPUT / WHAT TO PREPAREAn approved topic, real customer questions, product facts and original photos or tests.
OUTPUT / WHAT TO DELIVER06-article.md, a source list and a local layout preview.

Steps · you supply facts, Codex executes, the owner reviews

  1. Select one topic and specify its reader, the decision it supports and its related product page.
  2. Approve an outline and evidence table first. Include test conditions, limits and real examples when available; do not write to an arbitrary word count.
  3. Create a natural English article and, when useful, a Chinese or other native-language checking draft. Keep terminology and units consistent.
  4. Use an independent review chat to check claims, repetition, citations and links before approving the preview.
Copyable prompt · replace the example details
Write a stainless steel bottle material guide for brand sourcing teams. Read the approved topic and verified sources. Start with an outline, then explain selection factors, use cases and limitations with traceable evidence. Do not invent tests. Provide an English publishing draft, an optional Chinese checking draft, title/description suggestions and relevant internal links. Help readers prepare a specification inquiry without keyword stuffing.
✓ Acceptance checkThe core question is answered; units and translations agree; citations resolve; tests and testimonials are not fabricated.
07Plan and write supporting pagesUse comparisons and application guides to support a buying decision.
INPUT / WHAT TO PREPAREA target product page, sales questions and verified differences between options.
OUTPUT / WHAT TO DELIVER07-supporting-page.md and a relevant path to products or a quote.

Steps · you supply facts, Codex executes, the owner reviews

  1. Choose one product and one barrier to purchase, such as material selection, corporate gifting or a procurement checklist.
  2. Check whether there is enough distinct information for a separate page. Merge a simple synonym variation into the main page.
  3. Add comparison criteria, suitable uses, limitations and evidence, with a helpful next step.
  4. Review the page for standalone value. Do not mass-produce repetitive doorway pages.
Copyable prompt · replace the example details
Plan a customization-method guide supporting our bottle OEM page. Compare only confirmed options, such as laser engraving and screen printing, with suitability and limitations. Decide whether a separate page is justified before drafting it. Include a useful comparison table and natural internal links. Cite performance figures and avoid duplicate doorway content. Save 07-supporting-page.md.
✓ Acceptance checkThe page answers a distinct question, adds original value and links naturally; technical claims are supported.
08Upload and verify WordPress draftsUpload approved content as a draft and review it before publication.
INPUT / WHAT TO PREPAREFinal copy, authorized images, the correct site account, backups and preferably staging.
OUTPUT / WHAT TO DELIVERDraft URL, desktop/mobile screenshots and an upload checklist.

Steps · you supply facts, Codex executes, the owner reviews

  1. Sign in yourself and authorize only the relevant site. Confirm the environment and backup; use staging where available.
  2. Have Codex inspect the editor, create a draft from the approved files and set the title, slug and descriptive image alt text.
  3. Preview the H1, module order, crops, buttons, language, canonical URL and indexing settings.
  4. Give the site owner the specific draft and screenshots to approve. After publication, recheck the form and keep a rollback copy.
Copyable prompt · replace the example details
Act as a WordPress upload reviewer. In the site where I have signed in, create a draft using the approved copy and images. Keep existing modules and do not change plugins, themes or global settings. Check links, mobile layout, image alt text and indexing settings. Return the draft URL and a screenshot checklist. Stop before publishing so I can approve this exact draft.
✓ Acceptance checkThe draft matches the approved files; preview links work; form testing is traceable; global settings are unchanged.
09Improve internal linksHelp buyers and crawlers reach relevant pages.
INPUT / WHAT TO PREPAREThe real URL inventory, existing copy and keyword-to-page map.
OUTPUT / WHAT TO DELIVER09-internal-links.csv: source, anchor, destination, context and reason.

Steps · you supply facts, Codex executes, the owner reviews

  1. Inventory indexable product, category, article and contact pages, and verify their status.
  2. Ask Codex to suggest links only where context makes them useful rather than forcing keywords into every paragraph.
  3. Check real destinations, accurate anchors and redirect chains; exclude unpublished draft URLs.
  4. Apply a small approved batch first, verify it and retain a before/after record.
Copyable prompt · replace the example details
Review our real page inventory and copy for useful internal links along a buyer journey. Return source URL, original sentence, proposed anchor, verified target URL, reason and priority. Do not invent URLs or stuff keywords. Save 09-internal-links.csv for review before editing, then verify destinations after approved changes.
✓ Acceptance checkDestinations resolve, context is relevant and core product pages are reachable; changes can be reversed.
10Write SEO titles and descriptionsDescribe each page accurately in search-facing copy.
INPUT / WHAT TO PREPAREPage content, primary intent, brand name and target language.
OUTPUT / WHAT TO DELIVER10-metadata.csv: original values, proposed values, language and rationale.

Steps · you supply facts, Codex executes, the owner reviews

  1. Export actual titles and descriptions by URL, identifying missing, duplicate or misleading entries.
  2. Write for one main intent per page, retaining meaningful specifications and differences.
  3. Review natural wording, brand placement and mobile presentation. Treat character counts as editorial guidance, not a ranking rule.
  4. Update a reviewable batch and monitor real search performance; search engines may rewrite the displayed title or snippet.
Copyable prompt · replace the example details
Use the page content, not just the URL, to propose an English title and meta description for each page. Address one intent, avoid unsupported pricing and certification claims, and do not repeat keywords. Save old and new values, character counts, evidence and priority to 10-metadata.csv. Do not promise an exact Google snippet or publish a bulk change without review.
✓ Acceptance checkCopy matches visible content, is distinct across pages and reads naturally; performance is measured afterward.
11Update existing product pagesFind procurement information gaps before changing the page.
INPUT / WHAT TO PREPAREThe current page, new product facts, GSC exports and historical inquiries.
OUTPUT / WHAT TO DELIVER11-product-update.md, a revised draft and a change log.

Steps · you supply facts, Codex executes, the owner reviews

  1. Back up the page and compare visibility, clicks, conversions and sales feedback. Separate no impressions from visits without inquiries.
  2. Check stale specifications, missing evidence, customization conditions and the quote path.
  3. Preserve useful content and effective URLs. Assess links and redirects before merging or deleting anything.
  4. Preview revisions locally or as a draft, then observe comparable periods after release.
Copyable prompt · replace the example details
Audit this product page using updated specifications, GSC and inquiry records. Separate factual errors, missing buying information, usability issues and unproven hypotheses. Prioritize by impact and effort while preserving useful content and URLs. Deliver a diagnosis and reviewable draft. Do not interpret a lack of clicks as proof of no product demand.
✓ Acceptance checkEvery change has a reason and rollback copy; facts are checked; follow-up metrics and an observation period are defined.
12Build relevant industry linksEarn useful recommendations through real industry relationships.
INPUT / WHAT TO PREPAREAssociations, partners, authorized case studies and valuable original resources.
OUTPUT / WHAT TO DELIVER12-outreach-opportunities.csv plus drafts for human review.

Steps · you supply facts, Codex executes, the owner reviews

  1. Find relevant associations, publications, resource pages and genuine partners that buyers would actually consult.
  2. Offer verifiable value such as engineering evidence, a joint case study or a helpful guide.
  3. Ask Codex for individual outreach drafts. A person verifies the recipient, identity and claims before sending.
  4. Track referral visits and qualified inquiries. Disclose paid or sponsored relationships appropriately; do not buy ranking promises.
Copyable prompt · replace the example details
Find relevant industry resources and editorial collaboration opportunities for our bottle OEM business. Record the source URL, relevance, material we can contribute, contact route and verification status. Draft outreach only; do not send messages without approval. Avoid paid ranking links, automated comments and bulk reciprocal links. Save 12-outreach-opportunities.csv.
✓ Acceptance checkOpportunities are real and relevant; the pitch offers original material; no unauthorized sending or spam links are involved.
13Check broken linksSeparate real failures from access restrictions and transient errors.
INPUT / WHAT TO PREPAREAn authorized domain scope, sitemap and a request/page limit.
OUTPUT / WHAT TO DELIVER13-broken-links.csv: source, target, status, retry and recommended action.

Steps · you supply facts, Codex executes, the owner reviews

  1. Limit checks to the authorized scope, start with the sitemap and use low concurrency. Avoid admin, logout and action URLs.
  2. Collect internal/external link status and timeouts. Treat 403, 429 and bot blocks as requiring review.
  3. Retest failures to distinguish redirects, temporary errors and true missing pages.
  4. Propose replacements, removals or justified redirects for approval, then verify the source page.
Copyable prompt · replace the example details
Check links within the authorized site scope. First state the expected request count and use low concurrency. Do not visit management, logout or write-action links. Record source URL, anchor, destination, status and retest evidence. Do not label 403, 429 or timeouts as broken without verification. Produce a repair list before changing anything.
✓ Acceptance checkEach issue has a source and retest evidence; restricted links are not removed as false positives; approved fixes resolve.
14Analyze website performanceTurn traffic changes into hypotheses that can be tested.
INPUT / WHAT TO PREPAREComparable GSC/GA4 exports, release logs and inquiry records.
OUTPUT / WHAT TO DELIVER14-performance-review.md: observations, evidence, hypotheses and validation actions.

Steps · you supply facts, Codex executes, the owner reviews

  1. Fix the dates, timezone, countries and devices, and compare equal-length periods with seasonality noted.
  2. Separate impressions, clicks, CTR, average position, landing visits and qualified inquiries.
  3. Segment by page, query, country and device. Check tracking changes, indexing issues and form failures.
  4. For each explanation, list supporting and opposing evidence, an owner and a next check.
Copyable prompt · replace the example details
Analyze comparable GSC, GA4 and inquiry exports. Validate dates, timezone, missing data and tracking changes first, then segment by country, device, query and page. Separate observations from causal hypotheses and explain how to disprove each hypothesis. Provide priorities, owner roles, validation metrics and follow-up dates. Do not turn correlation into causation.
✓ Acceptance checkCalculations are reproducible, scopes match and each action has an owner and a follow-up check.
15Diagnose and fix technical problemsReproduce the issue, make a small fix and verify the outcome.
INPUT / WHAT TO PREPAREThe URL, screenshots, device/browser, reproduction steps and authorized code or admin access.
OUTPUT / WHAT TO DELIVER15-technical-fix.md: root cause, changes, verification and rollback.

Steps · you supply facts, Codex executes, the owner reviews

  1. Open a focused technical chat and describe expected versus actual behavior, such as an unclickable button.
  2. Ask for reproduction evidence and the smallest affected scope. Missing access should lead to a diagnosis rather than a guessed fix.
  3. Apply the minimal change locally or in staging, keeping a backup and treating complex issues separately.
  4. Retest the original issue, adjacent flows, mobile and desktop; review the real page after approved release.
Copyable prompt · replace the example details
Act as our website repair specialist. Use the supplied URL and screenshots to reproduce the issue. State expected and actual behavior, root-cause evidence and the minimal change before editing locally. Do not alter unrelated pages or upgrade dependencies. Deliver before/after screenshots, checks and rollback steps. Show production-setting changes for approval before applying them.
✓ Acceptance checkThe issue is reproducible, the original path passes after repair and adjacent navigation/forms still work.
16Audit an older websiteInventory assets before deciding what to retain, update or merge.
INPUT / WHAT TO PREPAREURL lists, GSC/GA4, inbound links, business status and change history.
OUTPUT / WHAT TO DELIVER16-page-inventory.csv with actions and evidence.

Steps · you supply facts, Codex executes, the owner reviews

  1. Merge sitemap, CMS and analytics URLs without losing language and parameter relationships.
  2. Attach search metrics, inquiries, links and update dates, distinguishing missing data from measured zeros.
  3. Classify by business value and content quality. Review seasonal and linked pages separately.
  4. Update a small first batch. Business approval and redirect mapping are required before merging or retiring pages.
Copyable prompt · replace the example details
Build an inventory of our existing pages with URL, type, language, recent impressions/clicks, qualified inquiries, inbound links and update date. Recommend retain, update, merge or investigate with explicit evidence. Missing values are not zero. Do not delete pages automatically. Save 16-page-inventory.csv and propose a reviewable first batch.
✓ Acceptance checkCoverage is documented; missing data is distinct from zero; retirement proposals include impact and redirect review.
17Create a useful calculatorGive buyers a small tool with a verifiable formula.
INPUT / WHAT TO PREPAREA real calculation need, approved formula, units and valid input range.
OUTPUT / WHAT TO DELIVERA working local calculator, formula notes and boundary-case checks.

Steps · you supply facts, Codex executes, the owner reviews

  1. Choose a relevant problem such as carton-volume estimation. Define inputs, outputs, units and assumptions.
  2. Have a business or engineering owner approve the formula. An estimate must not masquerade as a final freight quote.
  3. Build the local tool with unit guidance and validation for missing and invalid inputs.
  4. Cross-check manual examples before linking it to products or a quote form; traffic benefits require real observation.
Copyable prompt · replace the example details
Create a carton-volume estimator for buyers. Confirm the formula, units, packing assumptions and valid range with me before inserting commercial defaults. Then build a runnable local page and check empty, zero, negative and unit-conversion cases. Explain estimation limits and keep final quotations separate. Deliver formula notes and manual cross-checks.
✓ Acceptance checkThe formula is approved, units and manual examples agree, and invalid inputs cannot generate apparently valid estimates.
18Generate and verify imagesSeparate product evidence from AI-generated scene concepts.
INPUT / WHAT TO PREPAREOwned product photos, image rights, page purpose and brand direction.
OUTPUT / WHAT TO DELIVERApproved images, prompts, alt text and a source record.

Steps · you supply facts, Codex executes, the owner reviews

  1. Use real photography for specifications and details. AI scenes need checks against the actual product.
  2. Provide an authorized reference image and specify composition, preserved features and prohibited invented details.
  3. Inspect lids, handles, accessories, text and reflections against the real product; reject or regenerate inaccuracies.
  4. Export suitable dimensions and compress files. Describe the visible image in alt text and label synthetic scenes when otherwise misleading.
Copyable prompt · replace the example details
Use my authorized product photo as the reference for a corporate-gifting scene concept. Preserve the bottle proportions, lid and accessories. Add no branding, certification, graduations or performance claims. Include no people or text. List possible differences from the real product and label the result as an AI scene illustration. Keep specification images as real photography.
✓ Acceptance checkRights and references are recorded; details remain accurate; files are compressed and no certification is invented.
19Review Google Ads campaignsVerify conversion quality before changing spend.
INPUT / WHAT TO PREPAREAuthorized Ads exports, search terms, landing pages, qualified inquiries and budget limits.
OUTPUT / WHAT TO DELIVER19-ads-review.md: waste, proposed tests, limits and stop conditions.

Steps · you supply facts, Codex executes, the owner reviews

  1. Confirm the account and reporting period, then check duplicate conversions, spam leads and timezone differences.
  2. Connect search terms, keywords, ads, landing pages and qualified leads rather than optimizing only for cheap clicks.
  3. Propose small tests with few changed variables, an observation window and a spending cap.
  4. Have the account owner approve budget, bidding and publication changes; retain an execution log.
Copyable prompt · replace the example details
Read-only: analyze our Google Ads and qualified-lead exports. First check duplicate, missing and spam conversions, then segment waste and opportunity by search term and landing page. Propose a small test with a budget cap, review period and success/stop conditions. Do not raise budgets, change bids or enable/disable campaigns. Return a concrete change proposal.
✓ Acceptance checkDiagnosis uses qualified leads, costs have a consistent scope and tests have an explicit cap and stop rule.
20Check indexing readinessResolve indexability problems before requesting a recrawl.
INPUT / WHAT TO PREPAREAuthorized Search Console access, a sitemap and the URLs to inspect.
OUTPUT / WHAT TO DELIVER20-indexing-review.csv: status, evidence, fix and request log.

Steps · you supply facts, Codex executes, the owner reviews

  1. Inspect each URL in the correct Search Console property, checking crawl access, noindex and canonical choices.
  2. Check the response, internal links and sitemap before requesting indexing.
  3. Use authorized individual requests for a small set and a sitemap for larger sets. Avoid repeated submissions.
  4. Log request dates and observe outcomes; requesting a crawl does not guarantee indexing or ranking.
Copyable prompt · replace the example details
Help assess these URLs on a site we manage. Check status, robots/noindex, canonical, internal links and sitemap before listing items for manual Search Console inspection. Do not promise indexing after submission or repeatedly request the same URL. Record evidence, repair steps and a follow-up date.
✓ Acceptance checkURLs are within authorized ownership; barriers are checked; requests and actual indexing outcomes are recorded separately.
21Validate emerging search queriesUse new queries to guide content decisions.
INPUT / WHAT TO PREPAREComparable GSC exports, same-country Semrush data and the current page map.
OUTPUT / WHAT TO DELIVER21-query-opportunities.csv: new term, evidence, destination and action.

Steps · you supply facts, Codex executes, the owner reviews

  1. Compare equal periods in the same country and note small samples and unavailable anonymous queries.
  2. Mark new, rising and falling queries, using third-party data only as supporting context.
  3. Manually check intent and fit with current product pages; prioritize questions an existing page can answer.
  4. Create a separate page only for a distinct need. Track later clicks and qualified inquiries rather than treating new keywords as sales.
Copyable prompt · replace the example details
Compare two GSC query exports with our keyword map. Identify new terms and meaningful changes, noting country, period, source and sample size. Use same-country Semrush exports as supporting estimates. Recommend updating an existing page, creating a distinct page or observing further, with reasons. Keep low-impression cases separate.
✓ Acceptance checkQueries are traceable, periods and countries match, destinations are clear and small samples are not overstated.
22Improve loading performanceMeasure the bottleneck and check the result.
INPUT / WHAT TO PREPARERepresentative URLs, performance reports, device and network conditions.
OUTPUT / WHAT TO DELIVER22-performance-log.md: baseline, evidence, changes and retests.

Steps · you supply facts, Codex executes, the owner reviews

  1. Fix test conditions and measure more than once, separating lab diagnostics from real-user data.
  2. Inspect hero images, fonts, scripts, caching and third-party plugins; prioritize user impact.
  3. Make small local or staging changes such as image sizing or loading adjustments, with backups.
  4. Retest layout, navigation and forms. Real-user metrics need time to reflect a change.
Copyable prompt · replace the example details
Diagnose this page using repeatable baseline measurements. Record device, network, time and repeated results; distinguish lab and real-user data. Find the main bottleneck from evidence and propose a minimal local change. After each change, retest the first screen, layout, menus and forms. Do not remove essential functionality just to improve a score.
✓ Acceptance checkBaseline and retest conditions match, improvements have evidence and core functionality remains intact.
23Analyze Semrush dataTreat competitive estimates as leads to investigate.
INPUT / WHAT TO PREPARELicensed Semrush exports, GSC data, database country and report date.
OUTPUT / WHAT TO DELIVER23-competitive-review.md and a validation backlog.

Steps · you supply facts, Codex executes, the owner reviews

  1. Confirm report purpose, country database and date. Use the tool’s current report names and interfaces.
  2. Compare relevant competitors by topics, page types, keyword overlap and traffic concentration.
  3. Check brand demand, unrelated countries and unusual changes; keep estimate labels and dates.
  4. Validate opportunities against your products and actual GSC performance. Manual exports work without an API or MCP connection.
Copyable prompt · replace the example details
Analyze the Semrush files I exported. Do not buy a plan or connect unknown tools. Keep country and date consistent; compare competitor keywords, strong pages and gaps. Label third-party traffic estimates, and use GSC for our actual performance. Return five opportunities with page destinations, evidence, missing materials and next steps.
✓ Acceptance checkDatabases align, estimates and observed data are separate and recommendations fit real products.
24Refresh existing articlesUpdate useful content without discarding what already works.
INPUT / WHAT TO PREPAREThe existing article, recent queries, outdated references and new product facts.
OUTPUT / WHAT TO DELIVER24-article-update.md, a change comparison and a draft preview.

Steps · you supply facts, Codex executes, the owner reviews

  1. Check whether demand, rankings, click-through or stale content explains the problem before rewriting.
  2. Keep sections that answer intent. Add evidence, new questions and corrections to outdated steps.
  3. Check references, images, links and terminology across languages; titles must match the revised content.
  4. Review independently, publish the real update date and retain the previous draft and measurement plan.
Copyable prompt · replace the example details
Audit this article against recent queries and verified product updates. Mark useful sections, outdated sections and unsupported claims, then make the smallest valuable revision. Repair references and links. Deliver the English draft, an optional checking translation, changes, reasons and a preview. Do not change only the date to imply a substantive update.
✓ Acceptance checkNew information is supported, useful sections remain, links resolve and the revision is reviewable.
25Make content clear for AI searchUse explicit answers and evidence that people can verify.
INPUT / WHAT TO PREPAREVerified product facts, genuine FAQs, business identity and original data.
OUTPUT / WHAT TO DELIVER25-content-clarity.md plus checked answers and specification tables.

Steps · you supply facts, Codex executes, the owner reviews

  1. Answer real buyer questions directly, then add scope, units, limitations and source links.
  2. Use semantic HTML tables for comparisons and specifications; identify the publisher and the real review date.
  3. Match any structured data to visible content. Do not invent numbers to make the page appear more authoritative.
  4. Monitor actual referral visits and qualified leads. SEO foundations remain relevant; special AI markup does not guarantee citations.
Copyable prompt · replace the example details
Review this page for clarity to buyers and search systems. Use only verified materials to add direct answers, scope, clearly labeled units, useful FAQs and sources. List evidence gaps rather than inventing numbers. Structured data must reflect visible content. Return a reviewable draft without promising rankings, AI recommendations or citations.
✓ Acceptance checkAnswers and figures match sources, FAQs are useful and no guaranteed citation or special-markup claim is made.
26Decide keyword ownership and page typeChoose whether related terms belong on one page or separate pages.
INPUT / WHAT TO PREPARETwo terms, manually recorded same-country/language search results and existing URLs.
OUTPUT / WHAT TO DELIVER26-keyword-ownership.csv: intent, page type, merge/split evidence and primary URL.

Steps · you supply facts, Codex executes, the owner reviews

  1. Manually inspect representative results in the same country and language, recording dates, URLs and types. Avoid unauthorized automated Google scraping.
  2. Compare procurement versus informational intent, category versus product results and overlapping URLs.
  3. Prefer one strong page when it can fully meet the same need; separate distinct needs only when each has enough useful material.
  4. Use business context and evidence rather than a universal overlap threshold. Assign one clear primary destination per cluster.
Copyable prompt · replace the example details
Using the two search-result samples and product facts I provide, assess whether insulated bottle manufacturer and vacuum flask supplier belong together. Compare intent, page types, URL overlap and real business differences. List evidence and uncertainty first, then choose a primary URL and supporting terms. Request more samples when needed instead of deciding from wording alone.
✓ Acceptance checkResults share a regional scope, the decision is explained and each cluster has a clear primary destination.
27Handle routine WordPress admin tasksLimit each task to a specific, reviewable scope.
INPUT / WHAT TO PREPAREThe correct admin URL, task list, authorized role and backup.
OUTPUT / WHAT TO DELIVER27-admin-change-log.md, screenshots and rollback instructions.

Steps · you supply facts, Codex executes, the owner reviews

  1. Sign in yourself and verify site, staging/production environment, role and backup. Keep credentials out of chat.
  2. Name the exact page or setting; have Codex read current values and show proposed changes.
  3. Use drafts for content. Review theme, plugin, permalink and global indexing changes individually before applying them.
  4. Check the real frontend, mobile, navigation and form afterward; keep previous values for rollback.
Copyable prompt · replace the example details
Work only on the WordPress tasks I specify. Verify the site and environment, read current values and show each proposed change with its impact. Save content as drafts. Do not change plugins, themes, roles, permalinks or site-wide indexing without item-by-item approval. Deliver before/after screenshots, frontend checks and rollback values.
✓ Acceptance checkThe environment is correct, each change has old/new values and the frontend and inquiry form pass a retest.
LAB

Example: turn “more websites” into a testable plan.

LESSON FROM A SHARED CONVERSATION
Use Codex to launch, improve and then verify whether the site attracts inquiries.

The supplied conversation described three sites, more than a hundred ranking keywords within a month and a few inquiries. This is an unverified account without the sites, measurement definitions, costs or qualified-lead evidence. It cannot predict your results.

Only the teaching point is retained; personal names and avatars are not published. The bottle OEM project below is fictional. Keywords and URLs illustrate the method, not existing rankings or customers.

Assume a manufacturer with real specifications wants to reach German brand sourcing teams. Validate one market, one site and a small core of useful pages first. Consider additional sites only where distinct languages, markets or business needs justify them.

STEP 01 / RESEARCH
Find evidence of need

Clean licensed keyword and competitor-page exports. A phrase such as custom stainless steel bottle still needs regional intent validation.

STEP 02 / BUILD
One product page, one guide

Explain real specifications, customization and how to request a quote. Link a genuinely useful material-selection guide to the product.

STEP 03 / VERIFY
Test submission to receipt

Trace a labeled test submission through the form, notification and sales handoff before measuring actual inquiries.

Illustrative keyword ownership table connecting procurement, selection and contact intent to appropriate page types
Figure 02. A rendered teaching table. Terms and URLs are illustrative; no search volumes, rankings or real customer data are shown.
StageAction and ownerDeliverable / acceptance
PrepareBusiness owner supplies approved specifications, public certification evidence, delivery constraints and buyer profile. Operations builds the workspace.Usable source index with missing facts marked.
ResearchCodex cleans exports; operations reviews database scope, representative search results and destinations.Keyword file and page map with traceable sources.
CreateA writing chat produces copy and scene concepts; a separate chat checks evidence; the business owner confirms claims.Natural English, accurate specifications and labeled synthetic scenes.
ReleaseOperations creates WordPress drafts; the site owner reviews mobile, buttons and the form.Draft screenshots and a traceable test submission from entry to receipt.
ObserveOperations compares search, analytics, ad sources and lead records; sales qualifies inquiries.Weekly review with enough data to expand, revise or stop rather than relying on a fixed promised timeline.

The inquiry path needs its own acceptance check.

  1. Use a clear Request a Quote action. Ask only for necessary business details, such as requirements, quantity, market and contact route, with a privacy notice.
  2. Show a success state or thank-you page. Record a conversion after successful submission, not simply after a button click.
  3. Send clearly labeled TEST data and verify storage, email notification and sales receipt. Keep test records separate.
  4. Track source/UTM, landing page, product, status and follow-up. Sales should define qualification consistently and exclude spam, duplicates and tests.
VisibilityGSC impressions and clicks by page and query.
SubmissionsSuccessful, deduplicated form records and matching events.
Qualified inquiriesSales-verified identity and relevant demand.
Acquisition costDefined cost scope divided by qualified inquiries.
Qualified-inquiry rate = qualified inquiries ÷ comparable landing visits. Record the visit definition, attribution window and timezone. If there are no qualified inquiries, report cost per inquiry as unavailable rather than dividing by zero. Keep site, tool, content, advertising and labor costs separate.
Copyable prompt · replace the example details
Act as the coordinator for our bottle OEM marketing project. Read the profile, market assessment, keyword map and verified product facts. Plan the first experiment around one target market and one site, including a product page, a selection guide and a quote path.
List evidence gaps, then deliver research, copy, local preview, draft review, form testing and post-release observation in stages. For each stage name an owner role, inputs, outputs, acceptance checks and decisions requiring my review.
Do not promise rankings, inquiries or revenue. Separate tests, duplicates, spam and qualified leads in a tracker with a consistent weekly review definition.
Q&A

Key terms and common questions

What is Codex for B2B marketing?

In this guide, it means using Codex to work with authorized files, research exports, website drafts and checks. You provide business facts and approve consequential actions. The practical output is a reviewable artifact, not a promise of leads.

How do SEO and GEO differ?

SEO helps search engines discover and understand useful pages. GEO, or generative engine optimization, concerns visibility in AI-generated answers. Google says its AI search features follow the same SEO foundations and require no special AI file or schema.

Can Codex guarantee qualified inquiries?

No. Define a qualified inquiry with sales, test the form end to end and measure actual outcomes. Exclude tests, spam and duplicates. Tools can assist execution; buyer demand and business results still need evidence.

Do I need programming skills or an MCP connection?

Start with product files, authorized CSV exports and clear briefs. An MCP or API connection is optional and requires its own setup and access. For website changes, use a local preview and independent review.

Does adding FAQ content or structured data guarantee AI citations?

No. Clear answers and accurate markup help describe the page. They do not guarantee crawling, indexing, rich results or citations. Structured data must agree with what readers can see.

REF

Check original sources and your actual environment.

This practical handbook is edited by WE2AI. It is not an official OpenAI, Google or Semrush course. Features, permissions, plans and report interfaces change; use manual exports and local files where a connection is unavailable.

Editorial owner: WE2AI. Updated 20 October 2026. Original sources support product and search guidance; the workflows and fictional example are editorial teaching material. Evaluate SEO, AI-search visibility and ads using observed data. Rankings, citations, inquiry counts and revenue are not guaranteed.

↑ Top