Skip to main content

<Slushman />

unsplash-logo JOSHUA COLEMAN

Editor Links for Headless WordPress Themes

Published Aug 22, 2018

In my previous post, I talked about creating a headless front end for WordPress using Create React App. Turning my WordPress site into a headless React app was a massive learning experience. There were many challenges, like learning React, then learning the REST API, and creating custom endpoints. I won’t even mention battling CORS headers. One of the more interesting issues I ran into, with editor links, ultimately had a very simple solution.

The Problem

My WordPress install lives at and my live site (the part you’re reading now) lives at So when I’m writing content in WordPress and link to another post on my site, it creates a little problem. Should I link to Ideally, I’d link to since readers would visit that page. The question is: how can I link to the live domain while the site exists on another domain? I’d like to avoid manually editing every single link, especially for all the existing posts.

The Solution

Thankfully, the solution was much simpler than I originally thought. In my mind, this problem was an insurmountable monster. But WordPress solved this problem years ago. Before the REST API existed, people wanted to install WordPress in a subfolder so all the files don’t clutter up their site’s root folder. But they wanted the WordPress content to appear like it was just part of the rest of the site. The solution for this problem also solves the editor links problem for a headless front end.

Change URL Settings

In the admin, on the Settings > General page, there are two fields for a URL:

Since most every site I’ve worked on used WordPress to both manage and display the content, these settings have always been the same. However, since the front end and back end are on two different URLs, they need to be different values.

WordPress Address is the URL where your WordPress install lives. In this case, this is my WordPress backend, so the correct value is

Site Address is the URL for the viewable site. Since I’m going headless, this setting would be WordPress uses this value when creating editor links. So now when I create a link within the editor to another page or post within the site, the link goes to

Site settings in WordPress

The other big upside is all the links I’ve already created in past posts point to valid locations within my headless front end. If someone tries to visit my WordPress backend, the browser redirects to the same requested location on the front end.

Coming Up

Those redirects happen in my Headless Theme. But wait, why would I have a theme in WordPress if it’s not displaying any content? In my next post, I’ll talk through the details of my Headless WordPress Theme and why you still need a theme.

Share this post!

Check out these related posts:

Deploying a React App to Netlify

After you've built your headless WordPress front-end, you'll want to publish it. This is process for how I published mine to Netlify.

Headless Theme for WordPress

How to create a theme for a headless WordPress install. Even when the front-end of your site isn't displayed by WordPress, you still need a theme.