With Voss. × Neumann Steel

02 · Why it works

Roughly half of what is paid for does not appear in a screenshot.

The visible design is about half the job. The rest decides whether the site keeps the rankings it already has, whether AI assistants can quote it, whether the specifications can be found at all, and whether anyone can break into it.

Keeping what you already have

The 301 redirect map
A written map of all 159 indexed URLs, each pointing at the page or the section that replaces it. Built before launch, tested before launch, and extended when the article library moves in Phase 2. Where eleven bar chair pages become one deep page, each old URL points at its own section, never at the homepage. This is the single thing that decides whether a rebuild keeps its rankings, and it is lost through carelessness rather than bad luck.
The parity check
On launch day every old URL and every new URL is crawled and compared side by side: titles, descriptions, headings, internal links and content. Nothing goes live with a gap. Merging is not deletion. A redirect map that is never verified is a document, not a safeguard.
Ninety days of watching
Search Console monitored weekly against the baseline recorded before the switch, and reported to you. If a page loses ground you hear it from us first, with what we are doing about it. The old site stays available until the new one has settled.
Specification data extraction
Your product data exists as PDFs: the Shapes Guide, the Product Guide and thirty six brochures. Each figure is read out, checked against the standard it cites, and published as a real table in the page. Anything not stated in a current Neumann document is published as to be confirmed, in its own marked panel. The largest single piece of hidden work in the project, and the reason the site becomes quotable.

Being found, and being quoted

Structured data
A local business record for each of the five branches, each with its own address, hours and link to its own Google listing, and built to take a sixth. Product records carrying the specifications from the tables. Question records on the nine FAQ answers you have already written. Breadcrumbs on every page. Today the site emits one generic record with one address, so four of the five branches do not exist in its data at all.
Written for AI assistants
An llms.txt file, which none of the four Australian competitors audited publishes, and every page structured in clean quotable sections. Then ten real buyer questions put to ChatGPT, Gemini, Copilot and Perplexity every quarter, answers recorded verbatim, and the content shaped until Neumann Steel is the name in them. When an assistant names one supplier, that supplier gets the call and nobody else knows the question was asked.
Titles, descriptions and share cards
Including the missing homepage share image, and meta descriptions on the five branch pages, which have none today.
Google Business Profile
Worked across all five branches, and connected to the site through the per branch structured data. There are eight reviews across the entire five branch national network and the Currumbin flagship has none, while a single shopfront competitor in Hervey Bay holds thirty six. That is a review generation problem, and it is a process we build and run.
Measurement
Search Console, Bing, phone taps and form submissions counted as enquiries, with a baseline recorded the week you launch. Everything afterwards is measured against it.

Safety, licensing and the build itself

Nothing to log into
Static build: no WordPress, no PHP, no database, no plugins, no login page. Most business websites are broken into through their own admin panel or an out of date plugin. That entire category of risk stops existing rather than being managed. Today the enquiry forms run on a plugin a full major version behind, missing two of the vendor's own security releases.
All six security headers
Content security policy, strict transport security, clickjacking protection, referrer policy, permissions policy and content type protection, set at the edge. A firewall and bot rules that can tell a legitimate reader from an attacker. Hardened upload handling with file type and size gates. The current site has none of the six, and its edge protection returned an empty challenge page as HTTP 202, a success code, forty times over twenty minutes.
Licensed typefaces, self hosted
Barlow Condensed and Barlow, licensed for web use and served from your own domain. Nothing loads a font, a script or an image from a third party host. The current stylesheet requests seven display families and delivers none: six are trial builds with the word Trial in the file name, one is another company's proprietary corporate face. It is a legal exposure and a design problem at once, and one change fixes both.
Staging that cannot be indexed
Every concept and preview build ships with indexing blocked in the page and blocked again in the robots file, and there is no deploy target for the concept until you approve one. The two controls come off together, deliberately, on launch day, as a single step on the written launch checklist.
Calculator verification
Every constant is written on the page it is used on, sourced, and signed off by someone technical at Neumann Steel before the tool ships. Publishing a number a builder orders steel against is a serious act. If nobody will own the lap length coefficients, that tool does not ship and the page says why.
Hosting, documented
The site runs in a dedicated Neumann group account that With Voss sets up and manages, built to carry every group website over time, with hosting on-charged as one line on the quarterly invoice. First year included. You own the work in full on final payment, everything is documented, and the account hands over intact whenever the group asks.

The short version for the board: the difference between a website that exists and a website that keeps its rankings, gets quoted by machines, publishes numbers people can order against, and cannot be broken into. None of it is on the current site. All of it is inside the fixed Phase 1 fee, and the security summary and launch checklist are handed over in writing.

← The conceptThe tools →