(ZIP FILE ATTACHED - SCROLL TO THE RIGHT) One of our members, Oliver, closed a €10,000 build plus a €2,500/month SEO retainer using exactly what's in this post. Not because the site looked good. Plenty of people can make a site look good now. Because it ranks, and because the client can run it without calling him. Everything I used is attached. The prompt that builds the site, the prompt that makes it rank, and the prompt that gives the client a CMS. THE THREE WAYS TO BUILD THESE SITES Every animated site I've built lands in one of three buckets. Pick one per site, don't try to do all three. 1. Scroll hub. One video, exported to frames, and the scroll position plays it forward or backward. That's the whole trick. Best for a single product launch, a flagship service, or a brand that needs one bold story from top to bottom. 2. Component build. Not one video. Separate elements that move at different speeds and react to each other. The plumbing site in the video is this: a 3D house that pulls apart as you scroll so you see the bathroom, then the kitchen, then the hot water system. Best when you have several services to show. 3. Custom interactive. One bespoke mechanic that only exists on that site. A tear, a pull, a grab. Silly, and it works: people stay on the page longer, and time on page is a metric Google pays attention to. You don't invent these, you steal the idea and hand it to the AI. Where to find them: - Scroll hubs: godly.design and motionsites.ai - Components: 21st.dev/community and app.spline.design/community - Custom mechanics: tympanus.net/codrops/demos and awwwards.com/websites/interaction-design Most of these let you copy the prompt straight off the page. Paste it in, change the product, and you have the build in about five minutes. THE PART THAT MAKES IT WORTH $10,000 A beautiful site nobody finds is a hobby. Run Lighthouse on anything you build and check four things: - Performance: 90+ - Accessibility: 90+ - Best practices: 90+ - Agentic browsing: 4 out of 4, or 3 out of 4 at worst

I've just made the workspace I use to run local SEO clients free for everyone here. It's one Notion page you duplicate per client. Everything you need to take a business from kickoff to a paying monthly retainer lives in it: the prompts, the audit checklist, the fix list, the weekly rhythm, the citation directory and the client prospecting pack. Grab it here: https://nice-rooster-633.notion.site/Local-SEO-Client-Workspace-3c02a8320ad2814ba1efcc9d8194dd45 Duplicate it into your own Notion, rename it to the client's business name, and work top to bottom. SET THE STACK UP ONCE (DO THIS BEFORE ANYTHING ELSE) - Claude Code: the engine that runs every prompt in the doc - DataForSEO MCP: live SERPs, keywords, backlinks, on-page, Lighthouse - Windsor.ai MCP: the client's Search Console and GA4 in one connection, no API keys or scripts - Zernio MCP: Google Business Profile posts, metrics and review replies - Fathom: records the onboarding call so you never take notes - DataWise: point-and-click backlinks, competitors and keyword research, included with the AI Ranking membership Set it up once and it works for every client after that. The Prompts & Tools Library page in the doc has the setup links and a walkthrough video for connecting DataForSEO. HOW TO ACTUALLY USE THE DOC, IN ORDER 1. ONBOARDING The goal is one file, client.md, that every job you run for that client reads first. Run the "build the client file" prompt BEFORE you speak to them: Claude researches everything public, then turns every gap into a "> CONFIRM:" block. The call is you reading those blocks out loud. Record it with Fathom and paste the link into the Meetings log. Onboarding is done when this returns zero: grep -c "CONFIRM:" client.md