CMS development
When a standard content management system begins to limit structure, employee roles, integrations, or SEO, further customization often turns into a chain of dependent modules. In such a situation, custom CMS development allows for the project's architecture to be defined in advance and the necessary business processes to be built directly into the system.
What is a custom CMS and when do you need your own content management system?
Seo-Gen creates CMS for websites, online stores, corporate resources, portals, and website networks. Within a single platform, you can manage content, language versions, users, forms, SEO parameters, integrations, and data from multiple projects.
A custom CMS is designed for a company's specific structure and operating methods. If a business requires multiple domains, separate languages, complex access rights, user accounts, CRM integration, or non-standard data types, these requirements are taken into account at the architecture stage.
A custom CMS is a content management system developed with the structure, processes, and technical requirements of a specific project in mind. The admin panel in such a system is linked to the server side, database, API, page templates, and publishing rules.
Creating a CMS for a website makes sense when a standard engine must be constantly customized to suit business needs. Instead of installing numerous third-party extensions, the team designs the necessary entities, roles, data relationships, and editor workflows.
A custom CMS is especially useful for projects that plan to grow over several years. The architecture can be expanded with new modules, integrations, and content types without migrating the entire system to another platform.
How does a custom CMS differ from a ready-made CMS?
WordPress, OpenCart, Joomla, and Drupal offer a ready-made architecture, a set of basic functions, and a large number of extensions. For a typical corporate website, blog, or small store, this is often sufficient, and the launch takes less time.
With a custom CMS, development begins with the specific requirements of the business. The data structure, admin panel, user roles, SEO settings, and integrations are created specifically for the project, eliminating the need to adapt company processes to the design of an existing engine.
The difference is especially noticeable with non-standard logic. When one employee needs access only to a specific website, another to a specific language, and a third to customer requests, permissions can be built directly into the access model.
When is custom CMS development justified?
Custom CMS development is typically needed for projects where a ready-made platform creates permanent technical limitations or requires too much customization. The decision is made after analyzing the website structure, company processes, and future development plans.
Most often, a custom system is chosen in the following cases:
- the company manages multiple websites, domains or brands from a single infrastructure;
- the project operates in multiple languages with separate URLs, SEO parameters and content;
- users need different roles, permissions and access to individual sections of the system;
- the site is connected to CRM, ERP, warehouse, payment systems or internal services;
- the standard structure of products, services, pages or categories does not correspond to the business model;
- the project requires a user account, complex search, automation or its own workflow;
- SEO settings should work at the core system level without dependence on third-party plugins.
Before ordering a custom system, it's worth comparing the cost of development with the ongoing maintenance of a ready-made CMS. For a simple project, custom development may be overkill, while for a larger platform, it reduces the number of technical compromises.
When is it better to use a ready-made CMS?
A ready-made CMS is suitable if the project structure is standard and doesn't require complex business logic. A small corporate website, blog, landing page, or store with a basic catalog is often faster and cheaper to launch on an existing platform.
This option is especially practical when budgets are limited and launch time is short. A large developer community and ready-made modules simplify support if the project uses standard scenarios and doesn't rely on deep integration with internal systems.
A custom CMS should be considered when the limitations of a ready-made platform already impact development costs, the speed of implementing changes, SEO, or employee performance.
What is included in custom CMS development?
CMS website development includes the administrative part, server logic, data storage, public site templates, user roles, and a set of editor functions. The system's composition is determined by the project's technical specifications and architecture.
CMS development services can include developing a new platform, migrating an existing website, creating modules, connecting external services, and ongoing support. Each project has its own set of features, so the processes the system must support are first defined.
Managing pages and site structure
The editor should manage the website structure without having to contact the developer for every change. The CMS stores pages, sections, categories, menus, nesting, and relationships between different types of content.
Depending on the project, you can create your own page templates and content blocks. The page receives the selected template, and the values of text, images, links, and other elements are stored separately from the program code.
This approach simplifies project development. A new section can be assembled from existing components while maintaining consistent design, responsiveness, and data display rules.
Content management
A content management system must take into account the actual types of project data. While one website may only need pages and articles, another requires products, specialists, documents, reviews, prices, FAQs, promotions, and complex reference data.
Content is stored in a structured format, so the editor works with easily understood fields instead of the page's source code. Images, files, and videos can be linked to specific entities, and output rules are defined in the template.
The CMS supports drafts, scheduled publishing, moderation, and content versions if needed. Revision history helps you understand who edited the content and what values were previously used.
Users, roles and access rights
A corporate system typically involves employees with different permissions, so a single administrator role isn't suitable for every project. A CMS can restrict access by site, language, section, content type, and individual operations.
The administrator manages settings and users, the editor manages content, the manager processes requests, and the client has access only to their own account. Additional roles are created as needed to suit the company's internal structure.
This model reduces the risk of accidental changes. Employees see only the necessary functions, while critical settings remain accessible to a limited group of users.
Multilingualism
A multilingual website requires separate data for each language version. Translating the main text alone isn't enough, as search engine optimization and the interface also depend on the chosen language.
The CMS stores URLs, Title, Description, H1 tags, menu items, breadcrumbs, buttons, images, and other values separately. Canonical, hreflang, and relevant Schema.org data can be specified for each version.
This approach helps avoid situations where a Ukrainian or English page receives Russian meta tags or generic template values. The editor immediately sees what data is filled in for each language.
Managing multiple sites
Multisite CMS is useful for agencies, chain businesses, and owners of multiple projects. A single installation can support multiple domains, with each site receiving its own design, languages, data, forms, and settings.
Each user logs into a single administrative system and works only with websites to which they have access. A role is defined by membership in a specific project, so permissions can be configured separately for each website.
At Seo-Gen, this approach is the foundation of the platform. Common functions are maintained centrally, while site-specific values are stored in its data and templates, so updating the shared block doesn't require manual editing of each project.
I recommend considering a custom CMS when a ready-made platform already limits the site structure, integrations, or technical SEO. If a project requires multiple sites and languages, complex roles, and custom logic, it's better to build these requirements into the architecture from the start rather than maintain dozens of dependent extensions.
Stages of CMS development
CMS development begins before any code is written. The team first defines users, data, integrations, and workflows, after which these requirements are translated into a technical architecture.
Sequential development reduces the amount of rework after launch. For a large system, it's especially important to validate the data model and access rights before building multiple modules on them.
Project diagram: Requirements analysis → architecture → UX/UI → development → integration → testing → migration → launch and support.
Requirements analysis
The team examines the business structure, existing website, users, and content management processes. Future integrations, language versions, and SEO requirements are identified separately.
At this stage, the functions that truly need to be in the CMS are identified. Some processes may already be supported by a CRM or ERP, so there's no need to duplicate them in the new system.
The result is a list of entities, roles, scenarios and constraints on which the subsequent architecture is built.
Technical specifications and architecture
The technical specification describes the CMS modules, data relationships, user roles, and interaction rules between components. APIs and exchange formats are defined for integrations.
Database architecture should accommodate project evolution. By properly defining entities and relationships from the start, new features can be added without constantly reworking existing tables.
Requirements for security, backup, infrastructure, and developer access are also recorded.
UX/UI CMS
The admin panel must take into account the daily operations of employees. If an editor publishes dozens of materials, they need search, filters, clear statuses, and quick access to key actions.
The interface is designed around roles. Users are not shown sections they don't have access to or that aren't relevant to their work.
Well-designed CMS UX/UI reduces errors and training time for new employees. For a large project, the usability of the administrative interface affects costs just as much as the public-facing design.
Development
Once the architecture is approved, the backend, frontend, API, and necessary modules are created. Development proceeds with separation of the overall platform logic and the site-specific data.
Changes are committed to Git to preserve the code history and show who made the changes and when. This simplifies review, bug detection, and reverting to previous versions.
The work is first tested in the development environment. Changes are transferred to production after testing to ensure that any errors don't disrupt the live website.
Integrations
CRM, ERP, payments, and other services are connected after the core data models are prepared. Authorization, API limits, and error handling are verified for each integration.
Data exchange is tested using real-world scenarios. We need to verify not only successful requests, but also situations where the external service is temporarily unavailable or returns incorrect data.
If synchronization is performed in the background, the CMS saves the operation status. The administrator can see the error and retry the operation after the cause is resolved.
Testing
Functional testing verifies the creation, editing, publishing, and deletion of data. The permissions of each role and access restrictions are checked separately.
The public website is tested on mobile devices and in supported browsers. For SEO purposes, response statuses, canonical tags, hreflang, meta tags, sitemaps, and internal links are checked.
The final check is performed through the working external environment, including Caddy. A successful local launch does not yet confirm the correct operation of the production configuration.
Data transfer
During migration, it's necessary to determine the correspondence between old and new entities. Pages, products, images, and users are transferred to the new CMS structure while maintaining their relationships.
For large volumes of data, import and validation scripts are used. Manually migrating thousands of data items increases the likelihood of errors and complicates re-running the migration.
A separate stage is dedicated to URL and SEO data. Before switching the domain, a map of old and new addresses is prepared.
Launch and support
After launch, logs, application errors, and the availability of key functions are checked. For SEO, indexing and the appearance of unexpected 404 errors are also monitored.
Support includes bug fixes and platform development. New modules undergo the same cycle of development, testing, and production.
Updates to the shared CMS should not overwrite site-specific values. Therefore, local data and platform code are separated from the outset.
What we actually did
Dental clinic · Kyiv and Chernihiv
+44% clicks from search
A domain with no history and a site on a website builder. We built the semantic core for the services and both cities, reworked the landing pages and built the link profile from zero. In four months: 34.8k clicks, impressions 1.32 → 1.76M, DR 0 → 41.
E-commerce · international
+96% clicks in two months
A catalog of digital 3D models. We clustered the semantics, rebuilt the hub pages and fixed duplicates and indexing errors. Google users 247 → 532, CTR 2.4% → 4%.
Medical center · Ukraine
+68.75% visibility in the first month
Narrow visibility and a small semantic core at the start. Semantics, landing page structure, metadata and internal linking, then gradual link building.
How long does it take to create a CMS?
The development timeline depends on the number of modules, integrations, and the readiness of the initial requirements. A small MVP and a multi-site enterprise platform differ significantly in the scope of work.
The project can be launched in iterations. First, the core system and the functions required for the business are developed, after which additional modules are added.
Data migration, design approval, and external API availability also impact the timeframe. Some integrations cannot be fully completed until the service provider has provided the necessary access.
It's wise to plan CMS development services in stages, with interim testing of the results. This schedule reduces the risk of discovering a fundamental architectural error just before launch.
How much does CMS development cost?
CMS development cost depends on dozens of parameters and cannot be accurately estimated based solely on the number of public pages. The main labor intensity often lies in the data model, integrations, roles, and internal processes.
The CMS development price is calculated after analyzing the requirements. The client receives an estimate based on functional blocks, allowing them to separate the required MVP from features that can be added later.
What determines the price of CMS development?
The cost is influenced by the number of content types and the relationships between them. A simple admin panel for a few pages requires less work than a system with a catalog, user accounts, and complex permissions.
The following tasks may make up a significant part of the budget:
- development of multiple websites and language versions within a common platform;
- integration with CRM, ERP, BPM, payments and external databases;
- creation of user accounts, complex roles and separate user interfaces;
- transferring a large volume of data from the old CMS and preparing a redirect map;
- Custom web design, responsive layout, and Figma layout transfer;
- requirements for high load, security, redundancy and infrastructure.
After evaluating these blocks, it becomes clear which functions are critical for the first launch. The rest can be carried over to subsequent iterations without rethinking the entire system.
Why can't a CMS be accurately assessed based on the number of pages alone?
Ten pages can work on a single template with minimal development effort. A single user account with multiple roles, integrations, and complex statuses can require significantly more time.
The price is determined by the system's logic and the number of unique scenarios. Therefore, the price tag "CMS for 100 pages" says virtually nothing about the project's true complexity.
The assessment examines how data is created and modified, who works with it, and what systems are involved in the process.
How is a project estimate prepared?
First, requirements and required features are defined. Then the team defines the architecture, modules, integrations, and scope of the existing data migration.
After this, tasks are broken down into stages and estimated separately. This approach reveals how much of the budget is allocated to the system core, integrations, public frontend, and additional features.
For a preliminary estimate, simply describe your current website, the new CMS objectives, and the required integrations. A project estimate can be obtained after a brief technical review of the requirements.
Why Seo-Gen for CMS development?
Seo-Gen is developing its own multi-site CMS with server-side rendering. The platform is designed for websites where SEO, language versions, roles, and multi-project management must operate under uniform rules.
Custom CMS development services include design, development, migration of existing projects, integrations, and support. Changes go through the dev environment and are checked before being released to production.
SEO is at the core: Canonical, hreflang, sitemap, SEO variables, and microdata are supported at the platform level. General rules don't need to be reimplemented for each website. The CMS can also check links and technical issues. This helps quickly identify errors after changing the structure or moving content. SEO parameters for a specific page remain separate data. Template updates should not overwrite individual Title or Description.
One CMS for multiple sites
A single installation supports multiple projects with separate domains, languages, designs, and data. Users only have access to sites for which they have a corresponding membership.
Shared components are updated centrally, while client-specific content remains isolated from other projects.
This approach reduces the number of independent installations and simplifies website network maintenance. This is especially useful for agencies with similar SEO and infrastructure requirements.
Migrating existing websites and Figma 1:1
A finished website can be migrated from another platform, preserving its structure, content, and key SEO parameters. If the design remains the same, the public portion can be reproduced on the new platform.
Figma layouts are implemented with typography, grids, margins, hover states, and mobile resolutions in mind. Content is kept separate from interface components.
After the migration, the site is tested using a working external environment. Only this test verifies that routing, TLS, and server-side rendering are working in the actual configuration.
AI functions
CMSs can leverage AI for tasks already integrated into the workflow. Content and design generation are queued, so operations can be monitored and accounted for.
The system stores task history, resource usage, and limits. This is useful for a platform where AI functions are used by multiple sites and employees.
The generated result remains regular managed CMS content. It can be reviewed, edited, and published as usual.
Turnkey infrastructure
The platform runs on Docker and can include domains, TLS, email, forms, newsletters, and a customer dashboard. Caddy is used as the outer layer for HTTPS and routing.
Files are stored in separate storage, while site data is stored in PostgreSQL. Redis handles tasks that require fast access or a job queue.
This scheme gives developers a unified deployment and testing method. The production configuration isn't manually assembled from unrelated services.
The CMS evolves with the business
A new feature is added as a separate module or extension to the existing data model. This does not require migrating the entire site to a different platform.
General code changes are applied at the CMS level, while site-specific settings remain in their data and templates. This principle allows for platform updates without losing local settings.
Before developing a new feature, determine whether it's needed for all projects or just one site. Localized tasks are best addressed through fields, templates, and design tokens, without changing the shared block unnecessarily.
Related services
Corporate website
Turnkey corporate website development at Seo-Gen: analytics, UX/UI, CMS, integrations, SEO preparation, testing, and launch. Get a quote.
Online store
Turnkey online store development: UX/UI, catalog, payment, shipping, CRM, SEO, and analytics. We design, launch, and maintain eCommerce websites for businesses.
Service website
Turnkey service website development: structure, design, SEO, request forms, and integrations. We create websites to promote services and attract clients.
Landing page
Turnkey landing page development for businesses: analysis, prototyping, design, responsive front-end coding, integrations, and SEO preparation. We'll estimate the cost and timeline for your project.
Brochure website
Turnkey brochure website development for your business: design, responsive layout, SEO, analytics, and launch. Order your website creation from Seo-Gen.
Catalog website
Turnkey catalog website development for products and services: structure, filters, cards, CMS, SEO, and integrations. We'll estimate the cost and project timeline.
Classifieds website
Turnkey classifieds website development: architecture, user accounts, search, filters, moderation, monetization, and SEO. We'll calculate the project cost based on your needs.
Web applications
Turnkey web application development for businesses: analytics, UX/UI, frontend, backend, API integration, testing, launch, and support. We'll calculate the project cost.
Vibe coding
Custom website vibe coding and MVPs: AI accelerates development, while the Seo-Gen team is responsible for architecture, testing, SEO, and project launch.
Answers to your questions
What is a custom CMS?
A Custom CMS is a content management system developed to meet the needs of a specific project. Its data structure, roles, integrations, and administrative panel are tailored to the company's processes.
In a ready-made CMS, some of these functions are already defined by the platform developer. A custom system makes sense when the standard architecture permanently limits the required scenarios.
When is it worth ordering your own CMS development?
Development is justified for complex data structures, multiple sites, multilingualism, non-standard roles, or a large number of integrations. It is also chosen for projects where standard plugins increase maintenance costs.
For a simple corporate website, a ready-made system is often more rational. The decision is best made after assessing the requirements and the cost of further development.
How much does CMS development cost?
The price depends on the number of modules, roles, integrations, languages, and migration volume. Therefore, a precise estimate is determined after analyzing the requirements and architecture.
The project can be divided into the required MVP and additional features. This helps launch key processes earlier and distribute further development into stages.
How long does it take to create a CMS?
The timeframe depends on the system's complexity and the number of external dependencies. Integrations, user accounts, and the migration of large amounts of data significantly increase the scope of work.
For large projects, it's wise to use a phased rollout. The team first implements the basic features, then adds additional modules after validating the core architecture.
Is it possible to migrate an existing website to a custom CMS without losing SEO?
This transfer is possible with proper URL and SEO data preparation. Existing URLs are either preserved or redirected via 301 to the corresponding new pages.
Meta tags, canonical tags, hreflang, and internal links are also transferred. After launch, check the sitemap, robots.txt, 404 errors, and indexing of important pages.
Is it possible to integrate CMS with CRM or ERP?
Yes, if the external system provides a suitable API or other data exchange method. The CMS can transmit requests, users, and orders and receive statuses or reference information in return.
Before development, the source of truth and synchronization direction are defined. This prevents a situation where both systems simultaneously change the same field to different values.
Why is your own CMS better than WordPress?
A custom CMS isn't considered a universal replacement for WordPress. For a standard website, WordPress can be faster, cheaper, and easier to maintain.
A custom CMS is chosen when specific data, roles, integrations, or centralized management of a network of sites is needed. The decision depends on the project's requirements, not the platform's name.
Is a custom CMS suitable for an online store?
Yes, if ready-made eCommerce platforms don't cover the store's business logic. A custom CMS can implement a customized catalog, price types, customer roles, and warehouse integration.
However, development requires a larger budget and extensive testing. For a standard store, it's worth first comparing custom development with ready-made eCommerce solutions.
Developing a CMS makes sense when a project requires custom logic, multiple sites, multilingual support, complex roles, integrations, or deep control over technical SEO. In such a system, the architecture is built around the company's actual processes and can evolve with the project.
Seo-Gen develops and migrates websites to its own CMS with server-side rendering, centralized SEO, multisite architecture, and integration support. Discussing CMS development is best done after preparing a list of current tasks, integrations, and requirements for the future platform.
We reply within one business day. No newsletters, no “just a reminder” calls.
He will look at the site himself instead of passing it to a manager.
More on: CMS development
SEO capabilities of your own CMS
Technical SEO is easier to maintain when the core rules are implemented at the platform level. Website CMS development allows you to pre-define canonicals, hreflang, sitemaps, meta robots, redirects, and other elements that affect indexing.
Seo-Gen builds SEO functions into the CMS core. This means fewer manual steps for the editor, and for the developer, consistent rules for generating technical tags and URLs across all projects.
Managing meta tags and SEO parameters
Each indexed page must have its own Title, Description, and H1 tag. The CMS stores these values separately from the page text and can use SEO variables for similar sections with a large number of URLs.
The system also manages canonical, meta robots, and URL generation rules. The trailing slash, URL structure, and other technical settings are set centrally, so different templates don't generate their own rules randomly.
For large catalogs, you can use template values with the option to manually override them. Important landing pages receive individual meta tags.
Indexing and technical SEO
The CMS can automatically collect a sitemap.xml from pages approved for indexing and update the sitemap after new content is published. Robots.txt and meta robots work together to provide search engine crawlers with clear instructions.
When changing a URL, the system must take into account 301 redirects and check for 404 errors. Separate monitoring is required for GET parameters, duplicate pages, and internal links that may lead to outdated addresses.
Checking for technical issues within the CMS reduces the time between error detection and resolution. This is especially useful for a large multi-site project, as the same issue can appear on multiple sites at once.
Schema.org micro-markup
Structured data is generated based on the page type and actual content. Organization or LocalBusiness might be used for the homepage, BreadcrumbList for navigation, and Article or BlogPosting for articles.
A catalog can use Product, CollectionPage, and ItemList if the page data matches the selected type. FAQPage is used where questions and answers are actually published to the user.
Reviews, AggregateRating, and prices cannot be generated without verified data. JSON-LD values must match the visible information on the page; otherwise, microdata creates technical and reputational risks.
SEO for multilingual websites
Each language version should be a standalone page with its own meta tags, URLs, and interface text. The CMS links the versions together and generates hreflang only for existing languages.
Canonical typically points to the current language page unless there's another reason to combine URLs. The sitemap should also contain current pages and not include technical or restricted sections.
What integrations can be connected to a custom CMS?
Custom CMS solutions are often used where a website needs to exchange data with other company systems. In this case, the CMS becomes part of the infrastructure and operates through APIs, task queues, or direct integration modules.
CMS website development services can include connecting existing CRM, ERP, inventory management, analytics, payment services, and internal applications. The specific exchange method is selected after reviewing the API and synchronization frequency requirements.
CRM and ERP
CRM integration helps transfer requests, contacts, lead sources, and other data without manual copying. After form submission, the CMS can create a deal, assign the responsible employee, and save the record ID.
An ERP or inventory management system is typically responsible for products, stock levels, prices, documents, and related transactions. A CMS receives the necessary data and displays up-to-date information to visitors without becoming a second, independent source of accounting.
For Ukrainian projects, integration with BAS, warehouse platforms, and other internal systems is possible if they have a suitable data exchange mechanism available.
BPM and business process automation
The request for a custom CMS for BPM integration is related to projects where website actions should trigger an internal business process. For example, a request creates a task, undergoes approval, changes its status, and sends notifications to the responsible employees.
The CMS can retrieve the final status and display it to the user in their account. Publications, document reviews, content approvals, and other multi-step operations are automated in the same way.
Before integration, process states, data sources, and error handling rules are documented. This helps avoid situations where two systems consider different statuses to be valid.
Payment systems and eCommerce
For an online store, the CMS links the catalog, shopping cart, orders, payment, and delivery. The logic depends on the business model, so one project operates with a fixed price, while another calculates it by customer, region, or order volume.
The payment system is connected via the provider's API, after which the CMS processes successful and unsuccessful payments. The order receives the appropriate status, and the information is transferred to the CRM or ERP.
If necessary, delivery services, warehouse accounting, product import, and automatic inventory updates are enabled. All operations must have clear logs so that synchronization errors can be quickly identified.
API and external services
The REST API connects the CMS to mobile apps, external services, and other company products. The API is also used in headless CMSs, where the administrative system stores data and the interface retrieves it through the software layer.
The platform can be connected to analytics, mailing services, external databases, and Telegram bots. Access rights, data format, and error handling are defined for each connection.
Integrations should not contain passwords and keys directly in the public-facing code. Secrets are stored in secure infrastructure settings.
Custom CMS for corporate and enterprise projects
A custom CMS for enterprise websites is needed where the site is shared by multiple departments, editors, or regional divisions. Roles, scalability, change history, stability, and clear publishing rules are especially important for such projects.
A custom CMS website can be developed in stages. The core features are launched first, then additional modules, new sites, and integrations are added without completely redesigning the architecture.
CMS for a corporate website
A corporate website typically contains services, departmental pages, employee pages, documents, news, forms, and language versions. The CMS should allow editors to update these sections without developer intervention.
You can set up separate permissions for different departments. HR manages job openings, marketing manages content and landing pages, and the administrator manages general settings.
For large structures, admin panel search, revision history, and content filters are useful. These features reduce editor time and reduce the likelihood of accidental errors.
CMS for large portals
Portals contain thousands of pages and a large number of related entities. The standard "page plus text editor" model is insufficient here, as content must be linked to categories, authors, regions, and additional reference data.
The CMS must support search, filters, bulk operations, and moderation. With a large number of editors, access rights and a transparent publication history are especially important.
The database architecture is designed with the growth of information in mind. By doing this in advance, new sections can be added without constantly revising the existing model.
CMS for an online store
An online store needs products, categories, attributes, prices, stock, and orders. For a custom eCommerce solution, this set is insufficient, so the structure may include different price types, individual customer terms, and additional reference data.
Custom CMS development services allow you to link your catalog to your CRM, warehouse, delivery, and payment systems. The public portion of the site uses only the necessary data and doesn't duplicate your internal accounting system.
Catalog SEO is also taken into account in the architecture. Categories, filters, canonical tags, meta tags, and indexing rules are best designed in conjunction with the product structure.
CMS for a network of websites
A network of independent CMS systems complicates updates, user management, and maintaining consistent functionality. With a common platform, core modules are updated centrally, and each site maintains its own data and design.
The administrator sees the projects available to them in a single panel. However, the editor of a specific brand does not have access to content from other sites.
This approach is suitable for agencies, franchises, international companies, and brand groups. The number of websites can be expanded without deploying a new administrative system for each domain.
CMS architecture and development technologies
The technology stack is selected based on the workload, existing infrastructure, integration requirements, and the support team's capabilities. CMS development begins with the data and module architecture, and specific frameworks are selected to meet these requirements.
Seo-Gen uses Express API, Next.js, PostgreSQL, Redis, and MinIO. The components run in Docker, and Caddy handles external access and TLS for the production infrastructure.
Backend and database
The backend is responsible for business logic, authorization, data processing, and interaction with external services. The API separates the admin panel and public website from direct access to the database.
PostgreSQL is suitable for structured data and complex relationships between entities. Redis is used for caching and tasks where fast access is more important than persistent storage.
Files and images can be stored separately in MinIO object storage. This approach simplifies media management and avoids overloading the main database with binary files.
Frontend and server rendering
The public site, built on Next.js, can use SSR so that the server delivers ready page markup to the search engine crawler. Content is accessible without waiting for the main client-side logic to execute.
Server-side rendering is beneficial for SEO, but it doesn't replace proper indexing architecture. Canonicals, meta robots, response statuses, and internal links still need to be formed correctly.
The administrative frontend is separated from the public website. This allows the CMS interface to evolve independently of the client's project design.
CMS development in PHP, Yii and Yii2
PHP CMS development remains a popular approach thanks to the wide selection of frameworks and specialists. Building a CMS in Yii can be justified if a team already works with this technology and an existing project is built on its components.
Building a CMS on Yii2 is used in projects where the stack and architecture are based on Yii2. However, the choice of a specific framework should be based on the project's requirements, not on a search query or the developer's personal preferences.
There are also simpler tasks, such as a custom PHP blog CMS, where a small in-house system for publishing content is enough. The architecture for such a project will be significantly simpler than for a corporate multisite CMS.
Should you tie your CMS to a specific framework?
While a framework influences development and support, what's more important to a business is the stability of the architecture and the ability to find specialists for further development. The technology should be selected after defining the functions, workload, and integrations.
If the existing infrastructure is already built on a specific stack, maintaining it can reduce integration costs. For a new project, the team can select technologies based on SSR, API, database, and scalability requirements.
Locking in to a rare or outdated solution increases support risks. Therefore, when designing, we evaluate not only the current development speed but also the system's lifecycle.
Custom CMS template and individual web design
A custom CMS template defines the structure of a specific page type, but the content itself is stored separately. A single template can be used by dozens of pages, each with its own text, images, and SEO settings.
Custom CMS web design is built around a design system and reusable components. This approach helps maintain a consistent interface without copying markup for each new page.
Page templates
A template defines the composition and order of blocks for a specific page type. For example, a service page might contain a hero section, benefits, steps, FAQs, and a form, while an article might use a different structure.
Page-specific values are stored in its fields. Interface labels are stored in language dictionaries, so the block code doesn't contain hardcoded strings specific to a single site.
If the structure of all pages of a given type needs to be changed, the template is updated. The content remains in the database and does not require manual transfer.
Custom design
CMS website development can include transferring an existing design or implementing Figma mockups. The grid, typography, margins, hover states, and mobile version are reproduced on the public website.
The design of a specific project shouldn't change the overall business logic of the CMS. Colors and visual parameters are best stored in design system tokens so that theme updates don't require component edits.
This approach is especially convenient for a multisite platform, where different sites run on a common CMS but look completely different.
Why shouldn't design be linked to content logic?
When content is tightly bound to the HTML of a specific template, a redesign becomes a data migration. Separating information and presentation allows the same content to be used even after a visual overhaul.
The editor works with entities and fields, and the frontend determines how they are displayed. This simplifies the creation of new themes, mobile interfaces, and additional public applications.
This architecture also helps with site migration. Data can be imported separately, and then the new interface receives it through the general CMS rules.
Ready-made CMS or developing your own CMS: which to choose?
The choice depends on the project's complexity, budget, and development plans. Ready-made platforms are well suited to standard tasks, while a custom CMS is designed for projects with unique requirements for data, roles, and integrations.
Before development, it's useful to compare both approaches across several criteria. This assessment helps understand where a custom system truly justifies the additional development effort.
| Criterion | Ready-made CMS | Custom CMS |
|---|---|---|
| Launch speed | Usually higher due to ready-made functions | Depends on the scope of design and development |
| Starting price | Usually lower for a standard site | Higher due to custom architecture |
| Custom logic | Limited by platform architecture and modules | Designed to suit company processes |
| Scaling | Depends on the system chosen | Taken into account when designing architecture |
| Integrations | Through ready-made plugins or API | Developed for the required data exchange |
| SEO | Depends on CMS, theme and extensions | Rules can be embedded into the core |
| Multisite | Features may vary by platform. | The structure is designed for a network of sites |
| Support | Community, plugins, and third-party experts | Development team and project documentation |
If a project fits within the standard model of a ready-made system, custom development may prove unnecessary. When platform limitations regularly require workarounds, it's worth calculating the cost of a custom CMS and comparing it with the subsequent costs of customization.
Migrating an existing website to a custom CMS
Migration is necessary for projects that already have traffic, content, and working URLs. The main goal is to transfer data without losing the site structure and accumulated SEO signals.
The creation of a website's CMS can be combined with a design transfer or subsequent redesign. The public site and the data are migrated independently, so the project can be migrated to the new system according to a prepared plan.
What can be transferred?
Pages, articles, products, categories, images, documents, and other data are migrated to the new CMS. If the old database structure is accessible, most of the information can be imported automatically.
Users and related entities are also migrated if this is acceptable from a security perspective. Passwords require separate verification, as their storage method depends on the legacy system.
The design can be reproduced on a new platform or replaced with a new interface. The key is to ensure that the content transfer is independent of a specific visual theme.
How to maintain SEO during migration?
If the URL can be preserved, this is usually the best option for important landing pages. When the address changes, the old URL should point to the corresponding new page via a 301 redirect.
Along with the content, the Title, Description, H1, canonical, and other SEO parameters are transferred. After launch, hreflang, sitemap, robots.txt, internal links, and response codes are checked.
It's a good idea to prepare a redirect map before switching your site. After the launch, you should check the new 404s and ensure that the search robot is accessing the pages you intended to index.
Is it possible to create a CMS yourself?
Building a CMS yourself is suitable for learning and small internal projects. Such a project helps you understand routing, CRUD operations, databases, authorization, and the operating principles of the admin panel.
A search for "CMS creation tutorial" yields many examples of small systems implementing pages, users, and an editor. A production platform requires significantly more security and operational mechanisms.
What do you need to create your own CMS?
A minimal system should store data, authorize users, and provide them with an editing interface. It is also necessary to define the page structure, roles, access rights, and publishing rules.
A real project will also require an API, file storage, backups, and monitoring. SEO includes meta tags, canonical tags, sitemaps, robots.txt, and correct response statuses.
As a project grows, content versions, change history, integrations, and background task processing are added. These are the aspects that most often differentiate a production CMS from a tutorial example.
Why is a simple tutorial CMS different from a production system?
A tutorial system typically demonstrates basic CRUD: create a record, open it, edit it, and delete it. This is sufficient for demonstrating the principle, but a business needs access control, error recovery, and predictable data updates.
A production CMS must withstand external service failures, user errors, and code updates. This is achieved through logging, backups, database migrations, and separate development environments.
Documentation and a clear deployment process are also required. When multiple developers work on a system, Git history and pre-production change review become essential for stable operation.