Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared hosting Managed WordPress Cloud hosting VPS hosting By reader location Hosting finder
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Blog Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

Hosting · Guide

How to Edit Website on WP Engine (Step by Step)

How to Edit Website on WP Engine (Step by Step)

Short answer

Log in to the WP Engine User Portal, choose your site and environment, and open the WordPress admin link. Edit pages, posts, menus and design in the normal WordPress dashboard. Use staging for bigger changes, SFTP for files, and clear WP Engine's cache so visitors see your edits.

Key takeaways

  • Everyday edits happen in WordPress admin, not the WP Engine portal.
  • Portal logins and WordPress logins are separate accounts.
  • Make bigger changes on staging, then copy to production.
  • Use SFTP users from the portal for theme or config files.
  • Local can pull a site to your computer and push it back.
  • Purge WP Engine's cache when edits do not appear.

How do you edit a website on WP Engine?

Log in to the WP Engine User Portal, open your site's environment, and click the link to WordPress admin; then edit pages, posts, menus and themes in the normal WordPress dashboard.

WP Engine hosts the site, but the content lives in WordPress. Almost every everyday edit, such as changing text, adding images, updating menus or installing plugins, happens inside the WordPress dashboard rather than in WP Engine's own portal.

The WP Engine portal is where you manage hosting tasks. That includes environments, backups, domains, SFTP users and caching.

This guide covers both: how to reach the editor, how to edit content safely, and when to use staging, SFTP or local development instead.

How do you log in to the WP Engine User Portal?

Go to WP Engine's portal login page, sign in with your account email and password, and choose your site from the Sites list.

The WP Engine User Portal overview explains each section. If someone else owns the account, ask them to invite you as a user with the right role.

Each site can have up to three environments: production, staging and development. Production is the live site that visitors see.

Pick the environment you want to edit. For anything beyond small text changes, staging is the safer place to start.

How do you open the WordPress dashboard from WP Engine?

In the environment's overview, click the WordPress admin link, or visit your domain followed by /wp-admin and log in with your WordPress username and password.

WP Engine portal accounts and WordPress accounts are separate. Your portal login does not automatically log you in to WordPress, so you need a WordPress user on the site too.

If you have not set up a custom domain yet, use the temporary WP Engine domain shown in the portal, followed by /wp-admin.

Not sure of the login address? Our guide on the WordPress admin URL explains the common variations.

How do you edit pages and posts?

Go to Pages or Posts, click the item you want to change, edit it in the block editor or your page builder, then click Update.

Most WordPress sites use the block editor. The block editor documentation shows how to add, move and style blocks.

If the site uses a page builder such as Elementor or Beaver Builder, you will see an extra button to edit with that builder. Use it for pages that were built with it.

For a broader walkthrough of editing an existing WordPress site, see how to use WordPress to edit an existing website.

How do you edit menus, headers and the theme design?

Use Appearance > Editor for block themes or Appearance > Customize and Appearance > Menus for classic themes, depending on which theme the site runs.

Block themes edit headers, footers and templates in the Site Editor. Classic themes split design options between the Customizer, the Menus screen and theme settings pages.

If you plan to change theme code, use a child theme so updates do not overwrite your work. The WordPress child theme guide explains how.

WP Engine does not change how these WordPress screens work. They behave the same as on any other host.

How do you give someone else access to edit the site?

Invite them as a WordPress user for content edits, and add them in the User Portal only if they also need hosting tools such as backups, staging or SFTP.

Most writers and editors never need portal access. Create a WordPress user under Users > Add New and choose a role such as Editor or Author.

Developers and agencies often need both. In the portal, give them a role that covers the environments they work on, and create a separate SFTP user for each person so access can be removed cleanly later.

Avoid sharing one admin login between several people. Separate accounts make it clear who changed what, and you can remove one person without resetting everyone's password.

When a project ends, remove the extra WordPress users, portal users and SFTP users. Old accounts are a common way into sites.

Why should you edit on staging first?

Staging lets you make and test changes on a private copy of the site, then copy them to production only when everything works.

In the User Portal, you can copy production to staging, make your edits on staging, then copy staging back to production. WP Engine calls this copying an environment.

Be careful with dynamic content. Copying staging over production can overwrite new orders, form entries or comments made on the live site since you created the copy.

For content-heavy shops, make design changes on staging but publish everyday content directly on production. Our guide on setting up a staging site covers this trade-off.

How do you edit files with SFTP on WP Engine?

Create an SFTP user for the environment in the User Portal, then connect with an SFTP client such as FileZilla using the host, port and login shown there.

SFTP is for editing theme files, custom plugin code or configuration that you cannot change in the dashboard. WP Engine's SFTP usage guide lists the connection details and limits.

Each environment has its own SFTP users. Make sure you connect to the right one, especially when production and staging look identical in your client.

Download a copy of any file before editing it, so you can put the original back if something breaks. WP Engine protects some core files and settings, so certain changes may be blocked or reset by the platform.

Can you edit a WP Engine site locally?

Yes; Local, WP Engine's free local development app, can pull a site to your computer, let you edit it offline, and push it back to WP Engine.

Local runs WordPress on your own machine. Its connect feature links to your WP Engine account so you can move sites between Local and your environments.

Local is useful for larger changes, theme development and testing plugin updates without touching the live server.

Local also keeps a copy of your work on your own computer. If a change goes wrong, you can throw away the local copy and pull a fresh one from WP Engine without the live site ever being affected.

Push to staging first, check it there, then copy to production. That gives you two chances to spot problems.

Why don't your edits show on the live WP Engine site?

WP Engine caches pages heavily, so purge the cache from the WP Engine menu in WordPress or the User Portal after you edit.

Logged-in users usually see fresh pages, while visitors may still get the cached version. Check in a private window to see what visitors see.

In WordPress, look for the WP Engine menu, which includes caching tools. The User Portal also has cache controls for each environment.

If you use a page builder, also regenerate its CSS files after big design changes. Builders store generated styles that can lag behind your edits.

Which editing method should you use?

Pick the method based on the kind of change; most content edits only need the WordPress dashboard.

ChangeBest methodWhere
Text, images, postsWordPress dashboardProduction or staging
Menus and layoutSite Editor, Customizer or page builderStaging for big changes
Plugin or theme updatesWordPress dashboardStaging first
Theme code or config filesSFTP or GitStaging, then copy
Large redesignLocal or stagingPush or copy when tested
Domains, backups, cachingUser PortalEnvironment settings

How do you protect the site before editing?

Create a backup checkpoint in the User Portal before big changes, so you can restore quickly if an edit breaks the site.

WP Engine takes automatic backups, and you can also create one on demand. Our guide on whether WP Engine includes backups explains how they work.

Give other editors only the WordPress role they need. Authors and editors can change content without touching plugins, themes or settings.

If you are moving an existing site onto WP Engine before editing it, start with how to migrate a WordPress site to WP Engine.

Frequently asked questions

Can I edit my WP Engine site without the User Portal?

Yes. If you have a WordPress user account, go to your domain followed by the wp-admin path and log in directly. The portal is only needed for hosting tasks such as backups, environments, SFTP users and caching controls.

Why can't I log in to WordPress with my WP Engine password?

WP Engine portal accounts and WordPress user accounts are separate. Use your WordPress username and password, or ask an administrator to create a WordPress user for you. You can also reset the password from the WordPress login screen.

Will copying staging to production delete live orders?

It can. Copying an environment replaces the destination's data with the source, so orders, entries or comments made on production since the copy may be lost. For shops, consider copying only files or making content changes directly on production.

Can I use the WordPress theme file editor on WP Engine?

Editing code through the dashboard file editor is risky on any host, and it may be disabled on some sites. Use SFTP, Git or Local on a staging environment instead, so a mistake does not take the live site down.

How do I clear the cache on WP Engine after editing?

Use the WP Engine menu inside WordPress, which includes caching tools, or the cache controls in the User Portal for that environment. Then check the page in a private window to confirm visitors see the new version.

Sources

  1. User Portal Overview WP Engine
  2. SFTP Usage and Access WP Engine
  3. Local WP Engine
  4. WordPress Block Editor WordPress.org Documentation
  5. Child Themes WordPress Developer Resources

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

Written and checked byWPLegible Editorial Team Independent WordPress reviews and guides

Researched from the primary sources listed above and checked against our editorial rules before publishing.