WordPress development

WordPress Development Company in India

B9 Solution designs and develops WordPress websites for businesses that need a site they can use, update and extend. We build around how your team publishes, how customers enquire or buy, and the tools the site has to connect to.

That covers new WordPress websites, theme and plugin customization, content management set-up, integrations, migration from an older site and technical improvements to a site you already run.

Every WordPress project is scoped to your requirements. There are no fixed packages.

  • Design & development
  • Customization
  • CMS functionality
  • Integrations
  • Migration
  • Technical improvements
Illustration: a sample site and its WordPress editor, drawn for this page. It is not a client project.

Reviews, Certifications & Partnerships

Why WordPress

Why WordPress? What Can You Build With It?

WordPress is a content management system: the part of a website where your team writes, structures and publishes content. That makes it a good fit when content is what the site is for, and a poorer fit when the site is mostly an application. Here is what it handles well for eight kinds of site, what to plan for, and where we would suggest something else.

  • Business websites

    WordPress handles well

    A handful of well-structured pages (home, about, services, contact) with menus, forms and a news area your team edits itself. Pages, menus and media are the core of what WordPress does.

    Plan for

    Decide early which content repeats, such as team profiles or services, so it becomes reusable fields and patterns instead of one-off pages that drift apart.

    • Pages and menus
    • Forms
    • News or blog
  • Service websites

    WordPress handles well

    One page per service and per area served, a quote or enquiry form, and a clear path from search to contact. Page templates keep every service page consistent.

    Plan for

    Every service page needs its own useful content. Copying one template across dozens of near-identical pages helps neither visitors nor search.

    • Service templates
    • Enquiry form
    • Service areas
  • Corporate websites

    WordPress handles well

    Leadership, divisions, news and stakeholder information, with several editors holding different permissions. User roles and review steps let the right people publish the right things.

    Plan for

    Governance matters more than layout: who approves, who publishes and how old content is retired. A larger site needs a content model and an owner for it.

    • User roles
    • Team profiles
    • News and insights
  • Editorial sites and blogs

    WordPress handles well

    Articles, categories, authors, featured images and scheduled publishing are what WordPress began with. Contributors can submit work for review and editors publish it.

    Plan for

    Archives grow. Plan categories, internal linking and page speed for an archive of hundreds of articles, not for the first dozen.

    • Categories and authors
    • Scheduling
    • Review workflow
  • Booking-based websites

    WordPress handles well

    Services, availability and time slots handled by a booking plugin, with confirmation emails and calendar sync where the plugin supports them. The rest of the site stays as editable as any other.

    Plan for

    Booking rules are business logic: durations, buffers, staff schedules, cancellations. Agree them first, test them with real scenarios, and check the plugin fits your payment and reminder needs.

    • Booking plugin
    • Availability rules
    • Reminders
  • Membership and gated content

    WordPress handles well

    Roles and access rules decide who sees what: a resource library, members-only articles, a course area. A membership plugin or custom code manages log-in and access.

    Plan for

    Gated content raises questions about privacy, password resets, payments and what search engines may see. Settle them before building.

    • Roles and access
    • Log-in
    • Gated content
  • Product catalogs

    WordPress handles well

    Products, specifications and downloads as custom post types, with filters and an enquiry or quote form instead of a checkout. Useful when you sell through conversations rather than carts.

    Plan for

    A catalogue is only as good as its data. Decide where product information lives (a spreadsheet, another system or WordPress) and who keeps it current.

    • Custom post types
    • Filters
    • Quote form
  • Online stores with WooCommerce

    WordPress handles well

    Products, variations, cart, checkout, payments and orders inside the same site as your content, so editorial and commerce share one admin and one design.

    Plan for

    A store adds payment, tax, shipping and stock to the list of ongoing tasks. The WooCommerce section below explains what that involves.

    • WooCommerce
    • Variations
    • Checkout
    See the WooCommerce section
Illustrations of kinds of WordPress site, drawn for this page. They are not client projects.

When WordPress is a strong fit

  • Content is the point of the site: pages, articles, resources, case material.
  • Several people publish, and you want them to do it without a developer.
  • You want to start with what the core provides and extend it with plugins or custom code as needs grow.
  • Search visibility matters and you want control over URLs, headings, templates and structured content.
  • You may later add selling, booking or a members area to the same site.

When another approach may fit better

B9’s developers work with PHP and Laravel, Node.js and React as well as WordPress, so the recommendation follows the project, not the platform.

  • A web application where the logic is the product

    Portals, dashboards, calculators and real-time tools. WordPress can host parts of this, but you end up bending a content system around a workflow.

    Often better: A purpose-built application, for example in Laravel, Node.js or React

  • A simple store with standard needs

    A modest catalogue, an ordinary checkout, and you would rather the platform handle hosting, checkout and security for you.

    Often better: A hosted store platform (B9 also builds on Shopify)

  • A very large multi-vendor marketplace

    Many sellers, commissions, disputes and heavy order volume carry more risk on a general-purpose CMS than on a platform built for it.

    Often better: A purpose-built marketplace platform, or a custom build

  • A small brochure site that rarely changes

    A few pages updated once or twice a year do not need a content system to keep patched and secure.

    Often better: A simpler, mostly static site, with less to update

  • Strict workflow or compliance systems

    Approvals, audit trails or regulated data usually belong in a dedicated system with its own controls.

    Often better: A dedicated system, with WordPress as the public site in front of it

We recommend the platform after scoping and explain why, including when the answer is not WordPress. Describe what you are building and we will tell you what we would use.

Discuss My WordPress Project

Services

Our WordPress Development Services

A WordPress website is a stack of decisions: how pages are built, how the editor works, which features come from plugins and which are written for you, how the site connects to other tools, and who keeps it running afterwards. These eleven services cover that stack, grouped by the part of the site they change.

Build

Build the site

The theme, the editing experience and the page-building approach, chosen to fit the team that will use it.

A website planned from your pages, content types and workflows, rather than a template with your logo on it. The structure, the design and the editing experience are decided together.

What this involves
  • Mapping your page types and the content your team will add and change, so the editor is built around them
  • A design system of reusable layouts and components, not one-off pages that drift apart
  • Content structure that suits WordPress: pages, posts and, where the content needs it, custom post types and fields
  • Search-friendly structure from the start: URLs, headings, internal links and templates for the pages you want to be found
Best when

You are launching a new site, or your current one no longer matches how the business works and a restyle will not fix it.

You decide
  • Which page types and content you need, and who maintains them
  • How much is built custom and how much reuses existing components

A theme is the layer that controls layout, styling and templates. We build a new one, or customize a theme you already own, so the site matches your brand and stays maintainable.

What this involves
  • Choosing between a bespoke theme, a child theme of an existing one and a lightly customized theme, and explaining what each costs you later
  • Templates for each page type, with typography, spacing, colour and responsive behaviour set once and reused
  • Keeping customizations separate from the parent theme, so a theme update does not erase them
  • Accessibility and performance basics built into the templates rather than added at the end
Best when

Your brand needs more than a theme options panel can give, or an existing theme has been edited so heavily that updating it is risky.

You decide
  • Custom theme, child theme or customized theme
  • Who owns the theme and any paid licence it needs

Extend

Extend what it can do

Functionality beyond the core: a plugin you already have, one that needs changing, or one written for you; and selling online.

WooCommerce turns a WordPress site into an online store. We plan the catalogue, checkout and order handling around how you actually sell, then build and test it.

What this involves
  • Product types, variations and categories structured so shoppers can find and compare
  • Cart, checkout, payment methods, shipping rules and tax set up for the markets you sell in
  • The order and stock workflow your team will use every day, tested before launch
  • A review of the extensions you need, because each one affects speed and the cost of updates
Best when

You want one platform for content and commerce, or a store with rules a hosted store platform makes awkward.

You decide
  • Which payment, shipping and tax options to support
  • Which extensions are worth their upkeep

Renew

Rebuild or move a site

Starting again on WordPress, or carrying an existing site across without losing what already works.

An older WordPress site can often be redesigned rather than replaced. We look at what is worth keeping, rebuild what is not, and plan the change so search visibility is protected.

What this involves
  • Reviewing the current theme, plugins, content and traffic to decide what to keep, rebuild or retire
  • A new design and templates on a cleaner foundation, with content moved across deliberately
  • Listing the URLs that matter and keeping or redirecting them, so existing links and search visibility are not thrown away
  • Removing plugins and code the site no longer needs
Best when

The site looks dated, is slow to edit, depends on abandoned plugins or has outgrown the structure it was built with.

You decide
  • What to keep, rebuild or retire
  • Whether the redesign includes new content and structure

Moving a site to WordPress, or from one WordPress host to another, is mostly planning. We protect the pages that earn traffic, test on a staging copy and check after launch.

What this involves
  • An inventory of content, URLs and functionality before anything moves
  • A staging copy to build and test on, so the live site is not touched until the new one is ready
  • A map from every old URL to its new home, with redirects where addresses change
  • Launch checks and a review of search and analytics afterwards, because problems show up after the move
Best when

You are leaving another platform, changing host or domain, or consolidating several sites into one.

You decide
  • Which content is carried over and which is rewritten
  • When the switch happens and who signs it off

Run

Connect and keep it running

The links to your other systems, the speed of the site, and what happens after launch.

A website rarely works alone. We connect WordPress to the systems around it so enquiries, orders and data arrive where your team works, without copying them by hand.

What this involves
  • Forms and lead capture that pass enquiries to the place your team actually works
  • Connections through REST APIs and webhooks, and clear handling of what happens when an external service is down
  • Analytics and tag set-up where appropriate, such as Google Analytics 4 and Google Tag Manager
  • Data that moves one way or both ways, with a clear rule for which system is the source of truth
Best when

Your team re-types website data into another system, or a process depends on information the site does not yet pass on.

You decide
  • Which systems connect and in which direction data flows
  • What the site does when a connected service is unavailable

Speed comes from many small decisions: how images are served, what loads on each page, how the site is hosted and which plugins it depends on. We find what is slowing a site down and fix the causes.

What this involves
  • Measuring before changing anything, with lab tests and, where it exists, real-visitor data
  • Image handling, caching, and the scripts and styles that load on each page
  • Plugin and theme weight: what each one costs and whether it is worth keeping
  • Hosting fit: whether the server is part of the problem, and what to ask your host
Best when

Pages feel slow, Core Web Vitals reports flag problems, or the site was built with more plugins and effects than it needs.

You decide
  • Which changes are worth their trade-offs
  • Whether hosting needs to change

After launch a WordPress site still needs updating, backing up and watching. Ongoing maintenance is available as a separately scoped agreement, agreed per engagement.

What this involves
  • WordPress core, theme and plugin updates, checked for compatibility before they reach the live site
  • Fixes and small changes as they come up, and technical support when something breaks
  • Backups, and a restore that has been tested rather than assumed
  • Improvements over time, planned with you rather than left to accumulate
Best when

You want a developer to look after the technical side while your team looks after the content.

You decide
  • What the agreement covers and how it is reviewed
  • Who holds the hosting account and the licences

Not sure which of these your project needs? Describe it and we will tell you what we would scope, and why.

Discuss My WordPress Project

Technologies and tools

Our WordPress Development Technologies & Tools

The tools below are the ones B9’s developers work with. A project does not use every one: specific plugins and hosting are chosen per project, to suit the site and the host. A tile marked Practice describes how a category of work is handled, not a product.

Core

What every WordPress site is built on: the platform, the languages and the database.

  • Technology

    WordPress

    The content management system itself: pages, posts, media, users and the admin area your team works in.

  • Technology

    PHP

    The language WordPress is written in. Custom themes, plugins and integrations are PHP code.

  • Technology

    HTML5

    The markup behind every page: headings, landmarks and forms that browsers, search engines and assistive technology read.

  • Technology

    CSS3

    Layout, typography and responsive behaviour, written once in the theme so every page inherits it.

  • Technology

    JavaScript

    Behaviour in the browser, from menus and forms to custom blocks, kept to what each page actually needs.

  • Technology

    jQuery

    A long-standing script library that many existing themes and plugins still depend on; relevant when working on an older WordPress site.

  • Technology

    MySQL

    The database where WordPress stores content, settings and users. Its structure affects speed as a site grows.

  • Technology

    REST API

    WordPress’s built-in way to send and receive data as JSON, used to connect the site to other systems and to power dynamic parts of a page.

  • Choices at this level, such as a custom theme, a child theme or a builder, are made per project, not by default.

Editors and builders

How your team lays out and edits pages.

  • Technology

    WordPress block editor

    The editor most WordPress content is written in. Patterns and block settings let a team build consistent pages without code.

  • Block editor or page builder is decided per project: by who edits, how often, and how much layout freedom they need.

Ecommerce

What lets a WordPress site sell.

  • Technology

    WooCommerce

    The store plugin: products, variations, cart, checkout, orders and stock inside a WordPress site.

  • Every extension added to a store is another thing to update and another thing that can clash, so extensions are chosen sparingly.

Performance

How pages stay light as the site and its content grow.

  • Practice

    Caching layer

    Ready-made copies of pages so the server does less work per visit, set up to suit the host and the parts of the site that must stay dynamic.

  • Practice

    Image optimisation

    Sensible sizes and modern formats, lazy loading, and dimensions set in advance so pages load lighter and do not jump.

  • Practice

    Script and style loading

    Loading only the scripts and styles each page needs, instead of everything on every page.

SEO and analytics

How the site is found and how its use is measured.

  • Technology

    Google Analytics 4

    Measures how visitors use the site and which pages lead to enquiries or orders, set up where appropriate.

  • Technology

    Google Tag Manager

    Manages tracking tags in one place, so measurement changes do not need a code change each time, where appropriate.

  • Measurement is set up where it is appropriate to the project, not by default.

Security and maintenance

How the site stays updated, controlled and recoverable.

  • Practice

    Core, theme and plugin updates

    Core, theme and plugin updates, checked for compatibility before they reach the live site, where an update arrangement applies.

  • Hosting, premium licences and maintenance are agreed per engagement. They are not included in every project.

Logos are trademarks of their respective owners and identify the technology only. They do not indicate a partnership, certification or endorsement.

WooCommerce

WooCommerce Development for Online Stores

WooCommerce is the store plugin for WordPress. It suits businesses that want products, content and orders in one site and one admin, and stores whose rules (variations, shipping, quoting, memberships) are easier to shape in code than in a hosted platform’s settings.

Illustration of a store’s front and back, drawn for this page. It is not a client store and shows no real products, prices or orders.

What shoppers see and do

Front of shop

  1. Store design and development

    The storefront is a WordPress theme with store templates for the shop, categories, products, cart, checkout and account. They are designed around how your customers shop and stay editable, so merchandising changes do not need a developer.

  2. Product catalogs

    Categories, attributes and filters set up around how buyers compare your products. Simple, variable and grouped products and downloads each have a place, and the structure decides how easy the catalogue is to search and to keep tidy.

  3. Product variations

    Size, colour, material or pack size as variations with their own images, stock and, where needed, their own price. Variation rules are planned before data entry, because changing them later means editing every product.

  4. Cart and checkout

    The cart and checkout are where orders are lost, so they are kept short: guest checkout where it suits, clear delivery and tax lines, and error messages that say what to fix. Fields and steps are chosen for your customers, not left at the default.

  5. Payment integrations

    Payment methods connect through a payment gateway you choose. For customers in India that usually means UPI, cards, net banking and wallets; customers abroad bring their own preferences. Payments, refunds and failed-payment handling are tested before launch.

  6. Shipping options

    Shipping zones, methods and rates that reflect how you actually deliver: flat rates, rates by weight or value, local pickup, and delivery at no charge above a threshold you set. Courier connections are added where an integration exists.

What your team runs

Back of shop

  1. Inventory workflows

    Stock levels, low-stock alerts and what happens when an item sells out: hide it, allow backorders or show a notice. If stock also lives in another system, decide which one is the source of truth before connecting them.

  2. Order management

    Orders move through statuses your team really uses, such as processing, packed, shipped, completed and refunded. Customer and staff emails, refunds and the invoice details your accountant needs, including GST where it applies, are set up to match your process.

  3. Plugin compatibility

    Stores lean on extensions for subscriptions, bookings, labels and reports. Each one touches checkout, so they are checked together, with your theme and with the current WooCommerce version, and the list is kept short.

  4. Store performance

    Product pages, search and checkout are the heavy parts of a store: images, variation scripts, cart fragments and database queries. They are tested on a realistic catalogue, and caching is set so carts and checkout stay correct.

  5. Ongoing management considerations

    A store needs more upkeep than a brochure site: WooCommerce, theme and extension updates, gateway changes, tax and shipping rule changes, and backups of orders as well as pages. Decide who owns each before launch. Maintenance is separately scoped.

Planning a store on WordPress? Tell us what you sell and how orders are handled, and we will say what we would scope.

Discuss My WordPress Project

Plugins and integrations

WordPress Plugins, Custom Features & API Integrations

WordPress does a great deal out of the box. Everything else comes from plugins, custom code and connections to the other systems your business runs on. The useful question is not which plugin to install. It is how much of the job a plugin should be trusted with, who looks after the result, and where your data ends up.

Illustration: WordPress at the centre of the systems around it. A generic architecture drawn for this page, not a specific client’s set-up.

WordPress, at the centre

Content, users, forms and orders live in WordPress. Eight kinds of connection link it to the rest of your business.

  • Content
  • Users
  • Forms
  • Orders

What each connection does, and what you decide

Each link below is a small design decision. The part that matters is the decision on the right: it is what keeps a connection working long after it is first built.

  1. Forms and lead capture

    Connects byA form plugin, or a custom formOut of WordPress

    A visitor fills in a form; the enquiry is stored in WordPress and passed on to the place your team works, so nobody copies it across by hand.

    You decideWhere enquiries land, who is notified, and how spam is stopped without blocking real people.

  2. Booking and scheduling

    Connects byA booking plugin, or a script embedded from a scheduling toolBoth ways

    Availability is shown on the site; confirmed bookings come back to your calendar and records.

    You decideWho confirms a booking, and how double bookings are prevented.

  3. CRM

    Connects byREST API or webhookOut of WordPress

    New leads and customers are created in your CRM with the details your sales team needs and the page they came from.

    You decideWhich fields travel, and what happens to a lead that fails to send.

  4. Analytics and tag management

    Connects byTags and scriptsOut of WordPress

    Page views and key actions are reported to Google Analytics 4 through Google Tag Manager, where appropriate, so you can see what the site is doing.

    You decideWhich actions count as conversions, and what visitors are asked to consent to.

  5. Payment gateways

    Connects byA gateway plugin and the gateway’s APIBoth ways

    Checkout hands the payment to the gateway, and the gateway confirms the result back to WordPress so the order status is correct.

    You decideWhich payment methods you support, and who reconciles payouts against orders.

  6. Email marketing

    Connects byA plugin or the tool’s APIOut of WordPress

    People who agree to hear from you are added to the right list, with the tags your campaigns need.

    You decideWhat consent is recorded, and which system holds the master list.

  7. External APIs

    Connects byREST API (GraphQL where the other service offers it)Both ways

    WordPress reads from or writes to another service: stock levels, a directory, a quoting tool, a payment status.

    You decideHow often to ask, what to store, and what the site shows when the service is unavailable.

  8. Data synchronisation

    Connects byScheduled jobs and webhooksBoth ways

    Records that live in two systems are kept consistent: products, customers, bookings, with a rule for which side wins when they disagree.

    You decideWhich system is the source of truth, and how conflicts are resolved.

Agree three things before anything is connected

  1. Which system is the source of truth

    When two systems hold the same record, one of them has to win. Decide which, and what happens when they disagree.

  2. What happens when a connected service is down

    Forms still need to capture the enquiry and orders still need to be recorded. Decide what the site shows, and where a failed message waits to be retried.

  3. Who owns the keys and the accounts

    API keys, webhook secrets and third-party accounts should belong to your business and be held by a named person, so access can change without anything being rebuilt.

Not sure whether a plugin will do? Describe what you need and we will tell you which rung it sits on, and why.

Discuss My WordPress Project

Migration and redesign

WordPress Website Migration & Redesign

Rebuilding or moving a website is mostly planning. The risky moments are predictable: a page that earned traffic and now has no address, a redirect that points to the wrong place, a staging site that search engines can see, a tracking tag that did not come across. This section is how those moments are handled before they happen.

Two common starting points, and a third

  • Moving to WordPress

    Your site is on another platform: an older CMS, a website builder, or hand-coded pages. The work is getting its content and structure into WordPress without losing what already earns traffic.

  • Rebuilding a WordPress site

    You already have WordPress, but the theme is tired, plugins have piled up or the editor is a struggle. The work is deciding what to keep, rebuilding on a cleaner foundation and holding on to the addresses that matter.

  • Changing host or domain

    The site stays as it is, but where it lives or what it is called changes. The content may not move at all; the addresses and the technical set-up do.

Example redirect map

Old addressNew addressWhat happens
/services-old.html/services/Permanent redirect (301)
/?p=482/blog/choosing-a-theme/Permanent redirect (301)
/about-us-2//about/Permanent redirect (301)
/category/news//news/Permanent redirect (301)
/old-offer/No equivalent pageRemoved on purpose (410), not sent to the home page

Each old address points straight at its final destination, in one step.

Illustration: a generic move from an older site to a new WordPress build, with an example redirect map. Addresses are reserved .example names. Drawn for this page; not a client project.

Twelve checks, in the order they happen

Each check has one job and one reason it matters for search visibility. None of them promises an outcome. They are how a move is planned so that the pages that earn traffic are protected, and how a problem is caught while it is still small.

Before launch

Understand it, then build and test it on a private copy

  1. Evaluate the existing site

    What is doneReview what the site does today: its pages, structure, forms, plugins, theme and hosting, and where the team loses time.

    Why it matters for searchYou cannot protect what you have not looked at. This is where the pages that earn traffic are told apart from the ones nobody visits.

  2. Content inventory

    What is doneList every page, post, media file and document, and decide for each: keep, rewrite, merge or retire.

    Why it matters for searchRetiring a page on purpose is safe. Losing one by accident leaves broken links and a gap where visibility used to be.

  3. Theme and plugin review

    What is doneCheck the theme and every plugin for what it does, whether it is still maintained and whether the new build needs it.

    Why it matters for searchPlugins quietly create addresses, redirects and tags. Knowing what they do stops those disappearing unnoticed.

  4. Staging environment

    What is doneBuild the new site on a private copy, kept out of search results, so the live site is not touched until the new one is ready.

    Why it matters for searchA staging site that search engines can see creates duplicate content. One they cannot see can be tested freely.

  5. Data migration

    What is doneMove content, media, users and settings across, then check that nothing was dropped or reformatted on the way.

    Why it matters for searchHeadings, image descriptions, links and page titles live in the content. If they do not survive the move, neither does what search engines read.

  6. URL mapping

    What is doneMatch every old address to its new home, one by one, including addresses created by old plugins and category pages.

    Why it matters for searchEvery old address that has links or visitors needs a clear destination. The map is the source for the redirects.

  7. 301 redirect planning

    What is donePlan permanent redirects from old to new pages, pointing straight at the final address instead of hopping through several.

    Why it matters for searchRedirect chains and loops slow pages and blur signals. A page with no equivalent should say so, not redirect to the home page, which search engines read as a soft 404.

  8. Internal links

    What is doneUpdate links inside the content and the navigation to the new addresses instead of relying on redirects to catch them.

    Why it matters for searchInternal links tell search engines which pages matter. Linking straight to the final page keeps that signal clear.

  9. Testing

    What is doneTest the staging site on phones and desktops: forms, checkout, search, redirects, templates and the editing experience.

    Why it matters for searchProblems are cheaper to fix before real visitors meet them than after.

At launch

The switch, checked line by line

  1. Launch validation

    What is doneAt the switch, confirm that the site is open to search engines, that canonical tags and the sitemap point to the live addresses, and that a sample of old addresses redirect as planned.

    Why it matters for searchA leftover noindex from staging, or a sitemap listing old addresses, can undo careful work in a single step.

After launch

Carry the data across, then check the live site

  1. Analytics and Search Console continuity

    What is doneCheck that analytics and tag management carry over, that the site is verified in Search Console and that the new sitemap is submitted.

    Why it matters for searchWithout continuity you cannot compare before and after, and you lose the data that shows what needs fixing.

  2. Post-launch verification

    What is doneCrawl the live site, watch Search Console for errors and coverage changes, and check the redirects and the top pages again.

    Why it matters for searchSome issues only show once real visitors and search engines arrive. Checking the live site is how they are found while they are small.

Moving a site, or rebuilding one you already have? Tell us what it runs on today and what is not working.

Discuss My WordPress Project

Technical quality

WordPress Performance, Security & Technical SEO

Speed, safety and findability are not features added at the end. They come from many small decisions in how a WordPress site is built, hosted and looked after. This is what we look at, and why. We do not promise scores, rankings or immunity from attack; we describe the practices and how they are tested.

What happens when a page loads

Core Web Vitals are three measurements of the same moment: a visitor arriving. The picture below is a simplified page load. It shows no scores, because the point is what causes each one.

  • LCPLargest Contentful Paint

    When the biggest thing on screen, usually the hero image or the main headline, has appeared. It is how soon the page feels loaded.

    In WordPress it is often an oversized hero image, a slow server response, or styles that block the first draw.

  • INPInteraction to Next Paint

    How quickly the page responds when someone taps a menu, a button or a field. A busy browser cannot answer yet.

    In WordPress it is often heavy scripts: page-builder widgets, sliders, chat and tracking add-ons.

  • CLSCumulative Layout Shift

    How much the page jumps while it loads, the moment you go to tap something and it moves.

    In WordPress it is often images without set sizes, banners that appear late, and fonts that swap in.

Illustration: a simplified, generic page load. No measurements; drawn for this page.

Performance

What makes a page quick or slow, and what we check first.

  1. Images are sized for where they are shownWe compare each image’s dimensions and format with how large it actually appears, because an oversized image is the most common reason a first screen is slow.
  2. Caching that knows what it must not cacheWe look at how page caching treats logged-in users, carts and forms. Caching that is too eager serves someone the wrong page.
  3. Each plugin has to earn its weightWe look at what loads on every page and why. A plugin used for one form should not load its scripts on every page of the site.
  4. Hosting is part of the pictureWe check whether the server is the bottleneck: response time, software versions, database load. Slow hosting cannot be optimised away in the theme.
  5. Real visitors, not one test runWhere field data exists we read it, because a lab test is one device on one connection. We use lab tests to find causes and field data to see whether they matter.
  6. Mobile is checked on phonesTap targets, text size, menus and forms are tried with a thumb, not only in a resized browser window.

Security and upkeep

Practices that reduce what an attacker can use and make recovery possible.

  1. Updates are applied, and tested first where it mattersWordPress core, theme and plugin updates are applied where applicable. On a site with custom code or a store we try them on a copy first. An update left unapplied leaves a known weakness open.
  2. Everyone gets the smallest role that worksPeople are given the lowest user role that lets them do their job, old accounts are removed, and administrators use strong, unique credentials with two-step sign-in where it is available.
  3. Fewer, better-maintained pluginsWe prefer a few well-maintained plugins to many, replace abandoned ones, and install nothing from an unknown source.
  4. Monitoring has an ownerDecide what is watched (availability, failed sign-ins, file changes, expiring certificates) and who is told. Monitoring is a service someone is responsible for, not a switch.

No site can be made immune to attack. The aim is to limit what can be used against it and to be able to recover.

Technical SEO foundations

What makes a site easy for search engines and people to read.

  1. A structure that can be crawledA clear page hierarchy, readable addresses and navigation that reaches every important page in a few clicks, so nothing that matters is buried.
  2. Pages grouped by topicRelated pages are grouped and linked to each other, so search engines and visitors can see how the content fits together.
  3. Indexing controls that say what you meanCorrect canonical tags, a clean XML sitemap, robots rules that do not block what should be found, and noindex only where it is intended.
  4. Templates that carry the basicsOne main heading per page, a logical heading order, and editing screens with fields for the title, description and image descriptions, so editors do not have to remember.
  5. Structured data only where it is trueMarkup that matches what is on the page, and none that is invented or promises a particular search appearance.
  6. Accessible to everyoneContrast, keyboard use, labelled form fields and meaningful link text. Good for people first, and consistent with what search engines can read.

WordPress does not guarantee rankings. These foundations make a site easier to crawl and understand; they are not a promise of position.

How we test

A claim about speed or safety is only as good as the test behind it. This is the order we work in.

  1. Measure first

    Lab tests to find causes, and real-visitor data where it exists, before anything changes.

  2. Change one thing at a time

    So that we know which change made the difference, and which made things worse.

  3. Compare like with like

    The same pages, the same conditions, before and after.

  4. Try it on real devices

    Phones and desktops, with a touchscreen and a keyboard.

  5. Restore a backup

    Prove that the backup works by using it, not by trusting that it ran.

Want a second opinion on a site that feels slow, fragile or hard to find? Tell us what you are seeing.

Discuss My WordPress Project

Pricing and scope

WordPress Development Pricing & Project Scope

WordPress projects are scoped, not sold as packages. What a project involves, and so what it costs, follows the amount of work inside it. These eleven factors are where that work comes from, so you can see where your project sits and what would move it.

What changes the scope

Each row is a spectrum of work, not a price. Most projects sit at different points on different rows.

  1. Site complexity

    Every extra page type, state and rule is something to design, build and test.

    What keeps it lighter
    A small set of pages that share the same few layouts.
    In between
    Several page types, a blog or news area and a few forms.
    What makes it heavier
    Many page types with relationships between them, member areas or multi-step journeys.
  2. Number of unique layouts

    Each distinct layout is designed once, built as a template and checked at every screen size.

    What keeps it lighter
    Pages reuse a handful of templates and patterns.
    In between
    Several distinct page designs, each with its own template.
    What makes it heavier
    Many bespoke page designs, each needing its own template and its own testing.
  3. Custom theme or existing theme

    A custom theme is built around your design; an existing theme is adapted to it. One gives more control, the other has less to build.

    What keeps it lighter
    An existing theme, configured and lightly adapted.
    In between
    A child theme with customized templates.
    What makes it heavier
    A custom theme built from your design, with components of its own.
  4. Builder-based or custom development

    A page builder speeds up layout work but carries its own weight. Custom code takes longer to write and gives tighter control.

    What keeps it lighter
    Layouts assembled with the block editor or a page builder.
    In between
    Builder or block layouts, with custom code for specific parts.
    What makes it heavier
    Mostly custom-coded templates and components.
  5. Plugin functionality

    Each plugin has to be chosen, configured, tested against the others and kept up to date.

    What keeps it lighter
    A few well-supported plugins used as they come.
    In between
    Plugins that need careful configuration and some customization.
    What makes it heavier
    A custom plugin, or heavy modification of a third-party one.
  6. Integrations

    Every connection to another system adds sign-in, data mapping, error handling and testing on both sides.

    What keeps it lighter
    Forms that send enquiries by email.
    In between
    One other system connected, such as a CRM, a booking tool or an email tool.
    What makes it heavier
    Several systems, data that moves both ways, or an interface that has to be learned and built against.
  7. WooCommerce requirements

    A store adds catalogue structure, checkout, tax and shipping rules, and an order workflow your team has to run.

    What keeps it lighter
    A small catalogue of simple products and a standard checkout.
    In between
    Variable products and several payment or shipping options.
    What makes it heavier
    Complex product rules, many shipping or tax cases, or links to stock and fulfilment systems.
  8. Content migration

    Moving content is not copying files. It is cleaning, restructuring and checking what has moved.

    What keeps it lighter
    A small amount of existing content, mostly reused as it is.
    In between
    A larger site where content is restructured or rewritten as it moves.
    What makes it heavier
    A very large or inconsistent content set, several sources, or a platform that is hard to export from.
  9. SEO migration requirements

    Protecting search visibility means knowing which addresses earn traffic, mapping them and checking after launch.

    What keeps it lighter
    A new site with no existing search presence to protect.
    In between
    An existing site whose addresses mostly stay the same.
    What makes it heavier
    A changed address structure, merged sites or a domain change, with many pages to map and redirect.
  10. Quality assurance

    Testing grows with what is built: more templates, features and devices mean more to check.

    What keeps it lighter
    A simple site checked on common browsers and screen sizes.
    In between
    Forms, integrations and editing workflows tested from start to finish.
    What makes it heavier
    An accessibility review, wide device testing, or several rounds of review with different people.
  11. Hosting and support arrangements

    Hosting and support are ongoing, not part of the build, so they are agreed and scoped on their own.

    What keeps it lighter
    You already have hosting you are happy with and will look after the site yourselves.
    In between
    New hosting to set up, then handed over to your team.
    What makes it heavier
    Hosting with particular requirements, and an agreement for ongoing support.

One-time development, and what is scoped separately

A build has an end. Several things around it do not, and they are agreed on their own so you can see what you are paying for and choose who provides it.

One-time

The development project

The work that is planned, built, tested and handed over as one project, as described in the agreed scope.

  • Planning, sitemap and content structure
  • Design of the templates and layouts in scope
  • Theme and editor build, with patterns for your team
  • Plugin set-up and any custom code in scope
  • Integrations and content migration, where in scope
  • Testing, launch and handover as agreed

Scoped separately

Recurring and optional

Each of these is agreed on its own. None is automatically included in a development project.

  • HostingThe server your site runs on, and the account it sits in.
  • Premium plugin and theme licencesPaid tools usually renew on their own schedule, and whose name they are held in matters.
  • MaintenanceUpdates, backups and fixes after launch. Scope is agreed per engagement.
  • Technical supportHelp when something breaks, or when you need a small change.
  • Ongoing content updatesAdding and changing pages and posts, if you want someone else to do it.

Maintenance, hosting, premium licences and support are not automatically included in every project.

What to bring so the scope can be accurate

You do not need a finished brief. These are the things that make a scope accurate rather than a guess.

  • The address of your current site, if you have one, and what is wrong with it
  • The pages and kinds of content the site needs
  • Sites you like, and what you like about them
  • The tools the site has to connect to
  • Who will edit the site, and how often
  • The domain, hosting and licences you already hold
  • Any date that matters, and why it matters

Next step

Planning a New WordPress Website or Improving an Existing One?

Whether the site does not exist yet, or exists and is holding the business back, the useful first step is the same: a conversation about what the site has to do. Tell us where you are, and we will tell you what we would scope and why.

A site that does not exist yet

New WordPress website

Helpful to bring

  • What the business needs the site to do, and who will use it
  • The pages and content you expect, even as a rough list
  • Anything it must connect to: forms, booking, a CRM, payments
Discuss a new website

A site you already have

Improving an existing WordPress site

Helpful to bring

  • The address of the current site, and what is not working
  • What it runs on, if you know: theme, plugins and host
  • What must not be lost: pages that bring enquiries, and addresses other sites link to
Discuss improving my site

Content management

A WordPress Website Your Team Can Actually Manage

The practical reason many businesses choose WordPress is not the technology. It is that the people who write the content can change it themselves, on the day, without waiting for a developer. This is what that looks like in a site we build, and where the responsibility sits once it is live.

Edit pages, text and images

Open a page, click the heading or the paragraph and type. Replace an image from the media library. The editor shows the page the way visitors will see it, so a change is checked as it is made.

  • Change headings, text, buttons and images in place
  • Preview the page on desktop, tablet and phone before it goes live
  • Step back after a mistake with undo and the revision history

Publish or schedule content

Save work as a draft, preview it, then publish straight away or choose a date. A page can stay private, or behind a password, while it is being prepared.

  • Draft, scheduled and published states
  • Public, private or password-protected visibility
  • The person who writes does not have to be the person who publishes

Update blog articles

Articles have their own settings: categories, tags, a featured image and an excerpt. Several people can write, with an editor reviewing what goes live.

  • Categories and tags to organise articles
  • A featured image and a short excerpt for listings
  • Contributors submit for review; editors publish

Reuse blocks and patterns

A layout you use often, such as a call to action or a contact strip, is saved once as a pattern. Change a synced pattern in one place and every page that uses it follows.

  • Patterns for the layouts you repeat
  • Synced patterns that update everywhere at once
  • Where the build sets it up, locked areas that editors cannot move by accident

Manage basic page information

Each page has its own address, a featured image and an excerpt in the sidebar. Where an SEO plugin is part of the build, its title and description fields sit in the same place.

  • The page address (permalink) and its parent page
  • A featured image and an excerpt
  • The template a page uses, where the theme offers more than one

Control who can do what

WordPress has built-in user roles. An administrator manages the whole site, an editor manages and publishes content, an author publishes their own posts and a contributor writes for review. People see only what they need.

  • Add, change and remove users without a developer
  • Give an agency or freelancer access for a project, then take it away
  • Keep site settings, themes and plugins for the administrator
Illustration of WordPress editing screens, drawn for this page. A real project’s screens depend on its version, theme and plugins.

Handover, training and what is yours after launch

Editing is the easy part to hand over. The rest should be agreed before the site goes live, not discovered afterwards.

  • Client handover

    What a handover covers is agreed in the project scope. It can include administrator access, a walk through the editor and the patterns built for you, and notes on what to leave alone.

  • Training, where included

    Where training is part of the scope, it covers the tasks your team will actually do: editing pages, publishing articles, using patterns and managing users. It is not assumed for every project.

  • Responsibility after launch

    Your team owns the content. Keeping the platform healthy (core, theme and plugin updates, backups and security checks) needs an owner too: your team, your host, or a separately scoped maintenance agreement.

    How ownership and support work

Industries

WordPress Solutions for Different Industries

Every sector asks something different of a WordPress site. These are the typical requirements, drawn as the content structures and flows each one tends to need. They describe what to plan for in a sector, not a list of projects.

  1. Professional Services

    What the site has to doEstablish credibility and make it easy to enquire: who the people are, what each service involves, and how the firm works.

    WordPress building blocks

    • Team profiles
    • Service pages
    • Case studies
    • Insights articles
    • Enquiry forms

    Plan carefully

    Case studies and profiles need the permission of the clients and people they show. Give every service its own page, since a service buried in a list is hard to find.

  2. Healthcare

    What the site has to doHelp patients find the right clinician or service and request an appointment from any device, in plain language.

    WordPress building blocks

    • Provider directory
    • Service and condition pages
    • Appointment request or booking link
    • Locations and opening times
    • Accessible templates

    Plan carefully

    Health information is sensitive. Decide with your legal or compliance adviser what a form may collect, where it is stored and how consent is recorded. Clinical content should be reviewed by the person responsible for it.

  3. Education

    What the site has to doLet applicants and parents compare programmes, check dates and requirements, and start an application.

    WordPress building blocks

    • Programme listings with filters
    • Events calendar
    • Enquiry or application form
    • Staff directory
    • Multilingual pages

    Plan carefully

    Student and parent data needs careful handling: decide what the website stores and what stays in your admissions system. Plan accessible templates from the first layout, not as a late fix.

  4. Ecommerce and Retail

    What the site has to doTake shoppers from browsing to a finished order, while your team manages the catalogue, stock and orders as part of its routine.

    WordPress building blocks

    • WooCommerce catalogue
    • Product variations
    • Search and filters
    • Cart and checkout
    • Order and stock workflow

    Plan carefully

    Extensions accumulate quickly in a store. Each one affects speed and the cost of updates, so decide which are worth keeping. Wider ecommerce strategy is a separate conversation.

  5. Real Estate

    What the site has to doKeep listings current, searchable and easy to enquire about, with every property worth a page of its own.

    WordPress building blocks

    • Listing post type with custom fields
    • Filters and map
    • Property enquiry form
    • Agent profiles
    • Feed or import

    Plan carefully

    Listings change constantly, so decide who updates them: by hand, by import or from another system. Image-heavy pages need care to stay quick on a phone.

  6. Hospitality

    What the site has to doShow rooms, tables or experiences well and let guests check availability or book without being sent elsewhere first.

    WordPress building blocks

    • Rooms, menus or experiences
    • Booking engine link
    • Seasonal offers
    • Galleries
    • Multilingual pages

    Plan carefully

    Availability and payment normally live in a booking system, so the website’s job is to connect to it cleanly. Seasonal content needs a simple way to switch offers on and off.

  7. Publishers and Media

    What the site has to doKeep a large and growing archive easy to browse, with many authors and a steady publishing rhythm.

    WordPress building blocks

    • Topics and series taxonomies
    • Author profiles and roles
    • Editorial workflow
    • Newsletter sign-up
    • Archive and search

    Plan carefully

    Volume is the issue. Thousands of articles need an archive structure that visitors and search engines can follow, and good caching. Settle the editorial roles before the first article is written.

  8. Home Services

    What the site has to doLet someone in a hurry see that you cover their area and ask for a quote or a call without hunting for the form.

    WordPress building blocks

    • Service pages
    • Service-area pages
    • Quote and call-back forms
    • Click-to-call
    • Work gallery

    Plan carefully

    Create an area page only where you genuinely work: thin duplicate pages for places you do not serve cause problems. Make sure every form reaches whoever answers the phone.

  9. Nonprofits

    What the site has to doExplain the cause, bring in donations, volunteers and event sign-ups, and keep supporters informed.

    WordPress building blocks

    • Donation form or link
    • Events with registration
    • Volunteer form
    • Stories and updates
    • Accessible templates

    Plan carefully

    Let payments sit with a provider built for donations, and link to it cleanly. Contributors are often volunteers, so roles and approvals matter more than usual.

  10. B2B and Manufacturing

    What the site has to doGive buyers specifications, documents and a clear route to a quote across a range of products.

    WordPress building blocks

    • Product post type with specification fields
    • Downloadable documents
    • Request-a-quote form
    • Distributor finder
    • Regional versions

    Plan carefully

    A catalogue is structured data. Decide the fields once, such as dimensions and materials, and import the rest. If buyers order through you, decide whether a store or a quote workflow suits better.

The small drawings are original illustrations made for this page. They show the kind of content structure a sector tends to need and are not screens from any project.

Process

Our WordPress Development Process

The steps are the familiar ones. What is particular to WordPress is what gets decided inside them: how the content is structured, how the editor is set up for your team, which plugins are allowed in, and how an old site’s addresses are carried across. Each stage ends in a decision that is yours.

  1. 1Discovery & ScopeWhat the site is for
  2. 2Architecture & Content PlanningHow content is organised
  3. 3Design & Build ApproachTheme, editor and plugins
  4. 4WordPress DevelopmentBuilt on a staging site
  5. 5QA & ReviewTested with real roles
  6. 6Launch & HandoverLive, then handed over

Approval point. A diamond marks a decision that is yours before the work moves on to the next stage.

  1. Discovery & Scope

    What is discussed
    What the site is for, who uses it and who edits it. What is wrong with the current site, if there is one. The tools it has to connect to, and what you already own: domain, hosting and licences.
    What is planned or built
    A written scope: the pages and content types, the features and integrations, what is migrated, what is out of scope, and which parts are one-time and which are recurring.
    What you can expect
    Questions rather than a pitch. If WordPress is not the right fit for the job, we say so and explain what we would suggest instead.
    What needs your approval
    The scope and its boundaries. Nothing is built until you have agreed what is in it.
  2. Architecture & Content Planning

    What is discussed
    How the content is organised: page types, posts, custom post types, categories and the links between them. Who needs which permissions to add and publish.
    What is planned or built
    A sitemap and address plan, the content model and custom fields, the editor roles and, for an existing site, a content inventory and a plan for the old addresses.
    What you can expect
    Plain-language documents you can read and correct, not code. Your content team is involved here, because they will live with the result.
    What needs your approval
    The sitemap, the address plan and the content structure. A change now is cheap; a change after the build is not.
  3. Design & Build Approach

    What is discussed
    How the design should work inside WordPress: a custom theme, a child theme or an existing theme; the block editor or a page builder; which layouts become reusable patterns.
    What is planned or built
    Designs for the key templates at phone, tablet and desktop sizes, the patterns your editors will use, and a short list of plugins with the reason each one is there.
    What you can expect
    Designs reviewed with the editing experience in mind, not only the look. Plugins that are justified one by one rather than piled on.
    What needs your approval
    The design direction, the theme and editor approach, and the plugin list, including any paid licence a plugin needs.
  4. WordPress Development

    What is discussed
    Progress, questions that come up while building, and any content or access we are waiting for from you.
    What is planned or built
    The theme and templates, patterns and blocks, plugin set-up and any custom code, and the integrations in scope. Everything is built on a staging site, not the live one, and content is loaded or migrated.
    What you can expect
    A working staging site you can click through and try editing on, shared as it takes shape so surprises come early.
    What needs your approval
    Any change to the agreed scope. Anything that adds work is raised and agreed first rather than absorbed quietly.
  5. QA & Review

    What is discussed
    What to check and who checks it: your team’s review of content and workflows, and our testing of devices, forms and integrations.
    What is planned or built
    Testing across browsers and screen sizes, forms and integrations from start to finish, the editing and publishing workflow with real user roles, redirects, and the performance and accessibility basics.
    What you can expect
    A list of what was tested and what was found, with fixes made or, where you choose to defer something, the decision recorded.
    What needs your approval
    Your sign-off that the site is ready, and your decision on anything left open.
  6. Launch & Handover

    What is discussed
    The launch plan: when to switch, who does what, and what to watch afterwards. What access, guidance and ongoing support you want.
    What is planned or built
    The switch to the live site, redirects and analytics checked, backups in place, search and analytics continuity, administrator access handed over and, where agreed, a walk through the editor and written notes.
    What you can expect
    A checked launch, follow-up checks on what matters (redirects, forms, analytics) and a clear answer to who looks after the site now.
    What needs your approval
    The go-live moment, and the arrangement for support after launch if you want one. Neither is assumed.

Timing depends on the scope, so it is agreed once the scope is. No stage is given a standard duration here because the honest answer is that it depends on the project.

Discuss My WordPress Project

Why B9

Why Choose B9 Solution for WordPress Development?

Choosing a WordPress developer is mostly choosing how decisions get made. This is how we work, and what you can expect to be asked before anything is built.

Illustration of the planning that comes before a build, drawn for this page. It is not a photograph and does not show B9 staff.

Who leads the work

B9 Solution is led by experienced digital marketing professionals, with leadership bringing 12+ years of experience in digital marketing and digital selling.

  • Founded in 2020
  • Serving businesses in India, the United States, Canada, the United Kingdom, Australia and the UAE
  1. We plan the site around the job it has to do

    B9 is a digital marketing and technology agency, so a website is planned as part of how a business is found and how enquiries are won, not as a stand-alone build. We ask what the site has to achieve for the business before we ask which theme to use.

  2. CMS planning starts from your business, not from a template

    The content model comes first: which kinds of page exist, what changes every week and what changes once a year, who edits what and who approves it. The editor is then built around those answers, so the people who publish are not working against it.

  3. Site structure is decided with search in mind

    Page types, URL patterns, headings, internal links and templates are settled up front, by a team that also works on search visibility. The aim is a structure that supports being found, rather than one that has to be repaired after launch.

  4. Publishing is designed, not assumed

    We look at how your team actually writes and publishes: who drafts, who reviews, how often, and from which devices. Roles, reusable patterns and templates are set up to match, so a routine update does not need a developer.

  5. Migration and maintenance are planned from day one

    Before any build we ask what exists today, which URLs bring in visitors, which plugins are fragile and who will look after the site afterwards. Those answers shape the design as much as the brief does, and they are why an upgrade later is not a rescue.

  6. Requirements and scope boundaries are written down

    What is included, what is scoped separately, what we need from you and which decisions need your approval are agreed before work starts. A change later is then a conversation about scope, not a surprise.

Maintenance and ownership

WordPress Maintenance, Ownership & Ongoing Support

A finished website and a looked-after website are different jobs. Launch hands you a working site; keeping it updated, backed up and secure is work that continues, and someone has to own it. This section explains who normally holds what, and what is agreed before the site goes live.

Who holds what: an ownership map

These are the things that cause trouble when nobody wrote them down. Agree each one before launch, in the project scope.

  • Domain name

    What to agree in writing
    Who is the registered owner, who holds the registrar login, and who renews it.
    Our recommendation
    Register the domain in your business’s own name and keep the login with someone you trust, so the address your customers know can never be locked away from you.
  • Hosting account

    What to agree in writing
    Whose account the site lives in, who pays for it, and who can contact the host about it.
    Our recommendation
    Hold the hosting account in your own name, with your developer added as a user for the project rather than the other way round.
  • WordPress admin access

    What to agree in writing
    Which administrator accounts exist, and how access is added and removed when people or agencies change.
    Our recommendation
    At least one administrator account belongs to your business, and agency or freelancer access is limited to the project and removed when it ends.
  • Theme and its licence

    What to agree in writing
    Whether the theme is custom, a child theme or a purchased one, who holds the licence, and whether it renews.
    Our recommendation
    License a purchased theme in your name where the licence allows, and record the renewal date.
  • Plugins and their licences

    What to agree in writing
    Which plugins carry a licence fee and which do not, who pays, and whose account receives updates and support.
    Our recommendation
    Keep a short list of every plugin, what it is for and who holds its licence, so any future developer can pick the site up.
  • Content and media

    What to agree in writing
    Who owns the text, images and files, and where the originals are kept.
    Our recommendation
    Keep the original files for everything you supply, and confirm usage rights for any images or fonts added during the build.
  • Backups

    What to agree in writing
    Where backups are stored, how often they run, how long they are kept, and who has tested a restore.
    Our recommendation
    Store backups somewhere you can reach and not only on the same server as the site, and test a restore at least once.
  • Custom code

    What to agree in writing
    What custom code was written for you, where it lives, and what the agreement says about it.
    Our recommendation
    Keep custom code in its own plugin or theme with short documentation, and set out the rights to it in the project agreement.

These are practical recommendations, not legal advice. The terms of your project are the ones agreed in writing in its scope, before work starts.

After launch: who looks after what

Most problems come from a task that nobody was given. Whoever takes each of these on, name them before the site goes live.

Your team

Usually

  • Editing and publishing content
  • Managing user accounts and roles
  • Keeping original files and licence details
  • Deciding who handles everything else on this list

You can also take on updates and backups yourself, or pass them to a developer you choose. What matters is that it is decided.

Your host

Depending on the hosting plan

  • The server and its software, such as PHP and the database
  • Server-level backups, where the plan includes them
  • Server security and availability
  • Hosting support requests

Hosting plans differ a great deal. Ask what yours includes and what it leaves to you, and write the answer down.

B9 Solution

Only under a separately scoped agreement

  • WordPress core, theme and plugin updates
  • Compatibility checks before an update goes live
  • Technical support requests
  • Improvements and, where scoped, ongoing content updates

What a maintenance agreement covers, and how it is reviewed, is agreed per engagement. There are no standard packages and no open-ended promises.

Every task needs an owner. A task with no name against it is a task that is not being done.

Want to know what a maintenance agreement for your site would involve? Tell us about the site and we will scope it with you.

Discuss My WordPress Project

Questions

WordPress Development FAQs

Straight answers to what buyers ask before a WordPress project. Where an answer depends on scope, it says so instead of guessing.

Getting started

Whether WordPress fits, and what to prepare. 3 questions

Often, when your team needs to publish and change content regularly, the site is mostly pages, articles, services or products, and you want room to add features later. It is a weaker fit for software with heavy real-time logic, for a simple shop where a hosted store platform would do the job with less upkeep, or for a few pages that never change. We would rather tell you that before a project than after. Describe what the site must do and who will manage it, and we will say whether WordPress suits it and why.

Enough to scope the work honestly: what the site is for and who uses it, the pages and content you already have, the website address if one exists, any tools it must connect to such as a CRM or booking system, who will edit it day to day, and any brand guidelines or design preferences. If you are unsure about some of this, say so. Working out the unknowns is part of the first conversation, and the enquiry form needs only a short brief.

Web design decides how a site looks and how visitors move through it: layout, visual identity and the interface. WordPress development builds that design on the WordPress platform and decides how it works underneath: the content structure, the theme, the editor your team uses, the plugins, the integrations and the technical set-up. On most projects the two overlap, so they are planned together. If you only need a visual redesign, the design work comes first and the development follows from it.

Development

Themes, builders, plugins, stores and integrations. 3 questions

A custom theme is one option, not the only one. For a site with its own brand and page types, we scope a theme built for it: templates for each page type, styling set once, and customizations kept apart from third-party code. Where an existing theme already fits, a child theme or a lightly customized theme can be the sensible choice, and we say what each costs you in upkeep. The decision depends on how different your site is from what an existing theme provides, and who will maintain it afterwards.

Usually, if the other system offers a way to connect, such as a plugin, a REST API or webhooks. Before building, we agree what has to move between the two, in which direction, and what the site should do when the other system is unavailable. A form that passes enquiries to a CRM is a smaller job than two-way synchronisation of bookings. We read your system’s documentation before promising a particular integration.

Yes. B9 builds on WooCommerce, the store plugin for WordPress. We plan the catalogue, variations, checkout, payment methods, shipping rules and the order workflow your team will use, then build and test it. Which platform suits a large or complex catalogue is worth settling first: WooCommerce is a strong fit when you also want content and commerce on one site, while a hosted store platform may suit a simpler shop. We give an honest view once we know how you sell.

Migration & performance

Redesigns, moves, speed and safety. 3 questions

Yes. We start by reviewing the current theme, plugins, content and search visibility to decide what to keep, rebuild or retire. Some sites can be redesigned on their existing foundation; others are cleaner to rebuild on a new one with the content moved across. Either way we list the URLs that matter and keep or redirect them, remove plugins the site no longer needs, and test on a staging copy before anything changes on the live site.

Carefully, and without promises about rankings, because rankings cannot be assured through a migration. Before moving anything we inventory the URLs, titles, headings and links that bring in visitors. We map every old address to its new home, plan permanent redirects where addresses change, keep internal links pointing at the right pages and test on staging. After launch we check that redirects work, pages can be indexed, and analytics and Search Console keep recording. Rankings can still move; the aim is to protect what already works.

Several things, usually in combination: the hosting plan and server, the weight of the theme, the number and quality of plugins, the size and format of images, the scripts and fonts that load on every page, and how caching is set up. Speed is measured, not guessed: we test before changing anything and again afterwards, ideally with real-visitor data as well as lab tests. We do not promise a particular score, because the result depends on the content and the host as much as on the build.

Pricing & ownership

What moves cost, and who holds what. 6 questions

Scope, mainly: the number of unique page layouts, whether the theme is custom or existing, whether the site is built with a page builder or custom code, the plugin functionality it needs, integrations with other tools, whether there is a WooCommerce store, how much content has to be migrated, how much SEO migration planning is needed, how thoroughly it is tested, and the hosting and support arrangements around it. We do not publish package prices, because the same page count can be a small or a large job. The pricing section on this page shows each factor.

It depends on the scope, so we do not quote a standard duration. The main factors are the number of page types, how much is custom, how many integrations there are, how much content must be moved or written, how quickly your team can give feedback and approvals, and any migration planning. After discovery we agree a schedule in the project scope, with the points where we need your decisions. Projects run longer when content or approvals arrive late, so it helps to know early who signs off what.

Ownership is agreed in writing before work starts, so nothing is left to assumption. Our recommendation is that the business registers its own domain, holds its own hosting account and has administrator access to the site, so you are never locked out of your own website. The custom work built for you is covered by the project agreement. Paid themes and plugins come with their own licences, which should be in your name where the licence allows. WordPress itself is open-source software.

Yes, that is the main reason to use WordPress. The editor lets your team change text, images, buttons and layouts, publish articles and manage menus without a developer. We set it up around your content so common changes are simple, and agree up front what your team can change and what stays fixed. Training is covered where it is part of the project scope; it is not assumed for every project.

A WordPress site needs looking after: core, theme and plugin updates checked for compatibility, backups with a tested restore, security checks, fixes when something breaks and small improvements over time. Ongoing maintenance is available from B9 as a separately scoped agreement, agreed per engagement; it is not included in every project. You can also handle it in-house or through your host. We will say which tasks matter most for your site and what each option involves.

Not automatically. Hosting is usually a separate arrangement, and we recommend the account is held in your name. Premium themes and plugins carry their own licence fees, often renewed on a regular cycle and paid to their vendors rather than included in development work. During scoping we list the paid components a build would need, so there are no surprises, and who holds each licence is agreed up front.

Project enquiry

Tell Us What You Want to Build With WordPress

Describe the project in your own words. Include your website address if there is one, what the site needs to do, and who will manage it afterwards. We read it, ask what is unclear and come back with a scoped proposal.

What happens next

  1. We read your brief and note what is missing or unclear.
  2. We come back with questions, or suggest a call to go through them.
  3. You receive a proposal that sets out what we would build, what is included, what is scoped separately and what we need from you.

Project details

Fields marked optional can be left empty.

Is this a new website or an existing one?
What should it do? optional