Bulk maintain, improve, and produce pages
Three bulk modes for site work
Sitemap work can happen in three modes: maintain, improve, and produce.
These words sound big, but the difference is simple. Maintain keeps existing pages healthy. Improve upgrades weak pages. Produce creates planned pages that do not exist yet.
Maintain existing pages
Maintain work checks pages that already exist.
This can include fixing metadata, checking links, refreshing old copy, adding missing JSON-LD, or running an on-page check.
Improve weak pages
Improve work starts from evidence.
For example, Analytics may show a prompt gap. Sources may show that AI reads a competitor page instead. Search Console may show impressions for a page that is not strong enough yet.
Produce planned pages
Produce work creates new page files.
This should happen when the gap is clear. The sitemap group should explain where the page belongs and what buyer question it should answer.
Bulk page work
Maintain existing pages, improve weak pages, or produce new pages only when the sitemap plan and proof are clear.
Inputs CLEA needs before bulk work
Bulk work needs strong inputs.
Useful inputs include the sitemap group, related prompts, source reads, competitor evidence, Search Console queries, page status, and a workflow file that tells CLEA how to choose work.
Review risks in bulk changes
Bulk changes can create bulk mistakes.
Do not ask CLEA to rewrite many pages without a review rule. It is better to create a short list of page briefs than to create many weak drafts.
Best use cases for each mode
| Mode | Best use |
|---|---|
| Maintain | Keep existing pages clean and current |
| Improve | Strengthen pages tied to weak evidence |
| Produce | Create pages for clear gaps |
| Pause | Stop when evidence is missing |
Goal: choose the right sitemap work mode. Inputs: Analytics, Sources, Search Console, Sitemap. Steps: decide if the page should be maintained, improved, produced, or paused. Output: one page brief or no action.