Advanced WordPress Support for Pantheon

Slow performance can stem from a wide range of issues—uncached pages, slow database queries, oversized autoloads, or large Git repositories. Knihter identifies bottlenecks using Pantheon’s performance diagnostics and resolves them through caching strategy, plugin audits, Git cleanup, and infrastructure alignment.

Pantheon doesn’t block broken plugins or track config mistakes. We diagnose slow performance, admin errors, bad cache behavior, and recurring update issues—and fix them.

Absolutely. As a Pantheon Platinum Partner, we integrate seamlessly with client teams and escalate technical issues directly to Pantheon engineers whenever necessary.

Yes—with constraints. We configure full multisite setups, migrate legacy networks, or decouple multisite into standalone sites. We also advise on plugin architecture and domain mapping.

Learn more about Pantheon multisite

No—they don’t. Pantheon doesn’t allow outbound SMTP from its containers. To ensure contact forms, password resets, and notifications send correctly, Knihter sets up authenticated SMTP or API-based services (SendGrid, SES, Postmark) with proper email deliverability measures like SPF/DKIM.

Learn more about Pantheon email delivery

Pantheon’s cache often strips UTM query parameters before they reach analytics tools—so traffic looks ambiguous or is mis-attributed. We help teams diagnose this, preserve UTM parameters through cache layers, and restore accurate campaign reporting in GA4 and Tag Manager.

Learn more in Pantheon’s UTM behavior guide

A Custom Upstream is a shared, reusable WordPress code base that ensures consistent theme and plugin stacks across multiple sites. We build custom upstreams (with composer or Git), configure Autopilot deployment workflows, and maintain dependency updates—all while avoiding merge conflicts across downstream sites.

Learn more about Pantheon custom upstreams

Yes—but it’s limited to specific use cases, like university blog networks or franchise sites. Unsupported scenarios (e.g. agency SaaS or networks with distinct ownership per subsite) may cause issues. We help you plan, migrate, or decouple multisite networks—including plugin isolation, database migration, and domain mapping—based on Pantheon’s governance considerations.

Pantheon does not prevent installation of incompatible tools, but many are unsupported or cause issues within container environments. The built-in Pantheon MU plugin compatibility layer flags these in Site Health. We audit your stack and resolve or replace problematic items.

View Pantheon’s list of known WordPress issues

Pantheon uses wp search-replace during cloning to update environment URLs, but custom code using SERVER_NAME or IP-based links can break if not handled properly. We audit and correct database references and redirect logic to ensure links remain stable across environments.

Learn more about broken links in Pantheon environments

On Pantheon-hosted WordPress sites, plugins like Yoast SEO cannot write to the web root (/) because it’s a read-only environment. This prevents Yoast from generating the llms.txt file used for AI indexing and similar SEO features.

Here’s how to work around this limitation and allow Yoast to create and manage the llms.txt file:
/wp-content/uploads/yoast/llms.txt

1. On your Pantheon environment, use SFTP or a plugin to create the directory and an empty file
On the server, create a blank text file in the /files directory as /yoast/llms.txt

2. Create a symlink in your Git repository
On your local machine, create a symlink to llms.txt and commit
ln -s wp-content/uploads/yoast/llms.txt llms.txt
git add llms.txt
git commit -m "Symlink llms.txt to uploads"
git push

3. Update Yoast’s file path via filter
Add the following to your functions.php or a custom plugin:
// Redirect Yoast llms.txt file path to writable location
add_filter( 'wpseo_llmstxt_filesystem_path', function () {
return WP_CONTENT_DIR . '/uploads/yoast/';
} );

4. Deploy and enable the feature
After pushing changes:
Go to Yoast SEO → Settings → Site features
Toggle the llms.txt feature off and on again to regenerate the file.