Prompt Like a Pro
Chapter 8 of 10

Post-Launch Toolkit

Maintaining Your Site

Chapter 8: The Post-Launch Toolkit

What Nobody Tells You About “Done”

Your site is live. People can visit it. Congratulations!

Now here’s what nobody mentions: you’re not actually done. Not because you did something wrong, but because live sites need maintenance. Users find bugs you missed. Browsers update and break things. You think of improvements. Content needs updating.

The difference between a site that withers and one that thrives is having the right prompts ready for these inevitable post-launch moments.

I learned this when my cleaning business site went live. Everything worked perfectly until:

  • A user emailed that the contact form broke on iPad
  • Google updated and my search rankings tanked
  • I needed to update pricing but couldn’t remember where that lived in the code
  • The site looked dated after 6 months

This chapter is your post-launch survival kit - the specific prompts and workflows that keep your site running smoothly without becoming a full-time job.

The Three Maintenance Categories

Emergency Fixes: Something is actively broken and users are affected. Forms don’t work, site is down, critical features fail. These need immediate attention.

Planned Updates: Content changes, new features, design refreshes. You decide when to do these.

Preventive Maintenance: Regular health checks to catch problems before users do. Updates, backups, security patches.

Having the right prompt for each category means you’re never scrambling.

Emergency Response Prompts

”The Site Is Down” Panic Protocol

First time my site went down (a deployment error), I panicked and started changing random things, making it worse.

The Diagnostic Prompt:

My site [URL] is showing [error message/blank page/etc.] for all visitors.

Before making any changes, diagnose:
1. Is this a hosting issue, code issue, or DNS issue?
2. What immediate checks can I run to identify the cause?
3. What's the fastest safe fix?
4. How to prevent this specific issue in the future?

Start with the most likely causes for sudden downtime.

This gives you a methodical approach instead of random fixes. Usually it’s:

  • Hosting platform issues (check their status page)
  • Recent deployment that broke something (rollback)
  • Domain/DNS expired or misconfigured (check registrar)

“User Reports Feature Broken” Response

When someone emails that something doesn’t work, you need specific information before debugging.

The User Issue Prompt:

User reported: [their exact description of the problem]

They were using: [device/browser if known, or "unknown"]

Create a debugging checklist:
1. What information do I need from them to reproduce this?
2. How can I test this myself?
3. What are the most likely causes?
4. If I can't reproduce it, what should I check?

Draft a friendly response email asking for the right details.

The AI will give you the questions to ask (browser version, screenshot, exact steps) and how to test it yourself.

Real example from my directory site:

  • User: “Search doesn’t work”
  • I asked for browser/device
  • They were on Safari iOS
  • I tested on Safari iOS: search worked for me
  • Asked them to try private browsing mode
  • Turned out to be a cached old version

Without the systematic approach, I would’ve wasted hours debugging code that wasn’t actually broken.

”Something Changed and Now It’s Broken”

You didn’t touch the code, but suddenly something doesn’t work. This happened when a third-party API I used changed their authentication.

The Environmental Change Prompt:

[Feature] was working yesterday but is broken today.
I didn't change any code.

Investigate:
1. What external dependencies could have changed?
2. Browser update issues affecting my code?
3. Third-party service changes?
4. SSL certificate or security changes?

Identify the most likely external cause and how to fix.

Content Update Workflows

”I Need to Change Text/Images But Forgot Where”

Three months after launching my cleaning business site, I needed to update the service pricing. I had no idea where that content lived in the codebase.

The Content Location Prompt:

I need to update [specific content - pricing, team member bio, service description, etc.]

This content appears on [page/section name].

Help me:
1. Identify which file contains this content
2. Show me the exact location in that file
3. Explain what else might be affected by this change
4. Provide the safest way to make this update

Include line numbers or search terms to find it quickly.

This saves you from grep’ing through files or changing the wrong thing.

”Adding a Blog Post/Portfolio Item/New Page”

The Content Addition Prompt:

I want to add a new [blog post/portfolio item/team member/etc.].

The content I'm adding:
- [summary of what it includes]

Guide me through:
1. What file to create or modify
2. What structure/format to follow (match existing)
3. Where images should be stored
4. How to ensure it appears correctly on the site
5. What to update in navigation/listings

Provide a template matching the existing style.

For my directory site, I used this exact prompt when adding new designers. The AI showed me the JSON structure to match, where images went, and how the filtering would automatically include the new entry.

”Updating Design/Colors/Fonts Globally”

When you want to refresh your site’s look without rebuilding everything.

The Design Update Prompt:

I want to update [colors/fonts/spacing/button styles] across the entire site.

Current style: [describe or show screenshot]
Desired change: [describe what you want different]

Make this change:
1. Centrally (not file by file)
2. Consistently (all instances update)
3. Safely (easy to revert if I don't like it)

Show me what file(s) to modify and the exact changes to make.

This usually involves CSS variables or a theme config file. The AI will show you the one place to change that updates everything.

Analytics and Monitoring Setup

”How Many People Visit My Site?”

You need basic analytics, but Google Analytics is overwhelming for beginners.

The Simple Analytics Prompt:

I want to know:
- How many people visit my site
- What pages they view most
- Where they come from (search, direct, social)
- If they use mobile or desktop

Recommend and set up the simplest analytics solution that:
1. Respects user privacy
2. Shows me only essential metrics
3. Doesn't slow down my site
4. Has a free tier

Guide me through adding it to my site.

I use Plausible for my sites - it’s simple, privacy-focused, and takes 5 minutes to add. The AI can walk you through alternatives like Fathom or Simple Analytics.

”Is My Site Fast Enough?”

Performance monitoring before users complain.

The Performance Check Prompt:

Check my site's performance at [URL]

I want to know:
1. Current page load speed
2. What's slowing it down most
3. Simple fixes to improve speed
4. Which performance metrics actually matter

Focus on improvements that don't require major code changes.

The AI will run diagnostics and usually points to image optimization or lazy loading as easy wins.

Backup and Recovery Strategies

”How Do I Back This Up?”

I didn’t think about backups until I accidentally deleted a critical file.

The Backup Setup Prompt:

Create a backup strategy for my site deployed on [platform].

I need:
1. Automatic backups of my code
2. Backup of my database (if applicable)
3. Backup of uploaded images/files
4. Simple restore process if something breaks

Recommend solutions that:
- Run automatically (I'll forget manual backups)
- Are free or very cheap
- Are beginner-friendly to restore from

Set up each piece step by step.

For most static sites, Git/GitHub IS your backup. For dynamic sites, the AI will show you database backup services or platform features.

”Oh No, I Broke Something - Restore Previous Version”

The Rollback Prompt:

I just deployed changes and [describe what broke].

I need to rollback to the previous working version.

On [your hosting platform]:
1. How do I see my deployment history?
2. How do I rollback to the last working version?
3. Will I lose any data by rolling back?
4. How do I then fix the broken changes and redeploy?

Walk me through the rollback process immediately.

Most modern platforms make this a single button click. The AI shows you where.

SEO and Search Visibility

”Why Doesn’t My Site Show Up in Google?”

Three months after launching my cleaning business site, I googled the company name. My site wasn’t even on the first page.

The SEO Checkup Prompt:

My site [URL] doesn't appear in Google search for [terms you expect it to rank for].

Perform an SEO audit:
1. Is Google even indexing my site?
2. What's preventing it from ranking?
3. What basic SEO elements am I missing?
4. What's the fastest way to improve discoverability?

Prioritize fixes by impact for a beginner.

The AI will check for:

  • Missing title tags and meta descriptions
  • No sitemap.xml
  • Robots.txt blocking search engines
  • Slow page speed
  • Mobile responsiveness issues

All fixable with specific prompts.

”Adding Basic SEO to My Pages”

The SEO Implementation Prompt:

Add proper SEO to my [specific page or entire site].

For each page, ensure:
1. Unique, descriptive title tag
2. Compelling meta description
3. Proper heading hierarchy (H1, H2, etc.)
4. Image alt text
5. Sitemap inclusion

Show me:
- Where to add these elements in my code
- What content to write for each
- How to verify they're working

Provide templates for title/description formats.

From my directory site, here’s what this looked like in practice:

Before SEO prompt:

<title>Directory</title>

After:

<title>Design Directory - Discover Top UI/UX Designers | 500+ Portfolios</title>
<meta name="description" content="Browse curated portfolios from 500+ talented UI/UX designers. Filter by style, industry, and location. Find the perfect designer for your project.">

Same page, now actually discoverable.

Security and Updates

”Is My Site Secure?”

The Security Audit Prompt:

Run a security check on my site deployed at [URL].

Check:
1. Is HTTPS properly configured?
2. Are there any exposed API keys or secrets?
3. Are dependencies up to date?
4. Common security vulnerabilities?

For any issues found:
- Explain the risk level (critical, important, minor)
- Provide the fix
- Show me how to prevent this in the future

Start with the highest priority items.

“Updating Dependencies Without Breaking Everything”

Your site uses various libraries and frameworks. They release updates. Sometimes updates break things.

The Safe Update Prompt:

My site uses [list your main frameworks/libraries].

I want to update to latest versions safely.

Create an update plan:
1. Which updates are critical (security fixes)?
2. Which are safe to skip?
3. How to test updates before deploying?
4. What's most likely to break from updates?
5. How to rollback if updates cause issues?

Prioritize safety over having the absolute latest version.

User Feedback Integration

”User Suggested a Feature - Should I Build It?”

The Feature Evaluation Prompt:

User requested: [describe the feature request]

Evaluate:
1. How complex is this to implement?
2. Does it align with the site's purpose?
3. How many users would benefit?
4. Estimated time to build?
5. Are there simpler alternatives that accomplish the same goal?

Recommend: build it, consider it for later, or politely decline.

This prevents scope creep. I’ve gotten requests for my directory site that would’ve taken weeks to implement for one person’s preference.

”Collecting User Feedback Systematically”

The Feedback System Prompt:

I want to collect user feedback on my site.

Set up a simple system to:
1. Let users report bugs
2. Suggest improvements
3. Rate their experience
4. Optional: email for follow-up

Requirements:
- Free or very cheap
- Doesn't require a database
- Shows submission confirmation
- Sends me notifications

Recommend the simplest solution and show me how to add it.

For my sites, I use a simple form that emails me. Takes 10 minutes to set up with the AI’s help.

The Monthly Maintenance Routine

Instead of reactive panic, build a simple monthly check-in.

The Health Check Prompt:

Run a monthly health check on my site at [URL].

Verify:
1. All critical features working (forms, navigation, search)
2. No broken links
3. Images loading properly
4. Performance hasn't degraded
5. Security updates needed
6. Backup is current

Provide a checklist I can run through in 15 minutes.

I do this the first Monday of each month for all my sites. Catches issues before users report them.

Real World Example: Six Months Post-Launch

Here’s what maintaining my cleaning business site actually looked like:

Month 1-2 Post-Launch:

  • Emergency: Contact form broke on Safari (used emergency diagnostic prompt)
  • Update: Changed service pricing (content location prompt)
  • Analytics: Set up Plausible (simple analytics prompt)

Month 3-4:

  • SEO: Site not ranking for company name (SEO checkup prompt)
  • Performance: Slow on mobile (performance check prompt)
  • Feature request: User wanted quote calculator (evaluated, declined as too complex for benefit)

Month 5-6:

  • Routine: Monthly health checks (found/fixed broken Instagram link)
  • Update: Refreshed team photos (content update workflow)
  • Security: Updated contact form library (safe update prompt)

Total maintenance time: Maybe 2-3 hours per month, mostly responding to specific needs rather than constant monitoring.

The Emergency Contact Sheet

Keep these prompts saved for when things break:

Site Down:

Site showing [error] at [URL]. Diagnose most likely cause and fastest fix.

User Reports Bug:

User says [exact description]. What info do I need to debug this?

Need to Rollback:

Recent deploy broke [feature]. How do I rollback on [platform]?

Security Alert:

Got security warning about [dependency/vulnerability]. Assess severity and provide fix.

What This Chapter Gives You

You now have:

  • Emergency response prompts for critical issues
  • Content update workflows
  • Analytics and monitoring setups
  • Backup and recovery strategies
  • SEO and security checklists
  • User feedback systems
  • A monthly maintenance routine
  • Real examples from actual post-launch scenarios

Post-launch isn’t about constant vigilance. It’s about having the right prompts ready for the inevitable moments when you need them.

Next up: Chapter 9 explores what happens when your simple site needs to grow - adding features, handling more traffic, and evolving your project without starting over.