Robotics Integrator Website: Off a Hosted Page Builder, Onto Owned Code

Industrial Automation Robotics Integration Site Migration

The Client

The client is a robotics and automation integrator. It programs and integrates robotic assembly lines for manufacturers. We do not name it here because the client has not published the relationship. The build record behind every figure on this page can be walked through on a call.

The Problem

• The website was a template on a hosted page builder that the company could not change in depth.
• Every page load made the visitor's browser contact 11 outside origins: the builder's own servers, its error tracking, a tag manager and an advertising pixel.
• The contact form had no action of its own. It posted to the builder's API, so on a copy of the site the fields rendered and nothing was sent anywhere.

What AppWT Built

1. A pure PHP rebuild. Same pages and same structure, rendered from shared PHP partials on owned code.
2. Every asset brought home. All 33 unique image URLs, 4 videos and 5 font files were moved onto the company's own origin, and each one was confirmed to load with the right content type.
3. Properly licensed fonts. Poppins and Open Sans are self-hosted under their open licenses. The form labels had used a commercial typeface that was not ours to redistribute, so they now use Open Sans in the same fixed-width columns, and the layout does not move.
4. A content security policy. A default-src 'self' header keeps outside calls from creeping back in after the next content edit.
5. A contact form that records the lead. A same-origin PHP form with server-side validation, a honeypot and a limit of 5 posts per 10 minutes per address. Leads are written to a store outside the web root, which was checked to return 404 over the web.
6. Nothing dropped silently. The old tag manager and advertising pixel belonged to the client's own accounts. AppWT recorded both, with the tag manager ID needed to add it back, instead of quietly removing them.

How We Proved It

Each page was loaded three times in real Chrome at 1440 by 900, scrolled, with the cache off, and compared with the live original using the same instrument both times.

• Home page: document height 6,072 pixels on both, all three runs. Words 411 of 412. Text similarity 0.9939.
• Solutions page: 3,073 pixels on both, all three runs. Words 257 of 258. Text similarity 0.9981.
• Contact page: 3,157 pixels on both, all three runs. Words 566 of 567. Text similarity 0.9991.

The one missing word on each page was a zero-width space inside an empty footer link. We left it out on purpose, because an empty link is an accessibility defect, not content.

Measurable Outcomes

On all three pages and on both hostnames, the rebuild showed 0 broken images, 0 console errors, 0 failed requests and 0 responses of 400 or higher. The 11 to 0 figure was measured at the migration. A later request to add an embedded map would bring back one outside origin on pages that show it, and the build record notes that.

What This Means for an Integrator or Manufacturer

A technical buyer judges your engineering by a page you may not be able to edit. Moving that page onto owned code gives you control of the content, the speed and the lead form, and a measured migration means nothing on the page changed by accident. See robotics integration, website migration services and industrial automation.