Most WordPress projects don't stumble on the design. They stumble on the small, invisible details — how an image stacks on mobile, whether a page carries one H1 or five, and how a single template scales cleanly across eighteen pages. This case study walks through a white-label Divi WordPress website I built for a German marketing agency and their industrial end client. You'll see the exact problems we hit, the responsive layout fix that removed hours of manual work, and the SEO cleanup that kept the site search-friendly. It's written for agencies searching for a dependable white-label WordPress developer, and for freelancers who want an honest, behind-the-scenes look at how a multi-page Divi build actually runs — from a slightly messy kickoff to a satisfied client.

The Client & The Problem

The client was a marketing agency in Germany ordering on behalf of their own end client — an industrial manufacturer offering metal fabrication, solar, lighting, heating, construction, and automotive services. In other words, this was white-label work: my job was to build the site quietly in the background while the agency owned the client relationship.

The kickoff had one hiccup worth mentioning honestly. The original brief mentioned "18 sites," which could mean eighteen separate websites or one website with eighteen pages. Before writing a single line, I asked.

Scope Confusion: 18 Sites or 18 Pages?

The client clarified it was one website with eighteen pages, built from Adobe XD design files with content supplied in German Word documents. That one question saved a huge amount of rework. On any WordPress development project, confirming scope before the build is cheaper than fixing it after.

There were also access hiccups early on — admin credentials took a couple of attempts to land. Once I was in, I generated a secure password, confirmed the login with the client, and got straight to work on the homepage.

What I Proposed

The agency already had a design direction in Adobe XD and an extended Divi Plus license, so the plan was straightforward: build the site in Divi, match the XD templates precisely, and keep everything modular so pages could be duplicated and populated quickly.

My proposal centred on three commitments. First, build one polished "master" template — the Solar page — then reuse it across the remaining sector pages. Second, keep the work fully white-label with no branding or links back to my profile. Third, treat SEO hygiene as part of the build, not an afterthought. For agencies, this kind of custom Divi work is most valuable when it arrives clean and ready to hand to their client.

The Build Process

The build ran across roughly two weeks of active work, with feedback loops handled through annotated PDFs and Word documents from the client. Here's how the key pieces came together.

Templating from Adobe XD in Divi

I started with the homepage, matching the XD layouts section by section. For a tabbed content area I used the Divi Supreme module, and the client kindly confirmed their Divi Plus extended license covered what we needed — so no extra plugin cost. Early feedback was encouraging: "Thank you for your fast and awesome work! It looks great to me."

The Responsive Image Problem

This was the most interesting challenge. On desktop, image-and-text rows alternated left and right for visual rhythm. But on mobile, that alternating structure broke the reading order — one image sat below its text, the next sat above, and the layout felt inconsistent.

The client's requested solution was elegant. Instead of manually duplicating rows for mobile, keep every image in the left column in the backend, then use a lightweight script to flip the output order on the front end. The result: images alternate left and right on desktop, but always sit on top of the text on mobile. I implemented it, tested it across breakpoints, and it held up. If your Divi site behaves oddly on phones, this same approach is part of my responsive design fixes.

Fixing the SEO Basics

The client had a sharp eye and flagged three issues that quietly hurt SEO. Images were exported as uncompressed PNGs instead of lighter JPGs. File names were random rather than descriptive. And several pages carried multiple H1 headings.

I worked through each one — compressing and re-exporting images, giving files logical names, and enforcing a single H1 per page. These aren't glamorous fixes, but they compound. Clean image weight and correct heading structure feed directly into page speed and crawlability, which is why I bundle them into every speed and SEO optimisation pass.

Menu, Footer, and Anchor Links

Once the Solar template was locked, I duplicated it across the sector pages and filled in content from the supplied Word file. I then built the main menu, restored the greenish underline styling that had dropped when new items were added, and wired up the footer menu. The services section needed anchor links — mapping items like "Stanzen," "Kanten," and "Montage" to specific segments on the correct pages, so navigation stayed logical across the whole site.

One honest moment: a preview footer briefly showed a link to my profile. The client reminded me the project had to stay strictly white-label — "on this project your service has to be white label service with no links" — and I removed it immediately. Respecting that boundary is non-negotiable in white-label WordPress work.

The Result

The core site — homepage plus eighteen structured pages across seven industrial sectors — was built in Divi, matched to the XD designs, and made responsive with the custom image-order script. The SEO basics were corrected, the navigation and footer were wired with anchor links, and the whole build stayed cleanly white-label.

Because Fiverr's delivery clock was running down, I delivered the order formally on time and kept refining the site through the client's feedback afterwards — a practical call that kept the order healthy while the polish continued. The relationship warmed along the way; the client moved us to a first-name, casual tone and, after a round of careful feedback, said it plainly: "Sorry to be so rigorous at this point! You're doing a good job and I'm satisfied with your work!" For a white-label agency partner, that trust is the real deliverable.

Key Takeaway

A few lessons stand out from this build that apply to almost any multi-page WordPress project.

• Confirm scope in one sentence. "18 sites" versus "18 pages" is a wildly different quote. Ask before you build.
• Solve layout problems structurally. A small front-end script beat duplicating rows by hand — cleaner backend, better mobile output, less future maintenance.
• SEO hygiene is build work. Image compression, logical file names, and a single H1 per page cost little during the build and pay off for years.
• Respect white-label boundaries completely. No links, no branding, no exceptions. That discipline is what earns repeat agency work.

If you're an agency looking for a developer who can quietly build clean, responsive, SEO-aware Divi sites under your own brand — or a business owner who wants the same care on your project — that's exactly the kind of work I do at CodeSyte. You can explore my WordPress and Divi services here and tell me what you're building. I'll help you get it right the first time.