Your post-launch owner's guide.

1. What's live on your domain.

Your site serves from your custom domain on Cloudflare Pages with HTTPS, HTTP/3, and a Brotli-compressed payload underneath. Google was told about your sitemap on launch day, and Bing usually picks it up from Google within roughly two weeks. The standard inventory of what is live includes the following:

• Pages. Home, About, Services (with anchor sections per offering), Pricing or Quote, Service Area pages (one per region you cover), Contact, Booking (if applicable), and your blog.
• Operational pages. Privacy Policy, Terms of Use, Accessibility Statement, Sitemap (HTML for humans and XML for crawlers), and Style Guide. These are not optional even when nobody ever clicks them.
• SEO assets. robots.txt, sitemap.xml, RSS feed (feed.xml), JSON-LD structured data on every page, Open Graph and Twitter Card tags for link previews, and canonical URLs.
• Search. A working full-text search box (Pagefind) that runs entirely in the visitor's browser, with no server, no cookies, and no API call attached to it.
• Forms. One or more contact and quote forms wired to Web3Forms. Submissions email you directly, and no copy is kept on my side.
• Favicons. A full favicon set (every device, every browser, every dark/light variant) generated automatically.

2. Who handles what.

Most disputes between agencies and clients come from fuzzy boundaries. Here are mine, in writing.

3. How to ask for changes.

The shortest path is a plain-language email or text. You do not need to write it like a ticket. The four examples below all get the same response time.

• "Our new hours are 7am to 6pm Monday through Saturday."
• "Add a new service page for gutter cleaning. Same layout as drain cleaning."
• "Please swap out the team photo on the About page. New one attached."
• "Grand Opening special. Can we put a banner at the top for two weeks?"

How to send it: email hello@pikespeakwebdesigns.com, text or call (928) 315-9094, or use the content update form. All three reach the same inbox, which is mine, and I tend to reply quickly on most business days.

Turnaround. Routine edits like a typo, a phone number, a price change, or a new staff bio are included on the standard plan and tend to land quickly on most business days. Anything genuinely outside the standard scope, like a custom calculator, a third-party booking integration, or a brand-new behavior on the site, is billed at a flat one hundred dollars an hour with a written estimate before I start.

4. What counts as an emergency.

An emergency is anything visitors will see that's wrong, dangerous, or broken. Three examples I will drop everything for:

• The site is down. Returning a 5xx error, blank page, or DNS failure to visitors.
• Wrong information is live. Wrong phone number, wrong address, wrong price on an active promo, an out-of-date hours block during a holiday weekend.
• A security or privacy concern. Defaced page, suspicious form submissions, anything that looks like an attack, or a customer reporting a data leak.

What to do. Do not wait for a form. Call or text (928) 315-9094 directly, and I will answer or call you back fast on most business days. The emergency form is also fine, since it pages me the same way.

What is not an emergency. A new service page, a copy tweak, a photo swap, or a missing comma all belong in the regular content-update channel rather than the emergency one, and they tend to land quickly on most business days.

5. Form submissions.

Every contact, quote, or booking form on your site posts directly to Web3Forms, which then emails the submission to the address I set on launch (usually a single inbox you already monitor). There is no dashboard to log into and no copy stored on my side or yours.

• Where they go. The address(es) on file. Usually owner@yourdomain or office@yourdomain.
• Spam protection. Honeypot field plus a per-form rate limit. No CAPTCHA. False-positive rate measured weekly; across all client sites the false-block count has been zero.
• Adding or changing recipients. Send one email to me, and the change tends to land quickly on most business days.
• Auto-reply. Visitors get an instant "I got it" email with your phone number. Edit the wording any time.
• Reading the data. Submissions arrive as plain-text email with every field labeled. No login required.

6. Your domain belongs to you.

You bought it; you own it. I do not register domains on behalf of clients (it creates control problems on your worst day). What I do:

• Configure DNS. I point the records at the hosting. The records sit at your registrar. You can see them any time.
• Remind you to renew. 60, 30, and 7 days before expiration. I do not pay the renewal; you do. I monitor the WHOIS expiration date directly so the reminder does not depend on the registrar's email.
• Help you find it. If you have lost track of where the domain was registered, search your inbox for "domain renewal" or "ICANN whois". The registrar will be in the headers.

If your domain ever lapses, the site goes dark within 24 to 48 hours. Recovering a lapsed domain is possible inside a 30-day grace window for most TLDs, but the registrar may charge a redemption fee. The 60-day reminder exists so this never happens.

7. Email on your domain.

Email is separate from your website even though they share a domain. I do not host email; I set the DNS records that tell the world where your email lives. Most clients use one of:

• Google Workspace. $7.20 per user per month. Best inbox, calendar, drive. I set the MX, SPF, DKIM, and DMARC records at no charge.
• Microsoft 365. $7.20 per user per month. Same deal.
• Forwarding. Free. you@yourdomain.com forwards to your existing Gmail or whatever. Good if you only need to look professional and already have a working inbox.

What I never do: lock email behind me, charge to "configure" DNS, or move your email when you switch hosts. The records are at your registrar. They are yours.

8. Hosting and uptime.

Your site runs on Cloudflare Pages: static files served from 300+ edge locations worldwide. The closest one to most US visitors is within 50ms. Uptime target is 99.99%, and the architecture is designed to make sustained outages vanishingly rare.

• Monitoring. 1-minute uptime checks from three geographic regions plus Cloudflare's own status feed. I get paged before you notice.
• What "down" looks like. Most outages affect a region, not the whole network. Even during an incident your site is usually up for most visitors.
• Bandwidth. Unlimited on the Cloudflare Free plan. No overage charges have ever been triggered, including during a client's TV ad spike.

9. Security and backups.

There is no admin panel, no database, no plugins, no PHP. The "attack surface" is essentially the static files on a CDN. Specifically:

• No login form anywhere on your site. Nothing to brute-force.
• No database to inject. Forms post to a third-party endpoint, not to a server I maintain.
• HTTPS-only. HSTS preload-eligible, with a 12-month max-age and includeSubDomains.
• Security headers. Content-Security-Policy, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, and Permissions-Policy on every response.

Backups. Every commit is its own backup. Source lives in a private GitHub repository. I can restore any prior version in under five minutes by reverting a commit and redeploying. If your home computer fails on the day you ask for a rollback, it does not matter. The history is in git.

10. SEO foundation.

SEO is two things stacked: technical foundation (which is binary; you have it or you do not) and ongoing content (which is gradual). I deliver the foundation; you control the content.

What I built in:

• Clean semantic HTML, one H1 per page, descending heading hierarchy.
• Per-page title and description (50-160 characters, with your service + city).
• JSON-LD structured data: LocalBusiness schema on the site, Service schema on each service page, Article schema on each blog post, FAQPage schema on the FAQ.
• Open Graph and Twitter Card tags so links shared on social show a real preview.
• XML sitemap submitted to Google Search Console at launch.
• Core Web Vitals well inside the green: LCP under 1.5s, CLS under 0.05, INP under 100ms on real-world data.
• Mobile-first responsive design (Google indexes mobile first).

What I do not promise: a specific ranking position. Anyone who promises that is lying or about to. What I do promise: your technical foundation will not be the reason you do not rank.

11. Analytics and tracking.

Two analytics systems run on your site by default. Both are cookie-free and GDPR-compliant by design. Neither requires a cookie banner.

• Cloudflare Web Analytics. Server-side Real User Monitoring. Sees every request, no client-side script needed. Tells me your real-world Core Web Vitals across actual visitors.
• Umami. Included with every monthly plan. I provision a private dashboard for your site and send you the live link on launch day. Shows page views, referrers, devices, top pages, and bounce. No personal data, no cookies, no GDPR banner. Your dashboard, your numbers; check it any time.

What I do not add unless you specifically ask: Google Analytics, Facebook Pixel, LinkedIn Insight Tag, TikTok Pixel, or any third-party advertising script. They slow the site, require a cookie banner, and most of them get blocked anyway.

12. Google Business Profile.

Your GBP is separate from your website but tightly connected. I do not manage it (Google won't transfer ownership to a third party for long without flagging it). What I do is wire your site to it: structured data on the site matches your GBP profile (name, address, phone, hours, services), so Google's matching engine treats them as the same entity.

Maintaining the GBP itself is your responsibility. The 15-minute quarterly checklist, hours, photos, review replies, one post, is published as its own guide on the blog: The quarterly Google Business Profile checklist for service businesses. Bookmark it; run through it on the first Monday of every quarter. Compound effect over a year is real local-pack movement.

13. Adding pages, posts, or content.

New content is part of why you have me on retainer. Most additions are included on the standard plan, and anything genuinely outside the standard scope is billed at a flat one hundred dollars an hour with a written estimate before any work starts.

• Edits to existing pages. Included on the standard plan, and they tend to land quickly on most business days.
• New blog posts. The blog system is part of your standard plan. Once you send me a draft, I edit, lay out, and publish it as part of your unlimited content updates.
• A new content page within scope. Send rough copy and photos, and the page gets built and shipped on most business days as part of the unlimited updates.
• A new region or service-area page. Send the city name and a paragraph of local color (which ranks better than generic copy), and the page is part of your unlimited updates.
• A new behavior or integration. Custom calculators, third-party booking integrations, email-marketing templates, and similar work are quoted at the flat one hundred dollars an hour rate before I start.

14. Seasonal and scheduled updates.

You can schedule changes ahead of time. Three patterns I run constantly for clients:

• Promo banners with auto-expiry. Tell me "this banner runs from Dec 1 to Dec 24" and I deploy the start and end at the right times. Set and forget.
• Holiday hours. Send your annual closure list once. I deploy each closure 48 hours ahead and reverse it after.
• Seasonal services. Snow removal Nov-Mar, lawn care Apr-Oct: tell me your dates, I hide and unhide the page automatically.

15. Reading your monthly invoice.

Your invoice is essentially one line. If a charge ever looks out of place to you, email me and I will explain or remove it; I have never had a billing dispute go past a single email.

• Monthly plan: $175. Covers hosting, SSL, monitoring, unlimited content updates, the blog system, and direct support. Same number every month.
• Hourly work outside the plan (rare). Itemized below the base line at a flat one hundred dollars an hour, only when you have specifically asked for something outside the standard scope and I have sent a written estimate first.
• Pass-through (rare). If I paid a third party on your behalf, like a stock photo or a paid font, it shows here at cost with no markup.

16. If you ever want to leave.

I do not hold your domain, content, or audience hostage. The day you ask, here is what happens:

• Your domain. Already at your registrar in your name. I hand off DNS configuration and unlink it from the hosting. Zero charge.
• Your content. Exported as a clean HTML/Markdown bundle plus original media. You can hand this to any developer.
• Your code. On the Lump-Sum plan it is already yours; I transfer the GitHub repo. On the Monthly plan I own the code, but I will provide a static export of the live site (HTML/CSS/JS) that runs on any host with no dependencies.
• Your forms. The Web3Forms account is in your name (or transferable to your name in one email).
• Your inboxes. Already yours; I never had access.

Reasonable handover, no exit fee, no last-month-of-spite invoice. The site keeps working until you point DNS at the new host.

17. Quick contact card.

• Email: hello@pikespeakwebdesigns.com. Best for anything with attachments or that needs a paper trail. One business day reply, usually faster.
• Phone or text: (928) 315-9094. This is the right channel for anything urgent or easier to talk through, and I am available for quick turnarounds on most business days.
• Forms on this site: /client-portal/ has structured forms for content updates, design feedback, emergencies, and referrals.
• Status page: if the site is down, check Cloudflare's status feed (cloudflarestatus.com) before calling. If their status is green and your site is down, that is on me; call.