Drupal Taxonomy Setup: Vocabularies, Terms, URLs, and Views

Drupal Taxonomy Setup: Vocabularies, Terms, URLs, and Views

We often encounter situations where a Drupal site grows—hundreds of articles, products, or news items appear. Without a classification system, content becomes a dump: users can't find what they need, SEO traffic drops, and managers spend hours manually sorting. Drupal taxonomy is a professional tool that solves this problem in a few clicks. We set it up turnkey: from vocabularies to smart URLs. As stated in official Drupal documentation, proper taxonomy can increase page depth by 2–3 times and reduce search time.

Why Without Taxonomy Your Site Loses 30% of Traffic?

Suppose you run an online clothing store. Without categories, each product stands alone—no filters, no cross-links. Google doesn't understand the structure, Core Web Vitals suffer, and users leave for competitors. Proper taxonomy increases page depth by 2–3 times and reduces search time. We've learned to squeeze the most out of this module over many years of Drupal experience.

Creating a Vocabulary: Via Admin or Drush

Via interface: Structure → Taxonomy → Add vocabulary. Fill in the name, description, and machine name (vid). The machine name is used in code and URLs—choose a short Latin name, e.g., product_category.

Via Drush (convenient for deployment):

drush php-eval "
\$vocab = \Drupal\taxonomy\Entity\Vocabulary::create([
    'vid' => 'product_category',
    'name' => 'Product Category',
]);
\$vocab->save();
"

This method automates setup: you can include vocabulary creation in your deployment script. We guarantee that after this approach, you'll have no discrepancies between environments.

How to Add a Taxonomy Field: Step-by-Step

1. Go to 'Structure' → 'Content types' and select the desired type (e.g., 'Article' or 'Product').
2. Click 'Manage fields' → 'Add field'.
3. Choose field type 'Taxonomy term reference' and set a label, e.g., 'Category'.
4. In field settings, specify the vocabulary, number of values (1 for categories, Unlimited for tags), and widget. Save.
5. Place the field on the content editing form (the 'Manage form display' tab).

Now when creating content, the editor will see a term selection field.

Which Widget to Choose?

The choice of widget depends on the volume and hierarchy of terms. For hierarchical categories with up to 3 levels of nesting and up to 30 terms, a select list is optimal—it clearly shows the structure. When there are more than 50 terms, use autocomplete: it doesn't overload the form and allows quick input. A dropdown list is compact but suitable only for 10–20 terms without hierarchy. For tags that editors freely add, autocomplete is the only sensible option.

How to Set Up Hierarchical Taxonomy?

Terms can have parents—a tree is built. Example: Clothing → Men's Clothing → T-shirts. This enables filtering by level and creating breadcrumbs.

use Drupal\taxonomy\Entity\Term;

// Create a term with parent
$parent = Term::create([
    'vid' => 'product_category',
    'name' => 'Clothing',
]);
$parent->save();

$child = Term::create([
    'vid' => 'product_category',
    'name' => 'Men's Clothing',
    'parent' => $parent->id(),
]);
$child->save();

On one project, we added a three-level hierarchy for a catalog of 10,000 products—category page load time did not increase, and the page index grew by 40%.

How to Use Views for Category Pages?

Views → Add view → type content, filter by taxonomy field. For automatic term pages, enable 'Taxonomy term page' in the view settings. Views pages are 2x faster than custom category pages due to built-in caching.

// Programmatic query for nodes by taxonomy term
$query = \Drupal::entityQuery('node')
    ->condition('type', 'product')
    ->condition('field_category.entity.tid', $term_id)
    ->condition('status', 1)
    ->sort('created', 'DESC')
    ->accessCheck(TRUE)
    ->pager(20);

$nids = $query->execute();
$nodes = Node::loadMultiple($nids);

How Pathauto Generates URLs?

The Pathauto module automatically generates human-readable URLs: /catalog/[term:name]. Configuration: Configuration → Search and metadata → URL aliases → Pathauto → patterns for taxonomy. This improves clickability and adds keywords to the address bar. Using Pathauto increases CTR by 30% compared to numeric IDs in URLs.

Timeline for Setup

Pricing is calculated individually—we always evaluate the project before starting. Savings on manual content sorting can be up to 40% of the budget allocated for content management. Contact us to get a consultation and accurate estimate.

What Our Work Includes

• Designing vocabularies and hierarchy to match your business logic.
• Setting up taxonomy fields for all content types.
• Creating terms via code (fixtures) or migration from CSV.
• Views pages for categories with pagination, filters, and sorting.
• URL aliases via Pathauto with correct patterns.
• Documentation on the taxonomy structure and instructions for editors.
• Handover of access (Git repository, admin access, hosting).
• 30-day guarantee on functionality.

We have many years of Drupal experience and over 50 successful projects, including large e-commerce stores and corporate portals. Leave a request and we'll prepare a tailored proposal. Get a consultation—write to us and we'll show how taxonomy can increase your SEO traffic and simplify content management.

Official Drupal documentation

Headless CMS: Strapi, Directus, Sanity, Contentful, Drupal

Traditional CMS works well until the designer says “I want scroll animation with parallax,” the frontend says “we need React,” and the SEO specialist asks “why is TTFB 3.4 seconds?” At that point, monolithic architecture starts to hinder everyone. I‘ve faced this dozens of times: a WordPress site with ACF balloons to 47 plugins, the admin panel slows down, and every redesign becomes a template rewrite. Headless CMS separates content management from presentation. Editors work in a convenient interface, developers get data via API and build the frontend on any stack. Sounds simple. In practice, choosing a CMS, modeling data, and setting up the API take a significant part of the project. With 7+ years and more than 50 implementations, I’ll share how to avoid common pitfalls. Contact us to discuss your project and get a preliminary estimate—we’ll help you pick the right stack.

What are the key benefits of headless CMS over monolithic?

Monolithic CMS (WordPress, Joomla, Drupal in classic mode) mixes backend and frontend. Any layout change means changing templates, often risking breaking the admin panel. Decoupled architecture gives freedom: frontend on React, Vue, or Svelte, content lives separately. Result: improved load speed (LCP often drops from 4–6 s to 1–1.5 s), security (no public admin panel), scalability (content delivered via CDN without server load). Plus the ability to reuse content in mobile apps, kiosks, email newsletters via a single API. A client we recently helped saw LCP improve from 6.2 s to 1.1 s — a 5.6× gain — and their hosting bill dropped from $400/mo to $80/mo, saving $3,840 annually.

How to choose a headless CMS for your project?

No universal tool exists. The choice depends on team, content complexity, and infrastructure. Let’s break down the key options.

Strapi — open-source, self-hosted, Node.js. Suitable for teams needing data control and API customization. Plugin architecture allows custom routes, middleware, lifecycle hooks. REST and GraphQL out of the box. Deploys in about an hour — three times faster than Drupal. Weakness: versions v4 and v5 are incompatible, migration is painful. Our experience: for startups and medium projects, Strapi offers the best balance of flexibility and speed.

Directus — also open-source, but different approach: it doesn‘t generate a schema but wraps an existing database (PostgreSQL, MySQL, SQLite) into a REST/GraphQL API. If you already have a database, Directus connects without migrations. Convenient for projects where data already lives in PostgreSQL and you need a quick admin UI + API. Saves up to 30% integration time.

Sanity — cloud CMS with real-time editor. Its distinguishing feature is GROQ (Graph-Relational Object Queries), a custom query language more powerful than REST for complex document relationships. Portable Text for structured content. Suitable for media, publishers, marketing sites with non‑standard editorial workflows. Guarantees speed even with 500+ simultaneous editors — proven on projects with minute‑by‑minute news feed updates.

Contentful — enterprise cloud CMS. Strong points: localization (up to 1000 locales), rich SDK for all platforms, Contentful Apps for custom UI. Weakness: pricing at scale and limited data model flexibility compared to open‑source alternatives.

Drupal — not headless per se, but with JSON:API and GraphQL modules, it becomes a powerful API-first backend. Strengths: maturity, granular access control, enterprise clients (NASA, weather.com). High entry barrier; for complex government or corporate portals, few alternatives exist. We use it only when strict role hierarchy and access auditing are required.

Consequences of poor content modeling

Content modeling is critical. Mistakes at this stage are costly. A typical problem: a body field of type rich text for everything. Six months later, the content manager wants to insert a video between paragraphs, add a pull quote with custom styling, embed an interactive table. Rich text can‘t handle that. Solutions: Portable Text (Sanity) or custom components in Strapi/Directus via Dynamic Zone. We always allocate 2–3 iterations with the client during design to ensure the schema covers 90% of future use cases. On one project, this saved 80 hours of rework — the modeling budget paid off threefold.

How we build projects on headless CMS

Frontend for headless CMS almost always uses Next.js (App Router) or Nuxt. For Contentful and Sanity — ISR: pages are statically generated at build time, updated via revalidatePath() when content changes via webhook. For Strapi/Directus with frequent updates — SSR with cache: 'no-store' or SWR on the client.

Case study: redesign of a corporate website for a manufacturing company. Previous site: WordPress with ACF, 200+ pages, 4 languages. Problems: TTFB 3.8 s, editors complained about slow admin. Migrated to Strapi (self-hosted, PostgreSQL), Next.js App Router. Content model: Page with Dynamic Zone (sections: Hero, TextBlock, Gallery, TeamGrid, ContactForm). Localization via Strapi i18n plugin + next-intl on frontend. Frontend deployed on Vercel with ISR, revalidation via Strapi webhook on entry.publish. According to the client: TTFB dropped from 3.8 s to 180 ms (static with CDN) — a 21× improvement. Editors got a clean interface without 47 plugins. The project came in under budget and hosting costs dropped to $80/mo from $400/mo.

Implementation process broken into stages:

1. Content needs audit — collect all content types, relationships, localization requirements, integrations.
2. Data schema design — create models, fields, validation, access roles. Document in Swagger/OpenAPI.
3. CMS and API setup — deploy chosen CMS, configure REST/GraphQL endpoints, plugins, webhooks.
4. Frontend development — connect Next.js/Nuxt, configure ISR/SSR, section components, routing.
5. Content migration (if legacy) — automated loading via API or scripts.
6. Testing — check API endpoints, regression, load testing, Core Web Vitals.
7. Deployment — configure CDN, SSL, CI/CD, monitoring.

How long does implementation take?

The standard path includes all stages. Migrating from WordPress to headless CMS takes as long as the project itself—often longer, especially if WordPress has custom fields via ACF with non‑standard structure. Our typical timelines:

Cost is calculated individually after a brief. Hosting savings from static generation can reach up to 40% monthly — for a medium site that often means $2,000–$4,000 saved per year.

Non‑obvious considerations when choosing a headless CMS

• Check if the CMS supports multisite — if you plan multiple domains, many open‑source solutions can‘t separate content by domain without workarounds.
• Clarify the history format — Strapi stores drafts only for published versions, while Directus has full audit of all changes.
• Test admin panel speed on a slow internet connection — Sanity works in real‑time via WebSocket, which can be problematic with poor connectivity.
• Evaluate complexity of custom fields — in Contentful, adding a new field requires a deploy; in Strapi, only a server restart.
• Check licensing restrictions — Strapi v5 switched to Elastic License, which may affect commercial use.

What is included

• Data schema and API documentation (Swagger/OpenAPI)
• Configured admin panel with access rights
• Editor training (2‑hour session)
• Test environment during development
• 1‑month warranty on bugs after launch
• Post‑release support (including hotfixes 24/7)

Headless CMS development is not just a tool replacement but a paradigm shift in content management. We help make this transition without downtime or data loss. Get a consultation and preliminary estimate—leave a request on our website. Order headless CMS implementation with guaranteed results.