The launch email goes out at nine tomorrow, and the homepage headline still promises last quarter's offer. You need to change one sentence. How you do that depends on how the site was built, and plenty of people asking this question have never been told which kind they have.
There's a quick way to find out. If someone once gave you a login to an editor, a WordPress dashboard or a Webflow or Framer project, the words live there and you can change them yourself. If every change so far has gone through a developer who "deploys" it, the words live in code, usually in a GitHub repository. Both can be sorted out today. For the code case there's also a route that skips the file editing altogether, since Refinar can make the change from a plain description and show you the real page first.
Why inspect element doesn't stick
Right-click a heading in Chrome, choose Inspect, double-click the text and type. The page changes in front of you, which is why this trick gets passed around. All you've edited is the copy of the page sitting in your own browser. Chrome's DevTools documentation says those changes disappear when you reload, and nobody else ever sees them.
It's still handy for one thing. Type the new headline in place and you'll see whether it fits on one line before you ask anyone to change it for real. Take a screenshot and attach it to the request.
If it's WordPress
Go to Pages in the dashboard, click the page's title, click into the heading or paragraph and type. On a page that already exists, the save button is labelled Update, according to WordPress's own Pages screen guide.
Header and footer text is different, because it doesn't belong to any one page. With a block theme it's in the Site Editor, under Appearance and then Editor, and WordPress warns that a change to the header or footer template applies to every page using it. That's what you want for a new phone number, less so for a campaign line. If your theme isn't a block theme, the Site Editor won't be there at all, which is usually the moment to ask whoever set the site up.
If it's Webflow or Framer
Webflow has a Content Editor role for exactly this. In edit mode you can rewrite text and links on the canvas, and publish if the site owner has switched that permission on (Webflow University). Without it, your edit waits for someone who has it.
Framer goes a step further and lets you edit on the published site itself. Owners and collaborators with Content permission see an Edit button on the right of the published site; you click the words and type. Pressing Finish Editing emails the collaborators who can publish, and the change goes live once one of them does (Framer's on-page editing guide).
If the text lives in code
A lot of sites, and nearly every web app, have no editor. The words are typed into the code itself, in a component file for the homepage or a translation file such as en.json if the site speaks more than one language. Changing them means changing a file, which is less alarming than it sounds when all you're touching is text.
On GitHub you can do it in the browser. Search the repository for a distinctive phrase from the sentence (a phrase, not one word, or you'll get forty results). Open the file and click the pencil icon. Change the words inside the quotes or tags without disturbing anything around them. When you commit, GitHub asks whether to add it to the current branch or to a new branch with a pull request (editing files on GitHub). Choose the new branch, so someone can glance at it before it goes out.
Two things catch people out. The same wording often appears twice, once on the page and once in the meta description Google shows under your link, and you'll want to decide whether both should change. And if the search finds nothing, the text may not be in the code at all. It could come from a database, or it's part of an image (if you can't select it with your cursor, it's a picture).
Changing coded text without the wait
The pencil works for a sentence you can find. It gets awkward when the request is "lead the pricing section with the annual plan" and you've no idea which of six files that means, or when you'd like to see the page with the new words before anyone approves it.
That's the gap Refinar fills. You connect the repository, then describe the change in plain words or click the headline in the live preview. Refinar starts the whole site up in a cloud sandbox, so you read the new wording on the real page before anything ships, and if it reads worse than the old one, you can undo it. The finished change goes out as a draft pull request for review, or you publish it yourself (how sharing a change works). Text is the easy case. A request that wanders into logins, payments or customer records is never published automatically and goes to a developer instead, which is a sensible line for a marketing team to have anyway. Plans begin at $50 a month (pricing), and Refinar for marketers walks through a typical page change. If you'd rather drive a coding agent yourself, Claude Code for marketers covers what that takes.
Before it goes live
- Read it on a phone. A headline that sits on one line on a laptop can wrap to three on a narrow screen.
- Check the other languages. If the site is translated, the old wording is still in the other language files.
- If the page ranks in search, make sure its title and meta description still match what it now says.
- Click the buttons near your edit. It's easy to break a link while changing the words inside it.
For a wider check, the free landing page analyzer loads a live page on a phone and a desktop and scores what visitors see first. If a bigger change is on the way, how to change a live app without breaking it covers staging and rollback.
If your site's words sit in a GitHub repository and every typo still means a ticket, try changing one sentence with Refinar before the next launch email goes out.