--- title: Elementor Rebuild Pattern — From Broken Site to Clean Build type: article created: '2026-04-05' updated: '2026-04-05' source_docs: - raw/2026-02-13-impromptu-zoom-meeting-122363825.md tags: - wordpress - elementor - site-rebuild - process - seo - project-management layer: 2 client_source: null industry_context: null transferable: true --- # Elementor Rebuild Pattern — From Broken Site to Clean Build When a client site is built on a bad theme, a mix of incompatible plugins, or a builder we don't control, fixing it in place is usually slower and riskier than starting fresh. This pattern documents the standard approach for spinning up a clean Elementor build and migrating content over. ## When to Use This Pattern Trigger a full rebuild rather than an in-place fix when you encounter: - A site built by the client or a previous developer using an unknown/unsupported builder - Multiple conflicting plugins (duplicate SEO tools, duplicate tag manager accounts, unsupported form plugins, etc.) - No clean template structure — pages built ad hoc with no reusable components - SEO tooling that doesn't match our stack (e.g., Rank Math instead of our standard) - A site that can't be reliably handed to a developer to extend > **Reference:** The [[wiki/clients/new-dawn/_index|New Dawn]] project stalled because the client built her own WordPress site using a bad theme and incompatible plugins. Fixing it in place was deemed inefficient; a full Elementor rebuild was chosen instead. See also the [[wiki/clients/cordwainer/_index|Cordwainer]] cleanup, where inherited plugins from a previous developer created similar instability. --- ## The Rebuild Process ### 1. Audit the Existing Site Before spinning up anything new, document what exists: - Identify all page types and group them into template categories (e.g., service pages, location pages, about/static pages) - Note which pages have finalized copy vs. which still need content - Flag any images that need polishing or replacement - Record existing forms, integrations, and analytics connections that need to be recreated ### 2. Spin Up a Fresh WordPress Environment - Create a brand new WordPress install — do not attempt to convert or clone the broken site - Install Elementor and our standard plugin stack from the start - Do **not** carry over plugins from the old site; install only what we need ### 3. Build Template Pages First Most sites have repeating page types. Build these as Elementor templates before touching one-off pages: - Identify 2–4 repeating layouts (e.g., specialty/service page, location page, team member page) - Build one template per type; all pages of that type inherit from it - Populate templates with finalized copy and swap images per page This is the bulk of the developer's work and can move quickly once templates are locked. ### 4. Hand Off Custom Pages to the Design Team Pages that don't fit a template (About Us, Contact, Client Center, etc.) need a design pass before the developer can build them: - Brief the design team with a list of non-templated pages - Ask for **simple Figma mocks only** — not full design explorations - Set a time expectation: these should take 30–45 minutes per page, not hours - Deliver Figma mocks to the developer alongside the template work > **Note:** The design team tends to over-engineer. Be explicit that these are utility pages for a small site — grab a Figma template, adapt it, move on. ### 5. Set Developer Timeline Once templates are defined and design mocks are in hand (or scoped), give the developer a firm deadline: - A typical rebuild of this type (templated pages + a few custom pages) should take **4–5 days** - The developer's job is largely: spin up environment → install templates → populate copy → build custom pages from mocks - Flag image review as a separate, lightweight pass at the end ### 6. Handle Backend SEO Setup (Separate from Dev Work) Backend setup should not block or be bundled with the developer's build work. Handle in parallel: - Install and configure our standard SEO plugin - Connect Google Analytics and Google Tag Manager - Submit sitemap to Google Search Console - Set up Instant Indexing to accelerate initial crawl - Verify all canonical tags are set correctly on launch This work can largely be done via automation/agents and should not require significant manual time. ### 7. Image Review Pass Before delivery, do a quick visual pass on all images: - Check that images are appropriately sized and compressed - Flag anything that looks off — stock photos that don't match the brand, low-res uploads, etc. - Loop in the client for final image approval; they often have preferences that aren't obvious from the copy ### 8. Client Communication Frame the rebuild clearly and positively when communicating with the client: - **Don't say:** "We're fixing your site." - **Do say:** "We're building you a completely new, professional site from scratch — done right from the beginning." - Quantify the value if appropriate (a site of this scope would typically cost $8k–$10k) - Set expectations for their involvement: they'll need to review pages and approve content/images - Give a concrete timeline (e.g., "We're aiming to have this done within a week") This framing also sets up a natural retainer conversation post-delivery: once the site is live and in good shape, the logical next step is ongoing SEO, ads, or maintenance. --- ## Roles | Role | Responsibility | |---|---| | **Developer (Eshok/Eshaq)** | Spin up environment, build templates, populate pages, migrate content | | **Design Team** | Figma mocks for non-templated pages only; keep scope tight | | **Mark (backend)** | SEO plugin config, Analytics/GTM, sitemap, Instant Indexing | | **Sebastian (PM)** | Client communication, content/image review coordination, developer tasking | --- ## Common Pitfalls - **Trying to fix in place:** Tempting when the site is "almost there," but inherited builders and plugins create compounding problems. Start fresh. - **Letting the design team scope-creep:** Custom pages for small sites don't need full design treatment. Timebox it. - **Bundling backend SEO into dev work:** These are separate tracks. Backend setup can happen in parallel and shouldn't gate the build. - **No client content review checkpoint:** Clients often have strong opinions about images and copy tone. Build in a review step before final delivery. --- ## Related - [[wiki/knowledge/website/gravity-forms-standard|Gravity Forms as Standard Form Plugin]] - [[wiki/knowledge/seo/sitemap-and-indexing-setup|Sitemap and Instant Indexing Setup]] - [[wiki/knowledge/seo/canonical-errors|Fixing Canonical Errors]] - [[wiki/clients/new-dawn/_index|New Dawn — Client Index]] - [[wiki/clients/cordwainer/_index|Cordwainer — Client Index]] - [[wiki/meetings/2026-02-13-impromptu-zoom-new-dawn-cordwainer-aviary|Meeting: New Dawn Rebuild, Cordwainer Cleanup, Aviary Recovery]]