Three phases. One recurring weekly block.
Why this mattersYou have the audit. You have the gaps. Now we turn them into a phased plan you can actually execute. The biggest reason Core 30 builds fail is not lack of strategy — it is overwhelm. 30 pages feels like a mountain when you are sitting at a desk on a Tuesday with three client calls scheduled. The solution is sequencing.
Read this once. Sit with it before you answer.
Of the gaps your audit just surfaced, what gets built first, what gets built second, and what gets deliberately deferred so the build does not crush you?
Where you stand right now.
By the end of this lesson, you will be able to:
- 1Sequence your Core 30 build into three phases (quick wins, service infrastructure, depth and expansion).
- 2Schedule a recurring weekly Core 30 block on your calendar.
- 3Set target completion dates for phase one (30 days) and outline phases two and three.
- 4Decide whether you will write the pages in your Claude Project or delegate to a writer or agency.
The whole lesson in a few points.
- 01Three phases. 30 days each plus a 90-day phase three.
- 02Phase 1 (days 1 to 30): quick wins. Title tags, schema markup, NAP fixes. No new pages yet.
- 03Phase 2 (days 31 to 90): build the missing service infrastructure. One new hub every two weeks. Two new service pages per week.
- 04Phase 3 (days 91 to 180): geographic expansion and topical depth. Dead zone neighborhood pages. Cost, comparison, and FAQ pages.
- 05Block 2 to 3 hours per week, same day, same time. Sporadic effort kills Core 30 builds. Consistent blocks finish them.
Phase one — the first 30 days.
Phase one is quick wins and foundation fixes. The goal is not to build new pages — it is to fix what already exists so it stops actively hurting you, and to lay the groundwork for what you will build in phase two.
Priority one. Update title tags and URLs across every existing service page to match the Service plus City format. This is a half-day project for most sites and one of the highest-impact moves in the entire module. Google picks up the changes within days.
Priority two. Add LocalBusiness schema markup if your site does not have it. A one-time technical install. On GoHighLevel it can be added through site settings or a code embed. On a custom build, a developer can add it in about an hour.
Priority three. Audit and fix your NAP in your website header and footer. Make sure your business name, address, service area, phone number, and hours match exactly what is on your GBP and your Module 6 citation master record.
By the end of day 30, your foundation is clean. No new pages yet. But the existing site stops sending fragmented signals.
Phase two — days 31 through 90.
Phase two is when you build the missing service infrastructure from Layer one of your Core 30. The goal is to close the gap between your GBP categories and services and your website pages.
First. Service hub pages for any GBP category that does not have one. Aim for one new hub every two weeks. Six categories missing hubs is 12 weeks of hub building.
Second. Specific service pages for each service that does not have a dedicated URL. Aim for two new service pages per week — shorter than hubs and faster to write.
Third. As each service page goes live, link it from the parent hub and from any related neighborhood content that already exists.
Use your Claude Project to draft each page. Customer language from your Quick Info. Caleb's title tag formula. Internal links to the hub and related services. Real photos from your job archive. By the end of day 90, you should have your full Layer one infrastructure — probably 18 to 24 pages. That is the bulk of Core 30 done.
Phase three — days 91 through 180.
Phase three is geographic expansion and topical depth — Layer two and Layer three from Lesson 10.2.
First. Neighborhood pages for the dead zones from your Module 9 heat map. One every two to three weeks. Same workflow as service pages but with the city or neighborhood name carrying the URL, title, and content.
Second. Topical depth pages. Cost, comparison, FAQ. The ones that match the questions your customers actually ask, pulled from the Lesson 5.6 review mining output.
Third. Link the new pages into the existing structure. Every new page links back to relevant service hubs and forward to related topical content.
By day 180, your Core 30 is complete or close to it. The site is a structured authority instead of a brochure.
Schedule the build sustainably.
Phased execution only works if you put it on the calendar. Block two to three hours per week for Core 30 work during phase one and phase two. One single recurring block. Same day, same time, every week. Whatever day works for you.
Two blocks a week accelerates the build. One block still finishes it. What kills Core 30 projects is sporadic effort — an hour here, an hour there, never finishing a single page in one sitting.
For the actual writing, use your Claude Project. Your Quick Info, services list, customer language, and brand voice are already loaded. You are not writing from scratch — you are running a prompt, editing the output to sound like you, and publishing. Owners who do not want to write themselves can delegate to a writer or agency. The structure is fixed (Core 30 architecture). The execution can be handed off.
Schedule the recurring block now.
Open your workbook to the 90-Day Alignment Plan page. Fill in phase one — the three specific priorities with target completion dates within the next 30 days. Sketch in phase two — which hubs and service pages get built first, in what order. Note phase three at a high level — the neighborhoods and topical pages you will tackle in days 91 through 180.
Schedule your recurring weekly Core 30 block on your calendar this week. The block is non-negotiable. Show up at the time. Build what you committed to.
Phase one cleans up. Phase two builds the spine. Phase three adds the depth.
180 days from now, your website backs up everything your GBP claims. The next module is where we turn the content engine on.
The vocabulary that follows you.
- Three-phase build
- The sequenced 180-day plan that splits Core 30 work into Phase 1 (quick wins, 30 days), Phase 2 (service infrastructure, 60 days), and Phase 3 (depth and expansion, 90 days). Prevents overwhelm.
- Quick wins phase
- Days 1 to 30. Fixes existing pages without building new ones. Title tags, schema markup, and NAP corrections.
- Service infrastructure phase
- Days 31 to 90. Builds out Layer one (service hubs and child service pages) at the rate of one hub every two weeks and two service pages per week.
- Depth and expansion phase
- Days 91 to 180. Builds Layer two (dead zone neighborhood pages) and Layer three (cost, comparison, FAQ pages).
- Recurring weekly Core 30 block
- Two to three hours per week, same day, same time. The single discipline that finishes a Core 30 build. Sporadic effort kills it.