Categories
AI Tools Web Hosting WordPress

How to Connect ChatGPT or Claude to Your WordPress.com Site (MCP Guide)

Last updated: November 8, 2026

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

You can now hook ChatGPT or Claude straight into a WordPress.com site and tell it what to do in plain English. Ask it to build a site from a short description, turn your notes into a draft post, or tell you which pages got the most traffic last month. Automattic built both integrations: the WordPress.com plugin in ChatGPT and the WordPress.com connector in Claude.

I manage this blog with an AI assistant every week, so I was curious how the WordPress.com version compares. Here is what it can do, how to connect it in a few minutes, and the settings I would check before you hand an AI the keys to your site.

The short version

What it isAn official WordPress.com integration for ChatGPT and Claude, built by Automattic on the Model Context Protocol (MCP)
In ChatGPTThe WordPress.com plugin. Type @WordPress.com in a chat to use it.
In ClaudeThe WordPress.com connector, listed in Claude’s connectors directory. Works on claude.ai and the desktop app.
What it can doBuild a site from a description, create and edit posts and pages, upload media, moderate comments, summarize stats, and more
Who controls itYou. Turn access on or off, pick read only or full access, switch off single tools, and exclude specific sites.
Which plansEvery WordPress.com plan, including free sites, through November 2026

What MCP means here (in one paragraph)

MCP, the Model Context Protocol, is an open standard that lets an AI assistant use outside tools. Instead of copying text out of ChatGPT and pasting it into the WordPress editor, the assistant talks to your site directly through a set of tools WordPress.com exposes: list posts, create a draft, read stats, change a setting. You approve the connection once with your WordPress.com login, and you decide which of those tools the assistant is allowed to touch.

If you have read my Pressable MCP overview, it is the same idea. Pressable MCP works at the hosting level (backups, PHP versions, domains, WP-CLI). The WordPress.com integration works at the site and content level. My Pressable MCP vs WordPress MCP post covers the difference in more detail.

What you can ask it to do

Build a site from a description

Describe what you want, something like “a simple site for my dog walking business in Portland with a services page, a booking contact form, and a friendly look,” and the assistant can create the site, pick and activate a theme, and add pages using the theme’s patterns. It is a fast way to get past the blank screen. You will still want to rewrite the copy in your own voice and swap in real photos before you launch.

Upload a post as a draft

This is the one I use most. Paste your notes or an outline, ask for a post, and have it saved to your site as a draft. You open the editor, read it, fix what needs fixing, and publish when you are ready. The assistant can also add categories and tags, upload images from a URL, and fill in alt text.

Summarize your traffic

Ask “how did my site do last month, and which posts brought in the most visitors?” and you get a plain summary of your WordPress.com stats instead of clicking through charts. It is handy for a quick weekly check-in or for spotting an old post that is suddenly getting attention.

Everything else

Per the WordPress.com capabilities list, the tools also cover comments (approve, reply, mark spam), themes and global styles, menus, plugins on plans that support them, domains and DNS, site settings, and users. Some things are off limits, such as WooCommerce prices, stock, and orders, and layouts built with page builders like Elementor.

Prompts to try

  • “Build me a one-page site for a yoga studio called Still Point. Calm colors, a class schedule section, and a contact form.”
  • “Turn these notes into a 900-word blog post and save it as a draft. Don’t publish it.”
  • “Summarize my site traffic for the last 30 days. Which five posts got the most views?”
  • “List my draft posts older than 60 days so I can decide what to finish or delete.”
  • “Find posts with images missing alt text and suggest alt text for each one.”
  • “Show me comments waiting for moderation and flag anything that looks like spam.”

Being clear about “save as a draft” or “don’t publish” is a good habit. The assistant asks before it makes changes, but saying it up front keeps things predictable.

How to connect ChatGPT to WordPress.com

  1. Log in to WordPress.com and open Preferences, then AI and MCP. Turn on Enable MCP access.
  2. In ChatGPT, open the WordPress.com plugin and click Install plugin.
  3. Log in with your WordPress.com account and pick an access level (more on that below), then click Allow.
  4. Start a chat and type @WordPress.com followed by your request.

If the connection ever drops, uninstall the plugin in ChatGPT’s settings and connect it again. WordPress.com’s ChatGPT setup guide has screenshots.

How to connect Claude to WordPress.com

  1. Turn on Enable MCP access in your WordPress.com AI and MCP preferences (same switch as above).
  2. Open the WordPress.com connector in Claude’s directory and click Connect.
  3. Log in to WordPress.com, choose an access level, and click Allow.
  4. Ask Claude about your site in any chat. It works on claude.ai and in the desktop app.

If Claude loses the connection, click the tools icon in the message box and choose Retry Connection. The full steps are in the Claude setup guide.

You stay in control of what the AI can touch

This is the part I like most, and the part worth five minutes of your time before you start.

  • Read only or full access. When you connect, you choose Read only (the assistant can look but not change anything) or Full access (it can create, edit, and delete). Start with Read only if you are nervous.
  • Tool by tool switches. In your AI and MCP preferences you can turn individual tools off. Want drafts but no deleting? Switch off the delete tools.
  • Per-site rules. Exclude specific sites from AI access, or set different rules for each site under Settings, then AI tools.
  • It asks first. The assistant asks for confirmation before it writes anything, and always asks before permanent deletes or billing changes.
  • User roles still apply. An editor on your site cannot use the AI to change settings or install plugins, because editors cannot do that in WordPress either.
  • There is a paper trail. Changes show up in your site’s Activity Log, and deleted posts and pages sit in the trash for 30 days.

Two cautions. Deleted media, categories, and tags are gone for good, so I keep delete tools off unless I need them. And any access level you pick applies to your whole WordPress.com account, so if you run client sites, use the site exceptions list.

Which WordPress.com plan do you need?

Right now you do not need a paid plan to try it. The integration works on every WordPress.com plan, including free sites, through November 2026. That makes this month a good time to test it on a real site.

Where a paid plan starts to matter is what the AI can work with. A paid plan gets you a custom domain, no ads, more storage, and on every paid tier you can now install third-party plugins and themes, which means more for the assistant to manage. Business and Commerce plans also include backups you can restore from, which is a nice safety net when you let an AI make changes. If you are weighing options, my WordPress.com vs WordPress.org comparison walks through the tradeoffs.

One more thing: WordPress.com’s Black Friday sale starts November 27. If you were already planning to upgrade, it may be worth waiting a couple of weeks.

Ready to let ChatGPT or Claude help run your site? Start on any WordPress.com plan, connect your assistant, and upgrade when you want a custom domain, plugins, and backups.

FAQ

Is the WordPress.com plugin for ChatGPT free?

Yes. It works on every WordPress.com plan, including free sites, through November 2026. You only need a ChatGPT account and a WordPress.com account.

Can Claude publish posts on my WordPress.com site?

It can if you give it full access. It asks before making changes, and you can ask it to save everything as a draft so you review and publish yourself.

Can I stop the AI from deleting things?

Yes. In your WordPress.com AI and MCP preferences you can switch off individual tools, including the delete tools, or connect with read only access.

Does it work with self-hosted WordPress?

WordPress.com says self-hosted sites connected through Jetpack can use MCP too. If your site is on a host like Pressable, you can also use Pressable MCP for hosting tasks.

What is the difference between this and Pressable MCP?

The WordPress.com integration manages your site and content: posts, pages, media, comments, stats. Pressable MCP manages hosting: backups, PHP versions, domains, and WP-CLI.

How do I disconnect it?

Turn off Enable MCP access in your WordPress.com AI and MCP preferences, and remove the plugin or connector in ChatGPT or Claude.

Related posts

Categories
AI Web Development WordPress

How to Get Your WordPress Site Cited in ChatGPT, Google AI Overviews, and Perplexity

To get a WordPress site cited by ChatGPT, Google AI Overviews, Perplexity, and the rest, you have three jobs: let the AI search crawlers reach your pages, write each page so a single passage can answer a question on its own, and then measure what happens. Most sites that never show up in AI answers are failing the first job without knowing it.

Last updated: November 1, 2026.

Disclosure: some links in this post are affiliate links, marked as sponsored. If you sign up through them I may earn a commission at no extra cost to you. I only recommend hosts I have used.

If you want the background on what AI optimization is and how it differs from SEO, start with What Is AIO? AI Optimization Explained. This post is the hands-on checklist.

Step 1: Know which AI crawlers matter

Each AI company runs more than one bot, and they do different jobs. The important split is between bots that power search and answers (block them and you disappear from that tool’s answers) and bots that collect training data (block them and you only opt out of future model training).

User agentCompanyWhat it doesIf you block it
GooglebotGoogleCrawls for Google Search, including AI Overviews and AI ModeYou drop out of Google entirely. Never block this.
Google-ExtendedGoogleA robots.txt token for Gemini training and grounding in some other Google productsOpts out of that use. Does not affect Search or AI Overviews.
BingbotMicrosoftCrawls for Bing, which also feeds CopilotYou lose Bing and Copilot visibility
OAI-SearchBotOpenAIFinds pages to show in ChatGPT search answersYou won’t appear in ChatGPT search answers
GPTBotOpenAICollects content that may be used to train OpenAI modelsOpts out of training only
ChatGPT-UserOpenAIFetches a page when a ChatGPT user asks it toOpenAI says robots.txt rules may not apply, since a person asked
Claude-SearchBotAnthropicIndexes pages for Claude’s search resultsLess visibility in Claude’s search answers
ClaudeBotAnthropicCollects content that may be used to train ClaudeOpts out of training only
Claude-UserAnthropicFetches a page when a Claude user asks a questionClaude can’t read your page for that user
PerplexityBotPerplexityIndexes pages for Perplexity answersYou won’t be surfaced in Perplexity search

Sources: OpenAI crawler docs, Anthropic’s help center article on its crawlers, and Google’s AI features documentation, which is explicit that Googlebot rules are the control for AI Overviews.

Step 2: Check and fix your robots.txt

Open yourdomain.com/robots.txt in a browser. If you see Disallow: / under OAI-SearchBot, Claude-SearchBot, PerplexityBot, or User-agent: *, that’s your problem.

A common middle ground is to allow the search bots and opt out of training. It looks like this:

# Show up in AI search and AI answers
User-agent: OAI-SearchBot
Allow: /

User-agent: Claude-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

# Opt out of model training
User-agent: GPTBot
Disallow: /

User-agent: ClaudeBot
Disallow: /

User-agent: Google-Extended
Disallow: /

# Everyone else
User-agent: *
Disallow: /wp-admin/
Allow: /wp-admin/admin-ajax.php

Sitemap: https://www.example.com/wp-sitemap.xml

Swap in your own domain on the sitemap line. OpenAI says changes to robots.txt take about 24 hours to reach its systems, so don’t panic if nothing changes the same afternoon. Whether you block training bots at all is a judgment call. Some site owners figure being in the training data helps brand recall later. I don’t think there is a wrong answer, as long as you block on purpose and not by accident.

Where robots.txt lives on WordPress

Unless a physical robots.txt file sits in your site’s root folder, WordPress generates one on the fly. That’s how this blog works: I checked, and there is no file on disk. The generated version lists my sitemaps and blocks only /wp-admin/, so every AI crawler is welcome here. You have three ways to change a virtual robots.txt:

  • Your SEO plugin’s robots.txt editor, if you run one (Yoast, Rank Math, and All in One SEO all have one).
  • Upload a real robots.txt file to the root folder. It overrides the virtual one completely, so include everything you need.
  • Add rules with the robots_txt filter in a small must-use plugin. This is what I prefer because it survives theme changes and needs no plugin:
<?php
// wp-content/mu-plugins/ai-robots.php
// Adds AI crawler rules to the robots.txt WordPress generates.
add_filter( 'robots_txt', function ( $output, $public ) {
    if ( ! $public ) {
        return $output; // Site is set to discourage search engines.
    }
    $output .= "\nUser-agent: GPTBot\nDisallow: /\n";
    $output .= "\nUser-agent: ClaudeBot\nDisallow: /\n";
    $output .= "\nUser-agent: Google-Extended\nDisallow: /\n";
    return $output;
}, 10, 2 );

While you are in there, check Settings > Reading. If “Discourage search engines from indexing this site” is ticked, WordPress tells every crawler to stay away. It gets left on after launches more often than anyone admits.

Step 3: Check your firewall and CDN

robots.txt is a polite request. Firewalls are not. If your CDN or security plugin blocks a bot outright, your robots.txt rules don’t matter.

  • Cloudflare. Starting July 1, 2025, Cloudflare began blocking known AI crawlers by default on newly added domains. If your site moved to Cloudflare after that, look at the AI crawler settings in your dashboard and decide which bots to let through. Cloudflare can control search bots and training bots separately.
  • Security plugins. Some bot-blocking rules in security plugins lump AI crawlers in with scrapers. Check the blocked traffic log.
  • Host-level protection. Many managed hosts run bot protection at the edge. Usually it leaves verified crawlers alone, but if your site disappears from AI answers after a move, ask support.

A quick test from the command line:

curl -s https://www.example.com/robots.txt

# Rough check for user-agent based blocking (a 403 here is a red flag)
curl -s -o /dev/null -w "%{http_code}\n" -A "OAI-SearchBot" https://www.example.com/
curl -s -o /dev/null -w "%{http_code}\n" -A "PerplexityBot" https://www.example.com/

This only catches blocks based on the user agent string. A firewall that verifies real bots by IP address may treat your test differently from the actual crawler, so treat a 200 as “probably fine” and a 403 as “definitely look into it.”

Step 4: Get indexed in Google and Bing

AI answers are built on search indexes, so the boring setup work still pays:

  • Verify your site in Google Search Console and submit your sitemap. WordPress has a built-in one at /wp-sitemap.xml unless an SEO plugin or Jetpack replaced it (this blog uses Jetpack’s /sitemap.xml).
  • Verify in Bing Webmaster Tools too. People skip Bing, but Copilot is built on it, and Bing now reports how often you get cited in AI answers.
  • Turn on IndexNow if your SEO plugin or host supports it. It pings Bing and other participating engines when you publish or update a post, instead of waiting for a recrawl.

Step 5: Make every page easy to quote

Once crawlers can reach you, the content has to be worth lifting. AI tools quote passages, so write in passages:

  • Lead with the answer. The first two sentences under the title should answer the question the title asks. Same rule under each H2.
  • Use question headings where it is natural, like “How long does a WordPress migration take?” That mirrors how people prompt AI tools.
  • One idea per paragraph, and name the subject instead of saying “it.” A paragraph that starts “This plugin also…” can’t be quoted alone.
  • Put comparisons in tables and steps in numbered lists.
  • Date your content. A visible “Last updated” line, and real updates when facts change.
  • Add an FAQ section for the questions people actually ask, with FAQPage structured data that matches the visible text word for word. Google is clear that structured data should match what’s on the page.
  • Keep key content in the HTML. Many AI crawlers fetch the raw page and run little or no JavaScript, so text that only loads through scripts, sliders, or tabs may never be seen.

Here is the difference in practice. A typical old intro:

“In today’s fast-paced digital world, website speed matters more than ever. In this article, we’ll explore some of the many factors that can affect how quickly your WordPress site loads.”

The AIO version:

“The fastest way to speed up a slow WordPress site is to fix hosting and caching first, then images, then plugins. Most sites get the biggest gain from page caching, which a good managed host handles for you.”

The second one can be quoted as a complete answer. The first one says nothing.

Step 6: Measure AI traffic and citations

Measurement is patchy, but you can get a decent picture:

  • GA4. In Explore, build a free-form report with Session source as the dimension and filter it with this regex: chatgpt\.com|perplexity\.ai|gemini\.google\.com|copilot\.microsoft\.com|claude\.ai. ChatGPT usually adds utm_source=chatgpt.com to the links it shows, which helps. Two caveats: many AI clicks arrive with no referrer and land in Direct, and in October 2026 a ChatGPT bug stripped that tag for about a week before OpenAI fixed it. Assume your AI numbers are an undercount.
  • Bing Webmaster Tools AI Performance. Shows total citations in Copilot and Bing AI answers, which pages get cited, and the grounding queries behind them.
  • Search Console. AI Overviews and AI Mode clicks are mixed into the regular Web numbers. You can’t separate them, but sudden drops in clicks with steady impressions are often an AI Overview taking the click.
  • Manual checks. Keep a list of ten questions your site should answer. Ask them in ChatGPT, Perplexity, and Google once a month and write down who gets cited.

The short checklist

  1. robots.txt allows OAI-SearchBot, Claude-SearchBot, PerplexityBot, Googlebot, and Bingbot
  2. “Discourage search engines” is off
  3. CDN and security plugin aren’t blocking AI search bots
  4. Sitemap submitted to Google Search Console and Bing Webmaster Tools
  5. Every key page answers its question in the first two sentences
  6. Comparisons in tables, steps in lists, FAQ with matching structured data
  7. Visible “Last updated” dates
  8. AI referral report saved in GA4

Fast pages for readers and crawlers

A crawler that times out can’t cite you. This blog runs on Pressable, which puts Edge Cache in front of WordPress and includes staging sites, so I can test robots.txt and plugin changes before they go live.

FAQ

How do I get my website to show up in ChatGPT?

Allow OAI-SearchBot in your robots.txt and firewall, make sure your pages are indexed in search engines, and write pages that answer a specific question in the first two sentences. OAI-SearchBot is the crawler OpenAI uses to find pages for ChatGPT search answers.

Does blocking GPTBot remove my site from ChatGPT?

No. GPTBot collects content for model training. Search visibility in ChatGPT is controlled by OAI-SearchBot, so you can block GPTBot and still appear in ChatGPT search answers.

Does blocking Google-Extended remove my site from AI Overviews?

No. Google says Googlebot robots.txt rules control crawling for Search, including AI Overviews and AI Mode. Google-Extended only covers Gemini training and grounding in some other Google products.

Where is the robots.txt file in WordPress?

Unless a physical robots.txt file exists in the site root, WordPress generates a virtual one. You can change it with an SEO plugin, by uploading a real robots.txt file, or with the robots_txt filter in a must-use plugin.

How do I track traffic from ChatGPT and Perplexity in Google Analytics 4?

In GA4 Explore, use Session source as the dimension and filter with a regex such as chatgpt.com, perplexity.ai, gemini.google.com, copilot.microsoft.com, and claude.ai. Expect an undercount, because many AI clicks arrive without a referrer and show up as Direct.

Related posts

Categories
Web Hosting WordPress

How to Fix ERR_TOO_MANY_REDIRECTS in WordPress

ERR_TOO_MANY_REDIRECTS means your browser got bounced between URLs until it gave up. Chrome and Firefox both stop after 20 redirects. On a WordPress site the cause is almost always two settings that disagree about the “real” address of the site: http or https, www or no www. Fix the disagreement and the loop goes away.

Last updated: October 28, 2026.

Disclosure: some links in this post are affiliate links, marked as sponsored. If you sign up through them I may earn a commission at no extra cost to you. I only recommend hosts I have used.

The same error shows up under different names depending on the browser:

  • Chrome and Edge: This page isn’t working. example.com redirected you too many times. ERR_TOO_MANY_REDIRECTS
  • Firefox: The page isn’t redirecting properly
  • Safari: Safari can’t open the page because too many redirects occurred

I have run into this on client sites more times than I can count, usually right after someone “just turned on HTTPS” or put the site behind Cloudflare. Here is the order I check things in, fastest first.

What causes a WordPress redirect loop

CauseTypical signFix
Stale cookies or cacheLoop only happens for you, or only when logged inClear cookies for the domain, purge caches
WordPress Address and Site Address disagreeStarted right after editing Settings > GeneralSet both to the same https URL
Cloudflare SSL mode set to FlexibleSite is behind Cloudflare and the host forces HTTPSSwitch SSL/TLS mode to Full (strict)
Two HTTPS or www redirects fightingStarted after adding a plugin, an .htaccess rule, or a host redirectKeep one redirect, remove the rest
HTTPS not detected behind a proxyOnly wp-admin loops, often after FORCE_SSL_ADMINAdd the X-Forwarded-Proto check to wp-config.php
A plugin redirecting on its ownRedirect, language, membership, or security plugin recently changedDeactivate plugins, then turn them back on one by one

Step 1: Rule out your own browser

Open the site in a private window or on your phone over cellular. If it loads there, the problem is a cookie or cached redirect on your machine. Clear cookies for that one domain (not your whole browser) and try again.

If you can use a terminal, curl shows you the whole chain, which is the fastest way to see where the loop is:

curl -sIL https://example.com | grep -iE '^(HTTP|location)'

You will see a list of status codes and Location headers. A loop usually looks like the same two URLs taking turns, for example http to https and back again, or www to non-www and back again. That pattern tells you which two settings are fighting.

Step 2: Check the WordPress Address and Site Address

WordPress stores two URLs: siteurl (WordPress Address) and home (Site Address). On most sites they should be identical, including https and www. If one says http://example.com and your host forces https://www.example.com, you get a loop.

You usually can’t reach wp-admin while the loop is happening, so check them with WP-CLI:

wp option get home
wp option get siteurl

# set both to the address you actually want
wp option update home 'https://www.example.com'
wp option update siteurl 'https://www.example.com'

No WP-CLI? Add these two lines to wp-config.php above the line that says “That’s all, stop editing”. They override the database values:

define( 'WP_HOME', 'https://www.example.com' );
define( 'WP_SITEURL', 'https://www.example.com' );

You can also edit the siteurl and home rows in the wp_options table with phpMyAdmin. If you’re on WP Engine, here is how to get into phpMyAdmin there.

Step 3: Fix Cloudflare’s SSL mode

This is the most common cause I see. With Cloudflare’s Flexible SSL mode, visitors connect to Cloudflare over HTTPS, but Cloudflare connects to your server over plain HTTP. Your server or WordPress sees an HTTP request and redirects to HTTPS. Cloudflare passes that redirect back to the browser, the browser asks again over HTTPS, Cloudflare fetches over HTTP again, and around it goes.

The fix: in the Cloudflare dashboard go to SSL/TLS and set the encryption mode to Full (strict). That makes Cloudflare talk to your server over HTTPS, which works as long as your host has a valid certificate installed. Every managed WordPress host I use issues one for free.

While you’re in Cloudflare, look for duplicate redirects in Redirect Rules or old Page Rules, and check whether Always Use HTTPS is on. That setting is fine on its own, but it adds one more redirect to the pile if your host or a plugin is already doing the same job.

Step 4: Remove duplicate HTTPS and www redirects

A redirect to HTTPS should happen in exactly one place. Common places it hides:

  • Your host’s dashboard (many managed hosts force HTTPS at the platform level)
  • An SSL plugin such as Really Simple SSL
  • Rules in .htaccess on Apache servers
  • A redirect plugin like Redirection, or your host’s redirect tool
  • Cloudflare or another CDN

Pick one, usually the host or CDN since it runs before WordPress loads, and turn off the others. Do the same for www versus non-www. If your host runs NGINX without Apache, .htaccess is ignored completely, so rules there won’t be the cause, but they won’t fix anything either. Pressable is one of those hosts, and it handles redirects with a custom-redirects.php file instead. For Apache sites, my .htaccess file for WordPress shows a clean HTTPS rule.

Step 5: Make WordPress see HTTPS behind a proxy

If the front end works but /wp-admin/ loops, WordPress probably doesn’t know the request came in over HTTPS. That happens behind load balancers and some proxies that end the HTTPS connection before it reaches PHP. WordPress checks is_ssl(), gets false, and redirects the admin to HTTPS again.

Add this to wp-config.php, above the “stop editing” line:

if ( isset( $_SERVER['HTTP_X_FORWARDED_PROTO'] ) && 'https' === $_SERVER['HTTP_X_FORWARDED_PROTO'] ) {
    $_SERVER['HTTPS'] = 'on';
}

Managed WordPress hosts normally handle this for you, so on those platforms this is rarely the fix. It matters most on self-managed servers and container setups.

Step 6: Turn off plugins without wp-admin

If the URLs and SSL settings are right and the loop is still there, a plugin is the next suspect. Save a list of active plugins first so you can put things back the way they were:

wp plugin list --status=active --field=name > active-plugins.txt
wp plugin deactivate --all

If the site loads, reactivate plugins one at a time and reload after each one until the loop comes back. No WP-CLI? Rename wp-content/plugins to plugins-off over SFTP, which disables every plugin, then rename it back and activate them individually from wp-admin.

Step 7: Purge every cache

A redirect can get cached at several layers: your host’s page cache, a CDN, a caching plugin, and the browser itself. After you fix the real cause, purge all of them, then test in a private window. On WP Engine that means the cache button in the User Portal or WP Admin, covered in How to Clear the WP Engine Cache.

Want HTTPS handled for you?

On managed WordPress hosting the SSL certificate, the HTTPS redirect, and the page cache all live in one dashboard, which removes most of the places a redirect loop can come from. WP Engine is the host I have written about most on this blog.

FAQ

Is ERR_TOO_MANY_REDIRECTS a problem with my computer or the website?

Usually the website. Test in a private window or on another device. If it loads there, clear cookies for that domain on your machine. If it fails everywhere, the site’s settings need fixing.

Will clearing cookies fix ERR_TOO_MANY_REDIRECTS?

Only when the loop is caused by a stale cookie or a cached redirect in your browser. If the loop happens on every device, the cause is on the server or CDN.

How many redirects does Chrome allow before showing the error?

Chrome and Firefox both give up after 20 redirects in a row.

Why does only wp-admin have a redirect loop?

Usually WordPress can’t tell the request arrived over HTTPS, which is common behind a proxy or load balancer. Setting $_SERVER[‘HTTPS’] from the X-Forwarded-Proto header in wp-config.php fixes it.

Can a redirect loop hurt SEO?

Yes, if it lasts. Search engines can’t crawl pages they can’t reach, so fix it quickly and then check Google Search Console for crawl errors.

Related posts

Categories
Web Hosting WordPress

How to Fix Mixed Content Warnings in WordPress

Mixed content means a page loaded over HTTPS is pulling in some files (images, scripts, stylesheets, fonts, iframes) over plain HTTP. On a WordPress site it almost always happens after a move to HTTPS, because old http:// URLs are still saved in the database. The fix is a careful search and replace, plus a quick look at your theme and any hardcoded embeds.

Last updated: October 28, 2026.

Disclosure: some links in this post are affiliate links, marked as sponsored. If you sign up through them I may earn a commission at no extra cost to you. I only recommend hosts I have used.

What mixed content looks like

Depending on what is loading over HTTP, you might see:

  • No padlock, or a “Not secure” label, even though the address starts with https
  • Images that don’t appear
  • A broken layout, because a stylesheet was blocked
  • Sliders, forms, or embeds that stop working, because a script or iframe was blocked

Modern browsers handle the two kinds of mixed content differently. Images, audio, and video are upgraded to HTTPS automatically, and blocked if the HTTPS version doesn’t exist. Scripts, stylesheets, and iframes loaded over HTTP are blocked outright, and that is what breaks pages.

Step 1: Find every insecure URL

Open the page in Chrome, press F12, and click the Console tab. Each problem shows up as a line like this:

Mixed Content: The page at 'https://example.com/' was loaded over HTTPS,
but requested an insecure resource 'http://example.com/wp-content/uploads/photo.jpg'.

That tells you exactly which file is the problem. Check a few different page types (home page, a post, a page, your contact form), because a widget or a single post can be the only offender.

To find every stored copy at once, search the database with WP-CLI:

wp db search 'http://example.com' --all-tables

Step 2: Set both site URLs to https

In Settings > General, make sure WordPress Address and Site Address both start with https:// and match the www or non-www version your site actually uses. If changing these locks you out with a redirect loop, see How to Fix ERR_TOO_MANY_REDIRECTS in WordPress.

Step 3: Search and replace old URLs in the database

This fixes most mixed content in one pass. Back up first. Then do a dry run, which reports what would change without changing anything:

wp db export before-https.sql

wp search-replace 'http://example.com' 'https://example.com' --all-tables --skip-columns=guid --dry-run

# looks right? run it for real
wp search-replace 'http://example.com' 'https://example.com' --all-tables --skip-columns=guid

A few notes from doing this on a lot of sites:

  • Run it again for http://www.example.com if your site ever used www.
  • WP-CLI’s search-replace handles serialized data correctly. A raw SQL UPDATE ... REPLACE() query does not, and can break widgets and theme settings.
  • Skip the guid column. WordPress uses it as a permanent ID, not a link, and the official advice is to leave it alone.
  • No WP-CLI? The Better Search Replace plugin does the same job from wp-admin, including a dry run.

Try it on a staging copy first if your host gives you one. Here is how staging works on Pressable.

Step 4: Check the theme, widgets, and custom CSS

If the console still shows warnings after the search and replace, the URL is probably not in the database. Places to look:

  • Theme files: search your theme for http://. Background images in style.css are a common one.
  • Page builders that cache CSS to files. Elementor, for example, has a Regenerate CSS option under Elementor > Tools. Run it after the replace.
  • Hardcoded script or font tags added by a plugin or in a header/footer code snippet
  • Third-party embeds. If an old widget or iframe only works over HTTP, swap it for an HTTPS version or remove it.

Step 5 (stopgap): Tell browsers to upgrade requests

The upgrade-insecure-requests directive tells the browser to request every http:// resource on the page over HTTPS instead. You can send it as a header from your server or CDN:

Content-Security-Policy: upgrade-insecure-requests

SSL plugins like Really Simple SSL can add it for you too. It only works if the file actually exists on HTTPS, and it hides the problem rather than fixing it, so I treat it as a stopgap while the database cleanup gets done.

Step 6: Purge caches and test again

Page caches, CDNs, and minify plugins can keep serving the old HTML with the old URLs. Purge everything, then reload the page in a private window and check the console again. A clean console and a padlock means you are done.

Where http:// URLs hide, and how to fix each

Where it livesExampleFix
Post and page contentImages inserted before the HTTPS switchwp search-replace or Better Search Replace
Widgets and theme settingsLogo URL, footer HTMLsearch-replace (handles serialized data)
Theme filesBackground image in style.cssEdit the file, use https or a relative path
Page builder CSS filesCached CSS with old URLsRegenerate CSS in the builder’s tools
Third-party embedsOld widget or iframe on httpUse the HTTPS embed code or remove it

Free SSL on every domain

Pressable issues free SSL certificates for every domain on your site, and includes staging sites, so you can test a database search and replace before you run it on the live site.

FAQ

What is mixed content in WordPress?

Mixed content is when a page served over HTTPS loads some files, such as images, scripts, or stylesheets, over plain HTTP. It usually comes from old http:// URLs left in the database after a switch to HTTPS.

How do I find mixed content on my site?

Open the page in Chrome, press F12, and check the Console tab. Each insecure file is listed with its full URL. WP-CLI’s wp db search command finds every stored copy in the database.

Do I need the Really Simple SSL plugin to fix mixed content?

No. A one-time search and replace of http:// URLs in the database fixes most cases without a plugin. An SSL plugin can help as a stopgap while you clean up.

Why does my site still say Not secure after fixing mixed content?

Check for cached pages, a form that submits to an http:// address, hardcoded URLs in theme files, or an expired SSL certificate.

Should I replace http with https in the guid column?

No. WordPress uses the guid as a permanent identifier, not a link, so skip it with –skip-columns=guid.

Related posts

Categories
AI Tools Web Hosting WordPress

WordPress.com AI Website Builder: How It Works and What to Fix Before You Launch

Some links on this page are affiliate links. If you sign up through them I may earn a commission at no extra cost to you.

Most people who want a website get stuck at the blank page. They know what the site is for, but picking a theme, writing a homepage, and finding images is where the project stalls for weeks.

The WordPress.com AI Website Builder goes after that exact problem. You describe the site you want, answer a few questions, and it builds a first draft with a layout, images, and starter content. Then you finish it in the normal WordPress editor. Here is how it works, what to have ready, and what you still need to do yourself before you hit publish.

What the AI Website Builder does

You describe your site in a chat box, something like “Create a website for my dog grooming business in Portland.” The AI asks follow-up questions about design and content, then shows you a site brief: an overview, the pages it plans to build, your goals, and your contact details. You can add or remove pages at that point. When you approve the brief, it builds the site.

What you get back is a real WordPress site, not a locked-down template. It has a designed layout, suggested images, starter text on each page, and a navigation menu. The site opens in the AI Editor with a live preview next to the chat, so you can keep refining with prompts or switch to editing by hand.

One thing to know up front: building and launching with the AI Website Builder requires a WordPress.com account and a paid plan. You pick the plan before the build starts.

What to have ready before you start

The AI does better work when you give it better input. Spend ten minutes on this list before you open the builder:

  • The site’s purpose. What is it for and who is it for? “A portfolio for a wedding photographer in Austin” beats “a photography site.”
  • The site name. Your business name or the name you want on the header.
  • Your preferred style. Colors you like, the mood you want (clean, bold, warm, minimal), and any sites you admire.
  • Your planned content. The pages you need (Home, About, Services, Contact, Blog) and a rough idea of what goes on each.
  • Optional social links. The builder lets you share links to your social profiles to guide the design and content.

Expect the AI to ask follow-up questions. Answer them with specifics. Vague answers get you a generic site.

How the build works, step by step

  1. Open the AI Website Builder and click Get started. Log in or create a WordPress.com account.
  2. Search for a domain, or skip it for now and use a free WordPress.com address. You can add a custom domain later.
  3. Choose a paid plan and check out.
  4. Describe your site in the chat and send it.
  5. Answer the AI’s follow-up questions about design and content.
  6. Review the site brief. Add or remove pages here, before anything gets built.
  7. Click Create site. The build takes several minutes. You can leave the page and WordPress.com will email you when it is ready.

The work between a generated draft and a finished site

This is the part most AI builder reviews skip. The AI gives you a strong starting point, not a finished site. Plan on spending real time here.

Rewrite the copy

Starter text is written to fill space. Read every page. You can rewrite text directly in the editor or ask the AI to change the tone or length of a section. Be specific in your prompts: name the section and describe what you want, such as “Make the About section shorter and more casual.”

Pay close attention to anything that makes a claim about you. Replace placeholder business descriptions, service lists, and testimonials with real, accurate material. A made-up testimonial on a live business site is a bad look, and it can be a legal problem.

Swap the images

Suggested images are a placeholder for your own photos. You can replace them with uploads, items from your Media Library, AI-generated images, or stock photos. Real photos of your work, your team, or your space almost always beat generic stock.

Adjust pages and navigation

You can add pages with a prompt like “Create a Team page for my business,” pick from the layouts it suggests, and save. The menu works the same way: select it and ask for changes such as “Add a Blog link to the navigation.” You can also add and edit pages and menu items manually.

Fine-tune the design

Ask for color or font changes in plain language, or click a single element and describe the change you want. Every change can be undone, and you can also set colors and fonts by hand in the Site Editor under Styles.

Your pre-launch checklist

New WordPress.com sites start in Coming Soon mode, so nobody sees your site until you click Launch site. Use that time. Before you launch, check:

  • Every button goes where it should. Click each one.
  • Social links point to your real profiles, not placeholders.
  • Contact details (email, phone, address, hours) are correct.
  • No placeholder testimonials, team members, or business descriptions are left.
  • Images are yours or properly licensed, and they fit the page they are on.
  • Each menu item opens the right page.
  • The site reads well on your phone.

What it does not do: online stores

The AI Website Builder does not currently create ecommerce features. It will not set up products, a cart, or checkout. If you need to sell online, build the site first, then install WooCommerce separately on a paid plan. If a store is the main point of your site, start with my comparison of WordPress.com Commerce vs DIY WooCommerce hosting instead.

Who it is a good fit for

  • New bloggers who want a clean, designed site without picking through hundreds of themes.
  • Freelancers and creatives who need a portfolio up quickly and plan to drop in their own work.
  • Service businesses such as contractors, coaches, salons, and consultants that need a few clear pages and a contact form.
  • Anyone launching a simple landing page for an event, product idea, or newsletter.

It is a weaker fit if you need a store, a membership site, or heavy custom functionality, or if you already have a WordPress site you want to redesign. In those cases you are better served by a full WordPress setup on managed hosting.

My take

I like the way this is set up. You are not locked into what the AI produces, and you are not stuck in a proprietary builder. Under the hood it is a normal WordPress site, so everything you learn in the editor carries over, and you can grow it with plugins and a custom domain later.

The catch is that the first draft is only as good as your input and your editing. Go in with your name, purpose, style, and content ready, and budget an afternoon to replace the placeholder material. Do that and you will have a site that looks designed, reads like you, and is ready to launch.

Ready to try it? Describe your site and let the AI build your first draft. A WordPress.com account and paid plan are required to build and launch.

FAQ

Is the WordPress.com AI Website Builder free?

No. You need a WordPress.com account and a paid plan to build and launch a site with it. WordPress.com says the builder is included with all paid plans.

Can the AI Website Builder make an online store?

Not right now. The AI does not build ecommerce features. If you need a store, you can install WooCommerce yourself on a paid plan after the site is created.

Can I edit what the AI builds?

Yes, all of it. You can keep asking the AI for changes or open any page in the WordPress editor and change the text, images, layout, pages, and menu by hand.

Will the AI write my business details for me?

It writes starter copy, but treat it as a placeholder. Replace any business descriptions, testimonials, and contact details with real, accurate information before you launch.

Does the site go live as soon as the AI finishes?

No. A new WordPress.com site starts in Coming Soon mode, so only you can see it. It goes public when you click Launch site.

What kinds of sites is it good for?

Blogs, portfolios, landing pages, and service business sites such as a bakery, a photographer, or a consultant. It is not the right tool for stores or apps with complex integrations.

Related