How an AI agent rebuilt a PDR shop's site end-to-end — without opening Elementor.

The problem

The old TOČA MARIBOR frontpage was technically functional and commercially flat. It worked, in the sense that a visitor could read the words and find the phone number — but it didn't sell. Symptoms:

• Hero that promised three things at once. "BREZ LAKIRANJA. BREZ KITANJA. BREZ KOMPROMISOV." — a triple negative as the first thing on the page. Slovenian for "no painting, no filler, no compromises", which sounds confident in the room and confusing on a screen. No supporting visual: just text on a flat background.
• Service cards that read like a tariff sheet. Six identical cards in a 3×2 grid, each with the same icon-on-coloured-square treatment. The visitor's eye had nowhere to land.
• No process anywhere. Nothing on the page explained what actually happens when you bring a hail-damaged car in: estimate, scheduling, repair, pickup. For a service most people use once in a decade, that gap was costing bookings.
• Final CTA was a button, not an offer. An orange "BREZPLAČNA OCENA" button at the end of the page, no second-line value-prop next to it, no urgency, no social proof.
• Generic stack signature. The Astra + Elementor + UAEL combination was visible from orbit — the same dividers, the same icon-box widget, the same default spacing. Nothing said "we run a workshop", everything said "we bought a template".

The approach

The customer didn't hire a designer or a developer. An AI agent (Claude, via the Claude Code CLI) connected to the TOČA MARIBOR WordPress site through the AgenticWP MCP server — a single subprocess speaking the Model Context Protocol. From there, every change was a structured tool call. No Elementor editor sessions, no FTP, no copy-paste between browser tabs.

What AgenticWP exposes that mattered here

• update_elementor_element — surgically replace a single widget's settings or its full element JSON, preserving its ID. Triggers Elementor's Document::save() so the rendered HTML and CSS regenerate atomically.
• patch_css — atomically write or remove a named CSS block inside astra-settings.custom-css. Idempotent. Roll back any block in one call by name.
• insert_elementor_element — slot a new container or widget into a specific position in the page tree (start / end / before / after a sibling), with parent-type validation so a widget can't accidentally land at the page root.
• render_page — fetch the live frontend (no auth, no editor) to verify what visitors actually see after each save, including stylesheet count, inline-style byte count, and selector-matched HTML snippets.
• flush_cache — flush object, Elementor and Astra CSS caches together so changes go live for visitors without an admin login.

What got built

1. Hero with a real workshop photo and a single promise

The triple-negative headline ("BREZ LAKIRANJA. BREZ KITANJA. BREZ KOMPROMISOV.") got replaced with a concrete, single-promise headline — what the workshop actually does, in two beats. The flat background was swapped for a real photo of the workshop with the car under shop lights, so the page finally communicates "an actual place exists behind this URL." Buttons were unified to a primary booking CTA + secondary "see process" link, instead of three competing actions.

2. Services rebuilt as a card grid, not a tariff list

The old "services" block was a single white card containing seven bulleted service names (Hladno kleparstvo · Cenitve vozil za zavarovalnice · Kleparska in ličarska dela · Vzdrževanje vozil · Menjava avtostekel · Čiščenje vozil) sitting on top of a blurred Ferrari front-end photo. Visually noisy, no scannability, no per-service detail. The agent rebuilt it as a clean six-card grid under the eyebrow "NAŠE STORITVE" and the headline "CELOVITA SKRB ZA VAŠE VOZILO" — each card has its own icon, a one-line description, and a per-service "Več →" link. Built via update_elementor_element on the existing services container so the element ID stayed intact, with a named homepage-2026-services CSS block for typography and hover states.

3. A real process timeline — inserted where there wasn't one

The original page didn't actually have a process. What it had was a "what is PDR" info card next to a heading "HLADNO KLEPARSTVO · poglejte posnetek popravila udrtine" — a card describing the technique with four feature bullets ("Postopek je hiter / Cenovno ugoden / Prijazen okolju / Ohranja originalno barvo") plus an embedded video. Useful for technique-curious visitors, useless for someone trying to decide whether to book. The agent inserted a new container into the page tree via insert_elementor_element — placed after the services block, validated as a section-type parent so the widget tree stayed structurally legal — containing a four-step horizontal timeline under the headline "OD TOČE DO PREDAJE V 48 URAH" ("from hail to delivery in 48 hours"): 1 Kontakt ali rezervacija → 2 Skeniranje vozila → 3 Hladno kleparstvo → 4 Predaja vozila. Each step has a numbered circle, a short title, and a description. The new section ships under its own named homepage-2026-process CSS block so it's removable in a single patch_css mode=remove call.

4. Final CTA that actually asks for the booking

The bottom of the page used to be a low-contrast "we offer comprehensive services for…" paragraph ("NUDIMO CELOVITE STORITVE ZA CENITVE, STROKOVNO OBNOVO IN SKRBNO VZDRŽEVANJE VAŠEGA VOZILA") sitting on a noisy concrete-grey texture, with two italic testimonial blurbs floating above it and a single dark-blue "Pregled storitev in ponudbe" pill button as the only call-to-action. AgenticWP rebuilt it as a high-contrast conversion block: a deep blue gradient panel with a "VAS JE POTOLKLA TOČA?" eyebrow pill, the headline "POKLIČITE NAS. CENITEV JE BREZPLAČNA." (with BREZPLAČNA highlighted in yellow), a one-line value-prop, and a yellow primary "Rezerviraj cenitev →" button beside a ghost "Kontakt" button. Below the buttons sits a single inline utility line — opening hours · location · email — for visitors who hate forms. The agent rebuilt the section in place via update_elementor_element on the existing CTA container, preserving the element ID so the rest of the page's anchor links kept pointing at the same place.

The numbers

What "one focused session" actually means in production for the TOČA MARIBOR frontpage:

• 4 major frontpage sections rebuilt — hero, services, process (newly inserted), final CTA — each as an independent named CSS block, each removable in a single patch_css mode=remove call.
• 1 new section inserted via insert_elementor_element, with parent-type validation so the widget tree stayed structurally legal — no risk of a widget landing at the page root and tripping Document::save().
• 0 plugins installed. The site's existing stack (Astra, Elementor, UAEL, RankMath, LiteSpeed, Complianz) handled everything. No new dependencies, no new attack surface.
• 0 PHP files touched. Every change was a REST call into a structured endpoint — the entire AgenticWP perimeter is "WordPress runtime state, not code."
• Whole-site work continues from the same MCP session. This case study is scoped to the homepage; the inner pages were rebuilt in the same workflow.

What the AgenticWP guardrails caught

One moment where the product's deliberate "no" list shaped the work in a way that mattered:

• No PHP edits, ever. When the original triple-negative hero needed to go, the easy lazy path would have been a snippet in the child theme's functions.php filtering the rendered HTML. AgenticWP doesn't expose a code-edit endpoint — and that constraint forced the cleaner answer: replace the actual Elementor widget in place via update_elementor_element, preserving the element ID, so the change is visible in the editor, indexable by Elementor's revision history, and removable from the customer's own admin if they ever want to roll back.
• No new plugins. A redesign that quietly installs three plugins is a redesign that the customer's hosting bill, security posture, and update cadence will pay for forever. AgenticWP can't install plugins by design. The whole homepage rebuild lives in one named CSS block per section + structured Elementor JSON edits.