Skip to content
Receipts, not vibes. See how your website actually scores against ours on our new website audit comparison tool!
Six ways a small business gets a website, compared on five things that matter, with the Loam site highlightedSix ways to get a websiteWho edits it, who keeps it safe, and whether search and AI can read it.LoamWix orSquarespaceWordPressWebflowAI-builtCustom-codedEdit without a developerEdits stay on brandStructured data for AINo plugins to patchMonthly review for you

What makes a Loam website different?

May 19, 2026

Loam built ten example websites for fictional businesses. Here is how those sites compare with Wix, Squarespace, WordPress, Webflow, AI-built and custom-coded sites.

A Loam website is one you own outright, that your team can edit without the design drifting, that search engines and AI assistants can read from the first day, and that real people check every month and report on in plain language. None of those things is rare on its own. What is uncommon is getting all of them at once, from the same team, without bolting pieces on.

That is a claim, and you should not take it on trust. So this article does two jobs. It shows how a Loam site compares with the usual ways a small business gets a website, giving each one credit for what it does well. And it gives you the questions to ask any web team or platform, so you can decide for yourself, whether or not you ever talk to us.

Why are the businesses on Loam's example sites fictional?

Quick answer: because our clients' websites are not ours to show off. We invented ten businesses, one for each industry we serve, and built each of them a real, working website.

Many of the businesses we work with handle information their customers trust them with, and a portfolio of their sites would put their business on display without their say. So the bakery, the dojo, the medical practice and the rest are made up. Their products, prices, people and reviews are invented. The websites are not: each runs the same content management system, the same search and AI markup, the same security and the same speed we build into client sites. The forms really submit, and they come to Loam Agency rather than to a business that does not exist, so nobody waits on a reply that will never arrive.

Every example site carries a page called "Why this website?" with a comparison table and a short list of the questions people ask. What follows is that page, written out at the length a decision deserves.

What should you compare when choosing how to get a website?

Quick answer: five things decide how a website treats you after launch day: who owns it, who can edit it, whether search engines and AI can read it, who keeps it secure, and who looks after it.

Most people compare websites by how they look in a demo. That matters, but nearly every option can produce a good-looking home page. The differences show up a year later, when you need to add a service, change your prices, move to a new provider or find out why a page stopped appearing in search. These are the five groups the example sites compare on:

  • Ownership: is it built on open-source software, can you export your content whenever you want, and are features capped by a plan tier?
  • Editing: can you change content without a developer, do your edits stay on brand, and do you get drafts, a live preview and history?
  • Search and AI: is SEO structure built in, is there structured data that AI assistants can read, and can AI agents talk to the site directly through WebMCP?
  • Security: are there plugins to keep patched, is the site's data API closed to the public, and does someone review security every month and tell you what they found?
  • Care: does the site keep getting improvements after launch, and are there people who actually know your site?
How a Loam site compares with the usual alternativesA Loam siteWhat is typical elsewhereWho edits itYour team, with drafts anda live previewA builder, a prompt box or adeveloperStaying on brandPages built from sectionsdesigned for your brandEasy to drift with every new pageSearch structureOne H1, real descriptions,sitemap and breadcrumbsBasic settings, plugins or handworkAI answersStructured data, llms.txtand WebMCP built inRarely, or added by handSecurityNo plugins to patch, nopublic data APIPlugins to update or an exposedAPIOwnershipOpen-source software andcontent you can exportA subscription you cannot takewith youCareA monthly review, reportedto youSupport tickets, or whoever youcan find

The table reflects typical small-business setups as of 2026. Every platform changes, and each of these routes is the right answer for someone. The sections below walk through each one fairly, using the same values the example sites publish.

What does a DIY builder like Wix or Squarespace do well?

Quick answer: a builder subscription lets you edit content yourself without a developer, and you never have plugins to patch or a public data API to worry about. The trade-off is that you rent it.

For a business that wants to start this week on its own, a builder is a reasonable choice. Editing is in your hands, the platform handles its own updates, and security problems that come from add-ons are largely taken off the table.

Where it typically stops: the software is not open source, content export is limited, and features are capped by your plan tier. Edits can drift off brand, because each page is designed by whoever is editing it that day. SEO comes as basic settings and structured data is basic too. There is no monthly security review reported to you, and help arrives through support tickets rather than people who know your site.

Ask yourself: if you wanted to move in two years, what would come with you?

What about WordPress?

Quick answer: WordPress is open source, your content exports, its features are not capped by a plan, and you can edit without a developer. The trade-off is the stack of plugins you have to keep patched.

WordPress earns its popularity. You own the software, you can take your content anywhere, and drafts, preview and history are part of it. If you have someone dependable looking after it, it can serve a business well for years.

The usual catch is what makes it flexible. A typical setup is a theme plus plugins, and SEO structure and structured data come with plugins too, each one more thing to keep up to date. Its data API is open by default unless someone closes it. Edits can drift off brand. A monthly security review happens if you hire it, and the people who know your site are whoever you find.

Ask yourself: who updates the plugins, how often, and how will you know they did?

Where does Webflow fit?

Quick answer: Webflow is a polished, hosted design platform. Editing is easy, edits stay on brand, drafts and preview are built in, and there are no plugins to patch. You rent it, much like a builder.

For a design-led business that wants tight visual control without managing hosting, it is a strong option. The platform keeps itself updated, and its data API is closed to the public.

The typical limits: it is not open source, export covers the CMS content only, and features are capped by plan. SEO structure is partly manual and structured data for AI answers is hand-coded. There is no monthly security review reported to you, and support comes through tickets.

Ask yourself: which parts of your site would you lose if you left, and which plan do the features you need sit on?

Is an AI-built website enough?

Quick answer: AI tools make a fast first draft, and that draft has no plan tier and no plugins. But most leave you with no editor, no security review and nobody to call, so every later change goes back to the prompt box.

If you need a placeholder page this afternoon, a generated site can do it. The trouble starts with the second change. Editing content without a developer is not typically possible, so you prompt again, and each prompt can change the design. There are no drafts, no preview and no history to fall back on. SEO structure is often missing, structured data is rare, and content rarely exports cleanly. The data behind the site is often exposed. After launch it gets no improvements, and the people who know your site are you and a prompt box.

Ask yourself: how will you change one price next month without redesigning the page?

When is a custom-coded site the right call?

Quick answer: a one-off developer build has no plan tier, no plugins, and its edits stay on brand because the developer controls every detail. Its weakness is what happens after the developer moves on.

If your business needs something genuinely unusual and you have a developer you trust for the long term, custom code can fit you exactly. The risk sits in the care column. Editing without a developer is rare, as are drafts, history and clean content export. SEO structure is there if the developer remembered it. A monthly review happens if you pay for it, improvements stop at launch, and the people who know your site are available when they are available.

Ask yourself: if your developer took another job tomorrow, who could change your site?

What does a Loam website do differently?

Quick answer: it answers yes in every row of that table, because the features are built in and maintained together, and the same team that built the site keeps looking after it.

In plain terms, a Loam site gives you six things:

  • You can edit it yourself. A real content management system with drafts and live preview. Text, pictures, pages, menus, prices and team members are edited in a private admin.
  • It stays on brand. Pages are built from sections already designed for your brand, using colors and type defined once as design tokens, so a page added next year still looks like it belongs.
  • Search engines and AI can read it. One H1 per page, real meta descriptions, structured data, a live sitemap, an llms.txt guide and WebMCP, all built in.
  • There is nothing to patch on a Tuesday night. No plugin marketplace, no public data API and no secrets in the page.
  • You are not renting it. It runs on open-source software, Payload CMS and Next.js, your content exports whenever you like, and the domain and database are in your name.
  • Real people keep it healthy. A monthly security and maintenance review, with a plain-language report of what was done.

One honest limit belongs here too. Nobody honest can promise you a ranking on Google or a mention in an AI answer, and we do not. What we can promise is that nothing technical holds the site back. The rest comes from what you publish, which is why every example site has a blog, and why we wrote about why every business needs a blog.

Which questions should you ask any web team or platform?

Quick answer: ask questions whose answers you can check. A good team answers them plainly and shows you; a weak one changes the subject to how the home page will look.

These work whether you are talking to an agency, a freelancer or a platform's sales page:

  1. Who owns the domain, the content and the database, and in whose name are they registered? You want the answer to be you, in writing.
  2. How do I export everything if I leave? Ask to see it done, not described.
  3. Show me how I would change a price, add a team member and publish an article. Watch whether it takes plain fields and a publish button, or a ticket.
  4. What stops my edits from breaking the design? Listen for designed sections and brand settings, rather than a blank canvas.
  5. Can I save a draft, preview it and roll back a change?
  6. How many headings does each page have, and who writes the meta descriptions? The right answer is one H1 per page, and a description on every page even when an editor forgets one.
  7. What structured data does the site publish, and can AI assistants read it?
  8. What third-party add-ons does the site depend on, and who updates them?
  9. Is the site's data reachable by anonymous visitors? Pages should be public; the content database behind them should not.
  10. Who reviews security each month, and will I get a report I can read?
  11. What happens after launch: does the site keep improving, and who do I call?
  12. What are the running costs, and which of them are in my name?

Write the answers down. The value is not in any single reply but in how the answers compare across the teams you talk to.

How do you decide which route fits your business?

Quick answer: start from what you will need in two years, not what you need next week, and weigh who will be doing the work after launch.

A few honest rules of thumb:

  • If you are just starting and want to do it yourself, a builder subscription gets you online quickly. Know that you are renting, and keep copies of your words and photos somewhere you control.
  • If you have a trusted person to maintain it, WordPress gives you ownership and flexibility. Budget their time for plugin updates and security, every month.
  • If visual control matters most and you are happy on a hosted platform, Webflow is a strong fit. Check which features sit on which plan and what an export would include.
  • If you need something on screen today, an AI-built page can hold the spot. Plan for what replaces it.
  • If your needs are truly one of a kind, a custom build can fit exactly. Settle who maintains it before a line of code is written.
  • If your customers need to trust you, your team will edit the site often, and you want it found by search and AI without managing any of the technical side, that is the job a Loam site is built for.

Whichever way you lean, take the twelve questions above to every conversation. They are as useful for ruling us out as for ruling us in.

Where can you see a Loam website working?

Quick answer: on any of our example sites. The businesses are fictional; the editors, the markup, the forms and the security behind them are real.

Open one, for example the fictional bakery's Why this website? page, to see the full comparison and its questions marked up as FAQ data that AI assistants can quote. Every example site also has a "How this site works" tour that points at each invisible feature on the page itself.

If you share your current website on any example site's "Get a site like this" page, we will send you a free Website Showdown: your site against that sample across speed, search, AI answers, accessibility, security and privacy, about 45 checks, each reviewed by a person before it reaches you. Or tell us about your business directly. Yours would be designed around your brand and filled with your real content, with none of the fiction.

Questions readers ask next

Yes. Pages, articles and images come across, and old addresses are redirected to the new ones so links and search standing are kept. The migration plan is agreed before anything moves.

Not for everyday edits. Your team changes text, images, pages and articles in the editor, and the design holds. A developer is only needed for genuinely new features.

Your domain is in your name and your content lives in a database account you own, so you can take both with you. Nothing is locked behind a contract you cannot exit.

It costs more up front than doing it yourself, and less than the time and patching a DIY site often absorbs later. Compare the total cost of ownership over a few years, including your own hours.

It depends on the number of pages and how much content is ready. A small site moves faster when the copy and photos are prepared early, and we agree a schedule at the start.