{"id":982,"date":"2026-07-17T19:33:01","date_gmt":"2026-07-17T19:33:01","guid":{"rendered":"https:\/\/www.ahosting.net\/blog\/?p=982"},"modified":"2026-07-17T20:07:39","modified_gmt":"2026-07-17T20:07:39","slug":"disable-wordpress-ai-features","status":"publish","type":"post","link":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/","title":{"rendered":"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)"},"content":{"rendered":"\n<script type=\"application\/ld+json\">\n{\n  \"@context\": \"https:\/\/schema.org\",\n  \"@type\": \"FAQPage\",\n  \"mainEntity\": [\n    {\n      \"@type\": \"Question\",\n      \"name\": \"How do I disable WordPress AI features in WordPress 7.0?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Specifically, add define('WP_AI_SUPPORT', false); to your wp-config.php file above the \\u201cstop editing\\u201d comment. The core function wp_supports_ai() then returns false everywhere, so no provider connector or AI-aware feature runs.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"WP_AI_SUPPORT constant vs. wp_supports_ai filter: which should I use?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Fundamentally, the WP_AI_SUPPORT constant is the stronger control because it is read at the top of wp_supports_ai() before any plugin loads, so nothing can override it. The wp_supports_ai filter runs later and a higher-priority plugin can undo it.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Is it safe to disable WordPress AI features in 2026?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes. Disabling WordPress AI features only short-circuits the core AI Client; it does not affect posts, editing, media, or any non-AI functionality. You can re-enable it in seconds by removing the constant.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Should agencies disable WordPress AI features across client sites on AHosting reseller hosting?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Typically, defaulting AI off is the lower-risk posture for agencies. On AHosting reseller hosting each client account is isolated, so you can set WP_AI_SUPPORT per account and opt a client in only when their contract allows external AI processing.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does WordPress 7.0 send my content to AI providers by default?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Notably, no. WordPress core ships no AI provider keys and, per changeset 61700, will not send prompts or data externally without explicit configuration and explicit calling code. The risk is that an editor can add a connector key later.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"WP_AI_SUPPORT constant vs. the Turn Off AI Features plugin: which is more reliable?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Typically, the constant is more reliable for production because it lives in wp-config.php and cannot be deactivated from the Plugins screen. A plugin is easier for non-technical owners but only enforces the setting while it stays active.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Will disabling WordPress AI features also stop plugins that have their own AI?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Importantly, no. WP_AI_SUPPORT gates only plugins that call the core AI Client. A plugin bundling its own AI integration ignores the setting, so you must disable that plugin's AI separately in its own settings.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"What happens if I define WP_AI_SUPPORT as false on a WordPress multisite network?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"On multisite, the constant applies network-wide from wp-config.php, so every subsite has AI off at once. The Settings \\u2192 Connectors screen can still appear on subsites, so pair the constant with the optional mu-plugin to hide it.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Can I edit wp-config.php to disable AI on AHosting WordPress hosting in 2026?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Yes. Every AHosting WordPress plan includes cPanel File Manager, one-click staging, and daily backups, so you can edit wp-config.php on a staging clone, verify the fix, and push it live with a restore point in place.\"\n      }\n    },\n    {\n      \"@type\": \"Question\",\n      \"name\": \"Does AHosting support disabling WordPress AI features in 2026?\",\n      \"acceptedAnswer\": {\n        \"@type\": \"Answer\",\n        \"text\": \"Indeed. AHosting runs WordPress 7.0 on LiteSpeed with cPanel access on every plan, so the WP_AI_SUPPORT constant, the wp_supports_ai filter, and the mu-plugin method all work without a support ticket.\"\n      }\n    }\n  ]\n}\n<\/script>\n\n\n<div class=\"wp-block-aioseo-table-of-contents\"><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-how-wordpress-7-0-turned-ai-connectors-on-by-default-4\">How WordPress 7.0 Turned AI Connectors On by Default<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-how-to-disable-wordpress-ai-features-in-7-0-9\">How to Disable WordPress AI Features in 7.0<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#aioseo-first-back-up-and-open-a-staging-copy-11\">First, Back Up and Open a Staging Copy<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-next-open-wp-config-php-in-cpanel-file-manager-13\">Next, Open wp-config.php in cPanel File Manager<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-then-add-the-wp_ai_support-constant-15\">Then, Add the WP_AI_SUPPORT Constant<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-finally-verify-that-ai-support-is-off-18\">Finally, Verify That AI Support Is Off<\/a><\/li><\/ul><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-three-ways-to-disable-wordpress-ai-features-constant-vs-filter-vs-plugin-22\">Three Ways to Disable WordPress AI Features: Constant vs. Filter vs. Plugin<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-disable-wordpress-ai-features-whats-covered-and-what-isnt-28\">Disable WordPress AI Features: What&#039;s Covered and What Isn&#039;t<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-optional-hide-the-settings-connectors-screen-with-an-mu-plugin-31\">Optional: Hide the Settings \u2192 Connectors Screen With an mu-plugin<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-diagnostic-did-you-fully-disable-wordpress-ai-features-35\">Diagnostic: Did You Fully Disable WordPress AI Features?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#aioseo-editing-wp-config-php-safely-on-ahosting-wordpress-hosting-38\">Editing wp-config.php Safely on AHosting WordPress Hosting<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-disable-wp-ai\">Frequently Asked Questions: Disable WordPress AI Features in 7.0<\/a><ul><li><a class=\"aioseo-toc-item\" href=\"#faq-how-disable\">How do I disable WordPress AI features in WordPress 7.0?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-constant-vs-filter\">WP_AI_SUPPORT constant vs. wp_supports_ai filter: which should I use?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-safe-2026\">Is it safe to disable WordPress AI features in 2026?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-agency-reseller\">Should agencies disable WordPress AI features across client sites on AHosting reseller hosting?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-send-content-default\">Does WordPress 7.0 send my content to AI providers by default?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-constant-vs-plugin\">WP_AI_SUPPORT constant vs. the Turn Off AI Features plugin: which is more reliable?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-own-ai-plugins\">Will disabling WordPress AI features also stop plugins that have their own AI?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-multisite\">What happens if I define WP_AI_SUPPORT as false on a WordPress multisite network?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-ahosting-wpconfig\">Can I edit wp-config.php to disable AI on AHosting WordPress hosting in 2026?<\/a><\/li><li><a class=\"aioseo-toc-item\" href=\"#faq-ahosting-support\">Does AHosting support disabling WordPress AI features in 2026?<\/a><\/li><\/ul><\/li><\/ul><\/div>\n\n\n<div class=\"ah-tldr\">\n  <span class=\"ah-tldr-badge\">TL;DR<\/span>\n  <p>To disable WordPress AI features in WordPress 7.0, add <code>define( 'WP_AI_SUPPORT', false );<\/code> to wp-config.php. It overrides the wp_supports_ai filter, blocks every AI provider call site-wide, and a plugin cannot re-enable it.<\/p>\n<\/div>\n\n\n\n<figure class=\"wp-block-audio\"><audio controls src=\"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/The_WordPress_7.m4a\"><\/audio><figcaption class=\"wp-element-caption\">Disable WordPress AI Features: Audio Explainer<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress 7.0 shipped a built-in AI Client and a Settings \u2192 Connectors screen that any administrator or editor can wire to OpenAI, Anthropic, or Google \u2014 and there is no dashboard switch to turn it back off. This guide shows how to disable WordPress AI features in minutes by adding one line to <code>wp-config.php<\/code>, then proving the change actually took effect. The whole fix is a single constant, but the reasons to apply it \u2014 contracts, data-protection rules, and a smaller attack surface \u2014 are worth understanding first.<\/p>\n\n\n\n<figure class=\"wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio\"><div class=\"wp-block-embed__wrapper\">\n<iframe loading=\"lazy\" title=\"Disable WordPress AI Features in 7.0 (One-Line Fix)\" width=\"500\" height=\"281\" src=\"https:\/\/www.youtube-nocookie.com\/embed\/L0s5DfhptnU?feature=oembed\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen><\/iframe>\n<\/div><\/figure>\n\n\n\n<h2 id=\"aioseo-how-wordpress-7-0-turned-ai-connectors-on-by-default-4\" class=\"wp-block-heading\">How WordPress 7.0 Turned AI Connectors On by Default<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress 7.0, released May 20, 2026, added three AI building blocks to core: the AI Client (a provider-agnostic PHP API exposed through <code>wp_ai_client_prompt()<\/code>), the Connectors API, and a new <strong>Settings \u2192 Connectors<\/strong> admin screen. That screen lists three featured provider cards \u2014 OpenAI, Anthropic, and Google \u2014 and lets an administrator paste one API key that every compatible plugin then shares, as documented in the <a href=\"https:\/\/make.wordpress.org\/core\/2026\/05\/14\/wordpress-7-0-field-guide\/\" target=\"_blank\" rel=\"noopener\">WordPress 7.0 Field Guide<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Importantly, this infrastructure is inert until someone enters a key. WordPress core bundles no provider credentials, and per <a href=\"https:\/\/core.trac.wordpress.org\/changeset\/61700\" target=\"_blank\" rel=\"noopener\">core changeset 61700<\/a>, the platform &#8220;will not send prompts or data to any external service&#8221; without explicit configuration and explicit calling code. The provider-agnostic layer itself lives in the bundled <a href=\"https:\/\/github.com\/WordPress\/php-ai-client\" target=\"_blank\" rel=\"noopener\">WordPress php-ai-client library<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">However, &#8220;off until configured&#8221; is not the same as &#8220;safe to ignore.&#8221; Any user with the right capability can open Settings \u2192 Connectors and paste a key, at which point content can flow to a third-party model. Connector keys are also stored masked but not encrypted in the database (tracked in Trac #64789), so a live key can travel inside database dumps, staging refreshes, and backups. For a site under an NDA or a data-protection obligation, that is a surface most teams would rather remove than police. In practice, disabling the AI Client by default and opting sites in later is the cleaner policy \u2014 and it is one line.<\/p>\n\n\n\n<div class=\"ah-infographic\" style=\"margin:24px 0;\">\n  <svg viewBox=\"0 0 760 300\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" role=\"img\" aria-label=\"Diagram of the WordPress 7.0 AI data path from editor to Settings Connectors to external AI providers, and the WP_AI_SUPPORT constant that blocks it.\">\n    <rect x=\"0\" y=\"0\" width=\"760\" height=\"300\" fill=\"#0f172a\" rx=\"10\"><\/rect>\n    <text x=\"30\" y=\"40\" fill=\"#ffffff\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"20\" font-weight=\"700\">The WordPress 7.0 AI data path (and where to cut it)<\/text>\n    <rect x=\"30\" y=\"70\" width=\"150\" height=\"70\" rx=\"8\" fill=\"#1e293b\" stroke=\"#2563eb\" stroke-width=\"2\"><\/rect>\n    <text x=\"105\" y=\"100\" fill=\"#ffffff\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"14\" font-weight=\"600\" text-anchor=\"middle\">Editor \/ Plugin<\/text>\n    <text x=\"105\" y=\"120\" fill=\"#94a3b8\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"11\" text-anchor=\"middle\">calls AI Client<\/text>\n    <rect x=\"230\" y=\"70\" width=\"180\" height=\"70\" rx=\"8\" fill=\"#1e293b\" stroke=\"#2563eb\" stroke-width=\"2\"><\/rect>\n    <text x=\"320\" y=\"100\" fill=\"#ffffff\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"14\" font-weight=\"600\" text-anchor=\"middle\">Settings -&gt; Connectors<\/text>\n    <text x=\"320\" y=\"120\" fill=\"#94a3b8\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"11\" text-anchor=\"middle\">stores provider API key<\/text>\n    <rect x=\"460\" y=\"70\" width=\"270\" height=\"70\" rx=\"8\" fill=\"#1e293b\" stroke=\"#38bdf8\" stroke-width=\"2\"><\/rect>\n    <text x=\"595\" y=\"100\" fill=\"#ffffff\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"14\" font-weight=\"600\" text-anchor=\"middle\">OpenAI \/ Anthropic \/ Google<\/text>\n    <text x=\"595\" y=\"120\" fill=\"#94a3b8\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"11\" text-anchor=\"middle\">your content leaves the server<\/text>\n    <line x1=\"180\" y1=\"105\" x2=\"228\" y2=\"105\" stroke=\"#2563eb\" stroke-width=\"3\"><\/line>\n    <polygon points=\"228,100 238,105 228,110\" fill=\"#2563eb\"><\/polygon>\n    <line x1=\"410\" y1=\"105\" x2=\"458\" y2=\"105\" stroke=\"#38bdf8\" stroke-width=\"3\"><\/line>\n    <polygon points=\"458,100 468,105 458,110\" fill=\"#38bdf8\"><\/polygon>\n    <rect x=\"230\" y=\"190\" width=\"180\" height=\"64\" rx=\"8\" fill=\"#7f1d1d\" stroke=\"#f87171\" stroke-width=\"2\"><\/rect>\n    <text x=\"320\" y=\"218\" fill=\"#ffffff\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"14\" font-weight=\"700\" text-anchor=\"middle\">WP_AI_SUPPORT = false<\/text>\n    <text x=\"320\" y=\"238\" fill=\"#fecaca\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"11\" text-anchor=\"middle\">wp_supports_ai() returns false<\/text>\n    <line x1=\"320\" y1=\"140\" x2=\"320\" y2=\"188\" stroke=\"#f87171\" stroke-width=\"3\" stroke-dasharray=\"6 5\"><\/line>\n    <text x=\"470\" y=\"215\" fill=\"#f87171\" font-family=\"Poppins, Arial, sans-serif\" font-size=\"13\" font-weight=\"700\">Cuts the path before any key is used<\/text>\n  <\/svg>\n<\/div>\n\n\n\n<h2 id=\"aioseo-how-to-disable-wordpress-ai-features-in-7-0-9\" class=\"wp-block-heading\">How to Disable WordPress AI Features in 7.0<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">To disable WordPress AI features, add <code>define( 'WP_AI_SUPPORT', false );<\/code> to <code>wp-config.php<\/code> above the &#8220;stop editing&#8221; line, then confirm <code>wp_supports_ai()<\/code> returns false. The four steps below do exactly that, safely, using the tools included with your hosting.<\/p>\n\n\n\n<h3 id=\"aioseo-first-back-up-and-open-a-staging-copy-11\" class=\"wp-block-heading\">First, Back Up and Open a Staging Copy<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First and foremost, never edit <code>wp-config.php<\/code> straight on production. On AHosting, open cPanel, create a one-click staging clone, and confirm your daily backup is current so you have a restore point. Editing a staging copy first means a typo in the config file \u2014 the classic cause of a white screen \u2014 never touches your live site. If you also manage many sites, the same edit is easy to standardize across them, which is why the wp-config approach scales better than clicking through each dashboard.<\/p>\n\n\n\n<h3 id=\"aioseo-next-open-wp-config-php-in-cpanel-file-manager-13\" class=\"wp-block-heading\">Next, Open wp-config.php in cPanel File Manager<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Next, in cPanel open <strong>File Manager<\/strong>, navigate to the site&#8217;s document root (typically <code>public_html<\/code>), select <code>wp-config.php<\/code>, and click <strong>Edit<\/strong>. Scroll to the line that reads <code>\/* That's all, stop editing! Happy publishing. *\/<\/code>. Everything you add must go <em>above<\/em> that line, because WordPress ignores configuration defined after it. If you prefer SFTP, the same file in the same location works identically.<\/p>\n\n\n\n<h3 id=\"aioseo-then-add-the-wp_ai_support-constant-15\" class=\"wp-block-heading\">Then, Add the WP_AI_SUPPORT Constant<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Then paste this single line above the &#8220;stop editing&#8221; comment and save. The constant is read at the very top of <code>wp_supports_ai()<\/code>, before any plugin or theme loads, which is why it is the most reliable off switch and cannot be reversed by a plugin at runtime, per the <a href=\"https:\/\/developer.wordpress.org\/reference\/hooks\/wp_supports_ai\/\" target=\"_blank\" rel=\"noopener\">official wp_supports_ai reference<\/a>.<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>\/\/ Disable the WordPress 7.0 AI Client site-wide (enforced)\ndefine( 'WP_AI_SUPPORT', false );<\/code><\/pre>\n\n\n\n<h3 id=\"aioseo-finally-verify-that-ai-support-is-off-18\" class=\"wp-block-heading\">Finally, Verify That AI Support Is Off<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Finally, prove the fix took effect rather than assuming it. If you have terminal access, WP-CLI answers in one line and should print <code>bool(false)<\/code>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wp eval \"var_dump( wp_supports_ai() );\"<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Alternatively, reload <strong>Settings \u2192 Connectors<\/strong> in wp-admin: with AI support off, provider connections no longer initialize. For a deeper look at editing configuration safely, our guide on <a href=\"https:\/\/www.ahosting.net\/blog\/wordpress-memory-limit-errors-2026\/\" target=\"_blank\" rel=\"noopener\">why raising limits in wp-config often fails<\/a> covers the same file and the two-ceiling gotcha that trips people up.<\/p>\n\n\n\n<h2 id=\"aioseo-three-ways-to-disable-wordpress-ai-features-constant-vs-filter-vs-plugin-22\" class=\"wp-block-heading\">Three Ways to Disable WordPress AI Features: Constant vs. Filter vs. Plugin<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Specifically, WordPress 7.0 gives you three levers, and they are not equal. The constant is enforced earliest and cannot be undone by a plugin; the filter is flexible but runs later and is override-able; a plugin is the no-code option for owners who cannot edit <code>wp-config.php<\/code>. The developer-friendly filter version, popularized in <a href=\"https:\/\/shawnhooper.ca\/2026\/05\/28\/disable-wordpress-ai-core\/\" target=\"_blank\" rel=\"noopener\">Shawn Hooper&#8217;s write-up<\/a>, looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>add_filter( 'wp_supports_ai', static function ( $supported ) {\n    return false;\n}, 1000 );<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Table 1 compares the three methods so you can match the lever to the site. Use it as a standalone reference when deciding what to deploy across a fleet versus a single site you fully control.<\/p>\n\n\n\n<table class=\"ah-datatable\" style=\"width:100%;border-collapse:collapse;margin:16px 0;font-size:0.95rem;\">\n  <caption style=\"caption-side:top;text-align:left;font-weight:700;padding:6px 0;color:#1e293b;\">Table 1 &mdash; WordPress 7.0 AI Disable Methods Compared<\/caption>\n  <thead>\n    <tr style=\"background:#0f172a;color:#ffffff;\">\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Method<\/th>\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Where it lives<\/th>\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Can an editor undo it?<\/th>\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Hides Connectors screen?<\/th>\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Best for<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\"><code>WP_AI_SUPPORT<\/code> constant<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">wp-config.php<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No &mdash; loads before plugins<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No (add the mu-plugin)<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Production sites, whole fleets<\/td>\n    <\/tr>\n    <tr style=\"background:#f8fafc;\">\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\"><code>wp_supports_ai<\/code> filter<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Theme or snippet<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Yes &mdash; a later hook can override<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Single sites you fully control<\/td>\n    <\/tr>\n    <tr>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Disable-AI plugin<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Plugins screen<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Yes &mdash; if deactivated<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Yes (most hide it)<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No-code owners, locked wp-config<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n\n\n<p class=\"wp-block-paragraph\">Consequently, the plugin route matters on managed platforms where <code>wp-config.php<\/code> is not directly editable. Two well-maintained options are &#8220;Turn Off AI Features&#8221; and &#8220;Disable AI for Security,&#8221; both of which wrap the same <code>wp_supports_ai<\/code> filter and add an admin badge. On AHosting you have full cPanel access, so the constant remains the recommended path.<\/p>\n\n\n\n<h2 id=\"aioseo-disable-wordpress-ai-features-whats-covered-and-what-isnt-28\" class=\"wp-block-heading\">Disable WordPress AI Features: What&#8217;s Covered and What Isn&#8217;t<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In practice, the constant is comprehensive for core AI but has one honest boundary: it only governs code that checks <code>wp_supports_ai()<\/code>. Plugins that ship their own AI integration \u2014 rather than calling the core client \u2014 are unaffected and must be handled in their own settings. Table 2 draws that line clearly so you do not assume more coverage than the constant provides.<\/p>\n\n\n\n<table class=\"ah-datatable\" style=\"width:100%;border-collapse:collapse;margin:16px 0;font-size:0.95rem;\">\n  <caption style=\"caption-side:top;text-align:left;font-weight:700;padding:6px 0;color:#1e293b;\">Table 2 &mdash; What WP_AI_SUPPORT = false Stops (and What It Doesn&#8217;t)<\/caption>\n  <thead>\n    <tr style=\"background:#0f172a;color:#ffffff;\">\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Surface<\/th>\n      <th style=\"text-align:left;padding:10px;border:1px solid #e2e8f0;\">Covered by the constant?<\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Core AI Client calls (<code>wp_ai_client_prompt()<\/code>)<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Yes &mdash; short-circuited site-wide<\/td>\n    <\/tr>\n    <tr style=\"background:#f8fafc;\">\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Featured connectors (OpenAI \/ Anthropic \/ Google)<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Yes &mdash; no prompts run, keys stay inert<\/td>\n    <\/tr>\n    <tr>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Settings &rarr; Connectors admin screen visibility<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No &mdash; still visible unless you add the mu-plugin<\/td>\n    <\/tr>\n    <tr style=\"background:#f8fafc;\">\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">Plugins with their own bundled AI<\/td>\n      <td style=\"padding:10px;border:1px solid #e2e8f0;\">No &mdash; disable each plugin&#8217;s AI separately<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n\n\n<h2 id=\"aioseo-optional-hide-the-settings-connectors-screen-with-an-mu-plugin-31\" class=\"wp-block-heading\">Optional: Hide the Settings \u2192 Connectors Screen With an mu-plugin<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Additionally, the constant blocks AI calls but leaves the Settings \u2192 Connectors menu item visible. To remove it and block direct access, drop a small must-use plugin into <code>wp-content\/mu-plugins\/<\/code> \u2014 a location that loads automatically, survives theme switches, and cannot be deactivated from the Plugins screen. The removal hooks <code>admin_menu<\/code> at a high priority (not <code>admin_init<\/code>, which would break admin-ajax) using the core <a href=\"https:\/\/developer.wordpress.org\/reference\/functions\/remove_submenu_page\/\" target=\"_blank\" rel=\"noopener\">remove_submenu_page function<\/a>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>&lt;?php\n\/**\n * Plugin Name: Hide WordPress AI Connectors\n * Description: Removes Settings -&gt; Connectors and blocks direct access.\n *\/\nadd_action( 'admin_menu', function () {\n    remove_submenu_page( 'options-general.php', 'options-connectors.php' );\n}, 999 );\n\nadd_action( 'admin_init', function () {\n    global $pagenow;\n    if ( 'options-connectors.php' === $pagenow ) {\n        wp_safe_redirect( admin_url() );\n        exit;\n    }\n} );<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That said, screen names can change between releases, so treat the mu-plugin as belt-and-suspenders on top of the constant, not a replacement for it. The constant is what actually stops the AI calls; hiding the menu just removes the temptation.<\/p>\n\n\n\n<h2 id=\"aioseo-diagnostic-did-you-fully-disable-wordpress-ai-features-35\" class=\"wp-block-heading\">Diagnostic: Did You Fully Disable WordPress AI Features?<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Interestingly, most &#8220;still exposed&#8221; sites have the constant right but miss the two edge cases: the visible Connectors screen and plugins with their own AI. Answer the four checks below to see exactly where your site stands.<\/p>\n\n\n\n<style>\n.ahaic-wrap{border:1px solid #e2e8f0;border-radius:12px;padding:20px;margin:20px 0;background:#ffffff;font-family:inherit;}\n.ahaic-h{font-size:1.05rem;font-weight:700;color:#0f172a;margin:0 0 14px;}\n.ahaic-q{margin:0 0 12px;padding-bottom:12px;border-bottom:1px solid #f1f5f9;}\n.ahaic-qt{font-size:.95rem;color:#1e293b;margin:0 0 8px;font-weight:600;}\n.ahaic-btn{display:inline-block;border:1px solid #cbd5e1;background:#f8fafc;color:#1e293b;font-size:.85rem;padding:6px 16px;border-radius:6px;cursor:pointer;margin-right:8px;}\n.ahaic-btn.ahaic-on{background:#2563eb;color:#ffffff;border-color:#2563eb;}\n.ahaic-out{margin-top:14px;padding:14px 16px;border-radius:8px;font-size:.92rem;line-height:1.6;background:#eff6ff;color:#1e293b;border-left:4px solid #2563eb;}\n<\/style>\n<div class=\"ahaic-wrap\" data-ahaic=\"1\">\n  <p class=\"ahaic-h\">AI Connector Exposure Check<\/p>\n  <div class=\"ahaic-q\">\n    <p class=\"ahaic-qt\">1. Is your site running WordPress 7.0 or newer?<\/p>\n    <span class=\"ahaic-btn\" data-q=\"ver\" data-a=\"yes\">Yes<\/span>\n    <span class=\"ahaic-btn\" data-q=\"ver\" data-a=\"no\">No<\/span>\n  <\/div>\n  <div class=\"ahaic-q\">\n    <p class=\"ahaic-qt\">2. Is define( &#8216;WP_AI_SUPPORT&#8217;, false ); in your wp-config.php?<\/p>\n    <span class=\"ahaic-btn\" data-q=\"constant\" data-a=\"yes\">Yes<\/span>\n    <span class=\"ahaic-btn\" data-q=\"constant\" data-a=\"no\">No<\/span>\n  <\/div>\n  <div class=\"ahaic-q\">\n    <p class=\"ahaic-qt\">3. Have you hidden the Settings -&gt; Connectors screen (mu-plugin)?<\/p>\n    <span class=\"ahaic-btn\" data-q=\"menu\" data-a=\"yes\">Yes<\/span>\n    <span class=\"ahaic-btn\" data-q=\"menu\" data-a=\"no\">No<\/span>\n  <\/div>\n  <div class=\"ahaic-q\">\n    <p class=\"ahaic-qt\">4. Do any active plugins ship their own built-in AI?<\/p>\n    <span class=\"ahaic-btn\" data-q=\"plugin\" data-a=\"yes\">Yes<\/span>\n    <span class=\"ahaic-btn\" data-q=\"plugin\" data-a=\"no\">No<\/span>\n  <\/div>\n  <div class=\"ahaic-out\" data-ahaic-out=\"1\">Answer all four to see your exposure verdict.<\/div>\n<\/div>\n<script>\n(function(){\n  document.addEventListener('DOMContentLoaded', function(){\n    var wrap = document.querySelector('[data-ahaic=\"1\"]');\n    if (!wrap) { return; }\n    var out = wrap.querySelector('[data-ahaic-out=\"1\"]');\n    if (!out) { return; }\n    var state = { ver:'', constant:'', menu:'', plugin:'' };\n    wrap.addEventListener('click', function(e){\n      var btn = e.target;\n      if (!btn) { return; }\n      var q = btn.getAttribute('data-q');\n      if (!q) { return; }\n      var a = btn.getAttribute('data-a');\n      state[q] = a;\n      var group = btn.parentNode.querySelectorAll('.ahaic-btn');\n      for (var i = 0; i < group.length; i++) { group[i].classList.remove('ahaic-on'); }\n      btn.classList.add('ahaic-on');\n      render();\n    });\n    function render(){\n      \/\/ require all four answers first\n      if (!state.ver) { return; }\n      if (!state.constant) { return; }\n      if (!state.menu) { return; }\n      if (!state.plugin) { return; }\n      var msg = '';\n      if (state.ver === 'no') {\n        msg = 'You are not on WordPress 7.0 yet, so the core AI Client is not present. Revisit this after you update.';\n        out.innerHTML = msg;\n        return;\n      }\n      if (state.constant === 'no') {\n        msg = 'Exposed: the AI Client is active and an editor could wire a connector. Add define WP_AI_SUPPORT false to wp-config.php.';\n      } else {\n        if (state.menu === 'no') {\n          msg = 'Mostly covered: AI calls are blocked, but the Settings -> Connectors screen is still visible. Add the optional mu-plugin to hide it.';\n        } else {\n          msg = 'Fully covered at the core level: AI support is off and the Connectors screen is hidden.';\n        }\n      }\n      if (state.plugin === 'yes') {\n        msg = msg + ' Note: at least one plugin bundles its own AI, which the constant does not gate. Disable that plugin AI separately.';\n      }\n      out.innerHTML = msg;\n    }\n  });\n})();\n<\/script>\n\n\n\n<h2 id=\"aioseo-editing-wp-config-php-safely-on-ahosting-wordpress-hosting-38\" class=\"wp-block-heading\">Editing wp-config.php Safely on AHosting WordPress Hosting<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Fortunately, the riskiest part of this fix is not the constant \u2014 it is editing <code>wp-config.php<\/code> without a safety net. Every <a href=\"https:\/\/www.ahosting.net\/wordpress-hosting.html\" target=\"_blank\" rel=\"noopener\">AHosting WordPress hosting plan<\/a> ships one-click staging, daily backups, and cPanel File Manager, so you can test the edit on a clone and restore instantly if anything looks off. That staging-plus-backup workflow is the same one we recommend in our <a href=\"https:\/\/www.ahosting.net\/blog\/wordpress-hosting-security-2026-server-level-protection\/\" target=\"_blank\" rel=\"noopener\">server-level WordPress security guide<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Moreover, if you run AI features intentionally, they make outbound calls from your server to provider endpoints \u2014 and every AHosting plan includes a free dedicated IP, so those calls carry a stable, isolated identity rather than a shared reputation. Agencies standardizing an AI-off policy across many client sites can do it per account on <a href=\"https:\/\/www.ahosting.net\/reseller-hosting.html\" target=\"_blank\" rel=\"noopener\">white-label reseller hosting<\/a>, and sites that have simply outgrown shared concurrency can move the same configuration onto <a href=\"https:\/\/www.ahosting.net\/vps-hosting.html\" target=\"_blank\" rel=\"noopener\">managed VPS<\/a> without changing a line of it. For the full pre-update picture, see our <a href=\"https:\/\/www.ahosting.net\/blog\/wordpress-7-0-hosting-requirements-is-your-host-ready\/\" target=\"_blank\" rel=\"noopener\">WordPress 7.0 hosting requirements checklist<\/a>.<\/p>\n\n\n\n<h2 id=\"faq-disable-wp-ai\" class=\"wp-block-heading\">Frequently Asked Questions: Disable WordPress AI Features in 7.0<\/h2>\n\n\n\n<h3 id=\"faq-how-disable\" class=\"wp-block-heading\">How do I disable WordPress AI features in WordPress 7.0?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Specifically, add <code>define( 'WP_AI_SUPPORT', false );<\/code> to your wp-config.php file above the &#8220;stop editing&#8221; comment. The core function <code>wp_supports_ai()<\/code> then returns false everywhere, so no provider connector or AI-aware feature runs.<\/p>\n\n\n\n<h3 id=\"faq-constant-vs-filter\" class=\"wp-block-heading\">WP_AI_SUPPORT constant vs. wp_supports_ai filter: which should I use?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Fundamentally, the WP_AI_SUPPORT constant is the stronger control because it is read at the top of <code>wp_supports_ai()<\/code> before any plugin loads, so nothing can override it. The wp_supports_ai filter runs later and a higher-priority plugin can undo it.<\/p>\n\n\n\n<h3 id=\"faq-safe-2026\" class=\"wp-block-heading\">Is it safe to disable WordPress AI features in 2026?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Disabling WordPress AI features only short-circuits the core AI Client; it does not affect posts, editing, media, or any non-AI functionality. You can re-enable it in seconds by removing the constant.<\/p>\n\n\n\n<h3 id=\"faq-agency-reseller\" class=\"wp-block-heading\">Should agencies disable WordPress AI features across client sites on AHosting reseller hosting?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Typically, defaulting AI off is the lower-risk posture for agencies. On AHosting reseller hosting each client account is isolated, so you can set WP_AI_SUPPORT per account and opt a client in only when their contract allows external AI processing.<\/p>\n\n\n\n<h3 id=\"faq-send-content-default\" class=\"wp-block-heading\">Does WordPress 7.0 send my content to AI providers by default?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Notably, no. WordPress core ships no AI provider keys and, per changeset 61700, will not send prompts or data externally without explicit configuration and explicit calling code. The risk is that an editor can add a connector key later.<\/p>\n\n\n\n<h3 id=\"faq-constant-vs-plugin\" class=\"wp-block-heading\">WP_AI_SUPPORT constant vs. the Turn Off AI Features plugin: which is more reliable?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Typically, the constant is more reliable for production because it lives in wp-config.php and cannot be deactivated from the Plugins screen. A plugin is easier for non-technical owners but only enforces the setting while it stays active.<\/p>\n\n\n\n<h3 id=\"faq-own-ai-plugins\" class=\"wp-block-heading\">Will disabling WordPress AI features also stop plugins that have their own AI?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Importantly, no. WP_AI_SUPPORT gates only plugins that call the core AI Client. A plugin bundling its own AI integration ignores the setting, so you must disable that plugin&#8217;s AI separately in its own settings.<\/p>\n\n\n\n<h3 id=\"faq-multisite\" class=\"wp-block-heading\">What happens if I define WP_AI_SUPPORT as false on a WordPress multisite network?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On multisite, the constant applies network-wide from wp-config.php, so every subsite has AI off at once. The Settings \u2192 Connectors screen can still appear on subsites, so pair the constant with the optional mu-plugin to hide it.<\/p>\n\n\n\n<h3 id=\"faq-ahosting-wpconfig\" class=\"wp-block-heading\">Can I edit wp-config.php to disable AI on AHosting WordPress hosting in 2026?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Yes. Every AHosting WordPress plan includes cPanel File Manager, one-click staging, and daily backups, so you can edit wp-config.php on a staging clone, verify the fix, and push it live with a restore point in place.<\/p>\n\n\n\n<h3 id=\"faq-ahosting-support\" class=\"wp-block-heading\">Does AHosting support disabling WordPress AI features in 2026?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Indeed. AHosting runs WordPress 7.0 on LiteSpeed with cPanel access on every plan, so the WP_AI_SUPPORT constant, the wp_supports_ai filter, and the mu-plugin method all work without a support ticket.<\/p>\n\n\n\n<script>\n(function(){\n  document.addEventListener('DOMContentLoaded', function(){\n    var allH3s = document.querySelectorAll('h3.wp-block-heading');\n    var inFaq = false;\n    for (var i = 0; i < allH3s.length; i++) {\n      var h3 = allH3s[i];\n      var prev = h3.previousElementSibling;\n      if (prev) {\n        if (prev.tagName === 'H2') {\n          var prevId = prev.getAttribute('id');\n          if (prevId) {\n            if (prevId.indexOf('faq-') === 0) {\n              inFaq = true;\n            } else {\n              inFaq = false;\n            }\n          }\n        }\n      }\n      if (inFaq) {\n        initToggle(h3);\n      }\n    }\n    function initToggle(h3) {\n      var answer = h3.nextElementSibling;\n      if (!answer) { return; }\n      if (answer.tagName !== 'P') { return; }\n      var chev = document.createElement('span');\n      chev.className = 'ahfaq-chev ahfaq-chev-closed';\n      chev.setAttribute('aria-hidden', 'true');\n      h3.appendChild(chev);\n      h3.setAttribute('tabindex', '0');\n      h3.setAttribute('aria-expanded', 'false');\n      answer.classList.add('ahfaq-collapsed');\n      h3.addEventListener('click', function(){ doToggle(h3, answer, chev); });\n      h3.addEventListener('keydown', function(e){\n        if (e.key === 'Enter') { e.preventDefault(); doToggle(h3, answer, chev); }\n        if (e.key === ' ') { e.preventDefault(); doToggle(h3, answer, chev); }\n      });\n    }\n    function doToggle(h3, answer, chev) {\n      var isOpen = h3.getAttribute('aria-expanded') === 'true';\n      if (isOpen) {\n        answer.classList.remove('ahfaq-open');\n        answer.classList.add('ahfaq-collapsed');\n        h3.setAttribute('aria-expanded', 'false');\n        chev.classList.add('ahfaq-chev-closed');\n        chev.classList.remove('ahfaq-chev-open');\n      } else {\n        answer.classList.remove('ahfaq-collapsed');\n        answer.classList.add('ahfaq-open');\n        h3.setAttribute('aria-expanded', 'true');\n        chev.classList.remove('ahfaq-chev-closed');\n        chev.classList.add('ahfaq-chev-open');\n      }\n    }\n  });\n})();\n<\/script>\n","protected":false},"excerpt":{"rendered":"<p>TL;DR To disable WordPress AI features in WordPress 7.0, add define( &#8216;WP_AI_SUPPORT&#8217;, false ); to wp-config.php. It overrides the wp_supports_ai filter, blocks every AI provider call site-wide, and a plugin cannot re-enable it. WordPress 7.0 shipped a built-in AI Client and a Settings \u2192 Connectors screen that any administrator or editor can wire to OpenAI, [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":983,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[128,8],"tags":[135,132,133,136,134],"class_list":["post-982","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-how-to","category-wordpress","tag-disable-wordpress-ai-features","tag-wordpress-7-0-ai","tag-wordpress-ai-connectors","tag-wp-config-php-ai","tag-wp_ai_support"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.10 - aioseo.com -->\n\t<meta name=\"description\" content=\"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.\" \/>\n\t<meta name=\"robots\" content=\"max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n\t<meta name=\"author\" content=\"Matt Chrust\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.10\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"AHosting Blog Home | AHosting Blog\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Disable WordPress AI Features in 7.0 (2026 Guide)\" \/>\n\t\t<meta property=\"og:description\" content=\"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t\t<meta property=\"og:image:height\" content=\"675\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-07-17T19:33:01+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-07-17T20:07:39+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Disable WordPress AI Features in 7.0 (2026 Guide)\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#article\",\"name\":\"Disable WordPress AI Features in 7.0 (2026 Guide)\",\"headline\":\"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)\",\"author\":{\"@type\":\"Person\",\"name\":\"Matt Chrust\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/author\\\/matt-chrust\\\/\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/disable-wordpress-ai-features-ahosting.jpg\",\"width\":1200,\"height\":675},\"datePublished\":\"2026-07-17T19:33:01+00:00\",\"dateModified\":\"2026-07-17T20:07:39+00:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#webpage\"},\"articleSection\":\"How To, WordPress, disable WordPress AI features, WordPress 7.0 AI, WordPress AI Connectors, wp-config.php AI, WP_AI_SUPPORT\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.ahosting.net\\\/blog\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/category\\\/wordpress\\\/#listItem\",\"name\":\"WordPress\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/category\\\/wordpress\\\/#listItem\",\"position\":2,\"name\":\"WordPress\",\"item\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/category\\\/wordpress\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#listItem\",\"name\":\"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#listItem\",\"position\":3,\"name\":\"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/category\\\/wordpress\\\/#listItem\",\"name\":\"WordPress\"},\"item\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/\"}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/#organization\",\"name\":\"AHosting\",\"description\":\"AHosting Blog\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/assets\\\/img\\\/ahosting-logo.svg\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#organizationLogo\"},\"image\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#organizationLogo\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/author\\\/matt-chrust\\\/#author\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/author\\\/matt-chrust\\\/\",\"name\":\"Matt Chrust\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/795895edac1c44589f6c7f5e6bb79df405fbbaac15817bdd387ec57da61731ec?s=96&d=mm&r=g\",\"width\":96,\"height\":96,\"caption\":\"Matt Chrust\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#webpage\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/\",\"name\":\"Disable WordPress AI Features in 7.0 (2026 Guide)\",\"description\":\"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \\u2014 then verify it.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/author\\\/matt-chrust\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/author\\\/matt-chrust\\\/#author\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/disable-wordpress-ai-features-ahosting.jpg\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#mainImage\",\"width\":1200,\"height\":675},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/blog\\\/disable-wordpress-ai-features\\\/#mainImage\"},\"datePublished\":\"2026-07-17T19:33:01+00:00\",\"dateModified\":\"2026-07-17T20:07:39+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/#website\",\"url\":\"https:\\\/\\\/www.ahosting.net\\\/\",\"name\":\"AHosting\",\"description\":\"AHosting Blog\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.ahosting.net\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Disable WordPress AI Features in 7.0 (2026 Guide)","description":"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.","canonical_url":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/","robots":"max-snippet:-1, max-image-preview:large, max-video-preview:-1","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#article","name":"Disable WordPress AI Features in 7.0 (2026 Guide)","headline":"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)","author":{"@type":"Person","name":"Matt Chrust","url":"https:\/\/www.ahosting.net\/blog\/author\/matt-chrust\/"},"publisher":{"@id":"https:\/\/www.ahosting.net\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg","width":1200,"height":675},"datePublished":"2026-07-17T19:33:01+00:00","dateModified":"2026-07-17T20:07:39+00:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#webpage"},"isPartOf":{"@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#webpage"},"articleSection":"How To, WordPress, disable WordPress AI features, WordPress 7.0 AI, WordPress AI Connectors, wp-config.php AI, WP_AI_SUPPORT"},{"@type":"BreadcrumbList","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog#listItem","position":1,"name":"Home","item":"https:\/\/www.ahosting.net\/blog","nextItem":{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/#listItem","name":"WordPress"}},{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/#listItem","position":2,"name":"WordPress","item":"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#listItem","name":"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#listItem","position":3,"name":"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)","previousItem":{"@type":"ListItem","@id":"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/#listItem","name":"WordPress"},"item":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/"}]},{"@type":"Organization","@id":"https:\/\/www.ahosting.net\/#organization","name":"AHosting","description":"AHosting Blog","url":"https:\/\/www.ahosting.net\/","logo":{"@type":"ImageObject","url":"https:\/\/www.ahosting.net\/assets\/img\/ahosting-logo.svg","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#organizationLogo"},"image":{"@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#organizationLogo"}},{"@type":"Person","@id":"https:\/\/www.ahosting.net\/blog\/author\/matt-chrust\/#author","url":"https:\/\/www.ahosting.net\/blog\/author\/matt-chrust\/","name":"Matt Chrust","image":{"@type":"ImageObject","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/795895edac1c44589f6c7f5e6bb79df405fbbaac15817bdd387ec57da61731ec?s=96&d=mm&r=g","width":96,"height":96,"caption":"Matt Chrust"}},{"@type":"WebPage","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#webpage","url":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/","name":"Disable WordPress AI Features in 7.0 (2026 Guide)","description":"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.ahosting.net\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#breadcrumblist"},"author":{"@id":"https:\/\/www.ahosting.net\/blog\/author\/matt-chrust\/#author"},"creator":{"@id":"https:\/\/www.ahosting.net\/blog\/author\/matt-chrust\/#author"},"image":{"@type":"ImageObject","url":"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg","@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#mainImage","width":1200,"height":675},"primaryImageOfPage":{"@id":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/#mainImage"},"datePublished":"2026-07-17T19:33:01+00:00","dateModified":"2026-07-17T20:07:39+00:00"},{"@type":"WebSite","@id":"https:\/\/www.ahosting.net\/#website","url":"https:\/\/www.ahosting.net\/","name":"AHosting","description":"AHosting Blog","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.ahosting.net\/#organization"}}]},"og:locale":"en_US","og:site_name":"AHosting Blog Home | AHosting Blog","og:type":"article","og:title":"Disable WordPress AI Features in 7.0 (2026 Guide)","og:description":"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.","og:url":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/","og:image":"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg","og:image:secure_url":"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg","og:image:width":1200,"og:image:height":675,"article:published_time":"2026-07-17T19:33:01+00:00","article:modified_time":"2026-07-17T20:07:39+00:00","twitter:card":"summary_large_image","twitter:title":"Disable WordPress AI Features in 7.0 (2026 Guide)","twitter:description":"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.","twitter:image":"https:\/\/www.ahosting.net\/blog\/wp-content\/uploads\/2026\/07\/disable-wordpress-ai-features-ahosting.jpg"},"aioseo_meta_data":{"post_id":"982","title":"Disable WordPress AI Features in 7.0 (2026 Guide)","description":"Disable WordPress AI features in 7.0 with one line in wp-config.php. Stop an editor wiring AI Connectors to OpenAI, Anthropic, or Google \u2014 then verify it.","keywords":null,"keyphrases":{"focus":{"keyphrase":"disable WordPress AI features","score":100,"analysis":{"keyphraseInTitle":{"score":9,"maxScore":9,"error":0},"keyphraseInDescription":{"score":9,"maxScore":9,"error":0},"keyphraseLength":{"score":9,"maxScore":9,"error":0,"length":4},"keyphraseInURL":{"score":5,"maxScore":5,"error":0},"keyphraseInIntroduction":{"score":9,"maxScore":9,"error":0},"keyphraseInSubHeadings":{"score":9,"maxScore":9,"error":0},"keyphraseInImageAlt":[],"keywordDensity":{"type":"best","score":9,"maxScore":9,"error":0}}},"additional":[]},"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-07-17 19:29:11","updated":"2026-07-17 20:50:02","seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.ahosting.net\/blog\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/\" title=\"WordPress\">WordPress<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tDisable WordPress AI Features in WordPress 7.0 (2026 Guide)\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.ahosting.net\/blog"},{"label":"WordPress","link":"https:\/\/www.ahosting.net\/blog\/category\/wordpress\/"},{"label":"Disable WordPress AI Features in WordPress 7.0 (2026 Guide)","link":"https:\/\/www.ahosting.net\/blog\/disable-wordpress-ai-features\/"}],"_links":{"self":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/982","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/comments?post=982"}],"version-history":[{"count":2,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/982\/revisions"}],"predecessor-version":[{"id":986,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/posts\/982\/revisions\/986"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media\/983"}],"wp:attachment":[{"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/media?parent=982"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/categories?post=982"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.ahosting.net\/blog\/wp-json\/wp\/v2\/tags?post=982"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}