how do i change text on my website without breaking it

web · 2026-09-25 · 3 min

log in, open the page, click the text, change it, save, publish. the difficult part is not the editing — it is finding where the text actually lives, and remembering that saving and publishing are two different buttons.

find where it lives

most text is in the page itself. some is not: the header, the footer, the cookie banner, the button labels, the "read more" strings. in wordpress those live in the site editor templates or in the theme, and a page edit will never touch them. in wix, header and footer are edited from the design panel, separately from the page.

search the exact sentence before you edit. if it appears in the header of every page, you are changing a template, not a page — fine, if you know.

the mechanics, briefly

wordpress: pages, all pages, edit. in the block editor, click the block and type. then update. the page editor has update, the site editor has save, and both have a preview you should check at phone width.

wix: click the text, edit it, then publish — the change is a draft until you press publish, and that is the most common reason people think the editor is broken.

a static site: edit the file, commit, wait for the deploy. no publish button, and no undo without repository history.

the traps

editing the wrong copy. duplications, drafts and translated versions look identical. check the url of the page you are editing.

changing a heading into a paragraph, or the reverse, because the text looked different. the visual size is a style; the tag is structure. keep the tag and change the words.

rewriting the title tag by accident. in most cms the title field feeds the page heading, the browser tab and sometimes the search result. if you meant to change one sentence in the body, do not touch it.

forgetting the cache. if the site has a caching plugin or a cdn, the old text can survive a publish. clear it once and look again before concluding anything.

read the page on a phone: a longer headline can push a button below the fold. if the change was substantial, request indexing in search console.

who can edit what

a website is not one permission, it is a set. on wordpress: administrator sees plugins, users and theme; editor changes all content; author only writes their own posts; contributor writes drafts and cannot publish. ask for editor, not administrator: whoever writes copy does not need to install a plugin.

on wix the roles are coarser, and access to single pages is handled separately. on shopify staff accounts have permissions per area. on a static site the access is to the repository, and that is closer to administrator than to editor: a bad commit can take the whole site down.

one person, one account, real name, two-factor on. no shared password in a chat: if two people use the same login, the log cannot tell you who did what, and when one leaves you have to change the password for everyone.

staging. any change longer than a sentence should be tried on a copy of the site first. if there is no copy, you need at least a backup and a known way back: wordpress revisions, the wix version history, the previous commit.

handover. one page with who owns the domain and the hosting, who has access, what to do if the site is down, how to undo the last change. it gets updated when someone leaves, and removing access is part of the job as much as giving it.

faq

why did my change not appear?

three usual suspects: you saved a draft instead of publishing, the cache is serving the old version, or you edited a different copy. check the url first.

can i change text without breaking the design?

almost always yes, if you keep the same block and the same tag. problems start when a longer text meets a fixed-height box, or when a heading becomes a paragraph to look smaller.

who should have the login?

whoever updates the site regularly, and as few others as possible. one editor account per person, no shared password, two-factor authentication on the admin account.

how do i make changes to my website myself?

ask for an editor role on a named account of your own, not the administrator login, and ask for a short handover: where header and footer text lives, how to publish, how to undo. try one small change on a staging copy or right after a backup before touching the live page. keep a list of who has access, and remove it when someone leaves.