Reprocess: SEO-safe applicants-only default (don't churn indexed shift/job URLs)

Reprocess deletes+rebuilds aggregated listings, which changes their IDs. Shift/Job detail pages are indexed and in the sitemap, so churning them would 404 ranked URLs. «آماده به کار» pages are NoIndex + Disallow, so rebuilding them has zero SEO impact — and that's where all the duplicate/sprawl problems were. ReprocessAsync(talentOnly: true) now only deletes/rebuilds TalentListings and skips non-talent raws (leaving shift/job listings + their RawListing links untouched). Admin button relabelled «پردازش مجددِ آماده به کارها (امن برای SEO)». Shifts/jobs self-clean via normal ingestion turnover. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-20 16:08:20 +03:30
parent e582597b20
commit fb7bfad9ce
3 changed files with 25 additions and 10 deletions
@@ -111,7 +111,9 @@ public class IndexModel : PageModel
            using var scope = _scopes.CreateScope();
            var svc = scope.ServiceProvider.GetRequiredService<IngestionService>();
            var log = scope.ServiceProvider.GetRequiredService<ILogger<IndexModel>>();
-            try { await svc.ReprocessAsync(); }
+            // talentOnly: «آماده به کار» is NoIndex/Disallow → rebuilding it doesn't churn any indexed
+            // URL. Shift/Job detail pages ARE indexed, so they're left to self-clean via turnover.
+            try { await svc.ReprocessAsync(talentOnly: true); }
            catch (Exception ex) { log.LogError(ex, "Background reprocess failed"); }
        });
        IngestMessage = "پردازش مجدد آیتم‌های ذخیره‌شده در پس‌زمینه آغاز شد. نتیجه پس از اتمام در «تاریخچهٔ اجرا» نمایش داده می‌شود (بسته به تعداد آیتم‌ها و سرعت هوش مصنوعی، چند دقیقه طول می‌کشد).";