Codex Control ControlINBOXContentPR gateHealthLearningPerformanceFiles connecting…Needs you —

Website PR gate

1 awaiting your localhost review · 2 open with owner · 3 merged
Open 3 Merged 3 All 6
/about-us 404 redirect Awaiting localhost
#— opened by Codex 5d ago · fix/about-us-404-redirect · needs your > APPROVED PR
3 / 8
+
!Problem
/about-us returns a 404 in production. Found via spec-02 site crawl on 2026-05-26. Affects internal links from social posts, GBP citations, and historical news-media references that point to the old URL. Estimated impressions loss: ~40/month.
✓Solution
Add a permanent 301 redirect from /about-us → /about/ at the Next.js framework level via next.config.js and public/_redirects. No content, template, or CSS changes — route-level only. Trailing-slash variant handled too.
Progress — 8 stages
✓
Draft
approved
✓
Branch
built
3
Localhost
needs you
4
Approved
pending
5
Opened
pending
6
Merged
pending
7
Deployed
pending
8
Live
pending
Per-PR details
Draft status✓ Approved — > APPROVED DRAFT by AXS on 2026-05-26 (5d ago)
Approved branchfix/about-us-404-redirect · built from main · clean rebase
Build status✓ Passing — Jest 63/63 · lint pass · npm run build pass
Localhost unitsnot yet checked — needs you · targets: /about-us, /about/, trailing-slash variant, no-regress on /projects/, /locations/mohali/
Approved datadraft & branch approved · PR-open approval pending your localhost run
Files changed 2 files · +18 / −2
PathDiff
Modnext.config.js+12 / −0
Modpublic/_redirects+6 / −2
Localhost test checklist
git checkout fix/about-us-404-redirect && cd repo/website-github && npm run devruns at http://localhost:3000
localhost:3000/about-usexpected: 301 redirect to /about/
localhost:3000/about/expected: 200 OK, renders About page
localhost:3000/about-us/ (trailing slash)expected: 301 redirect to /about/
No regressions on /projects/, /locations/mohali/, /news-media/expected: each returns 200 with original content
Approval phrase
> APPROVED PR fix/about-us-404-redirect
or reject: > REJECTED fix/about-us-404-redirect: <reason> · approving here opens the PR to the owner; it does not merge, deploy, or go live.
GSC indexing cleanup Open
#49 opened by Codex 11d ago · fix/gsc-indexing-cleanup · awaits owner merge
6 / 8
+
!Problem
GSC indexing export (2026-05-21) flagged 132 not-indexed pages, including 51 with redirect issues (legacy news&media URLs), 13 returning 404 (mis-cased PDF URLs), and 29 news/media detail pages with no H1. Two redirect-only aliases (/flats-in-mohali/, /flats-in-gurugram/) were also in the sitemap.
✓Solution
Add redirects for legacy news&media URLs; redirect mis-cased PDF URLs; inject H1 on news/media detail pages; remove redirect-only aliases from the sitemap. Net: 57 of 132 not-indexed issues resolved (43% reduction).
Progress — 8 stages
✓
Draft
2026-05-19
✓
Branch
2026-05-20
✓
Localhost
2026-05-20
✓
Approved
2026-05-21
✓
Opened
2026-05-21
6
Merged
awaits owner
7
Deployed
pending
8
Live
pending
Per-PR details
Draft status✓ Approved — 2026-05-21
Approved branchfix/gsc-indexing-cleanup · fast-forward merged into local main · ahead of origin/main by 1 commit
Build status✓ Passing locally · Vercel preview FAILED — tech1onegroup needs Vercel project access
Localhost units✓ Verified on 2026-05-21 · news&media redirects, PDF case fixes, news/media H1 all confirmed
Approved dataPR approved · > APPROVED PR fix/gsc-indexing-cleanup by AXS on 2026-05-21
Files changed 7 files · +94 / −31
PathDiff
Modnext.config.js+34 / −0
Modpublic/_redirects+22 / −0
Modsrc/pages/news-media/[slug].js+8 / −2
Modpublic/sitemap.xml+0 / −14
Modscripts/generate-sitemap.js+6 / −3
Modsrc/data/news-media.json+18 / −6
Modtests/redirects.test.js+6 / −6
Blocker
⚠ Vercel access — Git author tech1onegroup lacks Vercel project/team permission, so preview deployments cannot run. Resolution: owner adds tech1onegroup to the Vercel project or manually merges + deploys.
Lead tracking generate_lead events Blocked
#45 opened by Codex 13d ago · feat/generate-lead-tracking · Vercel access blocker
6 / 8
+
!Problem
No lead-conversion events flowing to GA4. Composite SEO score weights leads at 35% but Codex has no way to know whether a contact-form submission, WhatsApp click, brochure download, or phone tap actually happened.
✓Solution
Wire dataLayer.push({event:'generate_lead', lead_type:...}) into all five lead surfaces (contact form, project inquiry, brochure download, phone click, WhatsApp click). Add helper src/utils/analytics.js + Jest tests. GTM-side dataLayer variable + GA4 custom dimension set up separately.
Progress — 8 stages
✓
Draft
2026-05-17
✓
Branch
2026-05-18
✓
Localhost
2026-05-18
✓
Approved
2026-05-19
✓
Opened
2026-05-19
6
Merged
awaits owner
⚠
Deployed
Vercel access
8
Live
pending
Per-PR details
Draft status✓ Approved — 2026-05-19
Approved branchfeat/generate-lead-tracking · based on main
Build status✓ Passing locally · Vercel preview FAILED — same Vercel access blocker as PR #49
Localhost units✓ Verified — contact form, project inquiry, brochure, phone click, WhatsApp click all fire generate_lead with correct lead_type
Approved dataPR approved 2026-05-19 · GTM Preview tested on 2026-05-21 for phone_click, whatsapp_click, contact_form
Blocker
⚠ Same Vercel access issue as PR #49. Aging at 13 days. Resolution path: owner grants tech1onegroup Vercel project access, or merges + deploys from an authorized account.
News-media URL redirect set Merged
#48 merged 2026-05-12 · fix/news-media-redirects · deployed · verified live
a b c d
+
!Problem
21 legacy news&media/<slug> URLs (with literal ampersand) returning 404. External backlinks still point to old form.
✓Solution
Add 21 individual 301 redirects mapping each legacy slug to its current news-media/<slug> form.
Progress — 8 stages
✓
Draft
2026-05-08
✓
Branch
2026-05-09
✓
Localhost
2026-05-09
✓
Approved
2026-05-10
✓
Opened
2026-05-10
✓
Merged
2026-05-12
✓
Deployed
2026-05-12
✓
Live
2026-05-13
Per-PR details
Draft status✓ Approved 2026-05-09
Approved branchfix/news-media-redirects
Build status✓ All checks green
Localhost units✓ 21 redirects spot-checked locally
Approved data> APPROVED PR fix/news-media-redirects by AXS 2026-05-10
Saavira spelling rename across codebase Live
#47 merged 2026-05-08 · fix/savira-to-saavira · verified live across project pages
8 / 8
+
!Problem
Project name “Saavira” was inconsistently spelled Savira / Sabira in 207 places across data, content, and asset paths.
✓Solution
Global rename across src/Components/ProjectDetail/details.json, project data, asset filenames. Asset folders kept under legacy savira/ path (in the don’t-touch list).
Progress — 8 stages
✓
Draft
2026-05-04
✓
Branch
2026-05-05
✓
Localhost
2026-05-06
✓
Approved
2026-05-07
✓
Opened
2026-05-07
✓
Merged
2026-05-08
✓
Deployed
2026-05-08
✓
Live
2026-05-09
Per-PR details
Build status✓ Green
Localhost units✓ Saavira URL spot-checked · 207 text rename verified via grep
Approved data> APPROVED PR fix/savira-to-saavira by AXS 2026-05-07
Brand capitalization audit (ONE Group / Mohali / Sector 48) Live
#46 merged 2026-05-05 · fix/one-group-capitalization · verified live
8 / 8
+
!Problem
Inconsistent brand casing — One Group, one group, ONE group — in ~80 places. Brand-voice rule: company phrase always renders as ONE Group.
✓Solution
Mechanical rename to ONE Group when the phrase refers to the company. Left ordinary uses of “one” untouched.
Progress — 8 stages
✓
Draft
2026-05-01
✓
Branch
2026-05-02
✓
Localhost
2026-05-03
✓
Approved
2026-05-04
✓
Opened
2026-05-04
✓
Merged
2026-05-05
✓
Deployed
2026-05-05
✓
Live
2026-05-06
Per-PR details
Build status✓ Green
Localhost units✓ Live HTML spot-checked · 0 incorrect-casing matches found in sampled pages
Approved data> APPROVED PR fix/one-group-capitalization by AXS 2026-05-04
Codex Control ControlINBOXContentPR gateHealthLearningPerformance connecting…Needs you —

Learning

Observing   0 / 20 data points to graduate
⚙
Advisory only. Nothing here authorizes a draft, PR, post, or schedule change. Learning surfaces patterns; you decide what to act on.
Learning phase
1
Observing
Watching outcomes;
no hypotheses formed yet
2
Hypothesis
Patterns proposed,
awaiting verdict
3
Confirmed / Rejected
Verdict rendered after
3+ data windows
!
Aborted
Data gap or missing source
made verdict impossible
Graduation progress0 / 20 data points · needs published outcomes
Codex graduates from Observing into Hypothesis once it has 20 published-outcome data points (post live + 14d of metrics). First data point lands after the first website PR is merged and tracked.
Data points by topic type
Buyer checklist0 / 20
Area guide0 / 20
Project showcase0 / 20
Comparison0 / 20
Founder story0 / 20
Construction update0 / 20
NRI guide0 / 20
FAQ0 / 20
Score signals
Seomachine threshold80
drafts below this score are rejected before review
Weakest category (30d)Readability
based on 1 draft sampled · not statistically meaningful yet
Fastest improving— no signal yet
needs at least 5 drafts across 2 windows
Banned-word hits0 in last 30 drafts
Claim verification rate95%
1 unverified claim out of 18 (above 90% target)
AXS preferences inferred
☉
0 preferences inferred
First inferences come from Day 2+ once you approve / deny / edit drafts.
learning/axs-preferences.md
Top-performing past topics
▲
No data yet
Top performers appear after ~20 published posts with 14+ days of GSC / GA4 metrics.
What Codex is stuck on (for learning)
!
No published-content outcomes yet
Learning can’t infer what works until at least 1 post is live with 14d of metrics. Currently 0 posts have been approved + published.
!
GA4 lead_type dimension not active
Without this dimension, Codex can’t learn which lead source (form / WhatsApp / brochure / phone) correlates with which content. Open INBOX item ›
!
DataForSEO weekly fetch blocked
Ranking-position deltas are a key learning signal. Resuming weekly SERP runs requires account top-up.
!
Wiki / OS repo not yet shared
Persona learning + brand-voice inference depend on the Marketing wiki being accessible to Codex.