The first 90 days after a site launches

The first 90 days after launch are for watching, repairing the lines people misunderstand, and publishing into the gaps. They are a poor time to redesign the site because the quiet feels uncomfortable.

What to do after website launch is a sequence. Confirm the basics still work. Read the words strangers stumble on. Add the page or the paragraph that the questions reveal. Leave the structure alone until the evidence says the structure is the problem.

The first week: confirm, then watch

Launch day proves the site can be reached. The days after prove the details. Check the form or the scheduler, the inbox that receives replies, the links in the navigation, and the pages on a phone. Read the titles and the opening lines as if you have never seen them. Fix what is broken before you interpret what is quiet.

Then watch, with a light touch. Which queries brought people. Which pages they entered on. Whether anyone took the action you named, a call, a purchase, a signup. A launch can be live and still be unclear in the first screen. The fix is usually a sentence, not a new visual system.

Write down what you will not do in week one. You will not commission a new homepage because an aunt said the color felt cold. You will not add three pop-ups because a thread said pop-ups convert. You will not change the title every morning to see what "sticks." Google's title-link documentation says the title element should describe the page, and that inaccurate or restless titles are the kind of thing their systems may replace with other text from the page. Stability is part of being understood.

Agree who watches. One person owns the inbox and the list of fixes. A channel where everyone drops reactions is how a calm launch becomes a second project.

Fix the lines people misunderstand

Collect the actual confusions. A caller who asks "so do you build, or only design?" has told you the homepage failed a basic test. A shopper who asks whether shipping is included has told you the product page hid the cost. A reader who bounces between two articles has told you the titles are too alike.

Change the line that caused the question. Put the answer in the first screen if the question is common. Put it in the FAQ if it is real but secondary. Keep a short log: the question, the page, the sentence you changed, the date. That log is more useful than a mood board.

Google's helpful-content guidance asks whether a reader leaves able to reach their goal, and it warns against changing dates or churning pages just to seem fresh. Editing a confusing sentence is the opposite of that churn. You are making the page more true. Rewriting the whole site so it feels new is the churn. Know which one you are doing.

Read the title and the H1 together after each edit. They should still agree. A cleverer H1 that abandons the promise in the title will confuse the person who clicked, and it may confuse the systems that have to name the page.

Do the same for the action. If people reach the page and cannot see how to talk to you, move the path. If they talk to you and expected a different service, fix the promise. Those are launch fixes. They are in scope for the first month.

Publish into the gaps

Questions that need more than a sentence become the next piece of writing, or the next section on an existing page. Prefer extending a page that already has a job. A new URL is justified when the question has its own buyer and its own search.

Keep the cluster in mind. If the homepage is about a specific offer, the new writing should help that offer. A gap around pricing shape, around what the client owns, or around how a redesign handles old URLs is a fair post. A gap around a trend you do not practice is a distraction.

Two or three additions across the quarter is plenty for a small team. Each one should link from a real sentence on an existing page, and each one should point back to the offer. Orphan posts published "for SEO" in week six are how the site loses the focus the launch just earned.

Update proof when you have something new to show. A project that shipped after launch can join the work section when you can say what was decided. A logo in a row, with no sentence, does not fill a gap. It fills space.

The operational list

Run this once in the first month, and again at the end of the quarter:

• Forms, scheduler, and the inbox, tested by a person who did not build them.
• Titles, descriptions, and H1s still true after the edits.
• Mobile pass on the homepage, the primary action, and one deep page.
• Redirects from any old URLs still landing on the right new page.
• Analytics still recording the action you care about, under the same definition as launch week.
• A note of which queries you showed up for, and which of them you deserve.

Speed belongs on the list as a health check. A page that became heavy because someone added a full-screen animation after launch will show up as a worse experience, and it will be blamed on "conversion" if you do not look. You do not need a new design to remove the weight.

Ownership belongs on the list too. You should still control the repository, the domain, the analytics, and the content logins. A launch that left those in a vendor's account is a risk to fix in the first month, while the details are fresh.

When a redesign is actually due

A redesign is due when the offer has changed, when people cannot complete the one action, or when the site cannot be edited safely. It is not due because the team has stared at the homepage for a month and grown bored. Boredom is a poor brief.

Give the current site the quarter. Use the log. If the same structural failure shows up after the sentences are clear, then scope a change: a revamp of the weak template, or a rebuild if the stack cannot be touched. Bring the log to that conversation so the new work starts from evidence.

If you want a partner for that judgment, book an intro call with the questions you heard and the lines you already fixed. The useful conversation is about the remaining gap, not about starting over for the feeling of motion.

Before you pick a number to panic about, read how to measure calls booked, not vanity traffic. The 90 days are easier to spend well when the metric is a conversation with the right person, and the edits are in service of that conversation.