Flow map

Requirement to screen coverage

15 of 15 drawn (text check; no reviewer pass yet).

IDRequirementStatusScreensWhat the screen showsCheck
R1Check every published page automatically at day 30, 60 and 90, then every 90 days: indexed, impressions, clicks, positiobuiltPG02, PG03PG02: the day 30, 60 and 90 checks for one post
PG03: a post before its first check
TEXT OK
R2One list of all pages with their state, age and next check. (SEO team: "list of pages and history")builtPG01PG01: all 24 posts with state, age and next checkTEXT OK
R3Not indexed: request indexing; still not indexed at day 60 means a quality rewrite. (SEO team, existing THE-288 nudge)builtPG04PG04: a post still not indexed at day 60, with a rewrite proposedTEXT OK
R4Indexed but zero impressions: nobody searches it. Retarget to a query with real demand, or merge or delete it. (SEO teambuiltRV04, RV05RV04: retarget a post nobody searches
RV05: merge a post with no demand
TEXT OK
R5Impressions from queries we did not target: add a section for them and update title and meta. (SEO team)builtRV03RV03: a new section for an unplanned query, with title and meta diffTEXT OK
R6Upgrade weak assets: compare with ranking pages and add infographics, diagrams, tables or video. (SEO team)builtRV02RV02: added diagram, video and section shown as a diffTEXT OK
R7Fulfil the intent: detect the format Google prefers (video, steps, images) and match it. (SEO team, "how to tie a tie")builtPG02, RV02PG02: search result formats vs our post
RV02: video and step diagram to match a how-to intent
TEXT OK
R8Suggest good keywords from Search Console data, as "add to this page" or "new post". (SEO team)builtKW01KW01: queries turned into add-to-page, retarget or new-post suggestionsTEXT OK
R9A history of every change: when, why, what changed, and before/after numbers 28 days later. (SEO team; SEOTesting idea, builtHS01, HS02HS01: every change with before and after numbers
HS02: one change that worked, 28 days each side
TEXT OK
R10Every change is a diff the customer approves; prune always needs explicit confirmation and shows backlinks and conversiobuiltRV06, RV01RV06: confirmation before a merge
RV01: every proposal waits for approval
TEXT OK
R11A change can be rolled back. (our proposal; free on the website builder)builtHS03, RV07HS03: rollback of a change that made things worse
RV07: new site version with rollback to v37
TEXT OK
R12Say how each change ships for each destination (website builder, Shopify, WordPress, Webflow, Ghost). (our proposal, frobuiltST02ST02: update, redirect and rollback per CMSTEXT OK
R13Settings: checkpoint days, what may auto-ship, who decides on managed sites. (our proposal)builtST01ST01: checkpoint days, auto-ship switches, managed-site mergesTEXT OK
R14Tell the owner when a checkpoint needs them, on email or phone. (our proposal)builtPH01PH01: checkpoint email on the owner's phoneTEXT OK
R15Low-CTR pages get a title and meta fix only. (existing low_ctr rule)builtRV01RV01: a title and meta only fix for the low click rate postTEXT OK