---
title: "XML-RPC"
description: "No. The Feast Plugin doesn't use XML-RPC, so it's safe to leave XML-RPC blocked on your site. If your host is turning on an XML-RPC block (for example, blocking requests to `/xmlrpc.php`), you don't need to change anything for Feast.…"
url: "https://docs.feastdesignco.com/learn/xml-rpc/"
updated: "2026-11-20"
category: Compatibility
---

# XML-RPC

No. The Feast Plugin doesn't use XML-RPC, so it's safe to leave XML-RPC blocked on your site. If your host is turning on an XML-RPC block (for example, blocking requests to `/xmlrpc.php`), you don't need to change anything for Feast.

## What is XML-RPC?

XML-RPC is an older way for outside apps and services to talk to WordPress, through a file called `xmlrpc.php`. WordPress has had it switched on by default since version 3.5.

It's used by:

- Remote publishing tools: apps that write and publish posts to your site without logging in to WordPress
- Pingbacks and trackbacks
- Jetpack, which connects to your site through `xmlrpc.php`

Because it's a common target for automated login attempts, many hosts now block it by default. Some, like BigScoots, already block it and have a guide for letting Jetpack through.

## Does the Feast Plugin affect this?

Only in one small way, and it's a protective one. The Feast Plugin never connects to your site over XML-RPC and nothing in it depends on XML-RPC being available.

What it does do is switch off pingbacks, the part of XML-RPC that's most often abused:

- The Feast Plugin always removes WordPress's pingback method from XML-RPC, so your site won't accept incoming pingbacks.
- Feast's recommended settings turn off pingbacks and trackbacks for new posts.
- **Admin > Feast Plugin > Tools > Disable Pingbacks and Trackbacks on All Posts** turns them off on every existing post in one click.

Whether XML-RPC is open or blocked is controlled by your host (or a security plugin), not by the Feast Plugin.

## What to do

For most food blogs: nothing. Leave your host's XML-RPC block switched on.

Before the block starts, check whether you rely on anything else that uses XML-RPC:

1. Do you publish posts from an app or tool outside WordPress? If so, check with that tool whether it still uses XML-RPC.
2. Do you use Jetpack? Ask your host whether Jetpack connections are still allowed once the block is on.
3. Make sure pingbacks and trackbacks are off (we recommend this anyway): run **Admin > Feast Plugin > Tools > Disable Pingbacks and Trackbacks on All Posts**, and in **Admin > Settings > Discussion** untick "Attempt to notify any blogs linked to from the post" and "Allow link notifications from other blogs (pingbacks and trackbacks) on new posts".

If one of your tools does need XML-RPC, turn off the block for that site in your hosting dashboard (your host's help docs will say where), or ask your host's support team.

## Related

- [Pingbacks](https://docs.feastdesignco.com/learn/pingbacks/)
- [Disable Trackbacks](https://docs.feastdesignco.com/learn/trackbacks/)

## Sources

- [XML-RPC Support](https://codex.wordpress.org/XML-RPC_Support) (WordPress Codex)
- [XML-RPC Extending](https://codex.wordpress.org/XML-RPC_Extending) (WordPress Codex)
- [Jetpack: How to Fix 'Server Unable to Communicate with Site' Error (Enable xmlrpc.php Access)](https://help.bigscoots.com/en/articles/512475-jetpack-how-to-fix-server-unable-to-communicate-with-site-error-enable-xmlrpc-php-access) (BigScoots Help Center)
- [Harden WordPress Login Security Without Performance Loss](https://www.bigscoots.com/blog/wordpress-login-security/) (BigScoots blog)
- [Everything You Need To Know About WordPress Security](https://www.dreamhost.com/blog/secure-your-wordpress-website/) (DreamHost blog, on disabling XML-RPC)
- [Using the Docket Cache plugin](https://help.dreamhost.com/hc/en-us/articles/11013621014676-Using-the-Docket-Cache-plugin) (DreamHost Knowledge Base, on Jetpack needing xmlrpc.php)
