[growth-manager/blogger][blogger-20260804] strengthen namuthaj محضر winner for رسمي/جاهز long-tails - #145
Merged
Merged
Conversation
…مي/جاهز long-tails Two consecutive empty blogger windows were caused by the seo worker's content-brief generator mislabeling US search volume as MENA (found 2026-07-22). This run re-verifies every محضر اجتماع family candidate live via DataForSEO with explicit Saudi Arabia/Egypt/UAE location targeting before picking anything, per Hassan's 2026-07-22 STEERING direction. Real MENA numbers (location queried alongside each): - نموذج محضر اجتماع رسمي word: SA 390 / EG 170 (clears the >=100 gate) - نموذج محضر اجتماع جاهز: SA 210 / EG 110 (clears the gate) - نموذج محضر اجتماع مجلس إدارة: SA 70 / EG 70 (under gate) - نموذج محضر اجتماع لجنة: SA 70 / EG 70 (under gate) - محضر جلسة: SA 20 / EG 40 / UAE 10 (under gate) - كيفية كتابة محضر اجتماع مجلس إدارة: 10/10/10 (under gate) - نموذج محضر اجتماع حكومي: 20/10 (under gate) - محضر اجتماع قصير وسهل: 70/40 (under gate, already known saturated 07-13) - محضر لجنة تدقيق / محضر اجتماع لجنة التدقيق: no measurable volume Cannibalization check (live serp_organic_live_advanced, KSA/ar): the only two candidates that clear the volume gate are BOTH already won by namuthaj-mahdar-ijtimaa-ar -- organic page-1 for "نموذج محضر اجتماع رسمي word" (rank_absolute 7) and "نموذج محضر اجتماع جاهز" (rank_absolute 6), just behind Canva/WHO/uqu.edu.sa authority giants, not yet #1. Every other variant fails the >=100 volume gate this pipeline enforces. No net-new page shipped -- this refresh deepens the confirmed winner instead, on demand it's already partially capturing: - New H2 "الفرق بين محضر اجتماع رسمي ونموذج جاهز للتحميل" (~150 words, exact-phrase-matches both newly-verified queries). - New FAQ sweeping the مجلس إدارة/لجنة sub-100-vol variants into the hub page instead of fragmenting authority onto weak standalone pages. Verified against PR #129's actual diff this doesn't duplicate the prior refresh (which targeted احترافي/قصير وسهل, different long-tails). Flagged, not fixed (outside content lane): app/lib/blog.ts:235 extractFaqs() requires heading "FAQ"/"الأسئلة الشائعة" for FAQPage schema; both namuthaj and jadwal use "## أسئلة شائعة" (no ال) and don't match -- FAQPage JSON-LD has likely never fired on either page. Recommend /bug-creator. Codex fact-flag pass attempted, timed out after 2 min -- manually reviewed: no new statistics/factual claims added, only standard KSA board-governance process guidance (quorum, session numbering, vote record) consistent with the page's existing voice. Odoo: n/a (content refresh, no ticket -- ticket-gate exempts content-only blog PRs per existing precedent, e.g. PR #133/#117) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe Arabic meeting-minutes article now includes updated metadata, formal-record guidance, and an expanded FAQ. Its blogger outcome record includes refresh metadata and evaluation details. ChangesMeeting-minutes post refresh
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Smetools
marked this pull request as ready for review
August 4, 2026 11:05
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Agent: growth-manager / blogger · run 4
What this is
Content refresh (no net-new page) on
namuthaj-mahdar-ijtimaa-ar— the site's only confirmed non-brand-click winner. Dispatched after two consecutive empty blogger windows, both caused by the seo worker's content-brief generator mislabeling US search volume as MENA volume (root-caused 2026-07-22, fix in parallel this run). This run re-verifies every candidate live via DataForSEO with explicit MENA location targeting before writing anything.Live MENA demand pulled this run (location + volume, no pre-existing brief trusted)
Cannibalization check (live
serp_organic_live_advanced, KSA/ar, today)The only two candidates that clear the volume gate are already won by this page:
Neither at #1 yet — still behind Canva (DR89) and gov/edu authority PDFs, expected per the PLAYBOOK's authority filter (Law 1). Every other variant checked fails the volume gate outright.
Conclusion: no net-new page justified. Verified against PR #129's actual diff that its two long-tails (احترافي, قصير وسهل) are different from this run's two (رسمي, جاهز) — this is not a duplicate touch on the same ground.
What changed
read_minutes10→11, added tagمحضر-مجلس-إدارة.post-outcomes.json: backfilled the full refresh history for this entry (PRs [blogger-refresh] strengthen namuthaj محضر winner for adjacent long-tails #129, [blogger-refresh] add short-vs-full template comparison visual to namuthaj #131 were never recorded there) + this run's finding.Separate finding — flagged, NOT fixed (outside blogger's content lane)
app/lib/blog.ts:235extractFaqs()requires the H2 heading text to be exactlyFAQorالأسئلة الشائعة(with definite article) to emit FAQPage JSON-LD. Bothnamuthaj-mahdar-ijtimaa-arandjadwal-aamal-ijtimaa-aruse## أسئلة شائعة(noال) — verified via grep across all 20 shipped posts, only these 2 (the department's two best-performing AR pages) have the non-matching heading. FAQPage schema has likely never fired on either page since publish — a live Law-5 (GEO/AI-citation) gap. Recommend routing to/bug-creator; not fixed in this PR (site-rendering code, not content, outside this dispatch's scope, and the two-agent filing bar needs an independent verify pass I can't do solo).Codex fact-flag (Step 4, assist not gate)
Attempted (
codex exec --sandbox read-only), timed out after 2 minutes. Manually reviewed instead: no new statistics/factual claims added — only standard KSA board-governance process guidance (quorum, session numbering, vote record) consistent with the page's existing voice and the existing body text it extends (lines already mention "مجالس الإدارة واللجان النظامية" needing extra fields).Verify
post-outcomes.jsonre-validated:json.loadsucceeds after the edit.How to test
.github/workflows/publish-blog-draft.ymlis NOT involved (this is a direct edit to an already-publishedapp/content/blog/*.mdfile, not a new draft — ships on merge like PR [blogger-refresh] strengthen namuthaj محضر winner for adjacent long-tails #129/[blogger-refresh] add short-vs-full template comparison visual to namuthaj #131/[blogger-20260719] jadwal-aamal-ijtimaa-ar: real .docx template + post-outcomes.json hygiene #133 did).Learned from: n/a — no ticket needed for this content-only refresh, matching established precedent (PR #129, #131, #133 — none reference an Odoo ticket; blogger content PRs are not gated by ticket-gate in this repo).
Summary by CodeRabbit