The structural decisions underneath your site, and the questions that reveal whether yours work
A professional services firm redesigns its website, and before long it’s slow to update, awkward to add pages to, and nobody can explain why a simple change needs a developer. The design looked right at launch. What went wrong sits underneath the design, in the WordPress architecture: how content is structured, how pages are built, how the site connects to everything else the business runs. Most owners never see that layer until it starts costing them time and money, and by then it’s shaping what the marketing team can and can’t do each week.
Why the layer underneath decides what your site can do
Architecture is the set of decisions about how a site is organised. Where content lives, how it’s categorised, which parts are reusable, what happens when a form is submitted, how a new service page gets created and by whom. None of it is visible to a visitor. All of it shapes what your team can do without calling someone.
When those decisions are made well, the site grows with the business. Your marketing coordinator adds a case study in twenty minutes because case studies are a defined content type with defined fields. Where they’re made badly, every page is a one-off, built by hand in a page builder, and nothing can be changed at scale. We see this a lot: the site isn’t broken, it’s just unable to keep up.
The site isn’t broken, it’s just unable to keep up.
WordPress is the common ground here. The RADAR Digital Index benchmarked 493 engineering and construction businesses in Australia in Q3 2026, and 92.9% ran their websites on WordPress. One sector, one quarter, so read it narrowly. But it does tell you where the decisions that matter get made: in how the platform is set up, not in choosing it.
What WordPress architecture covers
Four areas carry most of the weight. They’re worth understanding at a business level, because you’ll be asked about each one in a build and the answers determine what the site costs you later.
Content structure. Pages, posts, custom post types, taxonomies. If your business has services, projects, team members and locations, each of those is a type of content with its own fields. Defining them properly means consistent pages, filtering that works, and data you can reuse. Skip it and every page gets written from scratch in the editor.
How pages get built. Elementor, Gutenberg blocks, custom templates, or some mix. A page builder gives flexibility to non-technical editors. Custom templates give consistency and speed. Most established businesses need both: a controlled template for the pages that matter commercially, and freedom on the ones that don’t.
Integrations. Forms, CRM, email platform, analytics, booking, payments. The architecture decides whether a Gravity Forms submission lands in HubSpot with the right source attached, or sits in an inbox nobody checks on Fridays.
Hosting and the environment. Where the site runs, how it’s backed up, how updates are tested. This is less glamorous than design and more likely to wake you at 2am.
The quickest way to see the shape of your own site is to ask what it takes to add one new page of each type. If the answer differs wildly between them, your structure is doing less work than it should.
Questions to put to whoever builds your site
You don’t need to evaluate the code. You do need answers you can understand, because these decisions are expensive to reverse.
- What content types are you defining, and why those?
- Which pages can my team edit without breaking the design?
- Where do enquiries go, and how will I know the path works?
- What happens to this site when we add a new service line next year?
- Who holds the hosting, the domain and the admin access?
- If we part ways, what do we take with us?
That last one is the honest test. A site built on standard WordPress conventions, with content properly structured, can be handed to another developer and understood. A site held together with bespoke plugin logic and no documentation can’t, and you’ll feel that the first time you want a second opinion.
Signs your current architecture is the problem
Three things tend to show up together. Small changes take days and need a developer. Your team avoids the CMS because they’ve broken something before. And the site has a page for everything, with no pattern to any of it, because each one was built individually.
If you recognise two of those, the issue isn’t your marketing output or your agency’s responsiveness. The structure underneath makes ordinary work slow. That’s a fixable problem, and it rarely requires starting again. We work through this in custom WordPress development, where the question is usually which parts to keep.
Architecture decisions you should be involved in
Most of this is technical. Two parts aren’t, and you should hold a view on both.
Who owns publishing. If your team can’t publish a service page, a case study or a news item without external help, your content programme will stall. Decide what you want to control internally, then make that a requirement of the build rather than a hope.
What connects to what. The site is one part of how you win work. Where enquiries go, how they’re tracked, what the sales team sees. That’s a commercial decision about your operation, and it belongs with you. The build should follow it.
Everything else, including the plugin choices and the template logic, is a job for people who do it daily. Judge them on whether they can explain their reasoning in plain terms.
How a well-planned build usually runs
The sequence matters more than the timeline. It starts with the business: what you sell, who decides, what has to be true for the site to help. Content structure comes next, because that determines the templates. Then design against real content, with no placeholder text. Then development, testing, migration and handover, with training your team sits through.
Where that order gets reversed, which happens when design leads, you end up fitting content into layouts drawn before anyone knew what the content was. The result looks good in a presentation and fights you from the first month. This is the logic behind how we work: Clarify, Create, Convert, Compound, in that order.
Frequently asked questions
It’s how a WordPress site is structured underneath the design: content types, templates, how pages are built, and how the site connects to your CRM, forms and other systems. It decides what your team can change without a developer.
No. Plenty of well-structured sites use Elementor or a commercial theme. What matters is whether content is properly typed and templates are consistent.
Often yes. If the content is sound and the hosting is stable, restructuring content types and templates can be staged over time. A rebuild is warranted when the foundations can’t support what the business needs next.
You should. Your business should hold the domain, the hosting account and administrator access, with your agency given the access it needs to work. That keeps your options open.
Where to start if something feels stuck
Open your site’s dashboard and try to add one new page of a type you publish regularly. Time it. If that takes longer than it should, or you can’t do it at all, you’ve found the layer that needs attention, and you have something concrete to raise with whoever maintains the site.
Redfox is a Sydney-based digital growth agency with more than 20 years behind it, working with established businesses to find where growth gets stuck. The structure underneath a WordPress site is one of the more common places it hides. We build and rebuild sites so the business can run them.
If your site has stopped keeping up with the business, tell us what’s slowing you down and we’ll give you a straight read on whether the problem is structural or something simpler. Book a discovery call.
