A reference matched section for section, with nothing borrowed but the shape

Get as close to the reference as possible — and copy nothing. Not its logo, its words or its photos.

This is the version of the job with legal exposure attached. A client wants a competitor-grade homepage that matches a reference closely: same layout, same scroll behaviour, same level of interactivity. What they cannot have is a single asset that belongs to somebody else.

It rebuilt the design language rather than the content. After studying the reference it planned the job out loud: a theme first, then original imagery, then the page built section by section.

It checked its own widget library and found nothing worth reusing, so it built fresh — fourteen original images, then nine sections, each one checked against the reference as it landed. Colour lives in theme tokens rather than hardcoded values, so retinting the palette recolours the whole page.

Mid-build it caught its own contrast bug and two mobile faults, fixed all three, and set the page live.

The partner logo grids are invented, and it said so — with the reason.

A logo wall is the easiest thing in the world to lift from a reference site, and the most damaging. WPOS generated its own placeholder logos instead, and explained why: the reference’s real clients are not this client’s to claim.

That is a legal judgement, made unprompted, about the agent’s own output. It also identified which parts of the page are placeholders needing replacement before launch, rather than leaving the reviewer to work it out.

• Nine sections matching the reference’s layout and scroll motion
• Fourteen original images, generated to the palette
• Its own theme with no hardcoded colour — retint the tokens and the page follows
• Zero console errors; desktop and mobile verified by the agent
• One contrast bug and two mobile faults caught and fixed mid-build
• Partner logos invented deliberately, with the legal reasoning stated on the record
• Not one word, image or logo taken from the reference

What this build actually used.

• Platform: WordPress with WPOS, nine sections on its own theme
• Reference analysis: the reference scraped and studied, then the job planned out loud before building
• Theme: its own theme and design tokens, with no hardcoded colour — retinting the tokens recolours the whole page
• Imagery: fourteen original generated images; no asset taken from the reference
• Widget reuse: the existing widget library checked first; nothing scored high enough, so all sections were built fresh
• Verification: desktop and mobile checked by the agent, which caught its own contrast bug and two mobile faults before going live
• Deliberate placeholders: partner logo grids generated rather than lifted, because the reference’s real clients are not this client’s to claim

Can I ask WPOS to match a competitor’s site closely without copying their assets?

Yes, and that was exactly this brief. It rebuilds the design language — layout, motion, type, palette — with its own theme, its own generated imagery and its own copy.

What does WPOS do about logos and client lists on a reference site?

It invents placeholders and tells you they are invented. Here it explained that the reference’s real clients would not be legitimate for this client to display.

Does it check its own work on mobile?

Yes. In this build it verified desktop and mobile itself, and caught a contrast bug plus two mobile faults before going live.

Start free for 30 days with 10,000 credits at wpos.ai. No card required, and nothing charges automatically. WPOS connects to any WordPress site, new or existing, on any host, and works alongside Gutenberg, Elementor, WooCommerce and Divi. Book a call with the founders at cal.com/algorismus/30min.