While Webmentions and Pingbacks serve similar purposes—notifying websites when they've been linked to—Webmentions are a modern replacement that fixes many of Pingback's limitations.

Key Differences

Protocol Simplicity

Pingbacks:

• Use XML-RPC, a complex protocol
• Require XML parsing libraries
• More prone to implementation errors
• Difficult to debug

Webmentions:

• Use simple HTTP POST requests
• Send data as form-encoded parameters
• Easy to implement and test
• Human-readable and debuggable

Verification Process

Pingbacks:

• Limited verification
• Only confirms the link exists
• Can't extract context or metadata
• Prone to spam

Webmentions:

• Flexible verification
• Can parse rich metadata via microformats
• Supports different interaction types (likes, replies, etc.)
• Better spam prevention options

Security

Pingbacks:

• XML-RPC endpoint can be exploited
• Often used in DDoS attacks
• Limited rate limiting options
• Many sites disable it entirely

Webmentions:

• Simpler attack surface
• Easier to implement rate limiting
• Better security best practices
• Asynchronous processing reduces attack vectors

Technical Comparison

Pingback Request

A Pingback request looks like this:

<?xml version="1.0" encoding="utf-8"?>
<methodCall>
  <methodName>pingback.ping</methodName>
  <params>
    <param><value><string>source_url</string></value></param>
    <param><value><string>target_url</string></value></param>
  </params>
</methodCall>

Webmention Request

A Webmention request is much simpler:

POST /webmention HTTP/1.1
Host: example.com
Content-Type: application/x-www-form-urlencoded

source=https://source.example.com/post&target=https://example.com/article

Feature Comparison

Why Webmentions Won

The web community has largely moved toward Webmentions because:

1. Simpler to implement: No XML-RPC required
2. More secure: Fewer attack vectors
3. Richer data: Microformats support
4. Better ecosystem: Active development and community
5. W3C standard: Official recommendation since 2017

Migration Path

If you're currently using Pingbacks, migrating is straightforward:

1. Keep Pingbacks Running (Optional)

You can support both during transition:

<!-- Support both protocols -->
<link rel="pingback" href="https://example.com/xmlrpc.php" />
<link rel="webmention" href="https://example.com/webmention" />

2. Convert Pingback Data

Existing Pingbacks can be converted to Webmentions:

// Pseudocode for migration
const webmentions = pingbacks.map(pingback => ({
  source: pingback.source_url,
  target: pingback.target_url,
  verified: true,
  type: 'mention',
  receivedAt: pingback.created_at
}));

3. Disable Pingbacks

Once Webmentions are working, you can safely disable Pingbacks:

WordPress:

// In functions.php
add_filter('xmlrpc_enabled', '__return_false');
add_filter('pings_open', '__return_false', 10, 2);

Nginx:

location = /xmlrpc.php {
    deny all;
}

Real-World Example

Pingback Flow

1. Alice writes a post linking to Bob's article
2. Alice's system sends XML-RPC request to Bob
3. Bob's system parses XML, verifies link exists
4. Bob shows "Alice linked to this" (no context)

Webmention Flow

1. Alice writes a post linking to Bob's article
2. Alice's system sends HTTP POST to Bob's endpoint
3. Bob's system fetches Alice's page
4. Bob parses microformats to get Alice's name, photo, and quote
5. Bob shows "Alice replied: [preview of her thoughts]" with her photo

Community Adoption

Major platforms supporting Webmentions:

• WordPress: Via plugins (Webmention, Semantic Linkbacks)
• Ghost: Third-party integrations
• Jekyll/Hugo/Eleventy: Static site plugins
• Micro.blog: Native support
• Known: Built-in support

Most modern platforms have deprecated or removed Pingback support.

Should You Support Both?

Short answer: No, focus on Webmentions.

Exceptions:

• You have many legacy Pingback connections
• You're transitioning and need overlap
• Your CMS supports both with zero effort

Otherwise, Webmentions provide everything Pingbacks did and much more, with better security and developer experience.

Learn More

• Webmention spec
• Pingback spec (deprecated)
• IndieWeb comparison