Page Lifecycle mock · example data, fictional clinic

Page Lifecycle + Growth Engine: every post checked, explained, improved and proven, on Google and in AI answers

Example data for Cedar Grove Animal Hospital, a fictional vet clinic whose site runs on the theStacc website builder. 52 screens; 38 are tagged Needs backend work. Linear THE-297. Updated 7 Nov with the Growth Engine plan: 19 new screens for connections, teardown, AI answers, refresh queue, site health, trust, local, safety, agencies and the internal Lab.

Skim all screensShort versionCoverageWalkthrough, short version and coverage list the original 33 screens until they are regenerated.
New in this updateNeeds backend workInternal (theStacc team only)

What this shows

  • Publish at about 80% quality, then let Search Console, GA4 and AI-answer data decide what each post needs.
  • Every post gets a job, a target query with real demand and a format copied from the top results, before it is written.
  • Each post gets a state at day 30, 60 and 90 and its causes, ranked. The teardown shows what the top 5 do that we don't: format, sub-questions, words, structure, design on a phone, authors, linking sites, speed, freshness.
  • Clicks lost to an AI Overview are told apart from lost rank, so we don't rewrite a post that only needs an answer that's easy to cite.
  • Every change is a diff the owner approves, with a protect list. Judged 28 days later against the rest of the site and against similar unchanged posts, with Google updates marked. Can be rolled back.
  • Safety limits run before anything ships: publishing pace, duplicates across all theStacc sites, vet sign-off, automatic pause on a penalty.
  • The Lab learns what works across millions of results, tests it on theStacc's own sites, then rolls it out in stages and updates every agent.

What's new in this update 19 screens

  • CN01 Connections: every data source in one place
  • CT01 Teardown: what the top 5 do that we don't
  • PG08 Page: clicks lost to an AI answer, not to rank
  • RQ01 Refresh queue: every post losing traffic, by bookings lost
  • OT02 Your tasks: press requests and mentions without a link
  • HS04 One change: judged against the site and similar posts
  • SH01 Site health: indexing and AI crawlers
  • TR01 Authors and trust: who wrote it and how we prove it
  • AI01 AI visibility: who AI assistants recommend, and why not us
  • GH01 Home: Google and AI answers side by side
  • LC01 Local: reviews, Business Profile and map rank
  • SF01 Safety: limits that keep the site out of trouble with Google
  • AG01 Agency: every client site in one table
  • PH04 Phone: the Monday email with wins
  • LB01 Lab: what the top 3 share, by type of search
  • LB02 Lab: what moved after a Google update
  • LB03 Lab: every tactic as a test before customers get it
  • LB04 Lab: one tactic rolling out in stages
  • LB05 Lab: the rules and prompts every agent reads

Two edits proposed to existing screens. ST01: remove "FAQ additions" from what may ship without asking, and from snippet changes on healthy posts; Google stopped showing FAQ results on 7 May 2026. HS01/HS02: add the "similar posts" comparison shown in HS04.

1Connect, then before publishing and the first 30 days

Connect the data once. A new post gets a job, a target query and a format before it is written. In the first 30 days we show crawling, indexing and the first queries.

2Checks, states and causes

The day-90 check with causes ranked, the full teardown behind it, a post losing clicks to an AI answer, an off-target post, a post Google has not indexed, a declining post, and the site-wide refresh queue.

3Review and approve proposals

Seven proposals and a rollback, each a diff with its evidence. Merging asks for confirmation and gets its own shipped screen. Each approval ships as its own site version.

4What only the owner can do

Links from other sites, photos, reviews and facts become tasks next to the proposals. Press requests and mentions without a link are drafted; the owner sends.

5Did it work

Every change judged 28 days later against the rest of the site and against similar unchanged posts, with Google updates marked. A rollback for a change that made things worse. One page a month in the owner's numbers.

6The whole site

Clusters, hubs, orphans and overlaps; whether Google and AI assistants can find every post; and the authors and structured data behind the content.

7AI answers

How often ChatGPT, Google AI Mode, Gemini, Perplexity, Copilot and Claude mention the clinic compared with nearby clinics, and the gaps turned into proposals and tasks.

8Where it meets what customers already have

Home shows Google and AI answers side by side. Analytics cards hand over to Pages. Keyword suggestions feed new posts. Local SEO reviews and Business Profile posts tie into Pages.

9Keeping the site safe

Publishing limits, a duplicate check across every theStacc site, vet sign-off, AI-leftover checks, and an automatic pause on a penalty or a sharp drop.

10When the data is missing

No Search Console: every state is unknown, never zero. A failed sync pauses checks and marks every number with its date.

11Who decides

The SEO lead's queue on a managed site, an agency's portfolio, and the settings that say who decides what and where changes ship.

12On the phone

The checkpoint email, the queue on the phone, a title fix approved from it, and the Monday email with wins.

13theStacc Lab (internal)

The brain behind the agents: what top results share by type of search, what moved after each Google update, every tactic tested on theStacc's own sites before customers, and the versioned rules every agent reads.