<b>The index-bloat quarantine SOP</b>
Never push 50k generated URLs straight to the sitemap. Stage them.
Step 1 — Owner: data lead. Generate the full URL set but flag each row with a coverage score (unique data points / template slots). Gate: rows below 0.4 do not enter the queue.
Step 2 — Owner: SEO. Release the first 500 pages only. Add them to a dedicated sitemap (sitemap-batch-01.xml), not the main one. Gate: wait 14 days.
Step 3 — Owner: SEO. Pull index coverage on the batch. Gate: if indexed ratio is under 60 percent, stop. The template or data is too thin for the next batch.
Step 4 — Owner: data lead. Compare indexed vs non-indexed rows. Find the data attribute that separates them. That attribute becomes your new minimum threshold.
Step 5 — Owner: SEO. Promote passing batch to main sitemap, release next 500. Repeat.
— Quarantine sitemaps make rollback a one-file delete
— Index ratio per batch is your true thin-content signal, not word count
Ship gate: don't publish until all boxes are checked.
Scale Engine SOP
@ScaleEngineSOP
<b>The index-bloat quarantine SOP</b>
Этот пост опубликован в Telegram-канале Scale Engine SOP. Подписаться можно по ссылке: @ScaleEngineSOP.