Admin panel extension: adding SEO service pages

Budget: 4000 UAH Deadline: 4 days

Hello, Denis! 👋

I am ready to help you with the implementation of the "Services" section and the ability to create SEO service pages through the existing admin panel.

I have reviewed the task. The project is clear: it is necessary to add a separate content type "Services," integrate it into the admin panel similarly to the blog, and ensure the creation, editing, publication, and SEO configuration of commercial pages without developer involvement.

I have over 10 years of commercial experience in web development and practical experience with Java, Spring Boot, MySQL, and Thymeleaf in monolithic projects. I have worked with admin panels and CRUD modules, and I know how to carefully reuse existing architectural solutions.

🔧 I will:
— Add a separate "Services" section in the admin panel with independent CRUD;
— Implement the creation/editing of a service page with fields: Title, URL (slug), H1, SEO Title, Meta Description, SEO Keywords, Main Content, Image, Status (Draft/Published);
— Connect/reuse the existing visual HTML editor to support formatting, H2–H6, lists, images, and links;
— Implement the generation of a unique URL for each service and automatic opening of the page by URL using a template (existing or new) and responsive display;
— Add SEO settings (Title, Description, H1, optionally Canonical and Open Graph) and a list of services in the admin panel with search, editing, deletion, and status change.

✅ I will do it carefully, taking into account the reuse of the current blog implementation and minimal changes to the architecture.

🤝 Always available for discussing details and providing prompt support.

🌐 My portfolio with recent cases:
https://mrnko.com

💼 Freelancehunt profile:
Freelancehunt

🤝 I would be happy to discuss the details, answer your questions, and offer the best solution for your project. Expand

Budget: 27000 UAH Deadline: 12 days

700 UAH for such a task is an unrealistic budget. Regarding the timeline, I would estimate 10-12 working days, with a cost of 48,000 UAH for the first working version with an admin panel, database, routing, SEO fields, and page publication.

I would implement it through a separate entity for services and, if the current architecture allows, through a more general mechanism for SEO page types. That is, not just copying the blog, but extracting common parts - slug, status, SEO, editor, images, display template. The database will likely need tables for service_pages, SEO fields, publication status, image relations, and if we are planning for the future, a table for content_types or page_types. It seems this is exactly the case where a penny-wise person pays twice - it's better to lay out the model properly once than to create separate hacks for each page later on.

Regarding the implementation, I see it as follows:
> audit of the current blog, entities, repositories, Thymeleaf templates, and admin screens
> design of tables and MySQL migrations
> CRUD for the Services section in the admin panel
> reuse of the existing visual editor
> public routing by slug and service page template
> SEO - Title, Description, H1, Canonical URL, Open Graph
> list of services, search, editing, deletion, status change
> testing on VPS Ubuntu with Apache2 reverse proxy

Two things need clarification:
> Are the 13 blocks of the page currently hard-coded in Thymeleaf or is there already a separate structure of blocks in the database?
> Should new types of SEO pages be created by the administrator entirely from the interface, or is it sufficient to lay down a general mechanism in the code for the following sections?

Similar works by Ingello:
> https://business.ingello.com/platforma - a platform with admin roles, data management, and business logic
> https://business.ingello.com/forma-bpm - a modular approach to processes and managed entities
> https://business.ingello.com/forma-crm - an example of a complex admin system where data structure and stability are important

The main page for system development - https://systems-fl.ingello.com

To start, I need access to the repository, a dump or MySQL schema, test access to the admin panel, an example of the current static service page, and a deployment method on VPS. After reviewing the code, I will be able to say more accurately whether we are creating a full-fledged universal mechanism or if we are carefully extracting the services section without unnecessary engineering acrobatics. Well, yes, sometimes architects also try not to complicate things. Expand

Budget: 700 UAH Deadline: 1 day

Hello!
I am ready to take on your project and will complete it urgently.
I have extensive experience with similar tasks, so there will be no difficulties.
If I have piqued your interest, feel free to write; I am happy to collaborate!

Budget: 3000 UAH Deadline: 1 day

Denis, this task can be solved by extending the existing CMS logic of the blog: a separate entity/section "Services," a common CRUD mechanism, custom slug URLs, SEO fields, statuses, and rendering through Thymeleaf. For the database, I will add a services table or universal content/SEO tables so that new types of pages can be created without code modifications. I have experience with Spring Boot, MySQL, and monoliths. I am ready to quickly analyze the current blog first and propose an optimal scheme.

Budget: 24000 UAH Deadline: 10 days

Good day! The task is completely understood.

How the task will be implemented:
To allow you to create new types of pages without a developer in the future, we will move away from the strict binding to the entity "Service." A universal page module will be created. To separate content, we will introduce an entity (Blog, Service, etc.). This will allow managing any future SEO pages through one table and a single mechanism.

Dynamic blocks:
The universal content block will connect the existing WYSIWYG editor from the blog. A basic Thymeleaf fragment (th:replace) will be created for the 9 static blocks of the service template, where unique service data will be dynamically substituted.

Routing (URL Generation):
I will configure a dynamic GetMapping controller to handle nested URLs. Validation of the slug for uniqueness will be implemented.

Database changes (MySQL):
Table pages (or an extension of the current articles table): adding fields for SEO, status, and page type (page_type).

Table page_types (reference): for storing types (blog, services) — will ensure the creation of new types in the future.

Indexes: Creation of a unique index on the combination of URL/Slug for quick page search in the database and exclusion of duplicates.

Terms and Budget:
Deadline: 7–10 working days.

Cost of work: 18,000 – 24,000 UAH (depending on the current architecture of Spring Security and the blog code).

Ready to start. For an accurate estimate and to begin, access to the code repository is needed. Can you send it? Expand

Budget: 5000 UAH Deadline: 4 days

Good day.

I will implement the task by reusing the architecture of your blog. To meet the requirement for creating new types of SEO pages without code modifications in the future, I propose a hybrid approach to the database. The main SEO attributes will be strict columns, while the content of thirteen blocks will be stored in JSON format. This will allow for flexible changes to the page structure without altering the database schema.

How the task will be implemented:

Creation of a new controller and Spring Boot service for the services entity.

Addition of a section in the admin panel on Thymeleaf with the integration of your visual editor to support HTML markup and headings.

Configuration of Spring MVC routing for proper handling of multi-level URLs.

Implementation of Canonical and Open Graph tag output in templates.

Changes to the database:
Creation of a services table with fields: id, title, slug, h1, seo_title, meta_description, seo_keywords, content_blocks (JSON type), image, status. A unique index will also need to be added to the slug field for quick page searches by URL.

The implementation timeframe will be about 5 days, and I estimate the cost of work at 8000 UAH. I am ready to start studying the source code. Expand

Budget: 700 UAH Deadline: 5 days

Need to move the creation of SEO service pages from manual code to the same admin panel where the blog currently resides.

I will do it this way: a new table `services` in MySQL (slug, h1, seo_title, meta_description, keywords, content, status, og fields), a Spring MVC controller with mapping `/admin/services/**` and public routing `/visa/**` through PathVariable. In the Thymeleaf template, I will connect the same WYSIWYG editor as in the blog, so the administrator doesn't have to relearn. The services list will include search, status change, editing, and deletion.

Please show the structure of the current blog articles table and how the routing for public service pages is currently organized (static files or a separate controller)?

Budget: 22000 UAH Deadline: 7 days

We already have a practically ready similar solution for admin panels and CMS modules, which can be quickly adapted for your Spring Boot project and launched ))

In terms of timing, I would estimate 5-7 working days.

Regarding the budget - starting from 22,000 UAH, because 700 UAH will likely not even cover a careful analysis of the current blog and the database schema.

Briefly on implementation - I would not just duplicate the blog, but extract a common mechanism for pages with content types, so that later we could add not only services but also other SEO pages without new code modifications.

> Analysis of the current blog entities, controllers, Thymeleaf templates, and editor
> Addition of tables for page types, the pages themselves, SEO fields, and blocks if necessary
> Admin section for Services with a list, search, creation, editing, deletion, and statuses
> Public routing by slug like /visa/usa/business-visa-usa
> SEO title, description, H1, canonical, and Open Graph
> Reuse of the existing blog editor if it is properly separated from the article entity

Look, there’s a nuance - you specified 13 blocks on the page, of which 4 are dynamic and 9 are static. We need to clarify whether these 4 blocks should be edited as separate fields in the admin panel or if a general HTML editor with markup preservation is sufficient?

Another question - do the services already have a ready Thymeleaf template, or does it also need to be designed and adapted for mobile devices?

Similar cases from Ingello
> https://business.ingello.com/forma-crm - admin panels, roles, entities, and data management
> https://business.ingello.com/platforma - corporate platform with extensible logic and modules

Main page for system development
> https://systems-fl.ingello.com

In touch, we can keep it simple - first, we look at the current implementation of the blog, and after that, we provide an accurate final estimate =) Expand

Budget: 3000 UAH Deadline: 3 days

Good day!

I have reviewed the technical specifications. The task is clear: to add a separate section "Services" to the existing admin panel with full CRUD and publication of SEO pages by slug, maximizing the reuse of the current blog implementation.

How I would implement it

First, I will analyze the current blog module: Entity, Repository, Service, Admin Controller, Thymeleaf templates, content editor, image uploads, SEO fields, and routing by slug. Then, I will extract the common logic into a base layer (publication, drafts, slug, SEO, media upload), and make "Services" a separate content type — independent of the blog, but on the same architecture.

In the database — a new entity (for example, service_page or a universal cms_page with a content_type field). Fields: title, slug, H1, title, meta description, keywords, canonical, OG fields, status, main image, content. For 13 blocks of the page (4 dynamic, 9 static) — either a JSON field with the structure of blocks or a separate table page_blocks with type and order. The second option is more convenient if different types of SEO pages are needed later without code changes — this is exactly your point about a unified CMS mechanism.

On the front end of the public part — one Thymeleaf template for services: static blocks are embedded in the template, dynamic ones are substituted from the database. The editor is the same as in the blog (TinyMCE/CKEditor or whatever is already in place). In the admin panel: list of services, search, create/edit/delete, change status. URL format /visa/usa/business-visa-usa — through a hierarchical slug or a url_path field with uniqueness validation.

SEO: the same meta tags as in the blog, plus canonical and Open Graph in the layout. Sitemap and robots — similar to articles, so that new pages are indexed in the same way.

Database changes (briefly)

A new table for services (or universal CMS pages), if necessary — a table for content blocks, indexes by slug and status, links to media/images. Migrations through Flyway/Liquibase, if they are already in the project.

Timeline

After access to the repository and a short audit: an estimate of 2–3 weeks when reusing the blog; 3–4 weeks if we immediately lay down an extensible CMS mechanism for new types of pages in the future.

Cost

I will clarify after reviewing the code and admin panel — the volume heavily depends on how much the blog has already been extracted into reusable components and how the template of 13 blocks is structured.

What is needed to start

Access to Git, a test/staging server, an example of 1–2 ready service pages as a reference for layout, a description of 4 dynamic blocks (which fields the admin edits).

I am ready to discuss the details and look at the project. Expand

Budget: 10000 UAH Deadline: 7 days

1. Analyze the current implementation of the blog and reuse the existing architecture for the new section "Services."
2. Implement a full CRUD with support for SEO fields, slug, publication statuses, and using the existing editor.
3. Configure automatic page rendering by URL through Thymeleaf and make the structure suitable for adding new types of content in the future without significant changes to the code.

First of all, it is important to assess how well the current blog architecture allows for the reuse of existing modules. If it is built correctly, most of the functionality can be implemented without code duplication.

We can discuss the details, review the current implementation, and after analysis, determine the exact scope of work and timelines.

Budget: 1000 UAH Deadline: 2 days

Good afternoon! We have experience working with the Java and Spring Boot stack, so we will quickly expand your admin panel for managing SEO service pages. We will implement the necessary entities in the MySQL database and configure the display through Thymeleaf, taking into account the current architecture of the monolith. We are ready to start working on the task soon.

Budget: 1234 UAH Deadline: 1 day

Hello, I have relevant development experience.
Message me privately, we will discuss the details.
I will be happy to help you!

Budget: 7000 UAH Deadline: 8 days

I can develop what is needed and complete the task; I have experience and am ready to take it on after seeing the project, of course, one of the works is https://pprintdim.com.

Budget: 700 UAH Deadline: 1 day

Hello, Denis!
For "Services," the logical approach is not to copy the blog code line by line, but to extract the common part of content management (title, slug, SEO fields, publication status, editor) into a reusable layer, and to make the blog and services different content types on top of this layer. This also addresses the point about new types of SEO pages without code modifications in the future - a separate CRUD module won't be needed for the new type, just the configuration of the field set.

Regarding the database: most likely a separate table for services (or a common table content_pages with a type field), plus a table for 4 dynamic blocks. I will provide the exact schema after I see the current structure of the blog articles table - it makes more sense to replicate the pattern you already have working than to come up with a new one.

A separate question about the structure of the service page: are 9 static blocks out of 13 a common design template, the same for all services (only the text and images change), or can the structure of the blocks differ for different services? This affects whether to implement a flexible block constructor or if a fixed template with variable fields will suffice.

For the nested URL like /visa/usa/business-visa-usa, we need to understand how the blog pages are currently routed to decide whether to create a hierarchy of service categories or a composite slug from several fields.

To provide an exact timeline and cost, I need access to the repository or a backup of the project. I will set it up on my end and see how the blog and admin panel are actually structured; I won't give blind estimates. Roughly, such a task (new content type, CRUD in the admin panel, SEO fields, URL generation) takes 3-7 working days depending on how clean and reusable the current blog code is - I will be more precise after reviewing it.

I am ready to start as soon as you provide access to the repository or backup. Expand

Budget: 12000 UAH Deadline: 4 days

Hello! Manual creation of SEO pages is slowing down traffic. I will quickly expand your Spring Boot monolith with a new CRUD module "Services."

I run the agency KenoStudio. We work with custom backends, so I will implement the module cleanly, securely, and with maximum reuse of your current architecture.

Responses in essence:

Implementation: I will create a new MVC binding (Entity, Repository, Controller) to isolate from the blog. For the admin panel in Thymeleaf, I will connect your current WYSIWYG editor. I will set up dynamic routing for correct generation of nested URLs (e.g., /visa/usa/slug).

DB (MySQL): I will add one new table service_pages with the necessary fields (title, slug, h1, seo_title, meta_description, content, image_url, status).

Timeline: 3–4 working days.

Cost: $300–$400.

I suggest a short call for 5 minutes to look at the repository structure and get started. Expand

Budget: 3000 UAH Deadline: 3 days

Hello.

I am ready to take on the task. From the description, it is clear that it is not just about adding a couple of fields, but creating a proper section for SEO service pages in the existing admin panel.

First, I will look at how the blog is currently implemented: entities, controllers, Thymeleaf templates, editor, image uploads, SEO fields, and routing. After that, we can maximize the reuse of the current logic and create a separate independent section for "Services" based on it.

I see the implementation plan as follows:

— add a separate entity for services in the database;
— create a table services / service_pages with fields: title, slug, h1, seo title, meta description, keywords, content, image, status, canonical, OG fields, and creation/update dates;
— implement CRUD in the admin panel: list of services, search, creation, editing, deletion, publication/draft;
— connect the existing visual editor that is already used for the blog;
— implement the output of published pages at the required URLs;
— configure SEO meta tags on the Thymeleaf side;
— check responsiveness and correct display on the site;
— if necessary, lay the groundwork for a more universal mechanism so that in the future new types of SEO pages can be added without constant code modifications.

All technologies are suitable: Java, Spring Boot, MySQL, Thymeleaf, HTML/CSS/JS, working with VPS on Ubuntu and Apache2.

Approximately in terms of deadlines: 5–10 working days, depending on the current project structure and the complexity of the service templates.
Regarding the cost, I will be able to provide a more accurate estimate after reviewing the code, but preliminarily, it can be estimated from ___ to ___.

I am ready to start with an analysis of the current blog implementation and then provide an accurate assessment of the deadlines, database, and volume of work. Expand

Budget: 1500 UAH Deadline: 7 days

Good day!

I have experience working with Java, Spring Boot, MySQL, Thymeleaf, and Linux. I will implement a separate CRUD module "Services" with maximum reuse of the existing blog logic: new tables (or extension of the current model), separate routes, templates, SEO fields, URL generation, content editor, status management, as well as laying the foundation for creating new types of content in the future without significant code changes.

Budget: 2000 UAH Deadline: 2 days

Hello! The task is clear, I have good experience with monoliths on Spring Boot + Thymeleaf. Since the functionality is similar to the existing blog, I will do everything neatly based on your current architecture to avoid unnecessary code.

Technically, I will create a new table services in the database with all the necessary SEO fields, add the corresponding Entity, Controller, and Service. For the admin front, I will adapt the existing blog template with the same editor, and on the service page itself, I will embed static blocks directly in HTML and pass dynamic ones through the model.

This will take 1-2 days including deployment on your Linux VPS. However, a budget of 700 UAH for developing a full-fledged CRUD module in Java is frankly underestimated. I am ready to implement this task qualitatively for 2000 UAH. Write to me, I would be happy to work on your project!

Budget: 10000 UAH Deadline: 7 days

Hello. I have extensive experience in website development. What should the services page look like?