Page Lifecycle: every published post checked at day 30, 60 and 90, then improved
Example data for Cedar Grove Animal Hospital, a fictional vet clinic whose site runs on the theStacc website builder. 18 screens; 9 are tagged Needs backend work. The whole feature is new; the tag marks only scheduled jobs, outside APIs and AI work. Linear THE-297.
What this shows
- Publish at about 80% quality, then let Search Console data decide what each post needs.
- Each post gets a state at day 30, 60 and 90: too new, not indexed, no search demand, off target, close to page 1, low click rate, healthy or declining. Each state has one proposed action.
- Every change is a diff the owner approves. Merging or deleting a post always asks again and shows backlinks and conversions first.
- Every change is measured 28 days later against the 28 days before, and can be rolled back.
- How a change ships depends on where the site lives: the theStacc website builder can update, redirect and roll back today; WordPress, Webflow and Ghost can only create posts today.
1Pages and their checkpoints
Every post with its state, the day-90 check of one post, a post too new to judge, and one Google has not indexed.
PG01Pages: every post with its stateNeeds backend workScheduled checkpoint job: a Search Console snapshot for each post at day 30, 60 and 90, then every 90 days
PG02Page: day-90 check for the dog nails postNeeds backend workSearch results format scan for the target query (DataForSEO SERP): video carousel, image pack, what the top 3 pages contain
PG03Page: too new to judge
PG04Page: not indexed at day 60Needs backend workSearch Console URL Inspection API: index status, last crawl and request indexing2Review and approve proposals
Seven proposals, each a diff with its evidence. Merging asks for confirmation. Approving ships a new site version.
RV01To review: 7 proposals
RV02Proposal: match the intent (video and steps)Needs backend workAI rewrite of the post, step diagram and nail chart generation, 90-second video from the video module
RV03Proposal: add a section for an unplanned query
RV04Proposal: retarget a page nobody searchesNeeds backend workDataForSEO keyword volumes (US) to find a nearby query with real demand
RV05Proposal: merge a page with no demand
RV06Confirm merge and redirect
RV07Approved: how it shipsNeeds backend workWebsite builder publish of a new site version, plus a Search Console indexing request for the changed URL3Did it work
Every change with before and after numbers 28 days later, and a rollback for one that made things worse.
4Keyword suggestions
Queries from Search Console turned into add-to-page, retarget or new-post suggestions.
5Settings and the owner's phone
What is checked and when, what may ship without approval, how changes ship per CMS, and the checkpoint email.
