Skip to content

Kidist Sandbox



Last Edited: 10/17/2025

Progress:
There are no rows in this table
There are no rows in this table
SB -All Pages Progress Bar (Total Yearly Goal)
All Pages
Pages Delivered
Pages Expected
Progress %
Progress Bar %
Total In Flight %
93
326
28.53%
Published (Live) %
30
326
9.2%
SB - GFD Pipeline Progress Bar (External)
GFD
Pages Delivered
Pages Expected
Progress %
Progress Bar %
GFD In-Flight %
49
199
24.62%
GFD Published (Live) %
0
199
0%
SB - Jasper Pipeline Progress Bar (Internal)
Jasper
Pages Delivered
Pages Expected
Progress %
Progress Bar %
Jasper In Flight %
43
126
34.13%
Jasper Published (Live) %
30
126
23.81%

test
All Pages
Pages Delivered
Pages Expected
Progress %
Total In Flight %
93
326
28.53%
Published (Live) %
30
326
9.2%
Key:
Planned Total
Total pages planned for 2025
Delivered
Draft GFD Finished and sent
Published
Completed/Live Pages
In Development
Pages IT is actively working on to implement
In Review
Pages currently going through the internal review process with different teams
Build
Pages currently GFD is building
Page Prep
Draft GFD delivered but needs to be prepared to be sent for business review. Kidist to-do
Kidist Need More Review
Feedback received, Kidist to revise before moving forward (Kidist to-do)
Pending ADO Ticket
Done with review & ready for IT (Kidist to-do)

SEO Progress Snapshot

test test

Page Status by Type of Initiative (Refresh vs Localized New Pages vs Non-Localized New Pages)


Page Type
Building
Page Prep
Marketing Review
Business Review
Legal Review
Pending ADO Ticket
GFD Revision
In Development
Pending Production
Published
Refresh Page
Non-Local New Page
Local New Page












Content Production Breakdown: Net New Vs Refresh

Out of all pages scheduled for production for 2025, 46% (261 pages) have been published. the remaining 54% (18% is with GFD being built and the remaining 36% is either undergoing internal review or being actively produced)
From the page that went to production 25% (42 pages) are refresh initiatives, 74% (123 pages) are local new pages for cycle, homeowners, renters, and boat, and 1% is non-local new pages for cycle.

What percent of pages are in ‘Build’ vs ‘In Review’ vs ‘In Dev’ vs ‘Published


How we are tracking against 2025 Goal


Percentage of Refreshed vs New Pages in Production


Page Status
Page Count
Agency Build
0
Agency Revisions
0
Implementation
In Review
0
Published
550
TOTAL
573


Page Status
Page Count
Planned
Published
TOTAL

Page Type
Page Count
Refresh Page
Non-Local New Page
Local New Page
TOTAL

Pages In Progress (Internally)

This section of the report includes everything we’ve received from GFD so far, but excludes pages that GFD is building

Pages published: 39% (167 Pages) have been published compared to prior week 31% (121 Pages).
Pages that reached major milestone: 57% (78 implementation + 167 published). A total of 245 pages have reached a major milestone with some already published and others ready to be published.
In Review: 38% (164 pages) are at different stage of review process - which is 1% WoW improvement.

‘In Review’ vs ‘Dev’ vs ‘Published’


Page Status
Page Count
Agency Revisions
Implementation
In Review
Published
TOTAL


Out of all the pages GFD delivered, what percentage are 'In Review,' 'In Development,' or 'Published' ?

Pages in Progress with GEICO per LOB


LOB
Page Count
Auto
Business Insurance
Commercial Auto
Homeowners
MOAT
Renters
Boat
Cycle
RV
TOTAL


How many pages per LOB are currently undergoing 'Review' or are 'In Development'?



Overview: Pages Development Status Report

The goal of the new CMS is self service and speed up page production. The ambition is that pages will go to production within 24 hours once they reach “implementation” stage or once legal approval.

Page Status Count

Page Status
Count
Building
Page Prep
Marketing Review
Business Review
Legal Review
Pending ADO Ticket
GFD Revision
In Moderation
In Development
Pending Production
Published
TOTAL




Tracking by Quarter

Page Status
1Q25
2Q25
3Q25
4Q25.
Building
Page Prep





Marketing Review
Business Review
Legal Review
Pending ADO Ticket
GFD Revision
In Development
In Moderation
Pending Production
Published
TOTAL

How many pages are in each status?


How are we tracking QoQ?


Average Time to Publish

Once page drafts are received from GFD, it takes an average of 60 days (which is longer than priors week 58 day mark), 53 days to publish refresh, and 50 days to publish non-local new pages as of 8/29/2025. The adjustment is due to the delay caused by the cms migration pause for homeowners state pages.

Average Time to Publish by Page Type


Page Type
Page Count
Average Duration
Refresh Page
9
79 days
Non-Local New Page
317
1 day
Local New Page
0
TOTAL







Average Time to Publish by LOB

LOB
Page Count
Average Duration
Auto
0
Business Insurance
Commercial Auto
Homeowners
MOAT
Renters
Boat
Cycle
RV
TOTAL

Copy 3 of Active: 2025 SEO Initiatives_Cal
Copy 4 of Active: 2025 SEO Initiatives_Cal

Page Type
Building
Page Prep
Marketing Review
Business Review
Legal Review
ADO Ticket Created
GFD Revision
In Development
Pending Production
Published
Refresh Page
4
0
0
0
0
1
0
1
2
1
Non-Local New Page
87
0
1
25
9
0
0
10
14
29

SandBox: 2026 SEO Initiatives_Test
Sandbox - Aging report

Average Time to Publish by Approval Method 2

SEO Workflow Dashboard

Top KPIs

(KPI cards: Total pages in pipeline, Pages Live, Review pages on track, Review pages overdue, Healthy pipeline %)
Table view (on track table view and bottle neck table view)
Add stage summary view (stage summary - page status by count and average day sin current stage) - this tells where the workflow is slowing down
Published performance view (historical learning view: this lets us know what took the longest)

Review Pages on Track

megaphone
0

Live Pages

ok

555


Total Pages in Pipeline

approval
397













Table
Total Pages in Pipeline
Live Pages
Review pages on track
Review Pages Overdue
Healthy Pipeline
397
555
0
12
95.97%

Want to print your doc?
This is not the way.
Try clicking the ··· in the right corner or using a keyboard shortcut (
CtrlP
) instead.