TECHNOLOGY · DRUPAL
Everything depends on how the content types were defined.
Drupal gets configured long before anything is published. Both the wins and the problems come from decisions taken when setting up content types, views and multisites.
Let's talk about your project- +15
- years working visibility for large brands
- +200
- projects with our own data behind them
- 48 h
- to reply, at most
Brands that have trusted Laika
Some of these situations may sound familiar
Views generate pages nobody decided to index
Filtered, paginated listings that get crawled and add nothing.
Several sites carry similar content
Multisite by country or brand, with repeated pieces and no relationship signals.
URL aliases have piled up
Patterns changed over the years and old addresses still responding.
Metadata depends on the content type
Some types generate it well and others leave it empty.
Every change needs the technical team
What's editable and what requires configuration are two different lists, and it helps to keep them apart.
The scope
We review content types, views, URL aliases, multisite configuration and metadata generation, and define what's solved by configuration and what needs development.
We work on the judgement and the spec: what needs to change on Drupal, in which order and how it gets checked afterwards. Your team or your development partner implements it, and we review that what reaches production is what was agreed.
The areas of work
Four fronts that come up again and again on Drupal projects. Depending on where your project stands, some weigh more than others.
Content types and fields
Make each type generate what it needs without manual work.
See the detail
- Inventory of types and available fields
- Generation of titles, descriptions and canonicals
- Structured data per type
- Missing fields and default values
Views, listings and indexing
Decide which listings exist for search engines.
See the detail
- Map of published views and the pages they generate
- Indexing, pagination and filter rules
- Internal linking from listings
- Crawl tracking
URL aliases and redirects
One address per content and a tidy history.
See the detail
- Review of alias patterns per type
- Old addresses still alive
- Redirect and cleanup plan
- Criteria for new content
Multisite and languages
Give each market its own site without them cancelling each other out.
See the detail
- Relationship between sites, languages and shared content
- Language and country signals
- Content that must differ by market
- Publishing governance across teams
Who does it?
A small team with real hours inside Drupal. MJ leads the strategy and the specialist who reviews your platform is the one who explains it to you.
Why Laika?
Knowing the platform changes the conversation: you stop arguing about whether something is possible and start deciding when it ships.
We've worked on Drupal projects long enough to know where its real limits are and what a second pass at configuration can solve.
We look at the configuration, not just the pages
On Drupal the cause of almost everything is how the content type was defined, and that's where it gets fixed.
You always talk to whoever decides
There's no management layer between you and the judgement. MJ leads the strategy and the specialist team executes.
If we're not the right fit, we say so
Even if that means there's no project for us, we'd rather say so before signing.
Frequently asked questions
Do you still work with Drupal 7?
Yes, though in that case part of the conversation is when to upgrade and what to tidy up first.
Do you need admin access?
Read access to the configuration plus Search Console is enough. We don't make changes ourselves.
Can you support a version migration?
Yes, and it's the best moment to review content types and aliases.
Tell us about your project
Knowing which version you run, who develops it and what worries you is enough for us to say whether it makes sense to talk.
Shall we talk about your platform?
We look at your project before proposing anything and tell you what can move without fighting the roadmap.
We look at your project before proposing anything. Reply within two working days at most.
Let's talk about your project