Checklist · 22 November 2026 · 6 min read
Just Launched Your WordPress Site? Everything to Set Up in Week One
Your WordPress site is live. Now make sure Google finds it, emails arrive and backups leave the server: a free day-by-day checklist for the first week.
By Nagz Studio
The site is live, the client is happy, and everyone wants to move on. This is exactly the week when the problems that show up a month later get set in place: a staging setting that tells Google to stay away, contact form emails going to spam, backups that only exist on the same server as the site.
None of these take long to fix. They just don't fix themselves. So here's what to do after launching a WordPress site, day by day: the free checklist we work through in the first week, roughly in the order we do it.
Day 1: Make sure search engines are allowed in
Check "Search engine visibility." In WordPress, go to Settings → Reading. If "Discourage search engines from indexing this site" is ticked, untick it. Staging sites have it on for good reason, and it often comes along when a site is moved to production. It's the single most expensive checkbox in WordPress.
Look at robots.txt. Open yourdomain.com/robots.txt. A line that says Disallow: / under User-agent: * blocks the whole site. WordPress's own default only blocks the admin area.
Check the permalinks. Settings → Permalinks. "Post name" gives clean addresses like /about/ instead of /?p=12. Change this now, not after Google has indexed the old addresses.
Set up redirects if this replaced an old site. Every old page address that people or Google know about should redirect (301) to its new home. List the old site's main pages and test each one. A rebuild that drops its old links loses the search traffic those links earned.
Day 2: Tell Google and Bing the site exists
Google Search Console. Add the site as a Domain property (it covers http, https, www and non-www together), verify it with the DNS record it gives you, and submit your sitemap. WordPress makes one at /wp-sitemap.xml; if you use Yoast SEO, it's at /sitemap_index.xml. Then use URL Inspection on the homepage and click "Request indexing".
Bing Webmaster Tools. It can import your sites straight from Search Console, which takes about a minute. Bing's index also feeds other search tools, so it's worth having.
Don't expect results the same day. Search Console fills in over days and weeks. The point of doing it now is that the data starts collecting from launch.
Day 2: Set up analytics, with consent in mind
Pick one analytics tool and install it once. Google Analytics 4 is free and detailed. Privacy-focused tools such as Plausible or Umami are simpler and, depending on where your visitors are, may not need a cookie banner. Whichever you choose, check it's recording by visiting the site from your phone and watching for the visit.
If you're using a tool that sets cookies and you have visitors in the EU or UK, you'll need a consent banner. That's a legal question for the site owner, not a technical one, so raise it with them.
Day 3: Test every email the site sends
Send each form yourself. Contact, quote, newsletter signup, anything with a submit button. Then check the email arrived, in the inbox, not spam, at the address the client actually reads.
Fix delivery with SMTP. If messages land in spam or don't arrive, WordPress is probably sending through the server's own mail function, which many inboxes distrust. A plugin such as WP Mail SMTP sends through a real mail service instead. Your domain's SPF and DKIM records then need to include that service.
Check WordPress's own emails too. Password resets and new user notifications go through the same path. Request a password reset for a test user and see if it arrives.
Day 3: Backups that leave the server
Ask two questions about the backups, and get real answers:
- Where are they stored? A backup on the same server as the site disappears with the server. You want copies somewhere else: cloud storage, or at least the host's separate backup system.
- Has anyone restored one? A backup you haven't tested is a hope, not a backup. Restore one to a staging site once, now, while it's calm.
If the host's backups don't meet both, add a backup plugin that sends copies off the server. BackupScope is free and verifies each archive before it counts the backup as done; any well-maintained backup plugin is better than none.
Day 4: Lock down the obvious
Most WordPress attacks are automated and go after the easy targets. Make sure the site isn't one:
- Update everything: WordPress, the theme and every plugin.
- Delete what isn't used: inactive plugins, old themes (keep one default theme as a fallback), the "Hello world!" post and "Sample Page".
- Check the user list. Remove test accounts, make sure nobody is called "admin", and give the client the lowest role that lets them do their job.
- Turn on two-factor authentication for every administrator.
- Turn off debug mode. In
wp-config.php,WP_DEBUGshould befalseon the live site, so errors don't print file paths to visitors.
Not sure which plugins should stay? Here are the 12 free plugins we'd keep on a new WordPress site, one per job.
Day 4: Something to tell you when it's down
Set up uptime monitoring so you find out the site is down before the client does. Free plans from services such as UptimeRobot check every few minutes and email you when the site stops responding. Point it at the homepage and, for a shop, the checkout page too.
Also check the SSL certificate renews automatically. Most hosts handle it now, but an expired certificate puts a full-page warning in front of every visitor.
Day 5: The details people notice
- Site icon (favicon). Appearance → Customize → Site Identity, or the Site Editor in a block theme. Without it, the browser tab shows a blank page icon.
- Social sharing preview. Paste the homepage into a LinkedIn or WhatsApp message and see what appears. If it shows no image or the wrong title, set the Open Graph image and title in your SEO plugin.
- The 404 page. Visit a page that doesn't exist. It should look like the rest of the site and point people somewhere useful.
- Page speed on a phone. Run the homepage and one inner page through PageSpeed Insights, using the mobile result. Big images are the usual cause of a slow score.
- Privacy policy and contact details. Make sure the privacy page describes the forms and analytics the site really uses.
- Google Business Profile, if it's a local business. Add the new website address, so the map listing and the site point at each other.
Day 6–7: Start telling people
A new site with no visitors gets no data, and Search Console takes time. Social media is the fastest way to get the first visitors while search catches up:
- Post the launch, with what's new for the visitor rather than "we have a new website".
- Share the pages that answer questions customers already ask: pricing, a service, a recent project.
- Plan a month of posts so the first one isn't also the last.
That last point is where most launches stall. If you'd rather not write 30 days of posts yourself, Nagz LaunchKit makes a month of Instagram posts and reels, YouTube Shorts and LinkedIn posts from the site, delivered within 24 hours of payment.
The whole list in one place
| When | Task |
|---|---|
| Day 1 | Search engine visibility, robots.txt, permalinks, redirects from the old site |
| Day 2 | Search Console and sitemap, Bing Webmaster Tools, analytics |
| Day 3 | Test every form and email, SMTP, off-site backups and a test restore |
| Day 4 | Updates, remove unused plugins and users, two-factor, debug off, uptime monitoring, SSL renewal |
| Day 5 | Site icon, social preview, 404 page, mobile speed, privacy page, Google Business Profile |
| Day 6–7 | Launch posts and a month of social content |
Haven't launched yet? Start one step earlier with our WordPress website testing checklist: 62 checks to run before a client sees the site.
Check it from the outside
A lot of this list can be tested from outside the site, without logging in. Our free WordPress launch check tests search engine access, the sitemap and robots.txt, HTTPS and the certificate, security headers, the 404 page, the site icon, the social preview and speed, and shows the evidence for each result. It takes about a minute, and it's a good way to end week one.
What's the one thing you've forgotten after a launch that you now never skip?
More from the blog
- Tutorial · 6 minHow to Build a WordPress Website With Claude Code, Step by StepWPShipReady
- Opinion · 6 minFree Tools as Marketing: What We Learned Building Them for ShareMyInvite and DocxToWPShareMyInvite
- Build story · 6 minHow We Built ShareMyInvite: A Wedding Invitation SaaS With Next.js, Supabase and Dodo PaymentsShareMyInvite