WotWP Blog

Where your Yoast or Rank Math settings go when you move

A small wooden index-card box of blank white cards, labeled SEO on a strip of kraft tape, with two cards lifted out and propped against it, on a blue background

The short answer

When you move a WordPress site to EmDash, two of your Yoast or Rank Math settings travel with the content: each page's SEO title and its meta description. They only travel through the EmDash Exporter plugin, and they land in plain fields that the new site's template has to print. Everything else the plugin did for you, from canonicals and noindex choices to redirects, schema, sitemaps and breadcrumbs, is rebuilt on the new site, so it has to be written down before the move and checked on every page after it.

  • Know what the plugin actually does. Yoast and Rank Math do eight jobs Google can see, some per page and some site-wide. The scores and traffic lights are advice for you, and Google never sees them.
  • Titles and descriptions can move. The exporter copies them into fields called SEO Title and SEO Description. If the template ignores those fields, the page quietly falls back to its plain title and excerpt.
  • The rest stays behind, and EmDash has a place for each one. Canonical and noindex live in each page's SEO panel, redirects on the Redirects screen, sitemaps and robots.txt are built in, and schema and breadcrumbs come from the template.
  • Check the page, not the settings screen. Compare what each live page sends to Google against a record of the old page, address by address.

None of this is hard to get right. It is easy to skip, because a page with a missing description still loads and looks fine.

What Yoast and Rank Math do on your site today

An SEO plugin does two kinds of work. It writes details into each page that search engines read, such as the title in the browser tab and the summary under it in Google. And it runs a few site-wide services, such as a sitemap and a redirect list. Only the parts Google can see need to survive a move.

What it does

What Google sees

Set per page or site-wide

SEO title

The blue headline in search results and the browser tab text

Per page, with a site-wide pattern as the fallback

Meta description

The short summary under the headline

Per page

Canonical

Which address is the "real" one when a page can be reached at two

Per page, usually automatic

Noindex

"Keep this page out of search results"

Per page, plus whole types such as tag pages

Redirects

An old address sending visitors and Google to its new one

Site-wide list (Yoast Premium or Rank Math)

Schema

Structured facts about the business and the page, in code visitors never see

Mostly automatic, site-wide

XML sitemap

A list of every page you want found

Site-wide, automatic

Breadcrumbs

The "Home › Services › Roof repair" trail on a page and sometimes in results

Site-wide, printed where the theme allows

Two more site-wide details often live in the plugin too: the Google Search Console verification code, and edits to robots.txt, the file that tells crawlers where they may go.

Yoast's schema is more than most owners realize. Its developer documentation says a base set of structured data, describing the web page, the website, and the organization or person behind it, is "included on every page of a website running the Yoast SEO plugin" (Yoast developer docs). That set disappears with the plugin unless the new site prints its own.

What does not need to move: the focus keyphrase, the readability score and the green, orange and red lights. They are writing advice shown in the editor. They never reach the page, so Google has nothing to miss.

What the EmDash importer carries: titles and descriptions

EmDash, Cloudflare's open-source CMS built on Astro that calls itself "the spiritual successor to WordPress", can carry your SEO titles and meta descriptions across, as long as the move uses its exporter plugin. Its SEO guide says the import through the EmDash Exporter "can copy Yoast and Rank Math SEO titles and descriptions into SEO Title and SEO Description fields on the target collection" (EmDash docs).

Three conditions sit inside that sentence.

  1. It needs the exporter, not the export file. WordPress's standard export file (Tools, Export) does not bring them. EmDash's migration guide says that import "writes the standard imported fields rather than copying every arbitrary meta key" (EmDash docs). Your SEO titles are one of those meta keys.
  2. It needs the switch on. The exporter "can also create and populate the supported featured-image and Yoast or Rank Math SEO fields when their import switches are enabled" (EmDash docs).
  3. It needs a template that prints them. The values arrive as "regular content fields, separate from the SEO panel, so the page template has to render them" (EmDash docs).

The third one is where moves go quiet. When a page's SEO fields are empty, EmDash's standard helper "falls back to the entry's title and excerpt fields" (EmDash docs). So a page whose imported title sits in an unread field still gets a title, just not the one you wrote. Nothing errors, the page looks normal, and the description Google shows becomes whatever the excerpt says.

The docs list titles and descriptions and nothing else from the SEO plugins. Plan for the social sharing titles and images you set in a plugin's social tab to be set again, too.

What stays behind, and where each setting lives on EmDash

Everything else is rebuilt, and EmDash has a built-in home for most of it. Its own SEO features cover each page's SEO panel, head tags, structured data, sitemaps, robots.txt, site-wide settings and redirects (EmDash docs). The job is to fill those homes with your old values, not to accept the defaults.

Setting

Moves on import?

Where it lives on EmDash

What to watch

Canonical

No

Canonical URL in each page's SEO panel

Usually left empty so each page points at itself. Re-enter only the pages that pointed somewhere else

Noindex

No

Hide from search engines in each page's SEO panel

It adds `noindex, nofollow` and drops the page from the sitemap. Re-hide every page that was hidden before

Redirects

No

The Redirects screen: 301, 302, 307, 308, or 410 for a page that is gone

Bring your old list across, then add one for every address that changed

Schema

No

The template. Built in: a `BlogPosting` graph on articles, a `WebSite` graph elsewhere

Business details, such as your organization, address or opening hours, need the template or a plugin to print them

XML sitemap

No, rebuilt

`/sitemap.xml`, built from your published pages

The address changes from the plugin's usual `/sitemap_index.xml`. Submit the new one in Search Console

Breadcrumbs

No

The template

Nothing prints them unless the template does

`robots.txt`

No, rebuilt

Built in, editable under Settings › SEO

Copy over any custom rules you relied on

Verification code

No

Settings › SEO (Google and Bing)

Only needed if you verified Search Console with a meta tag rather than DNS

A few details from EmDash's documentation are worth knowing as an owner.

  • Redirects are the biggest gap. The importer carries none of them, and the migration guide tells you to record existing redirects before you begin (EmDash docs). Your old list may sit in Yoast Premium, in Rank Math, in a separate redirect plugin, or with your host, so check all of them. Yoast's redirect manager can export its rules (Yoast). What a redirect is, and why it decides whether you keep your traffic explains which type to use.
  • EmDash adds some redirects on its own. When you rename a published page later, it "creates a 301 redirect from the old URL to the new one" and logs addresses that answered "page not found", up to 10,000 of them (EmDash docs). It cannot know what your old site redirected.
  • Schema is simpler by default. EmDash's built-in structured data is a BlogPosting graph on article pages and a WebSite graph on others (EmDash docs). A plugin or the template can add more. If your business details showed up in search through Yoast's organization data, decide whether the new site prints them.
  • The sitemap only lists what should be found. EmDash lists entries that are published and not hidden from search engines (EmDash docs), so hiding a page in the SEO panel removes it from the sitemap too.

How to check every page after the move

The check that catches all of this compares what each live page sends to Google with a record of the old page, address by address, before your domain switches. The settings screen tells you what someone typed. The page tells you what Google will read. EmDash's own docs warn that a template's hand-written tags that "read only data.title or data.excerpt do not apply the editor's canonical URL or no-index setting" (EmDash docs), which is exactly the kind of gap a settings screen hides.

  1. Before anything changes, record the old site. Crawl every public address and save, for each one, the title, the meta description, the canonical, whether it is hidden from search, and which schema types it carries. Export the redirect list. Note the sitemap address, any custom robots.txt rules and how Search Console is verified.
  2. On the new site, compare titles and descriptions. For every address, the <title> and meta description in the page's source should match your record, or differ on purpose. A crawler does this for a whole site. For a handful of pages, view the page source and search for <title>.
  3. Check canonicals. Each page's canonical should point at its own address on your real domain, unless the old page deliberately pointed elsewhere.
  4. Check what is hidden. Pages that were noindex before should be noindex now, and nothing else should be. The preview copy of the site should be hidden until launch, and unhidden after.
  5. Check redirects. Every address on the old list, and every address that changed, should answer with a single 301 to its closest match.
  6. Check schema on each kind of page. Run your home page, a post and a service or contact page through Google's Rich Results Test, old and new, and compare what each finds.
  7. Check the sitemap. Open /sitemap.xml and confirm it lists every page that should be found. Submit it in Search Console, and point the old sitemap address at the new one.
  8. Look at the breadcrumbs. On pages that had them, they should still be there and still link to the right pages.

This sits inside the wider move. The website migration SEO checklist covers the rest: the URL list, forms, launch and the 90 days after.

Who should stay on WordPress

If your site works, costs you little and nobody touches it, staying is a fine answer, and your SEO plugin can keep doing its job. Stores, member areas, online courses and sites built around one plugin feature should also stay for now, because moving them means rebuilding the feature, not just the pages. Check the fit guide if you are unsure which side you are on.

How we check this on a move

On every move from WordPress to EmDash, we check every URL, redirect, form, title, description, canonical and schema against your live site before anything switches. We carry the SEO details over from a crawl of your live pages, so a title or description reaches the new site even when the importer could not bring it. You see the comparison on a private preview, approve it, and keep a written way back. The conversion starts at $790 for up to 25 pages (pricing).

To see where your own site stands first, check your site for free.

Frequently asked questions

Will my Yoast titles and meta descriptions transfer to EmDash?

Yes, through the EmDash Exporter plugin with its SEO import switch turned on. They arrive as plain SEO Title and SEO Description fields, and the site's template has to print them. WordPress's standard export file does not carry them. Check each page's live title and description against the old site before launch.

Do I still need Yoast or Rank Math after moving to EmDash?

No. WordPress plugins do not run on EmDash. It has its own SEO panel on every page for the title, description, canonical and noindex, plus built-in sitemaps, robots.txt, redirects and basic structured data. Your old values still have to be entered or imported into those places.

What happens to my Yoast or Rank Math redirects when I move?

They stay behind. The importer carries no redirects, so export or copy your old list first, then add each rule on EmDash's Redirects screen. Add a 301 for every address that changes in the move too, and keep them for at least a year.

Will my XML sitemap still work after the move?

EmDash builds a new one at /sitemap.xml from your published pages. The address usually differs from the plugin's sitemap_index.xml, so submit the new sitemap in Google Search Console and redirect the old address to it. Hidden pages are left out automatically.

Does my schema markup move with my site?

No. Schema is code the plugin writes into each page, not content, so it ends when the plugin does. EmDash prints a basic article or website graph by default. Business details such as your organization, address or hours need the new template or a plugin to print them.

Does my Yoast focus keyphrase or SEO score matter after the move?

No. The focus keyphrase, readability score and colored lights are writing advice inside the WordPress editor. Google never sees them, so nothing is lost when they stay behind. What matters is the title, description and other details each live page sends to search engines.