Get a Free Month of Claude

As a gift from EXPRE, experience the power of Claude AI with a complimentary one-month subscription.

What is Claude?

Claude is Anthropic's advanced AI assistant, designed to be helpful, harmless, and honest. With Claude, you can:

• Generate high-quality content and copy
• Analyze documents and extract insights
• Write and debug code
• Brainstorm ideas and solve complex problems
• Automate repetitive tasks

The post Get Claude Free appeared first on EXPRE.

Built for a Sector That Runs on Trust

Housing decisions are scrutinised and slow to reverse, so the website has to do the early reassurance work. That means accessible, fast pages, accreditations and case evidence on show, and a clear route to contact whether the visitor is a resident, a housing officer or a procurement lead.

Many residents and frontline staff arrive on a phone. We build mobile-first, so reporting a repair or finding a policy takes seconds, and so a contractor looks as capable on a small screen as it does in a framework submission.

Accessibility is treated as a requirement, not an add-on. WCAG 2.2 AA is standard on the sites we build, which protects both the people using them and the organisations accountable for them.

Content and Search That Reach Decision-Makers

The people who award housing-sector work search in specific ways: a service plus a region, a framework name, a compliance requirement. Winning that visibility takes service pages with genuine depth, local relevance, and content that answers the questions buyers ask during research.

We help organisations publish at a credible pace using AI-assisted drafting with expert review, so the technical accuracy that this sector demands is never traded for volume. That keeps your expertise visible without pulling delivery staff off the work that earns the contracts.

View our AI Content Creation service

The post Social Housing appeared first on EXPRE.

Built for How Clients Choose a Firm

Buyers in property and construction are cautious for good reason: the jobs are expensive and hard to reverse. The website has to do the early reassurance work. That means fast pages, an obvious phone number, accreditation on show, and recent projects within a click.

Most of this audience arrives on a phone, often from a site or a van. We build mobile-first, so the firm looks as capable on a small screen as it does in person, and so a quote request takes seconds rather than effort.

Accessibility is part of credibility. Clean, well-structured pages that meet WCAG 2.1 AA standards read as professional and reach every potential client, not only the ones on the latest hardware.

Content That Ranks for Real Queries

The searches that matter are specific: a survey type in a town, a construction service in a county, a material or method a client has been told to ask about. Winning them takes service pages with genuine depth and location relevance, not thin pages that say little.

For Phoenix Consulting, a firm of chartered surveyors, we built an AI content engine that cut research time by around 75 per cent while keeping a qualified expert in control of accuracy. That lets a busy practice publish at a pace that builds authority without pulling fee earners off client work.

View our AI Content Creation service

The post Property & Construction appeared first on EXPRE.

Every "you do not need this" is a statement about how the system works underneath, and once you have that, the list of things that genuinely move citations becomes short, specific, and harder to fake than most agencies want to admit.

This post takes Google's negatives, pairs each with what the wider evidence says, and lands on five practices that actually affect citation rates in 2026. The mechanism that explains almost all of it is query fan-out, and the page that wins is the one whose every H2 reads as a self-contained answer to a sub-question the user never asked out loud.

What Google said you do not need, and what that really means

Google's mythbusting post is a list of distractions to ignore. Each negative encodes a positive about retrieval: AI features read normal HTML, pick passages at query time, run on dense vector embeddings, and filter manipulated mentions. Once you reverse the negatives, the work is the same work that strong organic search has always rewarded, just more sharply weighted toward passage-level structure and named-entity specificity.

LLMs.txt and special markup

Google said you do not need a separate machine-readable file. The translation: AI features read your normal HTML and pick passages out of it at query time. The structure has to live in the content people see, not in a sidecar file no engine is parsing. That matches how passage-level retrieval has worked since BERT, when Google began annotating and scoring passages within a page independently of the page's overall rank. The whole page still gets indexed; what changed is that any 150-word slice of it can be lifted out and used to answer a query on its own.

Chunking content into tiny pieces

Google said you do not need to do this, because they do it for you. Industry analysis estimates the chunks the system picks are roughly 200 to 500 tokens, which is a few sentences to a couple of short paragraphs (NoGood, 30 January 2026). Each passage is evaluated independently. The practical instruction is not "ignore structure". It is: make sure any 150-word slice of your page reads as a self-contained answer.

Rewriting for AI systems

Google said synonyms and meaning are handled, so a separate AI version of your content is not needed. Correct, because retrieval now runs on vector embeddings rather than literal keyword matching. Your query becomes a vector. Every page on the web becomes a vector. Matches come from cosine similarity, not from counting how many times the keyword appears. The follow-on is straightforward: long-tail keyword stuffing is dead, and accurate naming of entities (the exact platform, the exact version, the named technique) matters more than it used to (Hall, June 2025).

Inauthentic mentions

Manufactured brand mentions on low-quality networks are filtered. Real mentions on sources Google already trusts are not. The signal is genuine, the manipulation is what gets thrown out. This is the same defensive posture Google has held since the Penguin update; what changed is that LLM-cited sources weight trusted-source mentions more heavily, so the gap between a synthetic PR push and an earned mention has widened.

Structured data

Google said schema is not required for AI Overviews. Also correct, but schema still helps with rich-result eligibility and entity disambiguation. A recent meta-analysis of citation studies found "Most studies that looked at schema and AI citations found a positive relationship. The effect was small, but it showed up consistently across multiple studies" (Vincet, May 2026). Worth doing for Article, Organization, FAQPage, and HowTo where they genuinely describe the content. Not worth fixating on.

The mechanic that explains almost everything: query fan-out

When a user types a question into Google's AI Mode, the system does not run that one query. It breaks it into multiple sub-queries and runs them in parallel. Google itself confirms this. Its May 2025 AI Mode announcement says: "AI Mode uses our query fan-out technique, breaking down your question into subtopics and issuing a multitude of queries simultaneously on your behalf." Deep Search "can issue hundreds of searches" using the same mechanic (Google blog, 20 May 2025). The model handling the decomposition is a custom version of Gemini 2.5.

In simple terms, Google no longer looks for one perfect page for one query. It looks for many smaller answers across many related questions.

Google: "AI Mode uses our query fan-out technique, breaking down your question into subtopics and issuing a multitude of queries simultaneously on your behalf."

How many sub-queries is a "multitude"? Google does not publish a number for standard AI Mode. Industry analysis estimates 8 to 12 for typical queries, with the figure rising into the hundreds for Deep Search (Ekamoira, January 2026). The exact count varies with topic and intent; the structural fact is that one user question triggers many parallel retrievals.

This explains why pages from positions 11 to 20 in classic search results now appear in AI Overviews. As Hall puts it: "you sometimes see content from page 3 of traditional search results appearing in AI Overviews. It wasn't ranking poorly for your main keyword. It was ranking well for one of the hidden synthetic queries." Your page can get cited not because it ranks for the headline term, but because it answers one specific sub-question the user never asked out loud.

The same mechanism runs, with different sub-query counts and different decomposition logic, inside ChatGPT, Perplexity, and Microsoft Copilot. iPullRank's analysis (December 2025) characterises the differences:

• Google is explicit and large-scale: "fires hundreds of searches" in parallel, organised by theme.
• Microsoft Copilot is iterative and graph-grounded: queries are generated sequentially, each one grounded before the next.
• Perplexity uses hybrid retrieval with multi-stage ranking, without labelling it as fan-out.
• ChatGPT is the least transparent: the number and shape of sub-queries are undisclosed (iPullRank).

The implication for any agency or in-house team is that "topical breadth around the entity" has displaced "single-keyword targeting" as the unit of work that pays back. The depth you bring to the secondary questions on a page is now doing more work than the primary H1.

For a popular-audience overview of the broader citation shift this post deep-dives, this Surfer Academy explainer covers the 2026 picture:

What actually moves citation rates

Five practices, in roughly the order to prioritise them on agency work.

1. Passage-level answerability

Every H2 section should open with a direct, complete answer in roughly 40 to 70 words, then expand. If you copy one section out of the page and read it cold, it should still make sense. Industry tracking suggests this is more than a stylistic preference: Averi reports 72.4% of ChatGPT-cited pages contain answer capsules of 40 to 60 words under H2 headings (Averi, updated April 2026). This single habit shifts more citation probability than any technical change to the page template.

Industry tracking (Averi): 72.4% of ChatGPT-cited pages contain 40 to 60 word self-contained answer capsules under H2 headings.

Practical test: open any one H2 on your existing top-revenue pages. Read only the next paragraph. Does it answer the H2 in 40 to 70 words? If it does not, you have left citation probability on the table.

2. Topical breadth around the entity, not the keyword

If you sell Hyvä Magento builds, the page that wins is the one that also handles Hypernode hosting trade-offs, B2B price-list configuration, Page Builder limitations, and migration paths from Magento 1. Each as its own well-answered sub-section. That breadth maps onto the sub-queries Google is firing in the background, which means more chances of being the source picked for one of them. iPullRank's Qforia tool simulates the sub-queries Google generates for a given seed query; running it on your top revenue pages exposes the gaps that traditional keyword research will not.

For Adobe Commerce 2.4.7 builds, the equivalent breadth is hosting (Adobe Commerce Cloud vs Hypernode), checkout customisations (Adobe Commerce Pay vs third-party), and the live-search vs Elasticsearch decision. For Shopify Plus builds, it is Hydrogen vs Liquid, B2B catalogues, and the Shopify Functions limits. Name the platforms, name the versions, name the trade-offs.

3. First-hand experience with specifics

This is the hardest one to fake and the easiest one to compound. Real numbers from a real account beat generic advice every time. Consider the difference between "we improved a client's paid search ROAS" and "an agency restructuring a Google Ads account from a handful of Performance Max campaigns into segmented SPAG groups, classifying every triggered search term, and roughly doubling ROAS over a quarter". The second cannot be replicated by an AI-written competitor page because the competitor does not have the data.

Examples in this paragraph are illustrative; see EXPRE's success stories for the actual client work.

Original case studies, named clients with permission, specific configurations, what failed and why, are now the moat. Google's E-E-A-T framework explicitly weights the first E, Experience, harder than it used to.

4. Freshness, particularly for Perplexity and ChatGPT

Perplexity is harsh on stale content. Industry tracking by Averi suggests content updated within the past twelve months earns roughly 3.2x more citations on Perplexity specifically. Freshness is weighted more heavily there than on any other major engine. Older analysis confirms the cliff is steep, with content beyond 60 to 90 days losing ground unless it continues to receive new citations or substantive updates (Ziptie, March 2026).

Industry tracking (Averi): content updated within twelve months earns roughly 3.2x more citations on Perplexity.

A quarterly review pass on your top 20 pages, refreshing statistics, adding a new sub-section, and bumping the date, outperforms publishing 20 new pages from scratch. The bottleneck is editing friction, and it kills more in-house programmes than any other single factor.

5. Source diversity across platforms

Google's mythbusting post is Google-only, which hides the fact that the same content does not get cited equally across engines. Industry citation tracking by Ziptie (March 2026) shows striking platform differences:

47.9% of ChatGPT top citations are Wikipedia.

46.7% of Perplexity top citations are Reddit.

23.3% of Google AI Overviews top citations are YouTube.

43.8% of Claude top citations are blog content.

Only 11% of domains are cited by both ChatGPT and Perplexity for the same query, and 71% of all cited sources appear on only one platform.

In practice, a Magento brand wanting cross-engine visibility has to be findable in more than one place. An active, well-moderated Reddit presence in the right subreddits helps with Perplexity. Captioned YouTube content covering the same topics as the written pages helps with Google AI Overviews, where video sources now carry significant weight (Pepper, May 2026). Well-edited industry-publication mentions help with ChatGPT, which leans on Wikipedia-adjacent reference sources. Detailed, well-argued blog content helps with Claude.

A single content asset rarely pays back across all four engines. A multi-channel strategy with the same expertise expressed in different formats does.

Things genuinely not worth the time

Reversing the evidence one more time, these are the activities with no measurable effect on citation rates:

• Creating an LLMs.txt file. Does nothing for Google and has not been confirmed as a ranking signal by any other major engine.
• Stuffing schema with redundant types. Use JSON-LD for Article, Organization, FAQPage, and HowTo where they genuinely describe the content. Stop there.
• Buying brand mentions on syndication networks. They get filtered.
• Maintaining a separate AI-friendly version of your content alongside the human version. The same well-structured page works for both audiences.
• Targeting hundreds of long-tail keyword variants as separate pages. Vector retrieval handles linguistic variation natively. The right move is consolidation around fewer, deeper pages that cover more sub-queries each.

A six-point scoring rubric for your top pages

If we were grading a client page right now, this is what we would check:

1. Does the H1 mirror the primary question, and does the first paragraph answer it directly in 40 to 70 words?
2. Does each H2 section open with a self-contained answer before expanding into detail?
3. Is there original data, a screenshot, a number, or a named case the competition cannot produce?
4. Are entities named specifically and consistently (Hyvä, Hypernode, Adobe Commerce 2.4.7, Shopify Plus), rather than as generic categories?
5. Has the page been substantively updated in the last 90 days, with a visible update date?
6. Is there a companion video or original image set covering the same topic, hosted in a way Google can index?

In practice, pages that score five or six out of six often compete far better than their domain authority would suggest, especially when the source material is genuinely first-hand. We have seen that play out repeatedly on EXPRE client work.

The whole shebang

Google's mythbusting post is a list of distractions to ignore. The work that remains is older and more familiar than the AI search conversation suggests. Write specifically. Structure each section as a self-contained answer. Keep it current. Cover the topic deeply enough to catch the sub-queries you cannot see. That is the whole game.

For more on the same shift from the EXPRE Insights archive, see how to optimise for Google's Generative Search Experience and why your website is losing traffic as AI replaces Google search. For practical help applying the rubric to a live site, EXPRE's AI SEO services include a first-pass audit and a quarterly content-refresh programme aligned with the citation mechanics described above.

The post Generative AI Search: What Actually Matters in 2026 appeared first on EXPRE.

Marketing teams ship faster when their agency runs like a system.

EXPRE is the digital operating partner for marketing leaders who are tired of two-week turnarounds, dropped briefs, and "we'll get to it next sprint". One small team, one operated platform, your website, search, ads and content moving as one.

Book a 30-minute call
Send your URL for a free audit

★★★★★ 5.0
on Google

How It Works

Our Agentic Orchestration System

Click any diagram to zoom in and explore how we coordinate people, platforms, and AI to deliver consistent marketing outcomes.

Click to zoom

Click to zoom

Click to zoom

×
‹
›

Trusted by

2 hrs

Median turnaround on a homepage edit via Webgentic

Last 90 days, n=341 changes

−38%

Average ad-spend waste cut after 90 days on intent-driven paid

Across 7 client accounts on Roasy

99.96%

12-month uptime across all managed sites

Monitored 24/7, ISO 27001-aligned

A Tuesday in your year

The same Tuesday, two agencies.

If you have run digital ops at an SMB or mid-market firm, the left column will look familiar. The right is what working with us looks like, built around an operated platform with a small named team.

Without an operated agency A typical day

You are 2 hours in and have shipped nothing.

• 09:14 Email your account manager about a homepage typo.
• 11:30 Reply to "could you confirm which line?" with a screenshot.
• 14:02 Get told the dev is on another project, ETA Thursday.
• 15:40 Notice last week's blog post is missing a meta description, log a ticket.
• 16:55 Open Search Console, see Core Web Vitals failing, log another ticket.
• 17:30 Forward an article on AI Overviews to your CEO with "we should do this".

With EXPRE Same Tuesday

You shipped 12 changes and still left at 5pm.

• 09:14 Type "fix the typo on hero, second line" into Webgentic. Live in 4 minutes.
• 11:30 Your specialist Slack: "shipped, also caught a missing alt tag on the same image, fixed."
• 14:02 Weekly ops report lands: 12 changes shipped, 2 conversion tests running, 1 LLM citation tracked.
• 15:40 Blog meta description was auto-checked at publish, no missing fields this month.
• 16:55 Performance monitor pinged us before you saw it, fix already in staging.
• 17:30 Forward the article. Reply lands tomorrow with our existing roadmap line item.

What we run for you

Sites, search, content. Run together, reported together.

Most agencies sell websites OR ads OR content as separate engagements. We run all three as one operated system, with a small named team and a shared memory of your brand, stack, and goals. Strategy and consulting sits inside each layer.

Layer 01 / Sites

Websites and ecommerce, operated.

Fast WordPress, Drupal, Magento and Shopify builds, fully maintained after launch. Your team edits via Webgentic; we monitor, patch, and step in for the changes that need judgement.

• Same-day edits via Webgentic, no ticket queue
• 24/7 monitoring, automated patching, ISO 27001-aligned
• Sub-second load, Core Web Vitals tracked weekly
• Quarterly strategy reviews, roadmap in writing

Read on websites →

Layer 02 / Search

Search, AI search, and paid.

Get found in Google, AI Overviews, and the answers your buyers ask LLMs. Technical SEO, generative SEO, and intent-driven paid (no PMAX). Roasy handles the bid layer.

• One reporting dashboard, not five
• LLM citation tracking and content built for it
• Ad-waste reduction targets in writing
• Monthly written readouts, no slide decks

Read on search →

Layer 03 / Operations

Operations and content.

Research, briefs, drafts, repurposing, reports, and lead nurture, run by orchestrated agents with a human reviewing every output. The boring half of marketing operations stops eating your week.

• Briefs and drafts in your tone, not generic
• Reports that land without you chasing them
• Lead nurture flows monitored weekly
• Consulting on tap, not by the hour

Read on operations →

The self-drive layer

Webgentic, in 30 seconds.

Your team logs in, types the change in plain English, the change is applied live. Our specialists watch and intervene if needed. It is how clients move from "open a ticket and wait" to "shipped this morning". 341 changes shipped via Webgentic across our managed sites in the last 90 days.

Tour Webgentic →

Case studies

Specific outcomes, named clients.

Turnaround times, traffic shifts, and ad efficiency, measured. Three recent below; the full library is at the success-stories page.

Nilfisk

391 Non-Branded Queries Ranking from Zero, with Page One Results in Five Days

Nilfisk's professional product catalogue ranked well for branded searches but captured almost nothing from the commercial intent queries buyers use when comparing options before shortlisting a supplier. EXPRE…

Read case study →

Fragrance Samples UK

Bespoke Automation Cutting Daily Order Processing from Hours to Minutes

Fragrance Samples UK needed to replace their 15-year-old Excel + VBA order processing pipeline that required 1.5 to 2.5 hours of manual work every day. EXPRE built a…

Read case study →

Phoenix Consulting

Modern WordPress Website with AI-Powered Content Research and Staff Photography System

Professional services firm delivered a modern WordPress site with AI-powered content research and staff photography system.

Read case study →

What working with us looks like

Your first 30 days of results.

Most agency timelines are vague to the point of useless. Here is what literally happens once we start.

Week 1

Audit and access

• 2-hour kick-off, named team meets you
• Stack, traffic, content audit, written
• Webgentic access provisioned
• Shared Slack or Teams channel live
• 30-day roadmap, with dates

Week 2 to 3

First wins shipped

• Quick-win edits live (typically 6 to 12 changes)
• Performance baseline locked
• Report cadence confirmed
• SEO and AI search visibility tracked
• Ad accounts audited and cleaned

Day 30

System in motion

• First monthly review, written
• Roadmap for month 2 agreed
• Your team running Webgentic edits unaided
• Compounding outputs measurable
• Renewal or scope adjustment, your call

Engagement bands

Honest about money.

Most clients land in one of three bands. Final scope and pricing land after a 30-minute call and a written proposal. No call required to see this.

Run

Single existing site, kept fast and current

£2.5k / month

From

• Up to 30 hours of changes a month
• Webgentic for your team
• Monthly performance review
• 24/7 monitoring, automated patching
• Quarterly strategy session

Most chosen

Run + Grow

Two of: Sites, Search, Operations

£6k to £15k / month

Range

• Everything in Run
• SEO and AI search visibility
• Paid media management (no PMAX)
• Content operations layer
• Monthly written roadmap

Operated System

All three layers, dedicated team

£18k+ / month

From

• Sites + Search + Operations
• Named specialists with brand memory
• Bi-weekly ops reviews
• Custom integrations and tooling
• Strategy and consulting layer

Not for everyone

Not a fit if any of these are true.

Saving us both a discovery call.

• You want a one-off project quote and no ongoing relationship.
• You want to keep using PMAX and "letting Google figure it out".
• You expect ranking guarantees in writing within 30 days.
• You need full WCAG 2.2 AAA compliance under public-sector procurement (we are aligned to AA, not AAA).
• Your team will not have 30 minutes a week to use Webgentic; the model needs an internal champion.
• Your decision criterion is the cheapest hourly rate. We are not the cheapest.

Two ways to start.

Either takes about five minutes of your time. We do the rest.

Book a 30-minute strategy call Send your URL for a free audit

The post Agentic Agency System appeared first on EXPRE.

AI Ecommerce Development

AI-Powered Magento and Shopify Stores That Sell While You Sleep

We build intelligent Magento and Shopify stores that increase conversions with AI product recommendations, dynamic pricing, and automated customer experiences that adapt to every visitor. We use AI assisted development to create platform and business specific workflows and tooling to help operations and save time.

25%+Higher conversion rates

3xFaster page loads

24/7AI optimisation

40%Reduced cart abandonment

Intelligent Commerce

Ecommerce Built for Profit, Not Just Traffic

Most online stores compete on price and hope for the best. We build stores that use AI to understand each visitor, recommend the right products, adjust pricing dynamically, and recover abandoned carts automatically.

Every store we deliver runs on high-performance architectures like Magento with Hyva or Shopify Plus, optimised for sub-second load times and continuous AI-driven improvements based on real customer behaviour.

Get a Free Store Audit

See exactly what's holding back your conversions and how AI can transform your ecommerce revenue.

Get My Free Audit

Prefer to talk?

George Kowalewski

Founder & AI Strategy Consultant

The post AI Ecommerce Development appeared first on EXPRE.

What AI Automation Actually Means for Your Business

AI automation is not a single product. It is a layer of orchestration connecting your existing systems and filling the gaps between them. A new lead from your website triggers a CRM entry, a welcome email, a task for your sales team, and a row in your tracking spreadsheet — without anyone touching a keyboard.

At a more sophisticated level, automation handles lead scoring: assessing incoming leads against your criteria and routing high-scoring prospects directly to sales, while lower-scoring leads enter a nurture sequence. When a lead's engagement reaches a threshold, they move automatically into the sales queue.

Reporting automation pulls data from multiple platforms, aggregates it into a consistent format, and delivers it to the right people on schedule. Your team gets the insight without the manual assembly work.

Most clients recover the cost of an automation project within three to four months.

The post AI Automation appeared first on EXPRE.

The Brief

Sumo Digital, a game development studio collective with over 20 years of industry experience, needed a complete website rebuild that could showcase their portfolio across multiple studios while capturing commercial search visibility for high-intent B2B queries. The previous site had minimal organic presence on the service and location terms that drive new business enquiries.

Our Approach

We deployed our AI-assisted development workflow using the Webgentic platform to compress the typical two-month delivery into three weeks without compromising on commercial focus or technical quality. Every commercial service page was structured with SEO alignment built in from day one, not retrofitted later.

The site architecture prioritised the terms prospective clients actually search when evaluating development partners: studio location queries, specialist service categories, platform capabilities, and co-development expertise. Content was written to match commercial intent, not to fill pages.

Delivery

The new site launched with:

• Complete service page structure covering game porting, full development, mobile development, and co-development capabilities
• Location-optimised content for studio queries across UK markets
• Clean, modern design built on Divi with responsive layouts across all devices
• High-quality game portfolio integration showcasing work with major franchises

Development time was cut in half through AI-assisted code generation, automated responsive design implementation, and streamlined content workflows, with no loss of customisation or technical precision.

Results: First 30 Days

The site began generating commercial visibility immediately, with measurable traction across the exact terms that matter to Sumo's new business pipeline.

New commercial visibility created from scratch

Over 65% of the terms now generating clicks had zero presence in the previous period. The site appears in search results for queries it simply did not exist for before, spanning game development services, studio locations, and specialist technical capabilities.

Position gains on studio and service terms

Location-based studio queries, among the highest-intent terms for clients researching development partners, improved by up to 87% in average position within 30 days. Broader UK studio and game development company terms improved between 20% and 33% in position, moving the site measurably closer to page one territory.

Strong CTR performance on new terms

Where the site now appears for relevant queries, click-through rates are converting well. Several terms are achieving CTRs between 25% and 100%, indicating the page structures, titles, and meta descriptions align with what prospective clients expect to find.

Commercial service impressions built from zero

Across game porting, full game development, mobile development, and co-development query clusters, the site generated meaningful impression volumes on terms with no prior presence. These positions are within reach of page one rankings with continued authority building, and the 30-day trajectory sits ahead of where a typical new site would perform at this stage.

What This Demonstrates

Webgentic's AI-assisted development approach doesn't just compress timelines. It ensures SEO strategy is embedded in site architecture from the first line of code, not added as an afterthought. The result is faster delivery with stronger commercial foundations.

For B2B sites where organic visibility directly feeds the sales pipeline, this matters. Sumo Digital's new site is appearing for the right terms, improving position on high-intent queries, and converting clicks where it ranks, all within the first month post-launch.

The post Sumo Digital: Premier Game Development Studio Site Delivered in Half Standard Timeline appeared first on EXPRE.

The market in 2026 looks very different from two years ago. Drupal has relaunched itself as an AI-first platform. WordPress 7.0 is shipping real-time collaborative editing. A generation of headless CMS products are genuinely production-ready. Several platforms that have appeared on "best CMS" lists for a decade are now effectively abandoned. This guide covers what actually matters: which platforms are worth evaluating, which are past their prime, and how to make the decision that fits your business.

• Overview
• PHP CMS platforms
• .NET CMS platforms
• Headless CMS platforms
• AI-powered CMS and site builders
• Reference: 50+ CMS platforms
• PHP vs .NET
• Open-source vs commercial licence
• Self-hosted vs SaaS
• Top 5 by market share
• CMS evaluation matrix
• How to choose

The 2026 CMS Overview

Three things define the market right now.

AI is being built into the platforms, not as an add-on. WordPress, Drupal, Webflow, and even Wix have all shipped substantive AI capabilities in the past 12 months, and not as premium add-ons. Drupal CMS 2.0 (January 2026) lets non-technical editors generate landing pages from a text prompt. WordPress 7.0 is bringing AI-assisted editing into core. The question is no longer whether a CMS has AI, but where it fits into the actual content workflow. For us it's also about how to ensure the AI in the CMS knows the brand, goals, tone of voice, visual styles and consistency.

Headless architecture is now a product category, not a pattern. Sanity, Storyblok, Contentful, and Directus have all matured to the point where marketing teams, not only developers, can manage content. For organisations publishing across multiple channels, a headless CMS with a polished visual editor is a practical option in 2026.

Legacy platforms are becoming less of a problem for some, but not all. A significant number of CMS platforms that appear on popular comparison lists are effectively dead. Bolt CMS lost its sole maintainer when its lead developer passed away in 2024. PHP-Nuke, Nibbleblog, Wolf CMS, N2 CMS, and BetterCMS have received no meaningful development in years. Running these in production is a security liability, not a cost saving. However, AI-assisted replatforming processes do help if you know how.

PHP CMS platforms

PHP powers the majority of CMS installations worldwide. The ecosystem is mature, hosting is cheap, and the talent pool is the largest of any web stack.

WordPress

WordPress runs 42.6% of all websites and approximately 60.7% of all CMS-powered sites. That market position has no parallel in software history. The figure has come down marginally from its 2022 peak of around 65% as Shopify, Wix, and Squarespace have grown, but WordPress remains in a category of its own.

WordPress 6.9 "Gene" (December 2025) introduced block-level Notes for editorial collaboration, the Interactivity API, and measurable performance improvements. WordPress 7.0, expected in the first half of 2026, is the more significant release: real-time multi-user collaborative editing (Gutenberg Phase 3), the WP AI Client moving into core, and a Workflows API for AI-assisted content actions.

The 2025 release schedule was reduced from three to two major versions because the Automattic/WP Engine dispute reduced contributor capacity. Automattic has since formed a dedicated AI team and the 2026 roadmap is back on track.

Suited to: marketing websites, blogs, WooCommerce e-commerce, organisations that need a large developer and plugin ecosystem, and teams without specialist developers.

WordPress frontend editors and page builders

WordPress ships with the native Gutenberg block editor, which is capable and improving rapidly. WordPress 7.0 adds real-time collaborative editing to Gutenberg as part of Phase 3. For teams that want a more visual, drag-and-drop experience, several frontend editors sit on top of WordPress and are worth knowing:

• Divi (Elegant Themes): one of the most widely used visual page builders, with a front-end editor that lets non-technical users design and edit pages directly on the live site. Divi includes a large library of pre-built layouts, a theme framework, and module-level controls for responsive behaviour. It is the builder EXPRE uses across our own client projects.
• Elementor: the most installed third-party page builder in the WordPress ecosystem, with over 12 million active sites. The free tier is functional; Elementor Pro adds dynamic content, popups, forms, and WooCommerce builder. Elementor introduced AI content and image generation in 2024, and its Agentic AI for automated site maintenance shipped in 2025.
• Beaver Builder: favoured by developers and agencies for clean code output, predictable rendering, and a stable, low-overhead architecture. Less feature-dense than Divi or Elementor, which makes it faster and easier to maintain. A strong choice for client sites where long-term maintainability matters more than design flexibility.
• Bricks Builder: a newer entrant that has built a strong following among developers. Outputs clean, semantic HTML with no shortcode lock-in. Performance-focused with native dynamic data and custom query support. Increasingly the builder of choice for developers building bespoke WordPress themes.
• WPBakery: one of the oldest page builders and still bundled with a large number of premium themes. Functional but dated in its approach compared to newer builders. Sites built on WPBakery can be difficult to migrate away from due to shortcode dependency.

The choice of page builder affects your site's performance, long-term maintainability, and the independence of your content team. Builders that store content in shortcodes (WPBakery, older Divi versions) create dependency on the plugin being active. Builders that write clean HTML to the post content (Bricks, Beaver Builder in most configurations) are easier to move if you ever change builder.

Drupal

Drupal's overall market share has declined from 6.1% in 2011 to approximately 1.2% today. That figure understates its relevance. Among the top 10,000 websites globally by traffic, Drupal holds 8.2% market share. Governments, universities, major media organisations, and regulated enterprises disproportionately run it.

Drupal CMS 1.0 (January 2025, formerly "Starshot") was the most significant repositioning in the platform's history: non-technical user focus, AI-powered content creation, a Recipes system with roughly 30 pre-configured packages, and an improved installer. Drupal CMS 2.0 (January 2026) added the Canvas visual page builder, an AI assistant for landing page generation, an admin chatbot, and site templates including the "Byte" template for SaaS and marketing sites. Drupal 10 reaches end of life in December 2026.

Suited to: enterprise, government, higher education, multisite deployments, complex content workflows, and organisations that need multilingual and compliance capabilities built in from the start.

For teams that want a visual frontend editing experience on Drupal, DXPR Builder is the most established option: a drag-and-drop page builder for Drupal that gives content editors a live editing interface comparable to Divi or Elementor on WordPress. Drupal CMS 2.0 also ships with Canvas, its own native visual page builder with live preview, which is becoming the default editing experience for new Drupal installations.

Other notable PHP CMS platforms

• Craft CMS : developer-preferred, highly flexible content modelling, strong API. Popular among UK agencies building bespoke marketing sites. A commercial licence is required for certain features.
• SilverStripe : well-regarded in the UK, Australia, and New Zealand. Clean MVC architecture, solid security record, used by several UK public sector organisations.
• TYPO3 : enterprise-grade PHP CMS, dominant in German-speaking European markets. Strong multisite, multilingual, and compliance capabilities. Rarely chosen for new UK projects, but worth knowing if you work with European partners.
• Joomla : 2.1% CMS market share, actively maintained but declining. Multilingual by default, reasonable plugin ecosystem. A sensible choice only when extending an existing Joomla installation.
• October CMS : built on Laravel, developer-centric, growing community. Fits PHP teams already working in the Laravel ecosystem.
• ProcessWire : a flat-file option with a devoted following. Exceptionally flexible content field system. Niche, but genuinely excellent for structured content projects with specific data requirements.

.NET CMS platforms

.NET CMS platforms suit organisations already running on Microsoft infrastructure: Azure, SQL Server, Dynamics 365, Active Directory. They tend to offer more structured long-term support windows and predictable upgrade paths than their PHP counterparts.

• Umbraco : the dominant open-source .NET CMS. Version 15 is the current release (2025/2026), with LTS tracks, active block editor development, and a maturing headless Delivery API. Free to download; commercial support and hosting are available through certified partners. The most consistently recommended .NET CMS for UK development projects.
• Optimizely (formerly Episerver) : enterprise DXP combining CMS, commerce, and personalisation. Significant licence and implementation cost. Most appropriate for large organisations with dedicated development teams and complex personalisation requirements.
• Kentico Xperience : mid-market to enterprise. Combines CMS, digital marketing tooling, and e-commerce. Solid Microsoft ecosystem integration across the stack.
• Orchard Core : modular, open-source, ASP.NET Core. Good developer experience and a growing community. A reasonable Umbraco alternative for teams that want something lighter and more modular.
• Sitefinity (Progress) : mid-market DXP with strong marketing features and a cloud hosting option. Positioned between Umbraco and Optimizely in capability and cost.
• Ibexa DXP : the commercial successor to eZ Platform, not to be confused with the legacy eZ Publish codebase. A funded enterprise platform used by major European businesses, with AI features, headless delivery, and multisite management. Strong in regulated industries.

Tip: align your CMS version to a supported .NET runtime. Microsoft publishes clear .NET end-of-life timelines, and a CMS built on an unsupported runtime version will force an unplanned upgrade cycle.

Headless CMS platforms

A headless CMS separates content management from content presentation. Editors work in the CMS; developers query it via API and render content wherever it needs to appear: website, app, digital signage, in-product documentation. The headless CMS market is growing at roughly 25% compound annual growth and was valued at over $1.6 billion in 2024.

• Sanity : the strongest growth story in the CMS market. Exceeded $40 million ARR in 2024, raised $85 million, and now serves 30,000 organisations including Nordstrom, Expedia, and Elastic. Real-time collaborative editing, GROQ query language, and structured portable text make it the developer's choice for complex content systems. Consistently rates number one or two on G2 for headless CMS.
• Contentful : dominant enterprise headless CMS with $175 million in funding. Strong governed collaboration, multi-brand, and multi-region content operations. Suited to large enterprise content teams with complex approval workflows.
• Storyblok : occupies the mid-market well. Visual component-based editing is a genuine differentiator: marketing editors can change layout without developer involvement. Strong for DTC brands and marketing-heavy organisations.
• Directus : 100% open-source, database-first headless CMS. Wraps any existing SQL database in a content API without requiring data migration to a proprietary structure. No vendor lock-in. Strong traction in industrial, medical, and data-heavy sectors.
• Strapi : open-source headless CMS with a large developer community. Self-hostable, flexible content types, REST and GraphQL. Good for developer-led projects that need full control over the data model without a commercial licence.
• Payload CMS 3.0 : worth watching. The first CMS to install directly into a Next.js app folder with no separate service. Down to 27 dependencies from 88, stable PostgreSQL support, Lexical editor, and $5.2 million raised from Y Combinator and Gradient Ventures. Early-adopter territory, but architecturally compelling for teams building on Next.js.
• Ghost : technically headless-capable but primarily a publishing and membership platform, competing with Substack and Beehiiv rather than with WordPress. Ghost 6.0 (August 2025) introduced native ActivityPub syndication across the decentralised social web. Non-profit foundation model, approximately 18,000 Ghost Pro licensees generating over £20 million annually. Not a general-purpose CMS.

AI-powered CMS and site builders

This category splits into two types that serve different purposes.

AI site builders (SaaS, prompt-to-site)

These platforms generate websites from natural language prompts. They matured considerably in 2025 and are viable for SME marketing sites, landing pages, and rapid prototyping. Webgentic.ai, our own platform, goes further than pure prompt-to-site: it combines AI-powered editing with analytics-driven optimisation and continuous site improvement, built on WordPress.

Visual and AI-assisted development tools

These are not traditional CMS platforms. They are visual layers that connect to existing content sources or codebases, reducing the developer involvement required to move a design into production.

• Builder.io : AI-powered headless CMS and visual editor. Drag-and-drop across React, Vue, and Angular, with structured content and API delivery. Includes design-to-code conversion. Good for enterprise teams that need marketing autonomy without breaking the design system.
• Webflow (full platform) : sits at the intersection of site builder, CMS, and hosting. Its AI features, AI Site Builder, App Gen, and AI Assistant, position it for teams that want design, code, and content in one environment. $213 million ARR in 2024, up 66% year-on-year.
• Plasmic : a visual builder that works on top of existing headless CMS back ends. Not a standalone CMS; it reduces the development overhead for translating designs into published pages.

The distinction that matters: pure prompt-to-site tools, the kind that generate a site once and step back, are not built for ongoing SEO work, complex integrations, or teams iterating on performance. That limitation is specific to that category of tool, not to AI-assisted web management as a whole. Webgentic.ai sits in a different category: it uses AI for continuous editing, connects to analytics to identify what to improve and why, and runs on WordPress so every integration, plugin, and technical SEO capability is available from day one. The question for most businesses in 2026 is not whether to use AI in their web stack, but which approach keeps improving the site after it goes live.

Pricing note: SaaS pricing changes frequently. Check vendor websites for current rates before budgeting.

Reference: 50+ CMS platforms

The lists below include active, maintained platforms. We have excluded platforms with no meaningful development activity: PHP-Nuke, Bolt CMS, Nibbleblog, N2 CMS, BetterCMS, Wolf CMS, Redaxscript, Bigace, sNews, and Grav. Running abandoned software in production is a security risk.

PHP CMS platforms:

1. WordPress
2. Drupal
3. Craft CMS
4. MODX
5. SilverStripe
6. Pimcore
7. TYPO3
8. Joomla
9. Concrete CMS
10. PrestaShop
11. Magento (Adobe Commerce)
12. WooCommerce
13. OpenCart
14. ExpressionEngine
15. October CMS
16. Contao
17. Ibexa DXP
18. ProcessWire
19. Bludit
20. Microweber
21. Tiki Wiki CMS
22. PyroCMS
23. Neos CMS
24. ButterCMS
25. Strapi
26. Contentful
27. Sanity
28. Hygraph
29. Storyblok
30. Directus
31. Payload CMS
32. Ghost
33. Builder.io
34. Kontent.ai
35. Prismic
36. CMS Made Simple
37. Zenario

Note on Webflow: Webflow (1.2% CMS market share, $213 million ARR) sits at the intersection of site builder, CMS, and hosting. Its growing enterprise feature set and AI Site Builder make it a legitimate shortlist candidate for design-led agencies and marketing teams in 2026.

.NET CMS platforms:

1. Umbraco
2. Kentico Xperience
3. DNN (DotNetNuke)
4. Orchard Core
5. Sitefinity
6. Piranha CMS
7. Raytha
8. Oqtane
9. nopCommerce
10. Optimizely (Episerver)
11. MojoPortal
12. Ibexa DXP

PHP vs .NET

The choice between PHP and .NET is rarely purely technical. It depends on your existing team skills, infrastructure, and long-term support expectations.

Why PHP suits most projects

WordPress alone powers 42.6% of the web. The number of PHP developers, plugins, and community resources available dwarfs every other web stack. For most marketing sites this translates to faster delivery and lower agency rates. The open-source platforms, WordPress, Drupal, and Joomla, are free to licence; shared hosting starts under £5 per month; and the developer talent pool is large enough that contractor rates remain competitive.

For a marketing site, landing page, or WooCommerce store, a PHP CMS can be live in days. A .NET implementation with equivalent scope typically takes longer to stand up, and the senior .NET developer rates in the UK are higher.

Where .NET has the advantage

If your organisation already runs on Azure, SQL Server, Dynamics 365, or Active Directory, a .NET CMS such as Umbraco integrates natively. Forcing WordPress to talk to your AD-authenticated internal systems adds friction and ongoing maintenance overhead that .NET simply avoids.

.NET's type safety and Visual Studio tooling also make it easier to manage large applications where multiple development teams are working simultaneously on the same codebase. And Microsoft publishes clear runtime EOL dates years in advance, so enterprise buyers can plan upgrade cycles without surprises.

The deciding factor

Who are your developers, and what infrastructure do you already run? If your team is PHP developers working on a LAMP stack with no Microsoft estate, .NET adds cost without benefit. If your team is C# developers working inside Azure, WordPress adds friction and security overhead. The right CMS is the one your team can maintain confidently for three to five years without becoming dependent on external support for routine tasks.

Open-source vs commercial licence

The open-source case

No licence fee is the obvious starting point, but the real advantage is ecosystem depth. WordPress has 59,000-plus plugins; Drupal has 50,000-plus modules. The vast majority of functionality any project needs already exists and is maintained by a global community. You are never dependent on a single vendor's roadmap decisions or pricing changes, and migrating to a different host or agency requires no vendor permission.

The trade-off is that security and maintenance fall to you. Unpatched WordPress installations are one of the most consistently exploited entry points for web attacks. This is entirely preventable with a good maintenance programme, but "free software" does not mean zero ongoing cost.

The commercial licence case

Commercial CMS platforms justify their cost with SLAs, dedicated support, compliance documentation, and managed upgrade cycles. For regulated industries, financial services, healthcare, and legal, the contractual accountability that comes with a commercial licence often makes budget sign-off easier than pitching community-supported software. Audit logs, GDPR tooling, role-based access, and multi-factor authentication are also more consistently implemented across commercial platforms than across the long tail of community plugins.

Practical guidance: for SMEs and most marketing sites, open-source delivers better value. For enterprise deployments with strict compliance requirements or 24/7 operational SLAs, a commercial platform's support structure often justifies the cost over three years.

Self-hosted vs SaaS

The clearer framing is control versus convenience.

For businesses where publishing speed is the priority and technical capacity is limited, SaaS removes genuine friction. For organisations that need custom integrations, full data portability, specific compliance controls, or unlimited technical flexibility, self-hosted is the only viable path. Most growing businesses start on SaaS and re-platform to self-hosted when they outgrow the constraints.

Top 5 CMS platforms by market share

Based on W3Techs data, March 2026:

1. WordPress, 42.6% of all websites, approximately 60.7% of CMS-powered sites
   The default starting point for marketing sites, blogs, and e-commerce via WooCommerce. Unmatched plugin ecosystem and global developer availability. WordPress 7.0 (expected H1 2026) adds real-time collaborative editing and native AI assistance. If you have no specific reason to choose otherwise, this is where to begin.
2. Shopify, approximately 6.8% of CMS market
   Not a general-purpose CMS, but the dominant platform for standalone e-commerce. Its content management capabilities have matured considerably. The right choice if your primary requirement is a commerce platform that also handles content.
3. Wix, approximately 5.7% of CMS market (up 32.6% year-on-year)
   The fastest-growing major platform, driven by AI-first positioning across Wix ADI and Wix Studio. Genuinely capable for SME marketing sites. Not suited to complex integrations or technical SEO strategies that require server-level control.
4. Squarespace, approximately 3.4% of CMS market
   Design-led SaaS platform with Blueprint AI for section-by-section site generation. Popular with creative professionals and small businesses. Growing steadily, though bounded by its closed architecture.
5. Drupal, approximately 1.2% of CMS market (8.2% among the top 10,000 sites by traffic)
   The market share figure understates Drupal's influence: it disproportionately powers high-traffic, high-complexity sites. Drupal CMS 2.0 (January 2026) is the most significant strategic pivot in the platform's history, an AI-assisted, template-driven rebuild aimed at reversing a decade of market share decline. Worth watching closely in 2026.

Notable outside the top five: Joomla (2.1%) is in steady decline but still has millions of active installations. Webflow (1.2%) is growing at 10% compound annual growth with $213 million ARR; its commercial momentum significantly outpaces its website count, which indicates strong average revenue per customer.

CMS evaluation matrix

Rather than a subjective ranking, a scoring matrix makes your prioritisation explicit. The example below uses a D365 integration scenario: a project where Microsoft ecosystem integration is a primary requirement. Adjust the column weights to reflect what actually matters for your project.

WordPress wins on talent pool and licence cost but ranks lowest on native D365 integration. If your integration requirement carries a higher weight, say 30% of the total score, Umbraco or Sitecore may pull ahead. That is exactly the value of the exercise: it replaces vendor preference with your actual criteria.

How to choose the right CMS

Most failed CMS projects fail not because the platform was wrong, but because the decision was made on feature comparisons rather than on how the team will actually operate the site day-to-day.

Start with your team, not the technology

The right CMS is the one your team can manage without depending on an agency for every content change. A non-technical marketing team needs a platform where editors can publish, update, and experiment independently. A PHP-competent development team does not need a .NET CMS. Match the platform to the people who will run it.

Map your integrations before shortlisting

CRM, ERP, marketing automation, e-commerce checkout, analytics: list every system the CMS needs to talk to before choosing a platform. A CMS that requires a custom connector for your core business system will cost more to maintain than one with a native integration. This single factor tends to eliminate more options than any feature comparison.

Calculate three-year total cost of ownership

Licence fee is only the beginning. Factor in: hosting, development time, plugin and extension costs, security and maintenance, agency or contractor day rates (which vary considerably by platform), and the likely cost of a future migration if you outgrow it. Free open-source software can cost more over three years than a commercial SaaS platform if your team lacks the technical depth to maintain it.

Test the editorial workflow before committing

Every major platform has a trial or sandbox environment. Run your actual content team through a realistic day of work before signing off on a platform: creating a page, editing a blog post, updating a product, uploading an image, checking the mobile preview. The best CMS is the one editors will use confidently without emailing a developer.

Match the architecture to your roadmap

If you plan to add a mobile app, customer portal, or partner-facing content within 18 months, a headless or API-first CMS avoids a painful re-platform later. If you are building a marketing website and nothing else for the foreseeable future, a traditional coupled CMS is faster and cheaper. Solve the problem you have now; architect for what you can see clearly on the horizon.

The post Which is the Best CMS for 2026? PHP, .NET and AI Platforms Compared appeared first on EXPRE.