Development of portals and media sites
Portals and media are a direction of website development at Best Boost Partners for projects with many pages and many users: user portals, listing sites, news and sports publications. We build user accounts, tools for publication and moderation, and an architecture that holds heavy load. New pages reach the index quickly, and archives and tags do not create duplicates. You receive the project on your own servers, with source code, access details and instructions for editors and moderators.
What do we build for a portal or a media site?
User accounts and roles
Registration, login, profiles and personal accounts with the roles of user, author, editor, moderator and administrator. Every role sees only its own actions and data.
Listings and publications
Forms for adding listings or articles with required fields, photo upload and a preview. For media we build an editor with drafts, scheduled publication, authors and sections.
Moderation
New content passes a queue with automatic checks for spam, duplicates and banned words, then goes to a moderator. Decisions are written to a log, and rejected content does not reach the index.
Architecture for heavy load
We write portals on Laravel with caching, task queues and a search index kept apart from the main database. Before launch the project goes through load testing on the expected number of pages and visitors.
Fast indexing of new pages
A new page enters the sitemap and the internal linking blocks at the moment of publication. For news we add a news sitemap, article markup and feeds.
Archives and tags without duplicates
Editors create tags from an approved list, and a tag page opens to indexing once it holds enough material. Pagination, date archives and sorting have canonical addresses and indexing rules, so they do not compete with the main sections.
What do you get with a portal or a media site?
- A portal or media site on your servers with accounts, roles and a moderation panel.
- A description of the architecture: components, database scheme, caching and queues.
- A document with indexing rules for sections, tags, archives, pagination and user pages.
- A load testing report with the test conditions and the measured response times.
- Source code, access details and instructions for editors and moderators.
When is the development of a portal or media site needed?
- You are launching a listing site, a catalogue with user content or an online publication.
- The current portal slows down as pages and visitors grow, and the platform cannot be scaled any further.
- New publications take a long time to appear in search, while tag and archive pages fill the index.
- User content arrives faster than it can be checked by hand, and spam reaches the public pages.
Frequently asked questions
Why are portals written on Laravel and not on a ready-made CMS?
A portal has its own logic: roles, moderation rules, paid placements, search by many parameters. On a ready-made CMS this logic is assembled from plugins that conflict with one another and slow the site as it grows. On Laravel the logic is written for the project, and the load is managed with caching and queues.
How quickly do new pages of a portal get into search?
The speed depends on how often search engines crawl the site, and an exact time cannot be named. We shorten the path: right after publication a new page appears in the sitemap and in link blocks on pages that are already indexed. In the server logs we check that the crawler reaches new pages and does not spend its visits on archives and filters.
What do you do with pages created by users?
User pages are indexed only after moderation and only when they hold enough content of their own. Empty profiles, expired listings and duplicates have rules: close to indexing, redirect to a category, or leave with a notice and similar offers. The rules are written into a document before development starts.
Tell us about the project
Fill in what you already know. Blank fields are fine: we will clarify the rest in conversation.
Brief sent
Thank you. We will reply within one working day.
Preview mode: the form handler is not connected yet, so nothing was sent.