How to audit internal linking and crawl traps in Drupal with Entity Mesh
Entity Mesh is a Metadrop Drupal module that makes a site's internal link structure visible. It audits every node the way an anonymous crawler sees it, then aggregates the result into one exportable picture: where navigation breaks, where crawl budget leaks, and where language versions fall out of step. For a content-heavy or multilingual Drupal site, that turns internal linking from an invisible assumption into a measurable part of Technical SEO.
Every link is a navigation intentionStructuring content well starts with knowing how the site actually connects. Few Drupal modules give aggregated, site-wide information about content and its connections, so that picture is usually missing when decisions get made.
Entity Mesh was built to answer a specific question: how do nodes interconnect, and does the navigation they create match the one that was intended? If the goal is for a visitor to buy a product, the path from a landing page should lead to the product, not to the contact form. If the goal is a donation, the path should not end at the newsletter signup.
That makes internal linking more than a UX concern. It is also part of Technical SEO, because search engines follow internal links to discover content and to judge which…
How to automate WordPress-to-Drupal content migration with WordPress Migrate SQL
Some WordPress sites reach a point where the content model no longer fits the organization's needs. Custom content types, custom entities, and custom fields become necessary to represent internal data precisely, and Drupal supports all three, shaping that data with full flexibility.
Other sites reach that point because of AI. Drupal has built a strong AI ecosystem over recent years, enabling integrations of every needed type: content creation, accessibility checks, RAGs, among others. These are the two situations behind most WordPress-to-Drupal migrations: an architecture the site has outgrown, or an AI integration WordPress cannot support natively.
The challenge of migrating WordPress content to DrupalThe core challenge in a WordPress-to-Drupal migration is migrating the content itself. WordPress sites may host thousands of pieces of content that need to be moved to the Drupal site.
A full migration project runs through several phases: redesigning the site if needed, building the new architecture, and creating a Drupal node for every WordPress post or page. Creating the content is where the real work concentrates, since every image, every user, and every translation has to make it across, on top of adapting content to a different format defined by the new architecture.
A manual content migration is not viable due to its high costs and risks. Handled by hand, this work is prone to human error. A single error is easy to fix, but a…
Responsibility follows control
An AI model does not decide what data it can access, which tools it can use, or whether it can act without approval. People make those decisions at different points. Upstream, a model developer trains and tests the model and decides whether and how to release it. Downstream, a developer builds the model into a system, connects that system to data and tools, and decides whether a person must review its proposed actions before they take effect.
Those choices determine whether harm is possible at all. So when harm occurs, responsibility should fall on those who controlled the relevant choices. That responsibility may be shared: model developers control training and release, product builders control permissions and deployment, and users control deliberate misuse.
Responsibility should follow meaningful control.
That principle is missing from much of the debate over open-weight AI models, which often treats the decision to release a model as the only one that counts.
Axios recently reported that United States officials had considered measures that could restrict American companies from using Chinese open-weight models. Open-weight models make their trained parameters available for others to download, modify, and run on their own infrastructure, without going through the company that built them.
What’s the Deal with Schema
It’s not new and it’s not sexy, but Schema.org is getting a lot more attention these days. The reason is AI.
You’ve probably heard that Schema improves your AI search results — apply it to your site and voilà, better results. But what is it? How does it help with AI? And, more controversially, does it actually help at all?
World Wide Web Day: The Birth of the Web, And How Drupal Supports its Values
If you’re reading this article online, you’ve already experienced the impact of one of history’s most influential inventions. Chances are you’ve also visited several websites today to check the news, compare products, or fill out an online form.
Why We Contribute: The Philosophy Behind 1xINTERNET's Top-Tier Drupal Status
This is a guest post from the incredible team at 1xINTERNET, a Top-Tier Drupal contributor and digital agency headquartered in Frankfurt, Germany.
When the Drupal Association announced that 1xINTERNET had become one of the world's Top-Tier Drupal Contributors, it was a proud moment for the company. Reaching the highest level of contribution recognition places 1xINTERNET among a select group of organisations helping shape the future of one of the world's leading open-source content management systems.
Yet, ask anyone inside the company about the achievement, and you'll hear the same response: becoming a Top-Tier Contributor was never the ultimate goal.
Instead, it is the natural outcome of more than a decade of believing that if you build your business on open source, you should help build open source itself.
For over thirteen years, 1xINTERNET has invested in the Drupal ecosystem, not only by delivering digital platforms for clients, but by contributing code, maintaining projects, sponsoring community events, supporting governance, leading strategic initiatives and encouraging employees to actively participate in the community.
Today, the company sponsors more than 500 hours of Drupal contribution every month, actively supports more than 85 Drupal projects, has sponsored over 50 Drupal events, and has contributed to hundreds of issues across the Drupal ecosystem. Those numbers tell one story. The people behind them tell another.
Automatic Content Translation System
Teaching AI to Speed Up Accessibility Testing
To paraphrase the much used line about writing: I don't enjoy doing accessibility testing, but I like having done accessibility testing. When a site becomes more usable for everyone, I feel good. Users feel good. Clients feel good. (Regulators feel good.) The process of getting there can be very tedious.
Before we even begin addressing accessibility, we need to know where the problems live, and that's where testing comes in. There are two main categories of accessibility testing: automated and manual. Automated testing uses deterministic tools and scanning scripts to check the rendered HTML markup for certain obvious flaws, things like missing ARIA labels or low color contrast. Manual testing checks what those tools can't. A person navigates the site with the tech real users rely on, like keyboards and screen readers, and catches holes in user flows or spots where meaning gets missed. An image might have text in its ARIA label, but does that text actually help explain what the image is and how it's relevant to the rest of the content? Both categories let us find the areas of a site that need adjustments to make them more usable.
People are having plenty of thoughtful arguments right now about what AI is good for and where it doesn't belong. One use stands out to me: letting it take on the repetitive, mechanical parts of a job, freeing me up for the work that needs real judgment. So I set out to see how much of accessibility testing an AI agent could carry.
A Love Letter to the DDEV Community

I've been working on DDEV for years now, and there's something I don't say often enough:
You make this so worthwhile.
Stas and I love to get up in the morning to hear what you have to say, learn from your experiences, share our path together.
We feel so thankful to be creating something useful in collaboration with you.
All of us have had jobs before where some boss was making random decisions on product features that we knew might be irrelevant in weeks or months. It's a frustrating feeling, and that lack of control is so terrible. With DDEV and your guidance, we always know that you're keeping us on track about real needs for real features. It's fantastic.
Real Feedback About Real ProblemsYour questions in Discord or Slack and the issues you file aren't "noise". They're signal. When something breaks (or is awkward) in your workflow, you tell us, often with enough detail that we can reproduce it immediately. When something is confusing, you ask questions that reveal where our assumptions were wrong.
That feedback shapes DDEV in ways that internal testing never could. We don't use DDEV on every possible OS, with every PHP framework, in every hosting environment. You do. And you tell us what you find.
We Love Your Questions and Comments.
AI has been replacing human interaction in support situations, and in many cases doing a decent job. It usually does a good job with questions about DDEV.
But getting answers to questions is not the only purpose of support. It's also a great way to communicate problems and ambiguities to project maintainers.
From personal AI experiments to shared tools
In April 2025, I published Claude Code meets Drupal, my first public experiment with an AI coding agent. I have been experimenting with coding agents ever since, often by building tools to solve problems in my own work.
Last week, I joined the Drupal AI Learners Club to discuss several experiments I had already published. Angie Byron started the club and runs it with co-organizer Amber Himes Matz. It gives people in the Drupal community a place to show how they are using AI and talk honestly about what works and what does not.
I spent an hour walking through the experiments, starting with Drupal Digests, a tool that uses AI to summarize key developments across Drupal Core, Drupal CMS, Drupal Canvas, and the Drupal AI initiative.
Drupal Digests led to another experiment: AI-generated Rector rules. When a Drupal Core change deprecates an API, Drupal Digests analyzes the issue and code changes and generates a rule that can automate the corresponding upgrade in other Drupal projects.
I also showed an API catalog that helps AI agents discover my website's search API.
These are only some of my AI experiments. Most begin as tools I build for myself, and many never go any further. When one seems useful beyond my own work, I publish it so others can try it and improve it.
Once it is public, we can see whether people use it and want to help improve it. If they do, it may eventually become a community project. If not, that is useful to know too.